| From: | Catalin Iacob <iacobcatalin(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(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:00:21 |
| Message-ID: | CAHg_5gqgk9bjumVStUAvJGG3U3h56POPn8p+eaJcNCe0bxyhyA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2016-11-15 18:03:43 | Re: postgres_fdw and defaults |
| Previous Message | Catalin Iacob | 2016-11-15 17:53:53 | Re: Patch: Implement failover on libpq connect level. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-11-15 18:14:23 | Re: Patch: Implement failover on libpq connect level. |
| Previous Message | Catalin Iacob | 2016-11-15 17:53:53 | Re: Patch: Implement failover on libpq connect level. |