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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs