| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sandro Dentella <sandro(at)e-den(dot)it> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_clog error after crash |
| Date: | 2004-07-01 22:05:17 |
| Message-ID: | 6331.1088719517@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Sandro Dentella <sandro(at)e-den(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2004-07-01 22:14:09 | Re: pg_clog error after crash |
| Previous Message | Tom Lane | 2004-07-01 21:50:21 | Re: Problems with select version |