Bug #114776 mysqlbinlog cannot print geometry correct

• Submitted: 25 Apr 2024 7:00
• Modified: 25 Apr 2024 7:51
• Reporter: phoenix Zhang (OCA)
• Status: Duplicate
• Category: MySQL Server: Replication
• Severity: S3 (Non-critical)
• Version: 8.0.32
• OS: Any
• CPU Architecture: Any

[25 Apr 2024 7:00] phoenix Zhang

Description:
use mysqlbinlog tool to parse geometry column, it will print error as below:

Don't know how to handle column type=255 meta=4

How to repeat:
1. use mysql-test start server: mtr rpl_wait_for_executed_gtid_set.test --start
2. connect 13000:
mysql> CREATE TABLE t1 (c1 INT PRIMARY KEY, c2 GEOMETRY, c3 INT);
Query OK, 0 rows affected (0.06 sec)

mysql> INSERT INTO t1 VALUES (1, point(1,1), 1);
Query OK, 1 row affected (0.04 sec)
3. use mysqlbinlog to parse binlog file
### INSERT INTO `test`.`t1`
### SET
###   @1=1 /* INT meta=0 nullable=0 is_null=0 */
###   @2=!! Don't know how to handle column type=255 meta=4 (0004)

[25 Apr 2024 7:51] MySQL Verification Team

Hello phoenix Zhang,

Thank you for the report and test case.
IMHO this is duplicate of Bug #72495, please see Bug #72495

regards,
Umesh