Hans-Jürgen Schönig wrote:
> in addition to that you have the “problem” of transactions. if you failover in the middle
> of a transaction, strange things might happen from the application point of view.
>
> the good thing, however, is that stupid middleware is sometimes not able to handle
> failed connections. however, overall i think it is more of a danger than a benefit.
Maybe I misunderstood the original proposal, but my impression was that the alternative
servers would be tried only at the time the connection is established, and there would be no
such problems as you describe.
Those could only happen if libpq automatically tried to reconnect upon failure without
the client noticing.
So the stupid middleware would get an error message, but the reconnect would actually work.
Yours,
Laurenz Albe