Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1o0l80-0000RX-UB
	for pgsql-admin@arkaria.postgresql.org; Mon, 13 Jun 2022 14:33:16 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1o0l7z-0006wE-7w
	for pgsql-admin@arkaria.postgresql.org; Mon, 13 Jun 2022 14:33:15 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1o0l7y-0006w4-Tf
	for pgsql-admin@lists.postgresql.org; Mon, 13 Jun 2022 14:33:14 +0000
Received: from mailout.easymail.ca ([64.68.200.34])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1o0l7s-0002wB-2t
	for pgsql-admin@lists.postgresql.org; Mon, 13 Jun 2022 14:33:13 +0000
Received: from localhost (localhost [127.0.0.1])
	by mailout.easymail.ca (Postfix) with ESMTP id EFCA761484;
	Mon, 13 Jun 2022 14:33:05 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at emo09-pco.easydns.vpn
Received: from mailout.easymail.ca ([127.0.0.1])
	by localhost (emo09-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wuyVrmnikyH3; Mon, 13 Jun 2022 14:33:05 +0000 (UTC)
Received: from smtpclient.apple (unknown [4.28.96.150])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mailout.easymail.ca (Postfix) with ESMTPSA id 914A8614A0;
	Mon, 13 Jun 2022 14:33:05 +0000 (UTC)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Subject: Re: Pgbouncer pool_mode and application behavior
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <CAOQPKauQYBMSwQV=t4mR6hsMU=whg=56h2TEEsG13aMaom2LzQ@mail.gmail.com>
Date: Mon, 13 Jun 2022 08:33:04 -0600
Cc: pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF6978CE-2FE2-4D57-B93C-F51B9E11F834@elevated-dev.com>
References: 
 <CAOQPKauQYBMSwQV=t4mR6hsMU=whg=56h2TEEsG13aMaom2LzQ@mail.gmail.com>
To: Kristjan Mustkivi <sonicmonkey@gmail.com>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/DF6978CE-2FE2-4D57-B93C-F51B9E11F834%40elevated-dev.com>
Precedence: bulk

> On Jun 13, 2022, at 8:04 AM, Kristjan Mustkivi <sonicmonkey@gmail.com> =
wrote:
>=20
> Am I correct to guess, that pgbouncer in this case in
> pool_mode=3Dsession 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=