Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id B5DCA9FB27A for ; Sat, 27 Jan 2007 21:47:12 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 22842-01-2 for ; Sat, 27 Jan 2007 21:46:58 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B34749FB29D for ; Sat, 27 Jan 2007 21:46:36 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l0S1kX8G026016; Sat, 27 Jan 2007 20:46:33 -0500 (EST) To: "Michael Schmidt" cc: "PostgreSQL General" Subject: Re: Password issue revisited In-reply-to: References: Comments: In-reply-to "Michael Schmidt" message dated "Sat, 27 Jan 2007 18:26:45 -0700" Date: Sat, 27 Jan 2007 20:46:33 -0500 Message-ID: <26015.1169948793@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/1645 X-Sequence-Number: 108185 "Michael Schmidt" writes: > Also, it appears > from the documentation that the PGPASSFILE environmental variable has > been deprecated for pg_dump and pg_restore. Eh? Certainly not ... where did you get that idea? > I would like to ask that we return to outputting the Password prompt on > stderr and accepting password input on stdin. I think it's unlikely we will revert that, as it's been a done deal for several releases now (since 7.4 in fact). regards, tom lane