Closed (duplicate)
Project:
Rules
Version:
7.x-2.x-dev
Component:
Rules Core
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Jan 2013 at 20:04 UTC
Updated:
1 Apr 2014 at 21:55 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
bdragon commentedNah, the variable is good for bootstrap performance. The *problem* is the excessive mucking about with it.
Seems to me that not deleting it at the drop of a hat and only updating it on an as-needed basis will prevent most of the pain here.
Comment #3
bdragon commented#1: 1903498-less-aggressive-variable.patch queued for re-testing.
Comment #5
bdragon commentedYa know, I think in the end this was probably just another case of #937284: DEADLOCK errors on MergeQuery INSERT due to InnoDB gap locking when condition in SELECT ... FOR UPDATE results in 0 rows.
It also appears that this bit of code doesn't exist anymore either.