From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Brainmue <brainmue(at)weiller(dot)eu> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Question: Multiple pg clusters on one server can be reached with the standard port. |
Date: | 2023-06-16 15:18:01 |
Message-ID: | 507b783267640f0b8dd6b6fdc0f132fa27cb4212.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 2023-06-16 at 14:49 +0000, Brainmue wrote:
> 16. Juni 2023 14:50, "Laurenz Albe" <laurenz(dot)albe(at)cybertec(dot)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.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2023-06-16 15:19:51 | Re: Question: Multiple pg clusters on one server can be reached with the standard port. |
Previous Message | Brainmue | 2023-06-16 14:49:34 | Re: Question: Multiple pg clusters on one server can be reached with the standard port. |