Re: Patch: Implement failover on libpq connect level.

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To:
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch: Implement failover on libpq connect level.
Date: 2015-11-09 07:14:02
Message-ID: CAMsr+YHr740oGcVQcuyvLt1bwBPLQtpm5U-O+tTEFifBgHWdzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

On 7 November 2015 at 04:59, Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2015-11-09 07:17:11 Re: bootstrap pg_shseclabel in relcache initialization
Previous Message Craig Ringer 2015-11-09 07:02:48 Re: PATCH: 9.5 replication origins fix for logical decoding

Browse pgsql-jdbc by date

  From Date Subject
Next Message Victor Wagner 2015-11-09 09:44:04 Re: Patch: Implement failover on libpq connect level.
Previous Message Robert Haas 2015-11-06 20:59:36 Re: Patch: Implement failover on libpq connect level.