Re: libpq async duplicate error results

I took another look at this.  The output from the test program at the 
beginning of the thread is now (master branch):

command = SELECT 'before';
result 1 status = PGRES_TUPLES_OK
error message = ""

command = SELECT pg_terminate_backend(pg_backend_pid());
result 1 status = PGRES_FATAL_ERROR
error message = "FATAL:  terminating connection due to administrator command
"
result 2 status = PGRES_FATAL_ERROR
error message = "server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.
"

command = SELECT 'after';
PQsendQuery() error: FATAL:  terminating connection due to administrator 
command
server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.
no connection to the server


It appears the "after" query is getting the error message from the 
previous cycle somehow.


The output in PG14 and PG13 is:

command = SELECT 'after';
PQsendQuery() error: no connection to the server


Is the change intended or do we need to think about more tweaking?