On Mon, Sep 8, 2008 at 4:34 AM, Wouter Sergeyssels <[EMAIL PROTECTED]> wrote:
> Hey Guys,
>
> Thanks for your input. Meanwhile we have recovered from a backup.
>
> Lesson of all this, upgrade asap to postgres 8.2?
Close, but I'd change that to 8.3.3 myself.
--
Sent via pgsql-general mailing list
Hey Guys,
Thanks for your input. Meanwhile we have recovered from a backup.
Lesson of all this, upgrade asap to postgres 8.2?
Thanks,
WS.
-Original Message-
From: Greg Stark [mailto:[EMAIL PROTECTED] On Behalf Of
Gregory Stark
Sent: zondag 7 september 2008 11:50
To: Tom Lane
Cc: Wouter
Tom Lane <[EMAIL PROTECTED]> writes:
> The only recovery strategy that I can think of in 8.1 is to blow away
> your WAL with pg_resetxlog, let the database come up in a damaged
> condition, and then try to extract data from it.
Would it work if he rebuilt 8.1 with a "return;" as the first line
"Wouter Sergeyssels" <[EMAIL PROTECTED]> writes:
> When doing a recover in a single-user backend we get the following
> error:
> $ postgres -D /var/lib/pgsql/data/ test
> PANIC: block 24929 unfound
This looks like it is probably a case of a design problem that was fixed
in 8.2: the WAL replay co
Hello,
When doing a recover in a single-user backend we get the following
error:
$ postgres -D /var/lib/pgsql/data/ test
PANIC: block 24929 unfound
Aborted.
All this was the result of an unclean postmaster shutdown while running
a VACUUM in single-user backend.
PGVERSION=8.1.6
DB S
