pgsql: Make pg_regress.c unset PGDATABASE during make installcheck.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Make pg_regress.c unset PGDATABASE during make installcheck.
Date: 2019-09-27 22:19:41
Message-ID: E1iDyaT-0007nJ-CD@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Make pg_regress.c unset PGDATABASE during make installcheck.

For the most part, we leave libpq-controlling environment variables
alone during "make installcheck", reasoning that connecting to the
server the user expects us to connect to may depend on those variables.
But that argument doesn't apply to PGDATABASE, since we always want
to connect to a specific database name within the server. And failing
to unset it causes certain ECPG tests to fail, as various people have
complained of in the past. So let's unset it.

Possibly this should be back-patched, but I'm disinclined to do that
right before 12.0 release. Maybe later.

Discussion: https://postgr.es/m/20180318205548.2akxjqvo7hrk5wbc@alap3.anarazel.de
Discussion: https://postgr.es/m/E1bOum4-0002EA-2y@gemulon.postgresql.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/5ee96b3e2221d154ffcb719bd2dee1179c53f821

Modified Files
--------------
src/test/regress/pg_regress.c | 8 ++++++++
1 file changed, 8 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Noah Misch 2019-09-28 04:27:05 Re: pgsql: Test pg_atomic_fetch_add_ with variable addend and 16-bit edge c
Previous Message Andres Freund 2019-09-27 21:30:10 Re: [COMMITTERS] pgsql: Establish conventions about global object names used in regressi