From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Bill Moseley <moseley(at)hank(dot)org> |
Subject: | Re: Tracking down a deadlock |
Date: | 2009-05-04 12:58:44 |
Message-ID: | 20090504085844.14eea88d.wmoran@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In response to Bill Moran <wmoran(at)potentialtech(dot)com>:
> In response to Bill Moseley <moseley(at)hank(dot)org>:
>
> > On Sun, May 03, 2009 at 09:08:29PM -0400, Tom Lane wrote:
> > > > There are no other updates to that account table in the transaction, so I'm
> > > > confused how that is causing a deadlock.
> > >
> > > Is there more than one row with the target id?
> >
> > No. It's a single SERIAL primary key.
>
> I've never gone to the trouble to isolate this to a reproducible test
...
> In any event, I hope that information is helpful to you.
And on second read ... that has absolutely nothing to do with your
scenario ...
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-05-04 13:03:33 | Re: diff-/patch-functionality for text-type data inside PostgreSQL |
Previous Message | Bill Moran | 2009-05-04 12:51:56 | Re: Tracking down a deadlock |