Re: Pgbouncer pool_mode and application behavior - Mailing list pgsql-admin

From Kristjan Mustkivi
Subject Re: Pgbouncer pool_mode and application behavior
Date
Msg-id CAOQPKasiV_pDg3R0TU8ZSEoQc6A02OAyOKJrKCngWtgrhHeebw@mail.gmail.com
Whole thread Raw
In response to Re: Pgbouncer pool_mode and application behavior  (Scott Ribe <scott_ribe@elevated-dev.com>)
List pgsql-admin
Thank you, Scott!

On Mon, Jun 13, 2022 at 5:33 PM Scott Ribe <scott_ribe@elevated-dev.com> wrote:
>
> > On Jun 13, 2022, at 8:04 AM, Kristjan Mustkivi <sonicmonkey@gmail.com> wrote:
> >
> > Am I correct to guess, that pgbouncer in this case in
> > pool_mode=session does not help at all and in order to improve
> > throughput, server engineers really must implement support for
> > transaction mode that pgbouncer provides?
>
> You are correct that session mode will not solve the problem you described. There are 3 possibilities:
>
> - as you mentioned, changed clients to be compatible with pgbouncer transaction pooling
>
> - increase pg max_connections
>
> - increase timeouts, use retries, etc so that the servers are more resilient to being temporarily denied connections



-- 
Kristjan Mustkivi

Email: kristjan.mustkivi@gmail.com



pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Recovery conflict due to buffer pins
Next
From: Nikhil Shetty
Date:
Subject: Re: Recovery conflict due to buffer pins