From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Louis-David Mitterrand <vindex(at)apartia(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump crashes the backend |
Date: | 2003-03-14 17:02:22 |
Message-ID: | 21862.1047661342@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Louis-David Mitterrand <vindex(at)apartia(dot)org> writes:
> [7.3.2 on debian unstable]
> We recently had an unclean server shutdown and now a pg_dump command
> crashes the backend:
> pg_dump: PANIC: open of /var/lib/postgres/data/pg_clog/0003 failed: No
> such file or directory
> Should we restore from a known good dump after an initdb?
If you have a good dump then initdb and reload seems like the best
answer. Before you do, though, I'd be interested to see an ls -l of the
pg_clog directory (I'm interested in the names/sizes/mod times of the
files therein). Can you give any more details about the server
shutdown?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2003-03-14 17:07:30 | Re: Roadmap for FE/BE protocol redesign |
Previous Message | scott.marlowe | 2003-03-14 16:51:16 | Re: SQL99 ARRAY support proposal |