| From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
|---|---|
| To: | Álvaro Hernández <aht(at)ongres(dot)com> |
| Cc: | Jan Wieck <jan(at)wi3ck(dot)info>, Damir Simunic <damir(dot)simunic(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Extensibility of the PostgreSQL wire protocol |
| Date: | 2021-02-22 12:34:51 |
| Message-ID: | CADK3HHJE2Qj4p8zCMyExKesHAoh2wxZS-W1OMWSwCkBR1+KA0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 19 Feb 2021 at 15:39, Álvaro Hernández <aht(at)ongres(dot)com> wrote:
>
>
> On 19/2/21 19:30, Jan Wieck wrote:
> > [...]
> >
> > I also am not sure if building a connection pool into a background
> > worker or postmaster is a good idea to begin with. One of the
> > important features of a pool is to be able to suspend traffic and make
> > the server completely idle to for example be able to restart the
> > postmaster without forcibly disconnecting all clients. A pool built
> > into a background worker cannot do that.
> >
> >
>
Yes, when did it become a good idea to put a connection pooler in the
backend???
Dave Cramer
www.postgres.rocks
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira | 2021-02-22 12:38:36 | Re: [PATCH] pg_hba.conf error messages for logical replication connections |
| Previous Message | Peter Eisentraut | 2021-02-22 12:28:54 | Re: SEARCH and CYCLE clauses |