Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 55605475BF9 for ; Sun, 29 Dec 2002 22:31:33 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id A198A475B8C for ; Sun, 29 Dec 2002 22:31:32 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id gBU3Vad0016433; Sun, 29 Dec 2002 22:31:36 -0500 (EST) To: ljb Cc: pgsql-interfaces@postgresql.org Subject: Re: Shouldn't .pgpass work with anything which uses libpq? In-reply-to: References: Comments: In-reply-to ljb message dated "Mon, 30 Dec 2002 02:44:47 +0000" Date: Sun, 29 Dec 2002 22:31:36 -0500 Message-ID: <16432.1041219096@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200212/80 X-Sequence-Number: 3493 ljb writes: > Digging into it a bit, I think no conninfo-based connection method will use > .pgpass, including libpq PQconnectDB() and libpgtcl "pg_connect -conninfo". Seems like a bug to me too. regards, tom lane