From d149fc30d0e48bf1d01e0a962fa74a228c63bb75 Mon Sep 17 00:00:00 2001 From: unknown Date: Tue, 14 Nov 2006 12:48:17 +0200 Subject: bug#19402 SQL close to the size of the max_allowed_packet fails on the slave ver 5.0 and 5.1 refinement. adding to the MAX_SIZE_LOG_EVENT_STATUS estimation status vars and EXECUTE_LOAD_QUERY_EXTRA_HEADER_LEN sql/log_event.cc: assertion on size of status vars sql/log_event.h: MAX_SIZE_LOG_EVENT_STATUS as the max bytes of contribution of status vars into repl message; MAX_SIZE_LOG_EVENT_STATUS is getting more wrt to 4.1 version. --- sql/log_event.cc | 1 + 1 file changed, 1 insertion(+) (limited to 'sql/log_event.cc') diff --git a/sql/log_event.cc b/sql/log_event.cc index 271658d8054..2ad52945c9e 100644 --- a/sql/log_event.cc +++ b/sql/log_event.cc @@ -1212,6 +1212,7 @@ bool Query_log_event::write(IO_CACHE* file) /* Store length of status variables */ status_vars_len= (uint) (start-start_of_status); + DBUG_ASSERT(status_vars_len <= MAX_SIZE_LOG_EVENT_STATUS); int2store(buf + Q_STATUS_VARS_LEN_OFFSET, status_vars_len); /* -- cgit v1.2.1