Date: Wed, 26 Jan 2022 14:52:03 +0100 (CET)
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: libpq async duplicate error results
In-Reply-To: <ab4288f8-be5c-57fb-2400-e3e857f53e46@enterprisedb.com>
Message-ID: <alpine.DEB.2.22.394.2201261448060.3813395@pseudo>
References: <ab4288f8-be5c-57fb-2400-e3e857f53e46@enterprisedb.com>
User-Agent: Alpine 2.22 (DEB 394 2020-01-19)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: 
 <https://www.postgresql.org/message-id/alpine.DEB.2.22.394.2201261448060.3813395%40pseudo>
Precedence: bulk


> 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 = "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.
> "

> Also, why are there multiple results being generated in the first place?

My interpretation is that the first message is a close message issued by 
the server before actually severing the connection, and the second message 
is generated by libpq when it notices that the connection has been closed, 
so there is some sense in having to results to report these two 
consecutive errors, and the question might be about when the buffer should 
be reset.

-- 
Fabien.