FATAL: password authentication failed for user "postgres"
Hi,
I am using trust authentication since some years, but I need now to
authenticate the user for a specific application when connect to
postgresql database. I found "trust" ignores the password, so I changed
it in pg_hba.conf to "password".
My application is working now, but I have problems running the usual
maintenance scripts. For instance, when I am running pg_dump with
postgres user, it requires the password. The problem is it doesn't
accept the password I used in pgAdmin to connect to the same database
for the same database user.
What is wrong ?
My pg_hba.conf looks like:
local all all password
host all all 127.0.0.1/32 password
The command I am running is:
pg_dump <my_db_name> -F c -v -X disable-triggers -U postgres -h
127.0.0.1 -p 5432 -f ./test.backup
TIA,
Sabin
On Thu, Nov 3, 2011 at 9:02 AM, Sabn Coanda <s.coanda@deuromedia.ro> wrote:
Hi,
I am using trust authentication since some years, but I need now to
authenticate the user for a specific application when connect to postgresql
database. I found "trust" ignores the password, so I changed it in
pg_hba.conf to "password".
You should probably switch this to md5. It gives the same basic
functionality, but it's more secure.
My application is working now, but I have problems running the usual
maintenance scripts. For instance, when I am running pg_dump with postgres
user, it requires the password. The problem is it doesn't accept the
password I used in pgAdmin to connect to the same database for the same
database user.What is wrong ?
My pg_hba.conf looks like:
local all all password
host all all 127.0.0.1/32 passwordThe command I am running is:
pg_dump <my_db_name> -F c -v -X disable-triggers -U postgres -h 127.0.0.1 -p
5432 -f ./test.backup
Does pgadmin also connect via 127.0.0.1? What happens if you dump via
the local socket? Also, do you get an error for pg_dump, or does it
just prompt for a password that it wont accept what you submit?
Robert Treat
conjecture: xzilla.net
consulting: omniti.com