From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
---|---|
To: | 'Mithun Cy' <mithun(dot)cy(at)enterprisedb(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter van Hardenberg <pvh(at)pvh(dot)ca>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "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 01:09:55 |
Message-ID: | 0A3221C70F24FB45833433255569204D1F6402E2@G01JPEXMBYT05 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Mithun Cy
> Thanks, my concern is suppose you have 3 server in cluster A(new version),
> B(new version), C(old version). If we implement as above only new servers
> will send ParameterStatus message to indicate what type of server we are
> connected. Server C will not send same. So we will not be able to use new
> feature "failover to new master" for such a kind of cluster.
No, the streaming replication requires the same major release for all member servers, so there's no concern about the mixed-version cluster.
Sorry, pmState can only be used in postmaster. In our context, postgres can use RecoveryInProgress(). Anyway, in addition to the reduced round trip, the libpq code would be much simpler.
Regards
Takayuki Tsunakawa
From | Date | Subject | |
---|---|---|---|
Next Message | Tsunakawa, Takayuki | 2016-11-15 01:44:01 | Re: Remove the comment on the countereffectiveness of large shared_buffers on Windows |
Previous Message | Craig Ringer | 2016-11-15 01:01:11 | Re: 9.6 TAP tests and extensions |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-11-15 14:32:55 | Re: Patch: Implement failover on libpq connect level. |
Previous Message | Mithun Cy | 2016-11-14 11:05:51 | Re: Patch: Implement failover on libpq connect level. |