From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christian Sengstock <csengstock@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: problem with dead 'drop table' process
Date: Fri, 20 Jan 2006 10:48:56 -0500
Message-ID: <17591.1137772136@sss.pgh.pa.us> (raw)
In-Reply-To: <febbf1590601200627w7d0a7406v@mail.gmail.com>
References: <febbf1590601200627w7d0a7406v@mail.gmail.com>
Christian Sengstock <csengstock@gmail.com> writes:
> to save the database on a filesystem basis i stopped the postgres server and
> tried to tar the entire pgdata directory. this process stopped with a
> "segmentation fault" during the tar process.
So there's something wrong beyond just postgres ...
> the server is running, and i can connect with another psql client, but the
> drop table process is still present. ps aux shows
> postgres 5548 0.0 0.8 16420 4548 ? D 07:58 0:00 postgres: postgres
> wlan [local] DROP TABLE
> i cannot kill it with kill -9, and also i'm not sure if i should. maybe the
> database is not running after it at all?
A process stuck in an unkillable disk wait is a pretty common symptom of
low-level problems. There might be a disk hardware issue --- have you
looked into the kernel message log on the machine?
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, csengstock@gmail.com
Subject: Re: problem with dead 'drop table' process
In-Reply-To: <17591.1137772136@sss.pgh.pa.us>
References: <febbf1590601200627w7d0a7406v@mail.gmail.com> <17591.1137772136@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