Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f33NUUK49202 for ; Tue, 3 Apr 2001 19:30:31 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f33NTcw29373; Tue, 3 Apr 2001 19:29:38 -0400 (EDT) To: Christophe Labouisse cc: pgsql-sql@postgresql.org Subject: Re: pg_dumpall and password access In-reply-to: References: Comments: In-reply-to Christophe Labouisse message dated "04 Apr 2001 00:47:23 +0200" Date: Tue, 03 Apr 2001 19:29:38 -0400 Message-ID: <29370.986340578@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/29 X-Sequence-Number: 2368 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). As long as the dumper will run on the same machine as the database server, consider using IDENT authorization instead. You'll need an identd daemon running, and you'll need to use a TCP connection because IDENT only works with TCP connections. The simplest form of pg_hba.conf entry is host all 127.0.0.1 255.255.255.255 ident sameuser If you have no other users you want to let in, you could use an explicit ident map instead of 'sameuser' to tighten this up even more. See the admin documentation for more info. I don't recommend using IDENT for connections from untrusted machines, but on localhost it's as trustworthy as your local sysadmin... regards, tom lane