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 ) id 1nF9l8-0008Uu-2F for pgsql-admin@arkaria.postgresql.org; Wed, 02 Feb 2022 07:08:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nF9l6-00080t-Vf for pgsql-admin@arkaria.postgresql.org; Wed, 02 Feb 2022 07:08:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nF9l5-00080f-Fv for pgsql-admin@lists.postgresql.org; Wed, 02 Feb 2022 07:08:52 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nF9l0-0004CY-Rx for pgsql-admin@lists.postgresql.org; Wed, 02 Feb 2022 07:08:51 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 9F8A45C00E9; Wed, 2 Feb 2022 02:08:43 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 02 Feb 2022 02:08:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=rWbyMESfQIuPmauWatfQY7MCo9YUTYyhTuD3KER/h0I=; b=U/eHI0/O d+x3i16MJNY0mFv5Sb0WwiaprWDHk+3BNiywHBDp1sMtjdNmpILn3eeSRq1H2xWe t8AZsNEYlIZ3dziN8VxDdIgMOxIU9rK79mCeAUoC/iTc3fzUTYOSps+AgZHoFSgC d9mX9leRy1z+FYVQUYSxpEoT5JLT2BZNHIQsP259NBV9p5swmlzd7t47aiapU1kN PY6MACGgP38Sfeve5HXcsdh2hPR7X0Dr3j/V64TKR9H5hOsC3PTQf6+rdrV9WaOE sxf5CmCXdb0/Ie5akRbdBC0wjwRA+Z5oAx5aosGTxEhy9mPHQhjYU3zswn0HNZWJ D/gmz9ZQBrtW/Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrgeeggddutddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtje ertddtfeejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghr rdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhmqeenucggtffrrg htthgvrhhnpeefjeegheetuefhveevudelueeftdejteeiffetvdduhfdtieefgfeutedt veeggfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 2 Feb 2022 02:08:42 -0500 (EST) Message-ID: <2d4321bd-0174-42c9-3671-fa9626326d10@enterprisedb.com> Date: Wed, 2 Feb 2022 08:08:40 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: pgbouncer logs and its efficiency Content-Language: en-US To: Victor Sudakov , pgsql-admin@lists.postgresql.org References: From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 28.01.22 05:14, Victor Sudakov wrote: > 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? These are the internal addresses of the server and client structures. You can use those to track a particular server or client connection through the logs and through SHOW SERVERS and SHOW SERVERS. > 2. How would you calculate the efficiency of pgbouncer, like > client_conns/server_conns ratio (current and average over over time)? This depends heavily on what you are using pgbouncer for and what metrics are relevant for your application.