On Thu, Jun 23, 2011 at 1:09 AM, Michael Widenius wrote:
>
> Hi!
>
> > "MARK" == MARK CALLAGHAN writes:
>
MARK> Per the code in set_var.cc:
>
>
> MARK> /*
>
> MARK> Perform a 'FLUSH TABLES WITH READ LOCK'.
>
> MARK> This is a 3 step process:
>
> MARK> - [1] lock_global_read_l
---
WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...: Multi-source replication
CREATION DATE..: Thu, 23 Jun 2011, 12:50
SUPERVISOR.:
IMPLEMENTOR
Hi!
> "MARK" == MARK CALLAGHAN writes:
MARK> It can be dangerous for us to run "set read_only" on a production server
MARK> because it can block in close_cached_tables. More details about the pain
MARK> this caused at a previous job are at:
MARK>
http://mysqlha.blogspot.com/2008/07/what-e
3 matches
Mail list logo