Re: "make check" and pg_hba.conf
| От | Jeff Janes |
|---|---|
| Тема | Re: "make check" and pg_hba.conf |
| Дата | |
| Msg-id | CAMkU=1waE0S0zvWmJBMoTD5s+kU1B7QpMuz0Xe2jNyg=Qf0zEA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: "make check" and pg_hba.conf (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: "make check" and pg_hba.conf
Re: "make check" and pg_hba.conf |
| Список | pgsql-hackers |
On Tue, Oct 18, 2016 at 2:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Jeff Janes <jeff.janes@gmail.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
В списке pgsql-hackers по дате отправления: