From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fabien COELHO <coelho@cri.ensmp.fr>
cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>,
        Thomas Munro <thomas.munro@gmail.com>
Subject: Re: Version reporting in pgbench
In-reply-to: <alpine.DEB.2.22.394.2106182300170.3211875@pseudo>
References: <1226654.1624036821@sss.pgh.pa.us>
 <alpine.DEB.2.22.394.2106182021570.3211875@pseudo>
 <1234107.1624041603@sss.pgh.pa.us>
 <alpine.DEB.2.22.394.2106182300170.3211875@pseudo>
Comments: In-reply-to Fabien COELHO <coelho@cri.ensmp.fr>
	message dated "Fri, 18 Jun 2021 23:18:45 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1320809.1624051719.1@sss.pgh.pa.us>
Date: Fri, 18 Jun 2021 17:28:39 -0400
Message-ID: <1320810.1624051719@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1320810.1624051719%40sss.pgh.pa.us>
Precedence: bulk

Fabien COELHO <coelho@cri.ensmp.fr> writes:
> Note that if no connections are available, then you do not get the 
> version, which may be a little bit strange. Attached v3 prints out the 
> local version in that case. Not sure whether it is worth the effort.

I'm inclined to think that the purpose of that output is mostly
to report the server version, so not printing it if we fail to
connect isn't very surprising.  Certainly that's how psql has
acted for decades.

			regards, tom lane