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
In response to
pgsql-bugs by date
|Next:||From: Gregory Stark||Date: 2008-08-26 16:28:17|
|Subject: Re: BUG #4281: some types of errors do not log statements|
|Previous:||From: Alvaro Herrera||Date: 2008-08-26 16:25:59|
|Subject: Re: Aborted VACUUM FULL -> crash + corruption (xlognon-existent)|