Horton

Re: BUG #14872: libpq requires a home directory

Michael Paquier <michael.paquier@gmail.com>

View thread View on postgr.es
From: Michael Paquier <michael.paquier@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: dcwatson@gmail.com, PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Date: 2017-10-26T05:20:06Z
Lists: pgsql-bugs 
On Wed, Oct 25, 2017 at 3:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Michael Paquier <michael.paquier@gmail.com> writes:
>> On Wed, Oct 25, 2017 at 2:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Poking around, it looks like parseServiceInfo's search for
>>> ~/.pg_service.conf has the same disease, but that code's been like that
>>> since 2010 --- I wonder why it's not causing you problems?  Are you maybe
>>> setting PGSERVICEFILE to prevent that from failing?
>
>> Yeah... I was halfway into hacking a patch for that but got drowned
>> into other things until I saw your message. Are you working on a
>> patch?
>
> Yeah, I'm on it.

Okay, I'm dropping the ball then. Note: this has been fixed as db6986f.
-- 
Michael

Commits

  1. Fix libpq to not require user's home directory to exist.

  2. Allow password file name to be specified as a libpq connection parameter.