pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_clog error after crash
4+ messages / 3 participants
[nested] [flat]
* pg_clog error after crash
@ 2004-06-30 15:59 Sandro Dentella <sandro@e-den.it>
0 siblings, 2 replies; 4+ messages in thread
From: Sandro Dentella @ 2004-06-30 15:59 UTC (permalink / raw)
To: pgsql-admin
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
when trying to acces a db.
I'm really clueless as I didn't find anything usefull with google to fix
it. The db is very little, and I'm the only one that writes on it, so I know
there shouldn't be real problems ignoring the transaction, but I don't know
what to say postgreSQL to ingore it.
Should I recreate an empty file?
TYA
sandro
*:-)
PS: can you cc to me too, I'm not on this list. Thanks
--
Sandro Dentella *:-)
e-mail: sandro@e-den.it
http://www.tksql.org TkSQL Home page - My GPL work
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_clog error after crash
@ 2004-07-01 22:05 Tom Lane <tgl@sss.pgh.pa.us>
parent: Sandro Dentella <sandro@e-den.it>
1 sibling, 1 reply; 4+ messages in thread
From: Tom Lane @ 2004-07-01 22:05 UTC (permalink / raw)
To: Sandro Dentella <sandro@e-den.it>; +Cc: pgsql-admin
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...)
You may have little choice but to restore from your last backup.
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_clog error after crash
@ 2004-07-01 22:14 Scott Marlowe <smarlowe@qwest.net>
parent: Sandro Dentella <sandro@e-den.it>
1 sibling, 0 replies; 4+ messages in thread
From: Scott Marlowe @ 2004-07-01 22:14 UTC (permalink / raw)
To: Sandro Dentella <sandro@e-den.it>; +Cc: pgsql-admin
On Wed, 2004-06-30 at 09:59, Sandro Dentella wrote:
> 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
>
>
> when trying to acces a db.
>
> I'm really clueless as I didn't find anything usefull with google to fix
> it. The db is very little, and I'm the only one that writes on it, so I know
> there shouldn't be real problems ignoring the transaction, but I don't know
> what to say postgreSQL to ingore it.
>
> Should I recreate an empty file?
What version are you running?
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_clog error after crash
@ 2004-07-01 23:39 Sandro Dentella <sandro@e-den.it>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 4+ messages in thread
From: Sandro Dentella @ 2004-07-01 23:39 UTC (permalink / raw)
To: Sandro Dentella <sandro@e-den.it>; pgsql-admin
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
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2004-07-01 23:39 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-06-30 15:59 pg_clog error after crash Sandro Dentella <sandro@e-den.it>
2004-07-01 22:05 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-07-01 23:39 ` Sandro Dentella <sandro@e-den.it>
2004-07-01 22:14 ` Scott Marlowe <smarlowe@qwest.net>
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