Bug #109496 mysqlbinlog command Got a packet bigger then max_allowed packet
Submitted: 29 Dec 2022 2:34 Modified: 29 Dec 2022 11:31
Reporter: HULONG CUI Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:8.0.20 OS:Any
Assigned to: MySQL Verification Team CPU Architecture:Any

[29 Dec 2022 2:34] HULONG CUI
I have a need to restore the database. using  full backup + binlog file。
the binlog file size mysql-bin.000160 is 1.7G. there have update one table big trasaction.

when the command mysqlbinlog excute, out put max_allowed packet error.
so i set global max_allowed_packet=1024*1024*1024 ,also error happend.

time mysqlbinlog mysql-bin.000160  | mysql -uroot -p'123456'  -s /opt/data/mysql.sock
at line 14047509: Got a packet bigger then 'max_allowed packet' bytes

read 3m57 788s
user 0m54.133s
sys 1m5.268s

How to repeat:
1.variables max_binlog_size set 2G
2.bigger 1G size binlog 
3.recovery binlog
using this  | mysql -uroot -p'123456'  -s /opt/data/mysql.sock
[29 Dec 2022 11:31] MySQL Verification Team
We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug.

For details on getting support for MySQL products see http://www.mysql.com/support/
You can also check our forums (free) at http://forums.mysql.com/

Thank you for your interest in MySQL.