MySQL Bugs: #31520: "Exclusive" transaction execution mode

Bug #31520	"Exclusive" transaction execution mode
Submitted:	10 Oct 2007 22:11	Modified:	10 Oct 2007 22:13
Reporter:	Vitaliy Filippov	Email Updates:
Status:	Open	Impact on me:	None
Category:	MySQL Server	Severity:	S4 (Feature request)
Version:	5.1 ?	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Hello!

"Exclusive" transaction execution is as follows:

0) some thread calls START TRANSACTION EXCLUSIVE
1) database is switched into the state when it does not accept new transactions, but already running ones are not interrupted at all
2) the calling thread blocks and waits for all other transactions to COMMIT or ROLLBACK
3) while database is in the state described above, all other threads block at the START TRANSACTION statement and wait for "exclusive" transaction to COMMIT or ROLLBACK
4) after "exclusive" transaction COMMIT or ROLLBACK, database is switched back into the normal state.

Isn't it already implemented?

How to repeat:
Feature-request.

* database is switched into the state in which it does not accept new transactions, but already running ones are not interrupted at all