Tracking down deadlocks - Mailing list pgsql-general

From Ben
Subject Tracking down deadlocks
Date
Msg-id 880475FE-BFAA-11D8-88F9-000A95BF2A8C@silentmedia.com
Whole thread Raw
Responses Re: Tracking down deadlocks  (Csaba Nagy <nagy@ecircle-ag.com>)
Re: Tracking down deadlocks  (Ben <bench@silentmedia.com>)
Re: Tracking down deadlocks  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.


pgsql-general by date:

Previous
From: John Sidney-Woollett
Date:
Subject: Re: tablespaces and schemas
Next
From: Csaba Nagy
Date:
Subject: Re: Tracking down deadlocks