> On 11 May 2021, at 09:29, Michael Paquier <michael@paquier.xyz> wrote:
> FWIW, I think that the case of getting some information about any
> failed connections while a connection has been successfully made
> within the scope of the connection string parameters provided by the
> user is rather thin, and I really feel that this is going to cause
> more pain to users than this is worth it. So my vote would be to
> clean up conn->errorMessage after a successful connection.
Agreed, given how conservative we typically are with backwards compatibility it
seems a too thin benefit to warrant potential breakage.
My vote would too be to restore the behavior by clearing conn->errorMessage.
--
Daniel Gustafsson https://vmware.com/