In response to "antiochus antiochus" <[EMAIL PROTECTED]>:
> On Thu, May 22, 2008 at 4:20 PM, Bill Moran <[EMAIL PROTECTED]>
> wrote:
> >
> > In response to "antiochus antiochus" <[EMAIL PROTECTED]>:
> > >
> > > On Thu, May 22, 2008 at 2:57 PM, Bill Moran <
> > [EMAIL PROTECTED]>
> > > wrote:
> > >
Hi All,
I have a deadlock situation, two transactions waiting on each other to
complete. Based on the details below, does anyone have recommendations for
me. Thanks.
Regards,
A.
I am using:
rpm -qa|grep postgres
compat-postgresql-libs-4-2PGDG.rhel5_x86_64
postgresql-server-8.2.6-1PGDG.rhel5
po
On Thu, May 22, 2008 at 4:20 PM, Bill Moran <[EMAIL PROTECTED]>
wrote:
>
> Please don't top-post. I've attempted to reconstruct the conversation
> flow.
>
> In response to "antiochus antiochus" <[EMAIL PROTECTED]>:
> >
> > On Thu, May 22, 2008 at 2:57 PM, Bill Moran <
> [EMAIL PROTECTED]>
> > wro
Please don't top-post. I've attempted to reconstruct the conversation
flow.
In response to "antiochus antiochus" <[EMAIL PROTECTED]>:
>
> On Thu, May 22, 2008 at 2:57 PM, Bill Moran <[EMAIL PROTECTED]>
> wrote:
>
> > In response to "antiochus antiochus" <[EMAIL PROTECTED]>:
> > >
> > > I have
Thanks for your responses, I appreciate the help.
I gather from this that 2 transactions concurrently running the exact same:
update table tt where ...
could end up in deadlock because it is not garanteed row-level locks are
taken in a consistent order in an update.
One possibility might th
In response to "antiochus antiochus" <[EMAIL PROTECTED]>:
>
> I have a deadlock situation, two transactions waiting on each other to
> complete. Based on the details below, would anyone have recommendations for
> me, please?
I have a theory on deadlocks, and that theory is that it's damn near
imp
Hi All,
I have a deadlock situation, two transactions waiting on each other to
complete. Based on the details below, would anyone have recommendations for
me, please?
Regards,
A.
I am using:
rpm -qa|grep postgres
compat-postgresql-libs-4-2PGDG.rhel5_x86_64
postgresql-server-8.2.6-1PGDG.rhel5
p