"John P. Looney" <[EMAIL PROTECTED]> writes: > What's up here ? Google is deathly silent.=20
> bash-2.05a$ pg_dumpall > db.out > connected to template1... > dumping database "MyPgSQLTest"... > dumping database "bb1"... > dumping database "bbadmin"... > pg_dump: [archiver (db)] connection to database "bbadmin" failed: FATAL > 1: SetDatabaseEncoding(): invalid database encoding > pg_dump failed on bbadmin, exiting A quick-and-dirty nostrum that sometimes helps for this sort of thing is "vacuum full pg_database". (The idea is to get rid of dead tuples that a new backend might be accidentally picking instead of the live ones --- it has to read pg_database before it's joined the PROC array, which among other things means it can't tell 100% accurately which rows are really committed.) If no go, could we see the output of "select * from pg_database"? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly