Re: URGENT: pg_dump & Postgres 7.2b4

Dont panic, it was just a stupid try and i had saved the file and then
restored it ;)

If you could tell me how to figure out why Postgres is still trying to
access a segment it deleted, i ll do it and report it.

Thanks in advance
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Christian Meunier" <jelan(at)magelo(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: Thursday, January 10, 2002 8:01 PM
Subject: Re: [GENERAL] URGENT: pg_dump & Postgres 7.2b4

> "Christian Meunier" <jelan(at)magelo(dot)com> writes:
> > Is there a way to clean up those commit log ?, i tried to remove 0002
but it
> > didnt help( it was then doing error on 0002 too)
>
> You did *what*?
>
> You may as well have done "rm -rf $PGDATA". You're hosed.
>
> I would have liked to look into why it was still trying to reference the
> 0000 segment after removing it; that suggests a logic problem somewhere.
> But with the database now completely nonfunctional due to loss of the
> active clog segment, there's probably no way to learn anything useful.
>
> Don't remove files when you don't know what they are.
>
> regards, tom lane
>