From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Question: Multiple pg clusters on one server can be reached with the standard port.
Date: Fri, 16 Jun 2023 10:41:34 -0500
Message-ID: <dbc7c4be-b8aa-bc8b-bc83-cc8e2f182b3f@gmail.com> (raw)
In-Reply-To: <507b783267640f0b8dd6b6fdc0f132fa27cb4212.camel@cybertec.at>
References: <4d70ad6a5a73b9e9faaf8f2715cac862c86def3c.camel@cybertec.at>
<6ba275cd2d442a913a234564aeaec27311ec1d16.camel@cybertec.at>
<71943c04e05c3c13d5cd2b287909f351@weiller.eu>
<a846bc8650c4e4299a7c9324f057b857@weiller.eu>
<6e8947e1d4394082e27f1f8354ae5d4f@weiller.eu>
<507b783267640f0b8dd6b6fdc0f132fa27cb4212.camel@cybertec.at>
On 6/16/23 10:18, Laurenz Albe wrote:
> On Fri, 2023-06-16 at 14:49 +0000, Brainmue wrote:
>> 16. Juni 2023 14:50, "Laurenz Albe" <laurenz.albe@cybertec.at> schrieb:
>>
>>> On Fri, 2023-06-16 at 12:35 +0000, Brainmue wrote:
>>>
>>>> We want to minimise dependencies between the application and the associated PostgreSQL DB.
>>>> The idea is that the application gets its DB alias and this is then used as a connection string.
>>>> This way we can decide in the backend on which server the PostgreSQL DB is running.
>>> There is an existing solution for that: the libpq connection service file:
>>> https://www.postgresql.org/docs/current/libpq-pgservice.html
>>>
>>> If you want to manage the connection strings centrally, you can use LDAP lookup:
>>> https://www.postgresql.org/docs/current/libpq-ldap.html
>> 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 client. And that's exactly what we don't want.
> Okay.
>
> Then why don't you go with your original solution, but use a unique TCP port number
> for each database? There are enough port numbers available. That way, there is no
> collision and no need for a proxy to map port numbers.
In practice, that gets very complicated is large organizations: every time
you add another database, you must file another request with the CISO RISK
office to get yet another non-standard port open from dozens of machines,
and the network team implement them.
Operationally much simpler to have a listener handle that.
--
Born in Arizona, moved to Babylonia.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: Question: Multiple pg clusters on one server can be reached with the standard port.
In-Reply-To: <dbc7c4be-b8aa-bc8b-bc83-cc8e2f182b3f@gmail.com>
References: <4d70ad6a5a73b9e9faaf8f2715cac862c86def3c.camel@cybertec.at> <6ba275cd2d442a913a234564aeaec27311ec1d16.camel@cybertec.at> <71943c04e05c3c13d5cd2b287909f351@weiller.eu> <a846bc8650c4e4299a7c9324f057b857@weiller.eu> <6e8947e1d4394082e27f1f8354ae5d4f@weiller.eu> <507b783267640f0b8dd6b6fdc0f132fa27cb4212.camel@cybertec.at> <dbc7c4be-b8aa-bc8b-bc83-cc8e2f182b3f@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox