Re: Tracking down deadlocks

See my previous post, there I mentioned updates, but it applies to
inserts too.


On Wed, 2004-06-16 at 17:53, Ben wrote:
> I hate to reply so quickly to my own post, but I found out how to turn
> on the current_query (I somehow missed that config file line - doh!).
>
> It turns out that my insert statements are blocking each other. (An
> insert in one thread blocks the same insert with different values in
> another thread.) That's curious to me, as I thought that inserts were
> atomic? It doesn't happen for all inserts, just some of them, and the
> problem gets worse as the threads increase in number.
>
> I compiled my client libs with thread safety, and am running on linux.
>
> On Jun 16, 2004, at 8:33 AM, Ben wrote:
>
> > 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.
> >
> >
> > ---------------------------(end of
> > broadcast)---------------------------
> > TIP 5: Have you checked our extensive FAQ?
> >
> >               http://www.postgresql.org/docs/faqs/FAQ.html
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faqs/FAQ.html