Re: Pgbouncer pool_mode and application behavior

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Kristjan Mustkivi <sonicmonkey(at)gmail(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Pgbouncer pool_mode and application behavior
Date: 2022-06-13 14:33:04
Message-ID: DF6978CE-2FE2-4D57-B93C-F51B9E11F834@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> On Jun 13, 2022, at 8:04 AM, Kristjan Mustkivi <sonicmonkey(at)gmail(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Nikhil Shetty 2022-06-13 18:05:35 Recovery conflict due to buffer pins
Previous Message Kristjan Mustkivi 2022-06-13 14:04:25 Pgbouncer pool_mode and application behavior