Horton

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

tsunakawa.takay@fujitsu.com <tsunakawa.takay@fujitsu.com>

View thread View on postgr.es
From: "tsunakawa.takay@fujitsu.com" <tsunakawa.takay@fujitsu.com>
To: 'Hubert Zhang' <zhubert@vmware.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2020-10-28T10:59:28Z
Lists: pgsql-hackers 
From: Hubert Zhang <zhubert@vmware.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

Commits

  1. Clear conn->errorMessage at successful completion of PQconnectdb().

  2. Avoid ECPG test failures in some GSS-capable environments.

  3. Try next host after a "cannot connect now" failure.

  4. Uniformly identify the target host in libpq connection failure reports.

  5. Allow pg_regress.c wrappers to postprocess test result files.

  6. In libpq, always append new error messages to conn->errorMessage.