Received: from correo.servidoresdns.net ([195.55.179.56]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f349Yd893843 for ; Wed, 4 Apr 2001 05:34:41 -0400 (EDT) (envelope-from david.lizano@izanet.com) Received: from servidornt.izanet.com [195.55.250.69] by correo.servidoresdns.net with ESMTP (SMTPD32-6.04) id AA2B97D0082; Wed, 04 Apr 2001 11:32:27 +0200 Message-Id: <4.3.2.7.0.20010404112720.00bf0c20@192.168.1.1> X-Sender: sj7010@192.168.1.1 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 04 Apr 2001 11:32:34 +0200 To: Tom Lane , pgsql-sql@postgresql.org From: David Lizano Subject: Re: pg_dumpall and password access In-Reply-To: <29370.986340578@sss.pgh.pa.us> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200104/34 X-Sequence-Number: 2373 At 19.29 3/4/01 -0400, you wrote: >Christophe Labouisse writes: > > I'm trying to run pg_dumpall to backup all my users' bases but since I > > have configure pg_hba.conf to "passwd" pg_dumpall always fails: > >pg_dumpall doesn't work very well with password authentication (and >even if it did, storing the password in a cron script doesn't seem >like a good idea to me). From the cron script you can execute somethin like this. su -l postgres -c pg_dumpall and then, "pg_dumpall" will be executed by the postgres user.