Issue 20 - mysql-master-master - Maybe obtain a global read lock before setting read_only=1

Issue 20:	Maybe obtain a global read lock before setting read_only=1	‹ Prev 3 of 22 Next ›
	1 person starred this issue and may be notified of changes.	Back to list

Status:	New
Owner:	m...@pascalhofmann.de
Type-Defect
Priority-Low
Release-1.0

Reported by m...@pascalhofmann.de, Nov 02, 2008

Maybe mysql_deny_write should obtain a global read lock before setting
read_only=1

FLUSH TABLES WITH READ LOCK;
SET GLOBAL read_only = ON;
UNLOCK TABLES;

See http://bugs.mysql.com/22009 and http://bugs.mysql.com/bug.php?id=11733

Comment 1 by m...@pascalhofmann.de, Nov 04, 2008

If we implement this, the agent user needs RELOAD privileges.

Comment 2 by baron.schwartz, Jan 14, 2009

(No comment was entered for this change.)

Labels: Release-1.0