On Mon, Dec 5, 2011 at 1:18 PM, Yann ROBIN <me.show@xxxxxxxxx> wrote: >> >> First things first: Before you do anything else, shut down >> PostgreSQL and make a copy of the data directory tree. >> >> http://wiki.postgresql.org/wiki/Corruption >> > > Did it. > >> Second, please post information about your environment. What >> version of PostgreSQL is this? What is your OS? What hardware is >> it running on? >> > > Version 9.0.4 on debian squeeze 6.0 running in KVM with virtio (kernel 2.6.32) > I think we have a hard drive issue. > >> Now, please copy from the log at the time of the crash and post all >> messages, plus any possibly relevant messages in the clients and the >> OS logs. Is there a core file from the crash? Can you get a >> backtrace from it? >> > > I rm the log file has it was taking too much space because of the 1000 > warning per seconds. > I feel dumb right now. Sorry. > >> >> It's best to keep notes of exactly what was done. What was the >> process description of what you killed? Which signal did you use? >> Keep notes as you go. >> > > kill -9 of the writer process Are you sure you killed all the postgres backends before restarting the server? If other backends are still running, with a dead postmaster, and you restart the server, instant corruption. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
