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 1sP6ek-002u6x-Qj for pgsql-admin@arkaria.postgresql.org; Wed, 03 Jul 2024 20:32:46 +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 1sP6ei-00C9zM-KV for pgsql-admin@arkaria.postgresql.org; Wed, 03 Jul 2024 20:32:45 +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 ) id 1sP6ei-00C9zE-6w for pgsql-admin@lists.postgresql.org; Wed, 03 Jul 2024 20:32:44 +0000 Received: from mailout.easymail.ca ([64.68.200.34]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sP6eg-000Fqo-4x for pgsql-admin@lists.postgresql.org; Wed, 03 Jul 2024 20:32:43 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id DC8C8E0F4F; Wed, 3 Jul 2024 20:32:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elevated-dev.com; s=easymail; t=1720038760; bh=DcXjg+AkUyJWJh+4UtP3NahBpbgTVowML8YK01Ajk8k=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=2mGZKPg7p6H7NbuoIcD/Jx7MS1IJu+1CL99CcT7wY6b58F4Ta+383l5dZ4RCX5Nhj T/yWiWOWUDDQebIkY5YC4nMK6ZZ1V770ypPCTgZrVCG5LEBbbpScXdSCJZvV7nL2XV YdDYS50TDdvMVC2FnRfGXKrIACSAmcujAo6uGr+4ZxMdTTOYQ0+QuqD2j6zHGPykCv ZBYWifyQtw8Ca78GaWzfqa4LgOvsdxXD1+WLrrmRjqDmfNfdDTOWNO/Vho63t1fu3g Y8TdXQljTth9KvhP9M+4F/mTI3CFg0/t/YIm0cbleVcR+V6ISTzvZVDcZxjepxT3x4 o8KUEJgYhhHJQ== X-Virus-Scanned: Debian amavisd-new at emo08-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo08-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RS4OQNxfzyP5; Wed, 3 Jul 2024 20:32:40 +0000 (UTC) Received: from smtpclient.apple (unknown [165.140.184.195]) (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 4EB95E03A0; Wed, 3 Jul 2024 20:32:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elevated-dev.com; s=easymail; t=1720038760; bh=DcXjg+AkUyJWJh+4UtP3NahBpbgTVowML8YK01Ajk8k=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=2mGZKPg7p6H7NbuoIcD/Jx7MS1IJu+1CL99CcT7wY6b58F4Ta+383l5dZ4RCX5Nhj T/yWiWOWUDDQebIkY5YC4nMK6ZZ1V770ypPCTgZrVCG5LEBbbpScXdSCJZvV7nL2XV YdDYS50TDdvMVC2FnRfGXKrIACSAmcujAo6uGr+4ZxMdTTOYQ0+QuqD2j6zHGPykCv ZBYWifyQtw8Ca78GaWzfqa4LgOvsdxXD1+WLrrmRjqDmfNfdDTOWNO/Vho63t1fu3g Y8TdXQljTth9KvhP9M+4F/mTI3CFg0/t/YIm0cbleVcR+V6ISTzvZVDcZxjepxT3x4 o8KUEJgYhhHJQ== Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\)) Subject: Re: Connection pooler / LDAP auth / Load Balancing on read-only queries From: Scott Ribe In-Reply-To: <1745e084-a408-445f-97e3-44e29977ccc5@cloud.gatewaynet.com> Date: Wed, 3 Jul 2024 14:32:29 -0600 Cc: pgsql-admin@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <1745e084-a408-445f-97e3-44e29977ccc5@cloud.gatewaynet.com> To: Achilleas Mantzios X-Mailer: Apple Mail (2.3774.600.62) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk the read only detection is tricky--consider transaction level pooling, = and the first query is read only -- Scott Ribe scott_ribe@elevated-dev.com https://www.linkedin.com/in/scottribe/ > On Jul 3, 2024, at 2:25=E2=80=AFPM, Achilleas Mantzios = wrote: >=20 > Dear Members >=20 > I am searching (like many others) of the holy grail of PostgreSQL = pooling + Load Balancing . Ideally I would like : >=20 > - A pgbouncer with better/native LDAP (not PAM) / and eventually = Kerberos support >=20 > - A pgbouncer enhanced with load balancing read-only queries (like = pgpool) >=20 > or >=20 > - A pgpool-II with better resources utilization / more efficient = pooling (like pgbouncer) >=20 >=20 > There are other solutions available pgcat (no LDAP), odyssey (no load = balancing) , pgagroal, supavisor, none of which seem to cover the above. >=20 > Some ppl advice , keeping pgbouncer close to the app(s) and pgpool = close to the DB. But kinda had mixed feelings putting the two work = together. >=20 > I'd like to ask if there any thoughts or even hopes that some of the = above will be available in a single software, or otherwise how do people = tackle this. >=20 > Thank you >=20 > --=20 > Achilleas Mantzios > IT DEV - HEAD > IT DEPT > Dynacom Tankers Mgmt (as agents only) >=20 >=20 >=20