Skip site navigation (1) Skip section navigation (2)

Re: pg_clog

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Edoardo Ceccarelli" <eddy(at)axa(dot)it>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_clog
Date: 2006-12-18 18:48:33
Message-ID: 25199.1166467713@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-jdbc
"Edoardo Ceccarelli" <eddy(at)axa(dot)it> writes:
> pg_dump: ERROR:  could not access status of transaction 1629514106
> DETAIL:  could not open file "pg_clog/0612": No such file or directory

This looks like a data corruption problem to me.  It may or may not be
significant that 1629514106 = 0x6120697a = ASCII 'zi a' (or 'a iz' if
you are on a big-endian machine).  That looks at least a little bit
plausible for Italian text, so I'm wondering if your disk drive or OS
has hiccuped and dumped a sector or two of some other file into your
database :-(.  We've seen it happen before.

Check the archives for past discussions about locating and recovering
from corrupted data.

			regards, tom lane

In response to

  • pg_clog at 2006-12-18 17:57:23 from Edoardo Ceccarelli

Responses

  • Re: pg_clog at 2006-12-18 19:01:17 from Edoardo Ceccarelli

pgsql-admin by date

Next:From: Edoardo CeccarelliDate: 2006-12-18 19:01:17
Subject: Re: pg_clog
Previous:From: Joshua ColsonDate: 2006-12-18 18:43:55
Subject: Where in the source is the "database system identifier" generated?

pgsql-jdbc by date

Next:From: Edoardo CeccarelliDate: 2006-12-18 19:01:17
Subject: Re: pg_clog
Previous:From: Edoardo CeccarelliDate: 2006-12-18 18:26:44
Subject: Re: pg_clog

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group