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 1qAAlg-0000yq-U0 for pgsql-general@arkaria.postgresql.org; Fri, 16 Jun 2023 14:49:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qAAlf-00029c-RH for pgsql-general@arkaria.postgresql.org; Fri, 16 Jun 2023 14:49:39 +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 1qAAlf-000298-GP for pgsql-general@lists.postgresql.org; Fri, 16 Jun 2023 14:49:39 +0000 Received: from prater.isola.red ([2a0a:4cc0:1:4e:2442::2]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qAAlc-002oEh-9k for pgsql-general@lists.postgresql.org; Fri, 16 Jun 2023 14:49:38 +0000 Received: from wm.joel-hatsch.net (unknown [172.29.0.3]) (Authenticated sender: michael@weiller.eu) by prater.isola.red (Postfix) with ESMTPSA id 23ED7CB1BD; Fri, 16 Jun 2023 16:49:34 +0200 (CEST) MIME-Version: 1.0 Date: Fri, 16 Jun 2023 14:49:34 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: "Brainmue" Message-ID: <6e8947e1d4394082e27f1f8354ae5d4f@weiller.eu> Subject: Re: Question: Multiple pg clusters on one server can be reached with the standard port. To: "Laurenz Albe" Cc: pgsql-general@lists.postgresql.org In-Reply-To: <4d70ad6a5a73b9e9faaf8f2715cac862c86def3c.camel@cybertec.at> References: <4d70ad6a5a73b9e9faaf8f2715cac862c86def3c.camel@cybertec.at> <6ba275cd2d442a913a234564aeaec27311ec1d16.camel@cybertec.at> <71943c04e05c3c13d5cd2b287909f351@weiller.eu> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 16. Juni 2023 14:50, "Laurenz Albe" schrieb: > On Fri, 2023-06-16 at 12:35 +0000, Brainmue wrote: >=20 >>=20We want to minimise dependencies between the application and the ass= ociated PostgreSQL DB. >> The idea is that the application gets its DB alias and this is then us= ed as a connection string. >> This way we can decide in the backend on which server the PostgreSQL D= B is running. >=20 >=20There is an existing solution for that: the libpq connection service = file: > https://www.postgresql.org/docs/current/libpq-pgservice.html >=20 >=20If you want to manage the connection strings centrally, you can use L= DAP lookup: > https://www.postgresql.org/docs/current/libpq-ldap.html >=20 >=20Yours, > Laurenz Albe Thank you, I already know this solution, but the LDAP solution is out of = the question for us and the file again means an intervention on the clien= t. And that's exactly what we don't want.