Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1qvqpC-007sqP-9i
	for pgsql-admin@arkaria.postgresql.org; Thu, 26 Oct 2023 03:14:22 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1qvqpA-00Bpwz-Pv
	for pgsql-admin@arkaria.postgresql.org; Thu, 26 Oct 2023 03:14:20 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <vas@sibptus.ru>)
	id 1qvqp9-00Bpwq-Vn
	for pgsql-admin@lists.postgresql.org; Thu, 26 Oct 2023 03:14:20 +0000
Received: from admin.sibptus.ru ([2001:19f0:5001:21dc::10])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <vas@sibptus.ru>)
	id 1qvqp2-002LAU-6a
	for pgsql-admin@lists.postgresql.org; Thu, 26 Oct 2023 03:14:18 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru;
	s=20181118; h=Message-ID:Subject:To:From:Date:In-Reply-To;
	bh=+2GURRJlCXGV2hEEyyKrkw2lKUVygPgqg/+LJbOnLT4=; b=arGuqu+53qzfmFedQs8hT/iNvA
	3/y37+q1yZvW3b/0uwIutao0YzrtB6HSw66+idiS8D2n2/+WX1Lw0C4bHM7bSHkXh91xbftodOF3R
	wAoDEeyNgLFaYJtg+MMrgJC80D76+w6502m9Y2keHgQ4aX/RQJlGebtbUyE5EmKc+4Bw=;
Received: from vas by admin.sibptus.ru with local (Exim 4.96.1 (FreeBSD))
	(envelope-from <vas@sibptus.ru>)
	id 1qvqoy-000FPY-2p
	for pgsql-admin@lists.postgresql.org;
	Thu, 26 Oct 2023 03:14:08 +0000
Date: Thu, 26 Oct 2023 03:14:08 +0000
From: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Subject: pgbouncer's default_pool_size and server limits
Message-ID: <ZTnZgG44QsjYT1rY@admin.sibptus.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-PGP-Key: http://admin.sibptus.ru/~vas/
X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9  3532 0DA4 F259 9B5E C634
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/ZTnZgG44QsjYT1rY%40admin.sibptus.ru>
Precedence: bulk

Dear Colleagues,

According to the documentation, the "default_pool_size" in pgbouncer
means "How many server connections to allow per user/database pair."

Do you know a way to specify the pool size (limit) per server, not per
user/database? E.g. no matter how many databases there are in a
cluster, we do not start more than N connections to the server where
the cluster lives.

-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet