if a long --databases= is given, backup will fail with signal 11.
the command is
when there is 1859 white space before db01.t1, it will fail.
when there is 1858 or less white space before db01.t1, it will success.
due to different username and password and table name, the number of white space needed to reproduce the bug might be varies. but a long enough --databases will reproduce the fail.
Environment
[root@localhost test]# mysqld --version /usr/local/mysql-8.0.35-linux-glibc2.12-x86_64/bin/mysqld Ver 8.0.35 for Linux on x86_64 (MySQL Community Server - GPL)
[root@localhost test]# xtrabackup --version 2024-12-03T15:55:30.917159+08:00 0 [Note] [MY-011825] [Xtrabackup] recognized server arguments: --open_files_limit=762140 --innodb_max_dirty_pages_pct=40 --innodb_autoextend_increment=128 --innodb_file_per_table=1 --innodb_open_files=762140 --innodb_log_buffer_size=64M --innodb_read_io_threads=16 --innodb_write_io_threads=8 --innodb_flush_method=O_DIRECT --innodb_adaptive_hash_index=0 xtrabackup version 8.0.35-31 based on MySQL server 8.0.35 Linux (x86_64) (revision id: 2b9a1f65)
High
if a long --databases= is given, backup will fail with signal 11.
the command is
when there is 1859 white space before db01.t1, it will fail.
when there is 1858 or less white space before db01.t1, it will success.
due to different username and password and table name, the number of white space needed to reproduce the bug might be varies. but a long enough --databases will reproduce the fail.