From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Liberman <mliberman@mixedsignals.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Corrupted DB - Help
Date: Thu, 27 Jul 2006 23:39:47 -0400
Message-ID: <15900.1154057987@sss.pgh.pa.us> (raw)
In-Reply-To: <9D938282F8C6EE43B748B910386DE93E0138B4BE@srvgpimail1.GPI.local>
References: <9D938282F8C6EE43B748B910386DE93E0138B4BE@srvgpimail1.GPI.local>
"Mark Liberman" <mliberman@mixedsignals.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
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: tgl@sss.pgh.pa.us, mliberman@mixedsignals.com
Subject: Re: Corrupted DB - Help
In-Reply-To: <15900.1154057987@sss.pgh.pa.us>
References: <9D938282F8C6EE43B748B910386DE93E0138B4BE@srvgpimail1.GPI.local> <15900.1154057987@sss.pgh.pa.us>
* 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