diff options
| author | Vlad Lesin <vlad_lesin@mail.ru> | 2022-04-01 15:58:31 +0300 |
|---|---|---|
| committer | Vlad Lesin <vlad_lesin@mail.ru> | 2022-04-04 12:19:09 +0300 |
| commit | 6a3545dd1e3a7fdf63ac22ad049fd7763f35a13e (patch) | |
| tree | d9b627cec68b572a09c1c71982e4f2be5f33770b /sql/share | |
| parent | 7f5a3cd2532716a7c8d8308d8afc2dcb3a856ba3 (diff) | |
| download | mariadb-git-6a3545dd1e3a7fdf63ac22ad049fd7763f35a13e.tar.gz | |
MDEV-26322 Last binlog file and position are "empty" in mariabackup --prepare output
The issue is caused by 59a0236da4810a5ae243e77cb7a9c6262639a6e4 commit.
The initial intention of the commit was to speed up
"mariabackup --prepare".
The call stack of binlog position reading is the following:
▾ trx_rseg_mem_restore
▾ trx_rseg_array_init
▾ trx_lists_init_at_db_start
▸ srv_start
Both trx_lists_init_at_db_start() and trx_rseg_mem_restore() contain
special cases for srv_operation == SRV_OPERATION_RESTORE condition, and
on this condition only rseg headers are read to parse binlog position.
Performance impact is not so big.
The solution is to revert 59a0236da4810a5ae243e77cb7a9c6262639a6e4.
Diffstat (limited to 'sql/share')
0 files changed, 0 insertions, 0 deletions