| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mark Liberman" <mliberman(at)mixedsignals(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Corrupted DB - Help |
| Date: | 2006-07-28 03:39:47 |
| Message-ID: | 15900.1154057987@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Mark Liberman" <mliberman(at)mixedsignals(dot)com> writes:
> <4983:2006-07-27 18:04:26 PDT>PANIC: could not open relation =
> 1663/128873/129201: No such file or directory
> <4981:2006-07-27 18:04:26 PDT>LOG: startup process (PID 4983) was =
> terminated by signal 6
That's really strange ... it's not supposed to be possible to get that
error during xlog replay, because XLogOpenRelation is always willing to
create a file that doesn't exist. Can you get a stack trace from the
crash dump this presumably left behind?
If you're just in a panic to get the DB up again, I'd try creating the
mentioned file ("touch $PGDATA/base/128873/129201") and see if it'll
start. But if you have some time to investigate, it'd be good to try
to determine exactly what went wrong here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel CAUNE | 2006-07-28 03:53:22 | Re: [SQL] PostgreSQL server terminated by signal 11 |
| Previous Message | Mark Liberman | 2006-07-28 01:55:28 | Corrupted DB - Help |