mysqlbinlog output ambiguous escaping

Description

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

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

This results in the mysqlbinlog output:

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

Environment

N/A

Status

Assignee

Michael Widenius

Reporter

Ian Good

Labels

External issue ID

None

External issue ID

None

Fix versions

Affects versions

Priority

Minor
Configure