pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Sandro Dentella <sandro@e-den.it>
To: Sandro Dentella <sandro@e-den.it>
To: pgsql-admin@postgresql.org
Subject: Re: pg_clog error after crash
Date: Fri, 2 Jul 2004 01:39:02 +0200
Message-ID: <20040701233902.GA3829@bluff> (raw)
In-Reply-To: <6331.1088719517@sss.pgh.pa.us>
References: <20040630155919.GA3174@bluff>
	<6331.1088719517@sss.pgh.pa.us>

On Thu, Jul 01, 2004 at 06:05:17PM -0400, Tom Lane wrote:
> Sandro Dentella <sandro@e-den.it> writes:
> > After a crash of the (frozen) system, postgreSQL issues a message:
> > 2004-06-30 17:51:39 [3165] LOG:  connection authorized: user=sandro database=sia
> > 2004-06-30 17:51:39 [3165] ERROR:  could not access status of transaction 4011600129
> > DETAIL:  could not open file "/var/lib/postgres/data/pg_clog/0EF1": No such file or directory
> 
> It looks like you've got data corruption in one of the system catalogs
> that is accessed during backend startup.  This is not good :-(.
> Do you get the same no matter which of the databases in your
> installation you try to connect to?  (Not that it will matter much,
> if all your important data is in this database...)

No, really I could connect to the database that had probles! I could "COPY
table TO 'file' for *each* table of the problematic db. The problem arouse
when trying to pg_dump it or when trying to access it via libpgtcl (I use
TkSQL as you can guess from the footer ;-).


After COPYing all tables I created the file that was missing, filled with
zeros according to a mail I found of a "similar" problem. PostgreSQL
complain disappeard. As far as I can say no data seems to be lost. 

I'm using PostgreSQL 7.4.2 last release of Debian Sarge.

Thanks for your time.
sandro
*:-)



-- 
Sandro Dentella  *:-)
e-mail: sandro@e-den.it 
http://www.tksql.org                    TkSQL Home page - My GPL work



view thread (4+ messages)

Message-ID: <20040701233902.GA3829@bluff>
Permalink:  ../20040701233902.GA3829@bluff/
Also on:    postgresql.org/message-id/20040701233902.GA3829@bluff

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: sandro@e-den.it
  Subject: Re: pg_clog error after crash
  In-Reply-To: <20040701233902.GA3829@bluff>
  References: <20040630155919.GA3174@bluff> <6331.1088719517@sss.pgh.pa.us> <20040701233902.GA3829@bluff>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox