"Heikki Linnakangas" <[EMAIL PROTECTED]> writes: > I'm not sure what to do about this. We could change the order the > triggers are fired to breadth-first. If all the setnull triggers were > executed first, there would be no problem. But that seems like a pretty > big change, and I'm afraid it might have other unintended consequences.
We could also check the queued triggers to see if there really is a trigger which will be invalidated by the second update and therefore needs to be rechecked (or even just change the tid of the existing queued check). I don't know what it would take to make that efficient though. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
