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 1sPG6h-003iaz-WA for pgsql-admin@arkaria.postgresql.org; Thu, 04 Jul 2024 06:38:15 +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 1sPG6f-00EBqV-FU for pgsql-admin@arkaria.postgresql.org; Thu, 04 Jul 2024 06:38:14 +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 1sPG6f-00EBqN-4S for pgsql-admin@lists.postgresql.org; Thu, 04 Jul 2024 06:38:13 +0000 Received: from cloud.gatewaynet.com ([185.90.37.94]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sPG6d-000L3t-3W for pgsql-admin@lists.postgresql.org; Thu, 04 Jul 2024 06:38:12 +0000 Message-ID: <5b9df232-3c9e-ad5c-ffde-7d6b07452041@cloud.gatewaynet.com> Date: Thu, 4 Jul 2024 09:38:07 +0300 MIME-Version: 1.0 Subject: Re: Connection pooler / LDAP auth / Load Balancing on read-only queries Content-Language: en-US To: Scott Ribe Cc: pgsql-admin@lists.postgresql.org References: <1745e084-a408-445f-97e3-44e29977ccc5@cloud.gatewaynet.com> From: Achilleas Mantzios - cloud In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 7/3/24 23:32, Scott Ribe wrote: > the read only detection is tricky--consider transaction level pooling, and the first query is read only Hello pgpool does a great job at that. pgpool does load balancing to the first statement that is considered a write statement, for that point on, the rest of the transaction is routed to the primary. But the question here is how to achieve all of the aforementioned features, of all those great tools combined, or ideally combined in one. > > -- > Scott Ribe > scott_ribe@elevated-dev.com > https://www.linkedin.com/in/scottribe/ > > > >> On Jul 3, 2024, at 2:25 PM, Achilleas Mantzios wrote: >> >> Dear Members >> >> I am searching (like many others) of the holy grail of PostgreSQL pooling + Load Balancing . Ideally I would like : >> >> - A pgbouncer with better/native LDAP (not PAM) / and eventually Kerberos support >> >> - A pgbouncer enhanced with load balancing read-only queries (like pgpool) >> >> or >> >> - A pgpool-II with better resources utilization / more efficient pooling (like pgbouncer) >> >> >> There are other solutions available pgcat (no LDAP), odyssey (no load balancing) , pgagroal, supavisor, none of which seem to cover the above. >> >> 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. >> >> 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. >> >> Thank you >> >> -- >> Achilleas Mantzios >> IT DEV - HEAD >> IT DEPT >> Dynacom Tankers Mgmt (as agents only) >> >> >>