Hi,

I'm using the pg_dump and pg_restore client applications to implement
our database backup-restore strategies. Wrt this, inorder to be able to
autoamate the backup process (run it as a cron job), I'm using the
..pgpass file for automating the password input. This is working for
pg_dump.

My restore script does a full restore - I first drop the existing
database using dropdb, create a new database using createdb and then use
pg_restore to restore the database from the backup file created (using
pg_dump)

I find that while pg_dump and pg_restore take/read the password from
the .pgpass file, dropdb and createdb do not. For these, i'm still
having to key in the password. The permissions for the .pgpass is 0600
as expected.

Can anyone please let me know why this is happening? Thanks.

-Anu

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

On Wed, May 11, 2005 at 11:35:16PM -0600, Sankaran Anupama wrote:
Using .pgpass is a behavior of libpq, which underlies utilities
like pg_dump, createdb, and dropdb. If createdb and dropdb are
linked against a libpq from PostgreSQL 7.3 or later, then they
should be using .pgpass. Have you done a process trace or examined
the access time of .pgpass to test your hypothesis that createdb
and dropdb don't use it? Have you used the --version option to
verify that the correct versions of those utilites are being used,
or ldd to see which libpq they're linked against?

createdb and dropdb make connections to template1. Have you checked
pg_hba.conf to see if connecting to template1 is different than
connecting to other databases?

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq