List:Commits« Previous MessageNext Message »
From:Lars Thalmann Date:December 14 2009 11:47am
Subject:Re: bzr commit into mysql-5.1-bugteam branch (alfranio.correia:3217)
Bug#46364
View as plain text  
On Mon, Nov 23, 2009 at 10:52:57PM +0000, Alfranio Correia wrote:
> === modified file 'sql/mysqld.cc'
> --- a/sql/mysqld.cc	2009-11-20 12:09:50 +0000
> +++ b/sql/mysqld.cc	2009-11-23 22:52:51 +0000
> @@ -5727,7 +5727,8 @@ enum options_mysqld
>    OPT_SLAVE_EXEC_MODE,
>    OPT_GENERAL_LOG_FILE,
>    OPT_SLOW_QUERY_LOG_FILE,
> -  OPT_IGNORE_BUILTIN_INNODB
> +  OPT_IGNORE_BUILTIN_INNODB,
> +  OPT_BINLOG_DIRECT_NON_TRANS_UPDATE
>  };
>  
>  
> @@ -7066,6 +7067,10 @@ The minimum value for this variable is 4
>     (uchar**) &max_system_variables.net_wait_timeout, 0, GET_ULONG,
>     REQUIRED_ARG, NET_WAIT_TIMEOUT, 1, IF_WIN(INT_MAX32/1000, LONG_TIMEOUT),
>     0, 1, 0},
> +  {"binlog-direct-non-transactional-updates", OPT_BINLOG_DIRECT_NON_TRANS_UPDATE,
> +   "Makes updates to non-transactional engines in the statement format to be written
> directly to binary log. Before using this option make sure that there is no possible
> causality among the statements, otherwise, slaves may diverge from the master.",
> +   (uchar**) &global_system_variables.binlog_direct_non_trans_update, (uchar**)
> &max_system_variables.binlog_direct_non_trans_update, 0, GET_BOOL, NO_ARG, 0,
> +    0, 0, 0, 0, 0},
>    {0, 0, 0, 0, 0, 0, GET_NO_ARG, NO_ARG, 0, 0, 0, 0, 0, 0}
>  };

"no possible causality among the statements" - sounds strange to me.

Paul, is this correct English/documentation?

/L


-- 
Dr Lars Thalmann, Development Manager, Replication & Backup, www.mysql.com
Thread
bzr commit into mysql-5.1-bugteam branch (alfranio.correia:3217)Bug#46364Alfranio Correia23 Nov
  • Re: bzr commit into mysql-5.1-bugteam branch (alfranio.correia:3217)Bug#46364Lars Thalmann14 Dec