Re: Patch: Implement failover on libpq connect level.

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Catalin Iacob <iacobcatalin(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Peter van Hardenberg <pvh(at)pvh(dot)ca>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch: Implement failover on libpq connect level.
Date: 2016-11-15 18:14:23
Message-ID: 20161115181423.dcfvuzou4xc6i2bg@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Catalin Iacob wrote:
> On Tue, Nov 15, 2016 at 3:42 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
> > FWIW I'm not sure "primary" is the right term here either. I think what
> > we really want to know is whether the node can accept writes; maybe
> > "pg_is_writable_node".
>
> This made me think of another complication: what about cascading
> replication where the middle node is both a master and a slave? You'd
> probably not want to fallback to the middle node even though it is a
> master for its downstream.

Exactly my thought, hence the above suggestion.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2016-11-15 18:18:27 Re: Snapshot too old logging
Previous Message Andrew Dunstan 2016-11-15 18:03:43 Re: postgres_fdw and defaults

Browse pgsql-jdbc by date

  From Date Subject
Next Message Robert Haas 2016-11-15 18:28:47 Re: Patch: Implement failover on libpq connect level.
Previous Message Catalin Iacob 2016-11-15 18:00:21 Re: Patch: Implement failover on libpq connect level.