Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 7C6F01337B9C for ; Wed, 9 Mar 2011 11:42:18 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 34999-04; Wed, 9 Mar 2011 15:42:11 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by mail.postgresql.org (Postfix) with ESMTP id AB24B1337B93; Wed, 9 Mar 2011 11:42:10 -0400 (AST) Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 4BCF31ECB408; Wed, 9 Mar 2011 15:42:10 +0000 (UTC) Date: Wed, 9 Mar 2011 10:42:08 -0500 From: Andrew Sullivan To: Tom Lane Cc: Andrew Sullivan , pgsql-general@postgresql.org, pgsql-admin@postgresql.org Subject: Re: [GENERAL] FW: backup using pg_dump postgreSQL 8.3.8 Message-ID: <20110309154207.GQ32629@shinkuro.com> Mail-Followup-To: Andrew Sullivan , Tom Lane , pgsql-general@postgresql.org, pgsql-admin@postgresql.org References: <10E646CF2170984794256AC2DD2C065C6BA882@Mcw-BS-Mail.mpdc.mcw.co.il> <20110309144810.GP32629@shinkuro.com> <24275.1299684716@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <24275.1299684716@sss.pgh.pa.us> User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201103/103 X-Sequence-Number: 36975 On Wed, Mar 09, 2011 at 10:31:56AM -0500, Tom Lane wrote: > Andrew Sullivan writes: > > On Wed, Mar 09, 2011 at 03:58:20PM +0200, Sandy Test wrote: > >> Unfortunately, even with the pg_hba.conf fix of adding host postgres ... > >> trust, > If it is asking for a password, and password authentication is what's > supposed to be used, then pg_hba is not where the problem is. Yes, but I think the OP was saying that the setting was moved to trust. My point was just that adding a trust entry isn't enough if there's an earlier password entry. I agree that .pgpass is probably the desired answer anyway. A -- Andrew Sullivan ajs@crankycanuck.ca