Add new property to specify local Socket Address

[jycr]

I'm submitting a ...

• feature request

Describe the issue
We use PostgreSQL in hardened security context where remote connection is allowed by source ADDRESS in pg_hba.conf.

On client side VM, we have several network interfaces. When we open JDBC connection toward remote PostgreSQL VM, the source address used by soket connection is always the first network interface. We can not specify another local socket address.
With MySQL, we can use property localSocketAddress, but no equivalent property exists with PostgreSQL.

It would be very useful to add a new property to specify the Hostname or IP address to explicitly configure the interface that the driver will bind the client side of the TCP/IP connection to when connecting.

Driver Version?
42.2.19

Java Version?
11.0.10

OS Version?
Windows 10

PostgreSQL Version?
10

[vlsi]

Nice idea.

Do you know if the feature already exists in psql and libpq?
It would be nice to align naming then.

I wonder how that should play with multiple DB hosts.
For instance, what if secondary db is located on a different subnet (from the client perspective).

[davecramer]

agreed, this sounds like something we could use

[jycr]

Do you know if the feature already exists in psql and libpq?
It would be nice to align naming then.

I am not a psql/libpq expert, but I found this comment posted at 2017-10-17:
https://dba.stackexchange.com/questions/188570/bind-psql-client-on-specific-network-interface#comment-365894

Since psql (and in fact libpq) doesn't have an option to bind() a socket to an address before connect(), it's the OS kernel that decides which network interface gets used based on the routing table. Whatever solution there is, it will be at the OS/networking level, not in PostgreSQL. – Daniel Vérité Oct 17 '17 at 12:02

[bokken]

Leveraging the OS routing tables is going to be a far more robust solution than anything which could be accomplished in the driver itself with connection properties. @vlsi's question on handling multiple db hosts on different subnets is one example of problems with trying to handle this in the driver.

[davecramer]

I thought this was more for use inside containers. Is it still simple inside containers ?

[bokken]

My initial reaction is that using OS routing tables is still the better answer in containers, but my use of containers has been pretty limited.

[jycr]

Do you need complementary stuff to the PR (#2082 ) before merging it on master for the next release?

[davecramer]

complementary stuff ?

[jycr]

complementary stuff ?

Do you need that I make other changes to the PR #2082 for you to be able to merge it to master and make a release?
We really need this feature for our PRODUCTION environnement.

[davecramer]

I'll deal with this today. Thanks! No guarantee on when we release tho

[davecramer]

closed by #2082