From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | Jim Buttafuoco <jim(at)contactbda(dot)com> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_clog problem (PG version 7.4.5) |
Date: | 2005-01-22 18:07:35 |
Message-ID: | 20050122180735.GA17096@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Jan 22, 2005 at 12:06:46PM -0500, Jim Buttafuoco wrote:
> didn't work.
>
>
> ERROR: could not access status of transaction 1076101119
> DETAIL: could not read from file "/usr/local/pgsql/data/pg_clog/0402" at offset 57344: Success
>
> any more ideas?
You need to extend the file further than byte 57344. So repeat the dd
command, with count=8.
Anyway, this situation is suspect anyway. There were bugs related to
pg_clog files not being there, but AFAIR they were triggered on segment
edges, not in the middle like this one.
What other files there are in the pg_clog directory? If they are
nowhere near the 0402 vicinity, you may have a memory or disk
corruption problem.
FWIW, 1076101119 is 1000000001000111111111111111111 in binary. Taking
the highest 1 yeilds Xid 2359295. So, what files do you have?
--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"La primera ley de las demostraciones en vivo es: no trate de usar el sistema.
Escriba un guión que no toque nada para no causar daños." (Jakob Nielsen)
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Buttafuoco | 2005-01-22 18:14:41 | Re: pg_clog problem (PG version 7.4.5) |
Previous Message | Dennis Bjorklund | 2005-01-22 17:27:01 | French site with postgresql name |