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 1nDIfX-0005Ni-SC
	for pgsql-admin@arkaria.postgresql.org; Fri, 28 Jan 2022 04:15:28 +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 1nDIf0-00040c-10
	for pgsql-admin@arkaria.postgresql.org; Fri, 28 Jan 2022 04:14:54 +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 <vas@sibptus.ru>)
	id 1nDIez-00040S-8y
	for pgsql-admin@lists.postgresql.org; Fri, 28 Jan 2022 04:14:53 +0000
Received: from admin.sibptus.ru ([2001:19f0:5001:21dc::10])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <vas@sibptus.ru>)
	id 1nDIer-0002Ir-Oc
	for pgsql-admin@lists.postgresql.org; Fri, 28 Jan 2022 04:14:51 +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=eVsHVJGojXsBBPFKDJr7tAjF4TTMGfs1j/T2b50yhTs=; b=SaWBs0QaOJtt9PtW35FP9CZcGK
	PP6uUhxIkE6N89VsiKMF7Dz8yJk63P+PZLisCfHvLiqvte/0df2p9jeLmh8RDcAg3PxYV44ZyBA5J
	dVpcQhWh4tNy/4JgknL2PDNGgoPzqYQdj+ObKuGvo+k3HqCmrejkd5dHFXTBibzwos3A=;
Received: from vas by admin.sibptus.ru with local (Exim 4.95 (FreeBSD))
	(envelope-from <vas@sibptus.ru>)
	id 1nDIeo-000IFW-8s
	for pgsql-admin@lists.postgresql.org;
	Fri, 28 Jan 2022 04:14:42 +0000
Date: Fri, 28 Jan 2022 04:14:42 +0000
From: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Subject: pgbouncer logs and its efficiency
Message-ID: <YfNtsr+D6JKPmncK@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/YfNtsr%2BD6JKPmncK%40admin.sibptus.ru>
Precedence: bulk

Dear Colleages,

I have two questions about pgbouncer logs, can you please share your
knowledge.

1. What is the meaning of those IDs in the log like
"S-0xaaaae460fcb0", "C-0xaaaae45d9fb0" ? I suspect that "S-" and "C-"
mean "server" and "client", but what are those HEX numbers?

2. How would you calculate the efficiency of pgbouncer, like
client_conns/server_conns ratio (current and average over over time)?

I have a case where pgbouncer is probably doing more bad than good,
but I would like to be able to prove or disprove it.

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