Re: pgdump error "Could not open file pg_clog/0B8E: No such file or directory" - Mailing list pgsql-general

From Merlin Moncure
Subject Re: pgdump error "Could not open file pg_clog/0B8E: No such file or directory"
Date
Msg-id CAHyXU0zcZAmRQuEMEx=ARB=RojtCUce=xPbmnYJZbQ-418W9dg@mail.gmail.com
Whole thread Raw
In response to Re: pgdump error "Could not open file pg_clog/0B8E: No such file or directory"  (jesse.waters@gmail.com)
List pgsql-general
On Thu, Apr 25, 2013 at 5:13 AM,  <jesse.waters@gmail.com> wrote:
> Sorry for the delay.
> No it does not exist.
>
> ls -l /var/lib/pgsql/data/pg_clog/0B8E
> ls: /var/lib/pgsql/data/pg_clog/0B8E: No such file or directory
>
> Have 92 files in directory which are all 262144 in size.

This file records if transactions committed or were aborted.  If it is
missing, this signifies corruption.  You can force a file in, but
chances are things will not be as they should be.   When is your last
good backup?  If it's fairly recent you can force a file with all
'commit' values and compare vs backup and attempt to repair any damage
if things don't look too bad I'd start with 'reindex' and/or full
database restore assuming you could pull a dump).  Take a full
filesystem backup before doing anything though.

merlin


pgsql-general by date:

Previous
From: Lonni J Friedman
Date:
Subject: Re: Replication terminated due to PANIC
Next
From: Karsten Hilbert
Date:
Subject: regex help wanted