diff options
| author | aelkin/elkin@dsl-hkigw8-fe00f800-98.dhcp.inet.fi <> | 2006-09-12 00:19:05 +0300 |
|---|---|---|
| committer | aelkin/elkin@dsl-hkigw8-fe00f800-98.dhcp.inet.fi <> | 2006-09-12 00:19:05 +0300 |
| commit | b4b06d7a67ca31c2d52a5e60fe900be654947948 (patch) | |
| tree | 343ad343539b5c63d01efe4105869aa5a2949fa8 /sql/sql_repl.cc | |
| parent | fb6151d0bccc25d4090a2348e6b3be316b70da4c (diff) | |
| download | mariadb-git-b4b06d7a67ca31c2d52a5e60fe900be654947948.tar.gz | |
BUG#19402 SQL close to the size of the max_allowed_packet fails on the slave
A communication packet can also be a binlog event sent from the master to the slave.
To be sent by master dump and accepted by slave io thread both have to have
the value of max_allowed_packet bigger than one that client connection had.
In the patch there is the MAX possible replicatio header size estimation for events
in binlog that embedded user query. Only these events of query_log_event type, i.e
just plain queries, require attention.
Diffstat (limited to 'sql/sql_repl.cc')
| -rw-r--r-- | sql/sql_repl.cc | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/sql/sql_repl.cc b/sql/sql_repl.cc index 963c4ccf5a6..90aabac115e 100644 --- a/sql/sql_repl.cc +++ b/sql/sql_repl.cc @@ -420,6 +420,8 @@ impossible position"; goto err; } packet->set("\0", 1, &my_charset_bin); + /* dump thread the whole header size of query_log_event */ + thd->variables.max_allowed_packet+= MAX_LOG_EVENT_HEADER; while (!net->error && net->vio != 0 && !thd->killed) { |