Re: NT + deadlock intended behaviour ? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: NT + deadlock intended behaviour ?
Date
Msg-id 20040718171740.GC2372@dcc.uchile.cl
Whole thread Raw
In response to Re: NT + deadlock intended behaviour ?  (Gaetano Mendola <mendola@bigfoot.com>)
List pgsql-hackers
On Sun, Jul 18, 2004 at 11:00:25AM +0200, Gaetano Mendola wrote:
> Alvaro Herrera wrote:

> >If I abort only the innermost transaction on session 2, the application
> >writer can have a retry loop on it, so it will issue the "begin" again
> >and the same update.  Since session 1 is still locked, session 2 will
> >see a deadlock again.  The user could cope with detecting a deadlock
> >condition and do something else, but frankly I don't think we can leave
> >this as is.
> 
> I understand your point but I don't like the solution of invalidate the 
> whole transaction tree ( I don't know the good one ).

FYI, this is all moot with savepoints because we don't allow to create a
savepoint in an aborted transaction block.

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"El sudor es la mejor cura para un pensamiento enfermo" (Bardia)



pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: pg_dump bug fixing
Next
From: Alvaro Herrera
Date:
Subject: Re: NT + deadlock intended behaviour ?