Re: Patch: Implement failover on libpq connect level.
Craig Ringer <craig@2ndquadrant.com>
From: Craig Ringer <craig@2ndquadrant.com>
To:
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2015-11-09T07:14:02Z
Lists: pgsql-hackers
On 7 November 2015 at 04:59, Robert Haas <robertmhaas@gmail.com> wrote: > So, I really wonder why we're not happy with the ability to substitute > out just the host and IP. I tend to agree. That solves 95% of the problem and doesn't foreclose solving the other 5% some other way if someone really cares later. I'd rather not see convoluted and complex connstrings, per my prior post. The JDBC extended URL style seems good enough. IMO the biggest problem is that client-side failover is way more complex than "got -ECONNREFUSED, try next host". I think we're all focusing on not being able to twiddle arbitrary settings while ignoring the real problem with client failover, i.e. making it actually work in the real world. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
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