Skip site navigation (1) Skip section navigation (2)

Re: Aborted VACUUM FULL -> crash + corruption (xlognon-existent)

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Peter Schuller <peter(dot)schuller(at)infidyne(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Aborted VACUUM FULL -> crash + corruption (xlognon-existent)
Date: 2008-08-26 16:27:11
Message-ID: 20080826162710.GK4920@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-bugs
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 StarkDate: 2008-08-26 16:28:17
Subject: Re: BUG #4281: some types of errors do not log statements
Previous:From: Alvaro HerreraDate: 2008-08-26 16:25:59
Subject: Re: Aborted VACUUM FULL -> crash + corruption (xlognon-existent)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group