RE: Multiple hosts in connection string failed to failover in non-hot standby mode

From: "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>
To: 'Hubert Zhang' <zhubert(at)vmware(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: Multiple hosts in connection string failed to failover in non-hot standby mode
Date: 2020-10-28 10:59:28
Message-ID: TYAPR01MB299054EDEC8CA6FFC86E0BD0FE170@TYAPR01MB2990.jpnprd01.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: Hubert Zhang <zhubert(at)vmware(dot)com>
> Hao Wu and I wrote a patch to fix this problem. Client side libpq should try another hosts in connection string when it is rejected by a non-hot standby, or the first host encounter some n/w problems during the libpq handshake.

Thank you. Please add it to the November Commitfest.

> Thanks. Is this email in text format now? I just use outlook in chrome. Let me know if it still in html format.

I'm afraid not. The Outlook's title bar says that it's in HTML format. I'm using Outlook 2016 client app on Windows 10. I may have failed to convert my previous email to text, but it should be text format this time.

Regards
Takayuki Tsunakawa

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Borisov 2020-10-28 11:37:53 Valgrind run error with Postgres on OSX
Previous Message Daniel Gustafsson 2020-10-28 10:56:26 Re: Support for NSS as a libpq TLS backend