[MDEV-20591] Wrong Number of rows in mysqlbinlog output. Created: 2019-09-14  Updated: 2019-10-09  Resolved: 2019-10-08

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.3, 10.4, 10.5
Fix Version/s: 10.3.19, 10.4.9

Type: Bug Priority: Minor
Reporter: Sachin Setiya (Inactive) Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: None
Environment:

All

Issue Links:
Problem/Incident
causes MDEV-20582 Asan failure in table_def::calc_field... Closed

 Description   

Following test case different way It print different no of rows the actual rows.

--source include/have_binlog_format_row.inc
 
 
 
--let $MYSQLD_DATADIR= `select @@datadir`
 
--let $binlog_file= $MYSQLD_DATADIR/master-bin.000001
 
--let $output_file= $MYSQLTEST_VARDIR/tmp/mysqlbinlog.output
 
 
 
CREATE TABLE t1(c_char_utf8 CHAR(10) ,
 
  c_varchar_utf8 char(10) ,
 
  c_text_utf8 blob );
 
 
 
INSERT into t1   values("B", "B", REPEAT("!", 20000));
 
 
 
--exec $MYSQL_BINLOG -F $binlog_file > $output_file
 
--remove_file $output_file
 
drop table t1;

Output

ISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEh
 
ISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEh
 
ISEhISEhISEhISEhISEhISEhISEhISEhISEhISEpm2rJ
 
'/*!*/;
 
# Number of rows: 313

So instead of ! we use # in repeat

INSERT into t1   values("B", "B", REPEAT("#", 20000));


IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
 
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMLiFNr
 
'/*!*/;
 
# Number of rows: 3670


INSERT into t1   values("B", "B", REPEAT("#", 2000));


IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
 
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMLiFNr
 
'/*!*/;
 
# Number of rows: 2



 Comments   
Comment by Sachin Setiya (Inactive) [ 2019-09-14 ]

http://lists.askmonty.org/pipermail/commits/2019-September/013988.html

buildbot branch bb-10.3-sachin

Comment by Michael Widenius [ 2019-09-22 ]

ok to push

Generated at Thu Feb 08 09:00:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.