On Mon, Mar 14, 2011 at 05:05:39PM +0100, Stefan Sperling wrote: > The concern seems to be that invoking a notification callback could > attempt to modify DB state, correct? Which would deadlock if you invoke > the callback after starting a transaction to tweak changelist information > but before this transaction has been committed (i.e. the write lock has > been released)?
Of course, the same problem happens when the notification callback does a *read* operation on the DB (because writers block readers -- somehow this restriction is kinda hard to getting used to...)
