On 10/18/16 6:31 PM, Jeff Janes wrote:
> 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.
Write a TAP test for it.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Developmen
Jeff Janes writes:
> On Tue, Oct 18, 2016 at 2:28 PM, Tom Lane 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
> does
On Tue, Oct 18, 2016 at 2:28 PM, Tom Lane wrote:
> Jeff Janes writes:
> > Is there a way to get "make check" to install a custom pg_hba.conf for
> its
> > temporary installation? Something like pre-prending the line:
> > local all password_user md5
> > To the default pg_hba.conf?
>
> No. Why
Jeff Janes writes:
> Is there a way to get "make check" to install a custom pg_hba.conf for its
> temporary installation? Something like pre-prending the line:
> local all password_user md5
> To the default pg_hba.conf?
No. Why would you want that? External connections to the test DB seem
li
Is there a way to get "make check" to install a custom pg_hba.conf for its
temporary installation? Something like pre-prending the line:
local all password_user md5
To the default pg_hba.conf?
Thanks,
Jeff
