Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2C39A9FA377 for ; Sun, 28 Jan 2007 13:09:17 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 86489-05-2 for ; Sun, 28 Jan 2007 13:09:12 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from bay0-omc3-s6.bay0.hotmail.com (bay0-omc3-s6.bay0.hotmail.com [65.54.246.206]) by postgresql.org (Postfix) with ESMTP id C8D999FB389 for ; Sun, 28 Jan 2007 13:06:56 -0400 (AST) Received: from hotmail.com ([65.54.169.77]) by bay0-omc3-s6.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Sun, 28 Jan 2007 09:06:55 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 28 Jan 2007 09:06:55 -0800 Message-ID: Received: from 71.221.112.215 by BAY114-DAV5.phx.gbl with DAV; Sun, 28 Jan 2007 17:06:55 +0000 X-Originating-IP: [71.221.112.215] X-Originating-Email: [michaelmschmidt@msn.com] X-Sender: michaelmschmidt@msn.com From: "Michael Schmidt" To: "Tom Lane" Cc: "PostgreSQL General" References: <26015.1169948793@sss.pgh.pa.us> Subject: Re: Password issue revisited Date: Sun, 28 Jan 2007 10:06:58 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01C742C4.0BD3ED90" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: MSN 9 X-MimeOLE: Produced By MSN MimeOLE V9.50.0034.2000 Seal-Send-Time: Sun, 28 Jan 2007 10:06:58 -0700 X-OriginalArrivalTime: 28 Jan 2007 17:06:55.0728 (UTC) FILETIME=[B6AD3700:01C742FE] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.722 tagged_above=0 required=5 tests=AWL, BAYES_05, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, HTML_40_50, HTML_MESSAGE, MSGID_FROM_MTA_HEADER, SPF_PASS X-Spam-Level: X-Archive-Number: 200701/1672 X-Sequence-Number: 108212 This is a multi-part message in MIME format. ------=_NextPart_000_001F_01C742C4.0BD3ED90 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Mr. Lane and Mr. Momjian, Well, I asked and I got an answer. So be it. Regarding how I concluded = that PGPASSFILE was deprecated for pg_dump, I offer the following. 1. The documentation for pg_dump in the manual (Section VI) includes a = section labeled "Environment". This lists PGDATABASE, PGHOST, PGPORT, = and PGUSER. It also says "default connection parameters" but there is = no hyperlink or reference to another manual section to explain/define = this term. =20 2. Neither the Index nor the Table of Contents has an entry for = "connection parameters" or "default connection parameters". =20 3. The application help (pg_dump --help) provides no further = information. 4. The pg_dump documentation in Section VI has a "See Also" section, = with a link to 29.12. In 29.12 there is a list of variables that "can = be used to select default connection parameters" for PQconnectdb, = PQsetdbLogin, and PQsetdb (no mention of pg_dump). The list includes = those mentioned in the pg_dump documentation () see 1 above) along with = several others (including PGPASSFILE). I was left wondering why would = some of these be mentioned in the pg_dump section and not the others? = Perhaps those not mentioned can't be used by pg_dump? =20 Given the above ambiguities, I was not able to conclude that pg_dump = would accept the PGPASSFILE environment variable. Michael Schmidt ------=_NextPart_000_001F_01C742C4.0BD3ED90 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Mr. Lane and Mr. Momjian,
Well, I asked and I got an answer.  So be it.  Regarding = how I=20 concluded that PGPASSFILE was deprecated for pg_dump, I offer the=20 following.
 
1.  The documentation for pg_dump in the manual (Section VI) = includes=20 a section labeled "Environment".  This lists PGDATABASE, PGHOST, = PGPORT,=20 and PGUSER.  It also says "default connection parameters" but there = is no=20 hyperlink or reference to another manual section to explain/define this=20 term. 
 
2.  Neither the Index nor the Table of Contents has an entry = for=20 "connection parameters" or "default connection parameters". 
 
3.  The application help (pg_dump --help) provides no further=20 information.
 
4.  The pg_dump documentation in Section VI has a "See Also" = section,=20 with a link to 29.12.  In 29.12 there is a list of variables that = "can be=20 used to select default connection parameters" for PQconnectdb, = PQsetdbLogin, and=20 PQsetdb (no mention of pg_dump).  The list includes those mentioned = in the=20 pg_dump documentation () see 1 above) along with several others = (including=20 PGPASSFILE).  I was left wondering why would some of these be = mentioned in=20 the pg_dump section and not the others?  Perhaps those not = mentioned can't=20 be used by pg_dump? 
 
Given the above ambiguities, I was not able to conclude that = pg_dump would=20 accept the PGPASSFILE environment variable.
 
Michael Schmidt
 
------=_NextPart_000_001F_01C742C4.0BD3ED90--