| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: Version reporting in pgbench |
| Date: | 2021-06-18 21:37:44 |
| Message-ID: | alpine.DEB.2.22.394.2106182336550.3211875@pseudo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> 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.
I'm fine with having a uniform behavior over pg commands.
Thanks for the improvement!
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-06-18 21:46:00 | Re: Failures with gcd functions with GCC snapshots GCC and -O3 (?) |
| Previous Message | Fabien COELHO | 2021-06-18 21:31:29 | Re: Failures with gcd functions with GCC snapshots GCC and -O3 (?) |