Tracking down deadlocks

From: Ben <bench(at)silentmedia(dot)com>
To: pgsql-general(at)postgreSQL(dot)org
Subject: Tracking down deadlocks
Date: 2004-06-16 15:33:35
Message-ID: 880475FE-BFAA-11D8-88F9-000A95BF2A8C@silentmedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'm doing a bunch of data mining against a postgres database and have
run into an interesting problem with deadlocks. The problem is,
postgres is detecting them and then wacking the offending process, and
I can't figure out what's causing them. I have a ton of select queries
(but none for update), and then a single query to insert into a table.
Nothing selects from that table. So where could the deadlock be?

pg_stat_activity has a column named current_query, which would seem
useful in tracking this down, but it's not being populated.

Oh, I'm running 7.4.2.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ben 2004-06-16 15:53:54 Re: Tracking down deadlocks
Previous Message John Sidney-Woollett 2004-06-16 15:28:21 Re: tablespaces and schemas