Horton

Re: Proposal: Implement failover on libpq connect level.

Oleksandr Shulgin <oleksandr.shulgin@zalando.de>

View thread View on postgr.es
From: "Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Stephen Frost <sfrost@snowman.net>, Victor Wagner <vitus@wagner.pp.ru>, Albe Laurenz <laurenz.albe@wien.gv.at>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2015-09-04T04:08:03Z
Lists: pgsql-hackers 
On Sep 3, 2015 7:30 PM, "Robert Haas" <robertmhaas@gmail.com> wrote:
>
> All of these objections seem pretty thin to me.  I'd accept any of
> them as a reason for preferring one alternative over another, but I
> don't accept that the presence of a few problems of this magnitude
> means we should give up on the feature.  It's a good enough feature
> that it is worth the possibility of slightly inconveniencing someone
> running in an unusual configuration.

I give up.

Though I still don't see any compelling reason for this to be in libpq
itself. By the way, what about mixing conninfo and uris - should this not
be allowed?

-
Alex

Commits

  1. libpq: Add target_session_attrs parameter.

  2. Remove superuser checks in pgstattuple

  3. Fix unwanted flushing of libpq's input buffer when socket EOF is seen.