Re: "could not open file" issue
От | Daniel Caune |
---|---|
Тема | Re: "could not open file" issue |
Дата | |
Msg-id | 1E293D3FF63A3740B10AD5AAD88535D20213292D@UBIMAIL1.ubisoft.org обсуждение исходный текст |
Ответ на | "could not open file" issue ("Daniel Caune" <daniel.caune@ubisoft.com>) |
Список | pgsql-sql |
> De : Alvaro Herrera [mailto:alvherre@commandprompt.com] > > Daniel Caune wrote: > > > > > De : Alvaro Herrera [mailto:alvherre@commandprompt.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
В списке pgsql-sql по дате отправления: