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.2106182021570.3211875@pseudo>
References: <1226654.1624036821@sss.pgh.pa.us>
 <alpine.DEB.2.22.394.2106182021570.3211875@pseudo>
Comments: In-reply-to Fabien COELHO <coelho@cri.ensmp.fr>
	message dated "Fri, 18 Jun 2021 20:27:16 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1234106.1624041603.1@sss.pgh.pa.us>
Date: Fri, 18 Jun 2021 14:40:03 -0400
Message-ID: <1234107.1624041603@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1234107.1624041603%40sss.pgh.pa.us>
Precedence: bulk

Fabien COELHO <coelho@cri.ensmp.fr> writes:
> Why not move the printVersion call right after the connection is created, 
> at line 6374?

I started with that, and one of the 001_pgbench_with_server.pl
tests fell over --- it was expecting no stdout output before a
"Perhaps you need to do initialization" failure.  If you don't
mind changing that, I agree that printing immediately after
the connection is made is a bit less astonishing.

			regards, tom lane