Re: URGENT: pg_dump & Postgres 7.2b4 - Mailing list pgsql-general

From Jelan
Subject Re: URGENT: pg_dump & Postgres 7.2b4
Date
Msg-id 009301c19a0f$b9566b40$0200a8c0@hurrican
Whole thread Raw
In response to URGENT: pg_dump & Postgres 7.2b4  ("Christian Meunier" <jelan@magelo.com>)
Responses Re: URGENT: pg_dump & Postgres 7.2b4  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
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@sss.pgh.pa.us>
To: "Christian Meunier" <jelan@magelo.com>
Cc: <pgsql-general@postgresql.org>
Sent: Thursday, January 10, 2002 8:01 PM
Subject: Re: [GENERAL] URGENT: pg_dump & Postgres 7.2b4


> "Christian Meunier" <jelan@magelo.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
>


pgsql-general by date:

Previous
From: Mike Schroepfer
Date:
Subject: Insert Performance with WAL and Fsync
Next
From: Andrew Perrin
Date:
Subject: Re: Performance tips