Re: Proposal: Implement failover on libpq connect level.
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Albe Laurenz <laurenz.albe@wien.gv.at>,
'''Victor Wagner *EXTERN*' *EXTERN*' *EXTERN*' <vitus@wagner.pp.ru>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2015-08-19T13:46:34Z
Lists: pgsql-hackers
On 2015-08-19 09:41:32 -0400, Tom Lane wrote: > In fact, they'd still need to use DNS balancing for Postgres, > because not everything connects with libpq (think JDBC for instance). It already does support this though. https://jdbc.postgresql.org/documentation/head/connect.html : > Connection Fail-over > > To support simple connection fail-over it is possible to define multiple > endpoints (host and port pairs) in the connection url separated by > commas. The driver will try to once connect to each of them in order > until the connection succeeds. If none succeed, a normal connection > exception is thrown. > > The syntax for the connection url is: > > jdbc:postgresql://host1:port1,host2:port2/database > So I think we ought to reject this proposal, full stop. I see no > reason to re-invent this wheel, and there are good reasons not to. I don't really buy this argument. Allowing to connect to several endpoints isn't exactly "new tech" either. A lot of database connectors do support something very close to the above pgjdbc feature. Greetings, Andres Freund
Commits
-
libpq: Add target_session_attrs parameter.
- 721f7bd3cbcc 10.0 landed
-
Remove superuser checks in pgstattuple
- fd321a1dfd64 10.0 cited
-
Fix unwanted flushing of libpq's input buffer when socket EOF is seen.
- c405918858c0 9.6.0 cited