Thanks Scott. We used a command like this '/usr/bin/pg_dumpall -cC' postgres to do the pg_dumpall. I started my postmaster with this command "/usr/bin/postmaster -D /var/lib/pgsql/data -i" I got my tables back in the database, but I don't see any data. What could have went wrong when I did the "psql -f /usr/pgsql/backups/31.bak template1"? Did I miss a step or something? Now, I'm really worried. Maybe I should have capture the log file when I did the restore? Please advise. Mary ------------------------------------------------ Mary Y Wang -----Original Message----- From: Scott Marlowe [mailto:scott.marlowe@xxxxxxxxx] Sent: Tuesday, February 02, 2010 3:17 PM To: Wang, Mary Y Cc: Tom Lane; pgsql-admin@xxxxxxxxxxxxxx Subject: Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush On Tue, Feb 2, 2010 at 3:29 PM, Wang, Mary Y <mary.y.wang@xxxxxxxxxx> wrote: > Thanks Tom. > > After talking to my co-worker, we decided to go to the last backup (we used the pg_dumpall -c command). > However, when I did enter "psql -f /usr/pgsql/backups/31.bak template1" to restore the database, I got " > psql: connectDBStart() -- connect() failed: No such file or directory > Is the postmaster running locally > and accepting connections on Unix socket '/tmp/.s.PGSQL.5432'? > ". > I can't start my postmaster. So how would I restore my last good backup? The normal way is to drop the old cluster and create a new one. I'm not entirely sure how to do that on something as old as RHEL 2.1. The normal way would be to mv or rm -rf the /var/lib/pgsql/data dir and run initdb again. something like: sudo /etc/init.d/pgsql stop sudo rm -rf /var/lib/pgsql/data/* sudo -u postgres initdb -D /var/lib/pgsql/data sudo /etc/init.d/pgsql start or something like that. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
