| From: | Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(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-14 07:38:41 |
| Message-ID: | CAD__OugUmpRZBxKie+PvS-TSJiMSpiOEYWcDbQ7CE5AvB+GY1A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
On Fri, Nov 11, 2016 at 7:33 PM, Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> We tend to use the term "primary" instead of "master".
Thanks, I will use primary instead of master in my next patch.
>Will this work with logical replication?
I have not tested with logical replication. Currently we identify the
primary to connect based on result of "SELECT pg_is_in_recovery()". So I
think it works. Do you want me test a particular setup?
--
Thanks and Regards
Mithun C Y
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mithun Cy | 2016-11-14 07:56:08 | Re: Patch: Implement failover on libpq connect level. |
| Previous Message | Craig Ringer | 2016-11-14 07:03:18 | Re: [PATCH] PostgresNode.pm enhancements, pg_lsn helper, and some more recovery tests |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mithun Cy | 2016-11-14 07:56:08 | Re: Patch: Implement failover on libpq connect level. |
| Previous Message | Tsunakawa, Takayuki | 2016-11-14 06:01:23 | Re: Patch: Implement failover on libpq connect level. |