From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: libpq async duplicate error results
Date: Fri, 6 May 2022 15:49:28 +0200
Message-ID: <de57761c-b99b-3435-b0a6-474c72b1149a@enterprisedb.com> (raw)
In-Reply-To: <1421785.1645723238@sss.pgh.pa.us>
References: <202202081500.xl3iwa7doscz@alvherre.pgsql>
<394797.1645388816@sss.pgh.pa.us>
<1262938.1645658107@sss.pgh.pa.us>
<1421785.1645723238@sss.pgh.pa.us>
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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@enterprisedb.com, tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org, coelho@cri.ensmp.fr
Subject: Re: libpq async duplicate error results
In-Reply-To: <de57761c-b99b-3435-b0a6-474c72b1149a@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox