| From: | Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(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-14 11:05:51 |
| Message-ID: | CAD__OujYB5e_dWrNBoGXSq-eyxRh0-Yc42yLfwstCO-dmG3R_A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
On Mon, Nov 14, 2016 at 1:37 PM, Tsunakawa, Takayuki <
tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> wrote:
> No, there's no concern about compatibility. Please look at this:
> https://www.postgresql.org/docs/devel/static/protocol-
flow.html#PROTOCOL-ASYNC
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.
--
Thanks and Regards
Mithun C Y
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2016-11-14 11:23:35 | Re: Fix checkpoint skip logic on idle systems by tracking LSN progress |
| Previous Message | Emre Hasegeli | 2016-11-14 10:41:52 | Re: Floating point comparison inconsistencies of the geometric types |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tsunakawa, Takayuki | 2016-11-15 01:09:55 | Re: Patch: Implement failover on libpq connect level. |
| Previous Message | Tsunakawa, Takayuki | 2016-11-14 08:07:31 | Re: Patch: Implement failover on libpq connect level. |