Roundup Tracker - Issues

Message4726

Author rouilj
Recipients ThomasAH, ber, ezio.melotti, rouilj, schlatterbeck
Date 2013-01-05.02:00:43
Message-id <201301050200.r0520cMK003240@mx1.cs.umb.edu>
In-reply-to Your message of "Sat, 05 Jan 2013 01:43:23 GMT." <1357350203.18.0.396444462484.issue2550731@psf.upfronthosting.co.za> <1357350203.18.0.396444462484.issue2550731@psf.upfronthosting.co.za>
In message <1357350203.18.0.396444462484.issue2550731@psf.upfronthosting.co.za>
 <1357350203.18.0.396444462484.issue2550731@psf.upfronthosting.co.za>,
Bernhard Reiter writes:
>Looks like this needs some better locking during the transaction:
>Once you read with the intention to update, you need to block other processes 
>with the same goal.

This explains the observation that the problem doesn't happen with
sqlite or bsddb back ends right? Their nature serializes the database
access, so there is an implicit lock that prevents multiple processes
from opening the database in update mode at the same time.

-- rouilj
History
Date User Action Args
2013-01-05 02:00:44rouiljsetrecipients: + rouilj, schlatterbeck, ber, ThomasAH, ezio.melotti
2013-01-05 02:00:44rouiljlinkissue2550731 messages
2013-01-05 02:00:43rouiljcreate