| From: | Chris Cogdon <chris(at)cogdon(dot)org> |
|---|---|
| To: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Big number of connections |
| Date: | 2016-03-31 23:12:51 |
| Message-ID: | B2F62CE5-A0D5-4FBB-82B6-FB1EBBD81996@cogdon.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Although somewhat academic, since pgboucer doesn’t support it (and might not ever), have a look at this ticket which, if it was ever supported, would give you what you needed:
https://github.com/pgbouncer/pgbouncer/issues/75 <https://github.com/pgbouncer/pgbouncer/issues/75>
> On Mar 31, 2016, at 15:47, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>
>> If they are going to keep the client connections open, they would need to
>> run pgbouncer in statement or transaction mode.
>
> As I understand, in pgbouncer you cannot have connections that serve
> different users. If each individual requires its own database-level
> user, pgbouncer would not help at all.
>
> I would look seriously into getting rid of the always-open requirement
> for connections.
— Chris Cogdon
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karl Denninger | 2016-03-31 23:27:07 | Re: Big number of connections |
| Previous Message | Alvaro Herrera | 2016-03-31 22:47:12 | Re: Big number of connections |