From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: "make check" and pg_hba.conf |
Date: | 2016-10-18 22:31:22 |
Message-ID: | CAMkU=1waE0S0zvWmJBMoTD5s+kU1B7QpMuz0Xe2jNyg=Qf0zEA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 18, 2016 at 2:28 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jeff Janes <jeff(dot)janes(at)gmail(dot)com> 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
> 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.
I don't see how connecting to an obscure unix socket with a password is
more "external" than connecting to the same obscure linux socket without a
password.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-10-18 22:49:37 | Re: "make check" and pg_hba.conf |
Previous Message | Petr Jelinek | 2016-10-18 22:27:39 | Re: PATCH: two slab-like memory allocators |