Morris Jobke 138219d74a Run cleanup of expired DB file locks to background job ... * fixes #22819 The old way fired a DELETE statement on each destruction of the DBLockingProvider. Which could cause a lot of queries. It's enough to run this every 5 minutes in a background job, which in the end could result in file locks that exists 5 minutes longer - in the worst case and for not properly released locks. This makes the DB based locking a lot more performant and could result in a similar performance to the Redis based locking provider.		2016-03-04 15:52:23 +01:00
..
abstractlockingprovider.php	Happy new year!	2016-01-12 15:02:18 +01:00
dblockingprovider.php	Run cleanup of expired DB file locks to background job	2016-03-04 15:52:23 +01:00
memcachelockingprovider.php	Happy new year!	2016-01-12 15:02:18 +01:00
nooplockingprovider.php	Happy new year!	2016-01-12 15:02:18 +01:00