It may not have an impact on you, but be aware of this severe (imho) bug that caused read_pnly to be ignored regardless of running transactions in version 5.5.8. See bug#58669 and others. We upgraded to 5.5.17 where the bug was fixed. David. ________________________________ From: Viacheslav Biriukov [mailto:v.v.biriu...@gmail.com] Sent: Monday, November 28, 2011 9:20 AM To: David Lerer Cc: mysql@lists.mysql.com Subject: Re: Read_only and InnoDB transactions
MySQL Community Server 5.1.59 on the Centos 5.7 2011/11/28 David Lerer <dle...@us.univision.com<mailto:dle...@us.univision.com>> What version do you use? David. -----Original Message----- From: Viacheslav Biriukov [mailto:v.v.biriu...@gmail.com<mailto:v.v.biriu...@gmail.com>] Sent: Monday, November 28, 2011 7:09 AM To: mysql@lists.mysql.com<mailto:mysql@lists.mysql.com> Subject: Read_only and InnoDB transactions Hi all. >From the Mysql Documentation: If you attempt to enable read_only while other clients hold explicit table > locks or have pending transactions, the attempt blocks until the locks are > released and the transactions end. While the attempt to enable read_only is > pending, requests by other clients for table locks or to begin transactions > also block until read_only has been set. But when I try to set "SET GLOBAL read_only = ON;" It brake running transaction. -- Viacheslav Biriukov BR The information contained in this e-mail and any attached documents may be privileged, confidential and protected from disclosure. If you are not the intended recipient you may not read, copy, distribute or use this information. If you have received this communication in error, please notify the sender immediately by replying to this message and then delete it from your system. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql -- Viacheslav Biriukov BR http://biriukov.com The information contained in this e-mail and any attached documents may be privileged, confidential and protected from disclosure. If you are not the intended recipient you may not read, copy, distribute or use this information. If you have received this communication in error, please notify the sender immediately by replying to this message and then delete it from your system.
