Re: ECPG installcheck tests fail if PGDATABASE is set

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Michael Meskes <meskes@postgresql.org>, pgsql-hackers@postgresql.org
Date: 2018-03-18T23:06:18Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> I got a bit confused running installcheck-world and seeing ecpg
> failures like:
> ...
> A bit of pondering pointed me towards my environment's
> PGDATABASE=postgres being to blame. Unsetting that makes the test
> succeed.

Hm ... pg_regress unsets PGDATABASE, along with the other related
environment variables, when it has a temp installation but not
when it doesn't.  So what I don't understand is why your environment
doesn't also break every other regression test besides ecpg.
Perhaps they're all connecting to "postgres", but it's hard to
believe there wouldn't be conflicts if so.

			regards, tom lane


Commits

  1. Make pg_regress.c unset PGDATABASE during make installcheck.