Date: Wed, 9 Mar 2011 09:48:10 -0500
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-general@postgresql.org, pgsql-admin@postgresql.org
Subject: Re: [GENERAL] FW: backup using pg_dump  postgreSQL 8.3.8
Message-ID: <20110309144810.GP32629@shinkuro.com>
Mail-Followup-To: Andrew Sullivan <ajs@crankycanuck.ca>,
	pgsql-general@postgresql.org, pgsql-admin@postgresql.org
References: 
 <10E646CF2170984794256AC2DD2C065C6BA882@Mcw-BS-Mail.mpdc.mcw.co.il>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <10E646CF2170984794256AC2DD2C065C6BA882@Mcw-BS-Mail.mpdc.mcw.co.il>
User-Agent: Mutt/1.5.18 (2008-05-17)

On Wed, Mar 09, 2011 at 03:58:20PM +0200, Sandy Test wrote:
> 
> We want to be able to run a nightly backup using the pg_dump command.
> 
> Unfortunately, even with the pg_hba.conf fix of adding host postgres ...
> trust, 
> 
> It still asks for a password.

pg_hba sometimes surprises people because of its matching rules.  If
there's another entry that matches before the explicit postgres entry,
that's the rule you're going to get:

    The first record with a matching connection type, client address,
    requested database, and user name is used to perform
    authentication. There is no "fall-through" or "backup": if one
    record is chosen and the authentication fails, subsequent records
    are not considered. If no record matches, access is denied.

(http://www.postgresql.org/docs/9.0/interactive/auth-pg-hba-conf.html).
Are you sure that's not your problem.  (It always is for me, and I
always make this mistake at least once per installation, even after
many years.)

A

-- 
Andrew Sullivan
ajs@crankycanuck.ca