Postgres Pro
Downloads
Home   >   mailing lists

Re: Aborted VACUUM FULL -> crash + corruption (xlog non-existent) - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: Aborted VACUUM FULL -> crash + corruption (xlog non-existent)
Date
Msg-id 20080826162710.GK4920@alvh.no-ip.org
Whole thread Raw
In response to Re: Aborted VACUUM FULL -> crash + corruption (xlog non-existent)  (Peter Schuller <peter.schuller@infidyne.com>)
List pgsql-bugs
Tree view 
Peter Schuller wrote:

> I will go hide in a corner now...

FWIW, as soon as you come out of the corner, you can solve the problem
easily by manually copying the file back from the archive location into
pg_xlog and restarting the server.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Aborted VACUUM FULL -> crash + corruption (xlog non-existent)
Next
From: Gregory Stark
Date:
Subject: Re: BUG #4281: some types of errors do not log statements