From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Casey T(dot) Deccio" <casey(at)deccio(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Transaction error |
Date: | 2005-09-01 15:59:31 |
Message-ID: | 21083.1125590371@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Casey T. Deccio" <casey(at)deccio(dot)net> writes:
> I recently shut down my machine (as far as I know, it went down
> cleanly). When I brought it back up, one of my databases was messed
> up. Here is the error I get when I try to select:
> ERROR: could not access status of transaction 4114057
> DETAIL: could not open file "/var/lib/postgres/data/pg_clog/0003": No
> such file or directory
> I tried restoring a backup of the data directory that did contain the
> 0003 file, but that didn't work either.
Define "didn't work" ... what happened, exactly, when you tried it?
People have occasionally dealt with this sort of scenario by creating
dummy clog segment files by hand, and I'd think that restoring the
segment file from a backup would do as well or better.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-09-01 16:05:32 | Re: Order By for aggregate functions (Simulating Group_concat) |
Previous Message | Scott Marlowe | 2005-09-01 15:51:55 | Re: Don't understand transaction error |