Tom Lane 138531f1bb Clear conn->errorMessage at successful completion of PQconnectdb(). ... Commits ffa2e4670 and 52a10224e caused libpq's connection-establishment functions to usually leave a nonempty string in the connection's errorMessage buffer, even after a successful connection. While that was intentional on my part, more sober reflection says that it wasn't a great idea: the string would be a bit confusing. Also this broke at least one application that checked for connection success by examining the errorMessage, instead of using PQstatus() as documented. Let's clear the buffer at success exit, restoring the pre-v14 behavior. Discussion: https://postgr.es/m/4170264.1620321747@sss.pgh.pa.us		2021-09-13 16:53:11 -04:00
..
ecpg	Fix error handling with threads on OOM in ECPG connection logic	2021-09-13 13:23:50 +09:00
libpq	Clear conn->errorMessage at successful completion of PQconnectdb().	2021-09-13 16:53:11 -04:00
Makefile	Fix parallel make when running make install before make all	2011-03-08 23:52:29 +02:00