The following bug has been logged online:

Bug reference: 1769
Logged by: Nigel Kukard
Email address: nkukard (AT) lbsd (DOT) net
PostgreSQL version: 8.0.3
Operating system: Linux
Description: pg_dumpall fails to run
Details:

On a clean build of postgresql 8.0.3, I seem to encounter a problem when
using pg_dumpall.

I'm trying to run...

# pg_dumpall -U postgres> backup.pgsql

My postgres password is "test".

When pg_dumpall prompts me for the password I type it in, and press enter
only to get another password prompt.

Apon looking in /var/log/pgsql, i see the following error...
LOG: unexpected EOF on client connection

Using psql I can get into the template1 database fine using...
psql -U postgres template1

My pg_hba.conf file looks like this...
# TYPE DATABASE USER CIDR-ADDRESS METHOD
local all postgres md5
local test test md5
local template1 all md5


Any help much appreciated!

Regards
Nigel

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

"Nigel Kukard" <nkukard (AT) lbsd (DOT) net> writes:
This doesn't seem particularly surprising: you are going to have to
enter the password once for pg_dumpall, and once for each of its
per-database invocations of pg_dump.

Most people try to set things up so that pg_dump(all) can be executed
without any manual password entry. You might be able to use another
authorization method for local connections; failing that, set up a
~/.pgpass file for the database superuser.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match