[MDEV-25277] mysqlbinlog --verbose cannot read row events with compressed columns: Don't know how to handle column type: 140 Created: 2021-03-27  Updated: 2023-02-16  Resolved: 2023-01-11

Status: Closed
Project: MariaDB Server
Component/s: Replication, Scripts & Clients
Affects Version/s: 10.3, 10.4, 10.5, 10.6
Fix Version/s: 10.11.2, 10.3.38, 10.4.28, 10.5.19, 10.6.12, 10.7.8, 10.8.7, 10.9.5, 10.10.3

Type: Bug Priority: Critical
Reporter: Elena Stepanova Assignee: Brandon Nesterenko
Resolution: Fixed Votes: 1
Labels: None


 Description    

--source include/have_binlog_format_row.inc
 
 
 
CREATE TABLE t1 (a TEXT COMPRESSED);
 
INSERT INTO t1 VALUES ('foo'),('bar');
 
FLUSH BINARY LOGS;
 
--let $binlog= query_get_value(SHOW BINARY LOGS, Log_name, 1)
 
--let $datadir= `SELECT @@datadir`
 
 
 
--echo # Running mysqlbinlog --verbose <binlog>
 
--exec $MYSQL_BINLOG --verbose $datadir/$binlog
 
 
 
# Cleanup
 
DROP TABLE t1;

10.3 480a0671

 
# Running mysqlbinlog --verbose <binlog>
 
bug.t                                    [ fail ]
 
        Test ended at 2021-03-27 17:51:42
 
 
 
CURRENT_TEST: bug.t
 
 
 
Error: Don't know how to handle column type: 140 meta: 2 (0002)
 
mysqltest: At line 10: exec of ...

Not applicable to 10.2 as compressed columns were introduced in 10.3.

 Comments   
Comment by Brandon Nesterenko [ 2021-06-04 ]

Hey Andrei,

This is ready for review.

Patch

Buildbot

Comment by Domantas Speciunas [ 2022-10-26 ]

Is this progressing?

Comment by Brandon Nesterenko [ 2023-01-11 ]

Pushed into 10.3 as b194c83

Note there is a merge conflict in 10.5 fixed in the following commit d89d7eb from 10.5-MDEV-25277-merge

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