From: | Carol Walter <walterc(at)indiana(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: error |
Date: | 2008-09-24 03:39:11 |
Message-ID: | 54E013EF-787E-4FE0-941C-80A410AA7878@indiana.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I've had no system crashes. I'm embarrassed to say that I may have
inadvertently caused this problem when I was do "house cleaning" a
couple of weeks ago.
When I upgrade, how to I get my data when pg_dumpall won't run?
Carol
On Sep 23, 2008, at 10:42 PM, Tom Lane wrote:
> Carol Walter <walterc(at)indiana(dot)edu> writes:
>> What would cause this error?
>
>> ERROR: could not access status of transaction 10274530
>> DETAIL: Could not open file "pg_clog/0009": No such file or
>> directory.
>
> We've seen that caused by bugs that made Postgres throw away clog
> files
> too soon; but as far as I know those bugs were all squashed in recent
> releases. What PG version is this? What files *are* present in
> pg_clog, and what are their mod times? Have you had any system
> crashes
> recently?
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tena Sakai | 2008-09-24 04:16:27 | Re: Missing pg_clog files |
Previous Message | Carol Walter | 2008-09-24 03:35:42 | Re: Missing pg_clog files |