Re: [HACKERS] [bug fix] PG10: libpq doesn't connect to alternativehosts when some errors occur - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject Re: [HACKERS] [bug fix] PG10: libpq doesn't connect to alternativehosts when some errors occur
Date
Msg-id 0A3221C70F24FB45833433255569204D1F6F58D7@G01JPEXMBYT05
Whole thread Raw
In response to Re: [HACKERS] [bug fix] PG10: libpq doesn't connect to alternativehosts when some errors occur  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
From: Michael Paquier [mailto:michael.paquier@gmail.com]
> It seems to me that the feature is behaving as wanted. Or in short attempt
> to connect to the next host only if a connection cannot be established.
> If there is a failure once the exchange with the server has begun, just
> consider it as a hard failure. This is an important property for
> authentication and SSL connection failures actually.

But PgJDBC behaves as expected -- attempt another connection to other hosts (and succeed).  I believe that's what users
wouldnaturally expect.  The current libpq implementation handles only the socket-level connect failure.
 

Regards
Takayuki Tsunakawa


pgsql-hackers by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: [HACKERS] CTE inlining
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: [HACKERS] Re: [doc fix] PG10: wroing description on connect_timeout whenmultiple hosts are specified