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 1qABYL-0003XC-Ik for pgsql-general@arkaria.postgresql.org; Fri, 16 Jun 2023 15:39:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qABYK-0007j3-9N for pgsql-general@arkaria.postgresql.org; Fri, 16 Jun 2023 15:39:56 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qABYJ-0007WB-Ul for pgsql-general@lists.postgresql.org; Fri, 16 Jun 2023 15:39:55 +0000 Received: from prater.isola.red ([2a0a:4cc0:1:4e:2442::2]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qABYF-002YGy-L1 for pgsql-general@lists.postgresql.org; Fri, 16 Jun 2023 15:39:54 +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 837D7C186D; Fri, 16 Jun 2023 17:39:48 +0200 (CEST) MIME-Version: 1.0 Date: Fri, 16 Jun 2023 15:39:48 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: "Brainmue" Message-ID: 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: <507b783267640f0b8dd6b6fdc0f132fa27cb4212.camel@cybertec.at> References: <507b783267640f0b8dd6b6fdc0f132fa27cb4212.camel@cybertec.at> <4d70ad6a5a73b9e9faaf8f2715cac862c86def3c.camel@cybertec.at> <6ba275cd2d442a913a234564aeaec27311ec1d16.camel@cybertec.at> <71943c04e05c3c13d5cd2b287909f351@weiller.eu> <6e8947e1d4394082e27f1f8354ae5d4f@weiller.eu> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 16. Juni 2023 17:18, "Laurenz Albe" schrieb: > On Fri, 2023-06-16 at 14:49 +0000, Brainmue wrote: >=20 >>=2016. Juni 2023 14:50, "Laurenz Albe" schri= eb: >>=20 >>=20On Fri, 2023-06-16 at 12:35 +0000, Brainmue wrote: >>=20 >>>=20We want to minimise dependencies between the application and the as= sociated PostgreSQL DB. >>> The idea is that the application gets its DB alias and this is then u= sed as a connection string. >>> This way we can decide in the backend on which server the PostgreSQL = DB 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 = LDAP lookup: >> https://www.postgresql.org/docs/current/libpq-ldap.html >>=20 >>=20Thank you, I already know this solution, but the LDAP solution is ou= t of the question for us and >> the file again means an intervention on the client. And that's exactly= what we don't want. >=20 >=20Okay. >=20 >=20Then why don't you go with your original solution, but use a unique T= CP port number > for each database? There are enough port numbers available. That way, t= here is no > collision and no need for a proxy to map port numbers. >=20 >=20Yours, > Laurenz Albe Thank you for dealing with our wishes. Because we are growing more and more and we have many databases in differ= ent networks. Therefore, we are looking for a solution that will make the firewall prob= lem more manageable for the future. And currently I believe that managing one more service in automation woul= d be the lesser of two evils for us. But that's exactly why we're looking for a service that does that at all. Regards Michael