[HACKERS] Re: [bug fix] PG10: libpq doesn't connect to alternative hosts whensome errors occur - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject [HACKERS] Re: [bug fix] PG10: libpq doesn't connect to alternative hosts whensome errors occur
Date
Msg-id 0A3221C70F24FB45833433255569204D1F77DDF6@G01JPEXMBYT05
Whole thread Raw
In response to [HACKERS] Re: [bug fix] PG10: libpq doesn't connect to alternative hosts whensome errors occur  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
From: Robert Haas [mailto:robertmhaas@gmail.com]
> Well, I started out believing that the current behavior was for the best,
> and then completely reversed my position and favored the OP's proposal.
> Nothing has really happened since then to change my mind, so I guess I'm
> still in that camp.  But do we have any new data points?  Have any
> beta-testers tested this and what do they think?
> The only non-developer (i.e. person not living in an ivory tower) who has
> weighed in here is Tels, who favored reversing the original decision and
> adopting Tsunakawa-san's position, and that was 2 months ago.
> 
> I am pretty reluctant to tinker with this at this late date and in the face
> of several opposing votes, but I do think that we bet on the wrong horse.

Thank you Robert and Tels.  Yes, Tels's comment sounds plausible as a representative real user who expects high
availability. I'm sorry to repeat myself, but this feature is for HA, so libpq should attempt to connect to the next
hostwhen it fails to establish a connection.
 

Who can conclude this?  I don't think that no feedback from beta users means satisfaction with the current behavior.

Regards
Takayuki Tsunakawa





pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [HACKERS] Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE insteadof UNBOUNDED for range partition b
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] dubious error message from partition.c