From: | James Hall <James(dot)Hall(at)RadioShack(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Pg_dumpall problem |
Date: | 2003-02-06 22:36:01 |
Message-ID: | EE80A67DD80E304DA779C72BC9FA999603808778@ntmailo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you very much for your reply.
Do you have suggestions for setting up a different authorization method for
local connections?
TIA,
-jim
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, February 06, 2003 8:52 AM
To: James Hall
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Pg_dumpall problem
James Hall <James(dot)Hall(at)RadioShack(dot)com> writes:
> I am trying to use pg_dumpall to backup my databases, and it is failing.
> The results of a attempted dumpall are below:
> [postgres(at)rspde postgres]$ pg_dumpall > 020503.out
> Password: psql: Password authentication failed for user 'postgres'
> Password: Password: psql: Password authentication failed for user
'postgres'
> Password: psql: fe_sendauth: no password supplied
> Password: psql: fe_sendauth: no password supplied
pg_dumpall is more or less useless for databases that use password
protection. I counsel setting up a different authorization method for
local connections.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alastair D'Silva | 2003-02-06 23:28:04 | OT: This list is Razored |
Previous Message | will trillich | 2003-02-06 22:21:31 | "Cannot insert a duplicate key..." -- but where? |