Re: "make check" and pg_hba.conf

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "make check" and pg_hba.conf
Date: 2016-10-18 22:49:37
Message-ID: 7715.1476830977@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> On Tue, Oct 18, 2016 at 2:28 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> No. Why would you want that? External connections to the test DB seem
>> like exactly what you *don't* want, for reproducibility's sake.

> I would want to do that so that the code dealing with password-based logins
> doesn't go completely untested by "make check", like it currently is.

Well, unless you create a user with a password and use that password to
log in, you're not performing much of a test. Getting the hba entry
in there seems to me to be about the least of the worries for making
a usable test case.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2016-10-18 22:55:16 Re: Indirect indexes
Previous Message Jeff Janes 2016-10-18 22:31:22 Re: "make check" and pg_hba.conf