database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-08-09 22:24:09 +03:00
Code Activity

Bug #24488141 ACTIVE UNDO TABLESPACE NOT UPDATED WHEN INNODB_UNDO_LOGS IS INCREASED

Browse Source 
Problem:
========
 If we increase innodb_undo_logs value during startup. New rollback
segment might get allocated during trx_sys_create_rseg(). Essentially, it
would make these tablesapces active with transaction undo data and purge.
But it doesn't come in active undo tablespaces. so these tablespace would
never get truncated.

Fix:
===
 Increase the number of active undo tablespace when we are assigning the
undo tablespace to the newly assigned rollback segment.

Reviewed-by: Kevin Lewis <kevin.lewis@oracle.com>
Reviewed-by: Debarun Banerjee <debarun.banerjee@oracle.com>
RB: 13746
This commit is contained in:
Thirunarayanan Balathandayuthapani
2016-09-07 12:40:10 +05:30
committed by Marko Mäkelä
parent bdfa49f6e2
commit d1bcc1f49f
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
storage/innobase/trx/trx0sys.cc
View File

@@ -921,6 +921,15 @@ trx_sys_create_rsegs()
" requested innodb_undo_logs"; " requested innodb_undo_logs";
return(false); return(false);
} }
/* Increase the number of active undo
tablespace in case new rollback segment
assigned to new undo tablespace. */
if (space > srv_undo_tablespaces_active) {
srv_undo_tablespaces_active++;
ut_ad(srv_undo_tablespaces_active == space);
}
} }
} }