[MDEV-4319] mysqlbinlog output ambiguous escaping Created: 2013-03-23  Updated: 2013-03-25  Resolved: 2013-03-25

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.1, 5.5.30
Fix Version/s: 10.0.2, 5.5.31

Type: Bug Priority: Minor
Reporter: Ian Good Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: upstream
Environment:

N/A


 Description   

With row-level binlogs enabled, the following command can produce ambiguously escaped output:

$ mysqlbinlog -v --base64-output=DECODE-ROWS master-bin.000001

To reproduce the issue, I can run the following SQL command (table schema not relevant):

INSERT INTO `mytest`.`tbl` VALUES ('\n test \\x0a');

This results in the mysqlbinlog output:

### INSERT INTO `mytest`.`tbl`
 
### SET
 
###   @1='\x0a test \x0a'

As you can see, it is impossible to differentiate the output of a new-line character (0x0A) from the un-escaped string "\x0a".

 Comments   
Comment by Elena Stepanova [ 2013-03-24 ]

The effect is reproducible on MySQL as well (at least 5.6, but I suppose on previous versions too).
However, I don't see any problems with replication as such, the events seem to be replicated correctly, so it's just visual representation that's ambiguous.
You might want to file a bug report or feature request at bugs.mysql.com.

Comment by Michael Widenius [ 2013-03-25 ]

Pushed into 5.5 tree

Generated at Thu Feb 08 06:55:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.