Re: Bad crash, pg_clog files missing ... ? - Mailing list pgsql-hackers

From Marc G. Fournier
Subject Re: Bad crash, pg_clog files missing ... ?
Date
Msg-id 20030307004031.O5683@hub.org
Whole thread Raw
In response to Re: Bad crash, pg_clog files missing ... ?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
'K, that's what I ended up doing ... the server crashed *really* hard, but
I had a backup from 24hrs previous that I used to do restores ... I kinda
figured that I was lost :(

But, the files available are/where ...

venus# ls -lt
total 1168
-rw-------  1 pgsql  pgsql   81920 Mar  6 19:50 0168
-rw-------  1 pgsql  pgsql  262144 Mar  5 20:06 0167
-rw-------  1 pgsql  pgsql  262144 Mar  5 14:10 0166
-rw-------  1 pgsql  pgsql  262144 Mar  5 09:03 0165
-rw-------  1 pgsql  pgsql  262144 Mar  5 02:08 0164


On Thu, 6 Mar 2003, Tom Lane wrote:

> "Marc G. Fournier" <scrappy@hub.org> writes:
> > FATAL 2:  open of /usr/local/pgsql/5432/pg_clog/06F6 failed: No such file or directory
>
> > The RAID controller went on our server today ... is it safe to just
> > 'touch' the files, or is this a 'restore from backup and deal with the
> > losses' sort of thing? :(
>
> What range of filenames is actually in $PGDATA/pg_clog/ ?
>
> I suspect 06F6 is well beyond that range, in which case this error
> implies corrupted table files, in which case "restore from backup"
> is the indicated course of action :-(
>
>             regards, tom lane
>


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Partial index on date column
Next
From: "Marc G. Fournier"
Date:
Subject: Re: pgsql.com website store