pgsql: Fix vcregress.pl's ancient misspelling of --max-connections.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix vcregress.pl's ancient misspelling of --max-connections.
Date: 2021-05-11 23:17:16
Message-ID: E1lgbcq-000064-4C@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix vcregress.pl's ancient misspelling of --max-connections.

I copied the existing spelling of "--max_connections", but
that's just wrong :-(. Evidently setting $ENV{MAX_CONNECTIONS}
has never actually worked in this script. Given the lack of
complaints, it's probably not worth back-patching a fix.

Per buildfarm.

Discussion: https://postgr.es/m/899209.1620759506@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/0b85fa93e4575183aa5a71ebe3c6bae8d97704ed

Modified Files
--------------
src/tools/msvc/vcregress.pl | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2021-05-12 00:07:23 pgsql: Tweak generation of Gen_dummy_probes.pl
Previous Message Alvaro Herrera 2021-05-11 21:56:16 Re: pgsql: autovacuum: handle analyze for partitioned tables