Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-bugs-owner+M49253=pgsql+2Dbugs=arkaria.postgresql.org@postgresql.org>)
	id 1e7UMN-0002ZS-Ig
	for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Oct 2017 22:41:15 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-bugs-owner+M49253=pgsql+2Dbugs=arkaria.postgresql.org@postgresql.org>)
	id 1e7UMN-0008Vw-0p
	for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Oct 2017 22:41:15 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1e7ULd-0007G7-RZ
	for pgsql-bugs@postgresql.org; Wed, 25 Oct 2017 22:40:29 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1e7ULW-0004np-Ma
	for pgsql-bugs@postgresql.org; Wed, 25 Oct 2017 22:40:29 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v9PMeKHZ028500;
	Wed, 25 Oct 2017 18:40:20 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael.paquier@gmail.com>
cc: dcwatson@gmail.com, PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Subject: Re: BUG #14872: libpq requires a home directory
In-reply-to: 
 <CAB7nPqTUiDc9+D7_k9i3AsWo5-+pjSE6scnu6_L14ecObwdXdA@mail.gmail.com>
References: <20171025200457.1471.34504@wrigleys.postgresql.org>
 <26003.1508967614@sss.pgh.pa.us> <27255.1508969436@sss.pgh.pa.us>
 <CAB7nPqTUiDc9+D7_k9i3AsWo5-+pjSE6scnu6_L14ecObwdXdA@mail.gmail.com>
Comments: In-reply-to Michael Paquier <michael.paquier@gmail.com>
	message dated "Wed, 25 Oct 2017 15:35:17 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <28498.1508971220.1@sss.pgh.pa.us>
Date: Wed, 25 Oct 2017 18:40:20 -0400
Message-ID: <28499.1508971220@sss.pgh.pa.us>
List-Archive: <http://archives.postgresql.org/pgsql-bugs>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-bugs.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@postgresql.org>
List-Post: <mailto:pgsql-bugs@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-bugs>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
X-Mailing-List: pgsql-bugs
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

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.

			regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs