pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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: Mon, 19 Jun 2023 07:49:49 -0500
Message-ID: <0f467ff1-8cdb-2460-75d6-0e0e4497890f@gmail.com> (raw)
In-Reply-To: <20230619103335.xyagd43uhneducxz@hjp.at>
References: <0c2dd853-08ec-dbed-00c3-a680ae711d89@proventis.net>
	<71943c04e05c3c13d5cd2b287909f351@weiller.eu>
	<d869925784c9af50aa4379d4ab5ffae2@weiller.eu>
	<c5f9c9b4-7a1f-8a35-406c-d7cc34285bcd@proventis.net>
	<20230619103335.xyagd43uhneducxz@hjp.at>

On 6/19/23 05:33, Peter J. Holzer wrote:
[snip]
> You cant setup firewall rules basedon dns names. firewall rules are based on
>> ip adresses and dns resolution happens on rule creation.
>> I dont have an example for nginx. As I remember nginx resolves dns names
>> only for variables. So setup a variable with your hostname and use this
>> variable in your server definition.
> 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.
>
> For HTTP this works because the HTTP protocol contains a Host field
> which the client fills with the name it used. But the Postgres protocol
> has no such information (and in any case nginx probably doesn't
> understand that protocol anyway).
>
> 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?


-- 
Born in Arizona, moved to Babylonia.





view thread (37+ messages)  latest in thread

Message-ID: <0f467ff1-8cdb-2460-75d6-0e0e4497890f@gmail.com>
Permalink:  ../0f467ff1-8cdb-2460-75d6-0e0e4497890f@gmail.com/
Also on:    postgresql.org/message-id/0f467ff1-8cdb-2460-75d6-0e0e4497890f@gmail.com

 · 

reply

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: <0f467ff1-8cdb-2460-75d6-0e0e4497890f@gmail.com>
  References: <0c2dd853-08ec-dbed-00c3-a680ae711d89@proventis.net> <71943c04e05c3c13d5cd2b287909f351@weiller.eu> <d869925784c9af50aa4379d4ab5ffae2@weiller.eu> <c5f9c9b4-7a1f-8a35-406c-d7cc34285bcd@proventis.net> <20230619103335.xyagd43uhneducxz@hjp.at> <0f467ff1-8cdb-2460-75d6-0e0e4497890f@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