From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jonathan Parkin <jonathan(dot)parkin(at)legendplc(dot)com> |
Cc: | PostgreSQL Admin Mailing List <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL 7.4.10 hanging on delete |
Date: | 2005-12-20 16:37:14 |
Message-ID: | 300.1135096634@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Jonathan Parkin <jonathan(dot)parkin(at)legendplc(dot)com> writes:
> I have a reasonably large, live, system-critical database. A perl
> script on another machine connects and issues a sequence of commands in
> a transaction, the last of which is a delete. The delete never returns
> a response, and the connection never times out. The postgres process
> handling the delete is in a scheduled state, but stracing it produces no
> output at all.
Sounds like it's stuck in a tight loop. Can you attach to the postgres
process with gdb and get a stack trace to find out where the loop is?
If this is a specific row causing the issue, then I'd wonder about
data corruption of some sort. It might be worth looking at the
table with pg_filedump (from http://sources.redhat.com/rhdb/)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-12-20 16:59:49 | Re: WITH SYSID feature dropped |
Previous Message | Donald Fraser | 2005-12-20 16:34:43 | Re: WITH SYSID feature dropped |