mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 12:02:42 +01:00
9fa718b1a1
Before MariaDB 10.3.5, the binlog position was stored in the TRX_SYS page, while after it is stored in rollback segments. There is code to read the legacy position from TRX_SYS to handle upgrades. The problem was if the legacy position happens to compare larger than the position found in rollback segments; in this case, the old TRX_SYS position would incorrectly be preferred over the newer position from rollback segments. Fixed by always preferring a position from rollback segments over a legacy position. Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org> |
||
---|---|---|
.. | ||
alter_table_pk_no_sort.inc | ||
autoinc_persist_alter.inc | ||
crc32.pl | ||
dml_ops.inc | ||
have_innodb_bzip2.inc | ||
have_innodb_lz4.inc | ||
have_innodb_lzma.inc | ||
have_innodb_lzo.inc | ||
have_innodb_punchhole.inc | ||
have_innodb_snappy.inc | ||
have_undo_tablespaces.combinations | ||
have_undo_tablespaces.inc | ||
ibd_convert.pl | ||
import.inc | ||
innodb-page-compression.inc | ||
innodb-util.pl | ||
innodb-wl6045.inc | ||
innodb_binlog.combinations | ||
innodb_binlog.inc | ||
innodb_bulk_create_index.inc | ||
innodb_bulk_create_index_debug.inc | ||
innodb_dict.inc | ||
innodb_isolation_selects.inc | ||
innodb_merge_threshold_delete.inc | ||
innodb_merge_threshold_secondary.inc | ||
innodb_merge_threshold_update.inc | ||
innodb_stats.inc | ||
log_file_cleanup.inc | ||
no_checkpoint_end.inc | ||
no_checkpoint_start.inc | ||
restart_and_reinit.inc | ||
show_i_s_tables.inc | ||
show_i_s_tablespaces.inc | ||
wait_all_purged.inc |