From: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
---|---|
To: | 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-19 17:15:36 |
Message-ID: | 20230619171536.2kcrdor36rqchicq@hjp.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)hjp(dot)at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"
From | Date | Subject | |
---|---|---|---|
Next Message | Jeffrey Walton | 2023-06-19 19:00:32 | Re: OpenSSL version 3 |
Previous Message | Daniel Gustafsson | 2023-06-19 15:38:48 | Re: OpenSSL version 3 |