From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Kristjan Mustkivi <sonicmonkey@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Pgbouncer pool_mode and application behavior
Date: Mon, 13 Jun 2022 08:33:04 -0600
Message-ID: <DF6978CE-2FE2-4D57-B93C-F51B9E11F834@elevated-dev.com> (raw)
In-Reply-To: <CAOQPKauQYBMSwQV=t4mR6hsMU=whg=56h2TEEsG13aMaom2LzQ@mail.gmail.com>
References: <CAOQPKauQYBMSwQV=t4mR6hsMU=whg=56h2TEEsG13aMaom2LzQ@mail.gmail.com>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, sonicmonkey@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Pgbouncer pool_mode and application behavior
In-Reply-To: <DF6978CE-2FE2-4D57-B93C-F51B9E11F834@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox