Re: missing pg_clog files ?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: missing pg_clog files ?
Date: 2003-09-24 21:57:53
Message-ID: 200309242157.h8OLvrG03663@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:
> > Indeed, the plain -d dump says that I have a chunk of /var/mail/prlw1
> > in 1000-13ff. No wonder postgres complained!
>
> Yipes. We have seen this sort of thing once or twice in the past.
> I don't know whether you are looking at a disk drive fault (dropping
> the right data onto the wrong sector) or a kernel fault (getting
> confused about which buffer holds which file block), but I believe
> it's one or the other. It's hard to see how anything at the application
> level could have gotten those two files switched. You might look to see
> if there are any updates available for your kernel.
>
> As for recovery, you probably want to drop and reload at least that one
> table. Whether it's worth a complete reload is your call.

Or just delete the row with that tid and see if you can access the other
data. You might be able to get away with just restoring that one row
from backup.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-09-24 22:03:45 Re: pgsql-server/src/backend catalog/index.c comma ...
Previous Message Hiroshi Inoue 2003-09-24 21:52:58 Re: pgsql-server/src/backend catalog/index.c comma ...