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 ) id 1uwhOr-006Oj2-Mr for pgsql-admin@arkaria.postgresql.org; Thu, 11 Sep 2025 13:31:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uwhOp-007aZV-UI for pgsql-admin@arkaria.postgresql.org; Thu, 11 Sep 2025 13:31:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uwhOp-007aZN-J3 for pgsql-admin@lists.postgresql.org; Thu, 11 Sep 2025 13:31:44 +0000 Received: from mail-lj1-x230.google.com ([2a00:1450:4864:20::230]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uwhOl-000CCE-0k for pgsql-admin@lists.postgresql.org; Thu, 11 Sep 2025 13:31:43 +0000 Received: by mail-lj1-x230.google.com with SMTP id 38308e7fff4ca-336c2194a65so5282501fa.2 for ; Thu, 11 Sep 2025 06:31:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1757597499; x=1758202299; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Qr0TLw3MutWwv18w8yqQTdRhzFG7T7kWxwLY9nbsj/E=; b=lf3zKlHHvFcSn/iPRzGKbNQ35ZROXgRpQfms47nCcqMwxtbS22e553eK+NDAh9YTbo H/ZbBDHwJuKmFJUuNPUiyo4zHZppHH7cWNX3VNqOtkzYhRk2BWlgP1zab0F5lAedlE1M LODrV0bRDz/PXA4clVOJyOHN/aK/6d0lX7koFBzgpFkzeW6EXm7HACRA9Ft5jyE7Hgto NfSB+YRJc8hMsvUtzbN4JdAWV9YsbNNhjBPGvlzqch4QV60IFF1Bc16e3+TfLaZ9+dhB 4aVX+i74sMHRcMo1+MTl4f19PbSIeqXenOlbZDdsL7A2oOvooUwyieDLuYpZrs2MP6rm vTJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1757597499; x=1758202299; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Qr0TLw3MutWwv18w8yqQTdRhzFG7T7kWxwLY9nbsj/E=; b=I8e+di11NawmLHIwkjc1KCVaKs4PPUBkuB+fq2FGU1zu/je70MKxT3YjGAM/nBaX0t 8/GS9dC6wy2x1rgCgtbqW4/zSNqc3yiY/Wa5gCrmWQ/VWAECs5E4Uih9TFV4O1PPukYf utA0q4KuGSMMQSvJ0HlM9+j0ys4PvGGxvx4qWiQGL/i8JgjSsySxmnhpjuiRtipu53m/ 28pc59wq6cIStbndXoT/zem3RPjZJAG7+W0zo71n++eWYZzfgJmH5hcr1HaS++z/RLJW rKpSTXYSKtpUIJGtq1VOJMnfEitOWCeKRChoNPsSuG+EkY6n6p+1MoQEjfSIdfURrl5e F0VA== X-Gm-Message-State: AOJu0YyLsBj+m0qxZJFPDsclDt/N/Ykkyzo3VumSf6lddZIRPMq1wRij wggWbDoM3mh22DMK8+GKq7KHehuyX0ReVMFhCkUXzz2Qw7242uotj0KwGKokDtIsasvvkJFw7tB TpxF6NxWZtiYsl9WYzRgDKZkIEr5u4QjQgwV8 X-Gm-Gg: ASbGncsT3F2Rn9OrtuIW87YC32sQDpBpWTt7UGzc9aBkNYlN9AHM/RO8ylCdtqDCLAw eyiRBC09DRin8KVUZgsZ+5Fq4/R4I313rC6jxzcVSCwnCORGwu1zF9U4rPk9O5OzP+xcDzfr1Gy AT+xyVnynYcde4PyCuSnbz7G5oa3GcGzre+71+UDvYpk/OHtAXp3YwAiPZW8ZIf9wvUh/yerRv5 feZMKxo+5qfDF0N4OLlHmgUNspY7iB/tbJ/XQy8+VfpYZfCGg== X-Google-Smtp-Source: AGHT+IH75QTEQIg9GbGVHn6gv76Y9wJt4YgxlZh620mpF/tWpqHQOdcB0Fwr1SvNPozM1JQdgfwdI2cIqjiV7PgcJ+k= X-Received: by 2002:a05:651c:411a:b0:336:7a78:4b67 with SMTP id 38308e7fff4ca-33b52b72cacmr41459881fa.33.1757597498677; Thu, 11 Sep 2025 06:31:38 -0700 (PDT) MIME-Version: 1.0 From: Raj Date: Thu, 11 Sep 2025 19:01:26 +0530 X-Gm-Features: Ac12FXwCoUPZc8yn4lCMM3CdWnPPKVua8MSDiHjwGVGWd0ArCEK2kkrW0JkbFRM Message-ID: Subject: Pgbouncer To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000911cce063e868ed4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000911cce063e868ed4 Content-Type: text/plain; charset="UTF-8" We are migrating from oracle.to postgres and its done. Now as a DBA, to improve performance say idle connecting handling or anything, if I want to recommend pgbouncer to the team, what's the compelling reason would it be? I may ask them to handle connections from application end and they may say ok but we still.may see idle connections are not closed. So, at point and for what compelling reason I should tell my manager, we must go-ahead and use etc. We use pg17 and in postgres itself I know idle_session_timeount, transaction_timeout, statement_timeout. Is this enough? Will it abruptly kill queries and if so, isn't it bad? --000000000000911cce063e868ed4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
We are migrating from oracle= .to postgres and its done.

Now as a DBA, to improve performance say idle connecting handling or anyth= ing, if I want to recommend pgbouncer to the team, what's the compellin= g reason would it be?

I = may ask them to handle connections from application end and they may say ok= but we still.may see idle connections are not closed.

So, at point and for what compelling reason = I should tell my manager, we must go-ahead and use etc.

We use pg17 and in postgres itself I know i= dle_session_timeount,=C2=A0 transaction_timeout, statement_timeout. Is this= enough? Will it abruptly kill queries and if so, isn't it bad?
--000000000000911cce063e868ed4--