From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Daniel Caune <daniel(dot)caune(at)ubisoft(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: "could not open file" issue |
Date: | 2006-04-24 20:35:52 |
Message-ID: | 20060424203552.GC18690@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | A. R. Van Hook | 2006-04-24 20:37:18 | Re: date array |
Previous Message | Daniel Caune | 2006-04-24 19:44:43 | Re: "could not open file" issue |