Re: Question: Multiple pg clusters on one server can be reached with the standard port. - Mailing list pgsql-general

From Peter J. Holzer
Subject Re: Question: Multiple pg clusters on one server can be reached with the standard port.
Date
Msg-id 20230619171536.2kcrdor36rqchicq@hjp.at
Whole thread Raw
In response to Re: Question: Multiple pg clusters on one server can be reached with the standard port.  (Ron <ronljohnsonjr@gmail.com>)
Responses Re: Question: Multiple pg clusters on one server can be reached with the standard port.
List pgsql-general
On 2023-06-19 07:49:49 -0500, Ron wrote:
> On 6/19/23 05:33, Peter J. Holzer wrote:
> > As Francisco already pointed out, this can't work with nginx either. The
> > client resolves the alias and the TCP packets only contain the IP
> > address, not the alias which was used to get that address. So nginx
> > simply doesn't have that information and therefore can't act on it.
[...]
> > So (again, as Francisco already wrote) the best way is probably to write
> > a simple proxy which uses the database (not DNS) name for routing. I
> > seem to remember that nginx has a plugin architecture for protocols so
> > it might make sense to write that as an nginx plugin instead of a
> > standalone server, but that's really a judgement call the programmer has
> > to make. Another possibility would of course be to extend pgbouncer to
> > do what the OP needs.
>
> How would this work with JDBC clients?

Same as with any other client, I guess. Any reason why it should be
different?

        hp

--
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"

Attachment

pgsql-general by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: OpenSSL version 3
Next
From: Jeffrey Walton
Date:
Subject: Re: OpenSSL version 3