Re: "could not open file" issue

From: "Daniel Caune" <daniel(dot)caune(at)ubisoft(dot)com>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: "could not open file" issue
Date: 2006-04-24 20:38:06
Message-ID: 1E293D3FF63A3740B10AD5AAD88535D20213292D@UBIMAIL1.ubisoft.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

> De : Alvaro Herrera [mailto:alvherre(at)commandprompt(dot)com]
>
> Daniel Caune wrote:
> >
> > > De : Alvaro Herrera [mailto:alvherre(at)commandprompt(dot)com]
> > >
> > > Daniel Caune wrote:
> > > >
> > > > select count(*) from eventplayerleaveroom;
> > > > ERROR: could not access status of transaction 3164404766
> > > > DETAIL: could not open file "pg_clog/0BC9": No such file or
> directory
> > >
> > > Are the files in pg_clog close to the vicinity of 0BC9?
> >
> > I don't have any skill in PostgreSQL administration. However I took a
> > look at /var/lib/postgresql/8.1/main/pg_clog and there is no file
> > close to the vicinity of 0BC9 ; the last file in that directory is:
> >
> > -rw------- 1 postgres postgres 221184 2006-04-24 19:27 00C9
> >
> > A bit far from 0BC9... Do you have any diagnostic?
>
> I'd say you have a corrupted table. How corrupted I don't know. You
> could try extracting a portion of the table, playing with LIMIT/OFFSET
> to find out the exact records that are corrupted.
>

Yes, I tried playing with the LIMIT clause, and LIMIT 90 is the better I can pass... :-(

> --
> Alvaro Herrera
> http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Browse pgsql-sql by date

  From Date Subject
Next Message Daniel Caune 2006-04-24 21:02:37 Re: "could not open file" issue
Previous Message A. R. Van Hook 2006-04-24 20:37:18 Re: date array