Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e7Ttc-0000uP-Et for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Oct 2017 22:11:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e7Ttb-0003wY-Sp for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Oct 2017 22:11:31 +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 ) id 1e7Tss-0002h5-Jo for pgsql-bugs@postgresql.org; Wed, 25 Oct 2017 22:10:46 +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 ) id 1e7Tsm-00042z-F2 for pgsql-bugs@postgresql.org; Wed, 25 Oct 2017 22:10:43 +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 v9PMAaEK027256; Wed, 25 Oct 2017 18:10:36 -0400 From: Tom Lane To: dcwatson@gmail.com cc: pgsql-bugs@postgresql.org Subject: Re: BUG #14872: libpq requires a home directory In-reply-to: <26003.1508967614@sss.pgh.pa.us> References: <20171025200457.1471.34504@wrigleys.postgresql.org> <26003.1508967614@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Wed, 25 Oct 2017 17:40:14 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <27254.1508969436.1@sss.pgh.pa.us> Date: Wed, 25 Oct 2017 18:10:36 -0400 Message-ID: <27255.1508969436@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org I 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? Ah, looking closer, we don't reach that code unless you've specified a service name (either as a connection parameter or through the PGSERVICE environment variable). So it's not so surprising that nobody complained about that case yet. But it's still wrong. 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