diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2017-04-25 09:26:01 +0300 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2017-04-26 23:03:28 +0300 |
| commit | 206ecb79a5f208547ac30ddd3fa108d208198eb0 (patch) | |
| tree | 7448bacfb4abc9d5ad2c0fcdcdc7f9d9b998ee7b /storage/innobase/trx/trx0sys.cc | |
| parent | 23ea4360fd1e93fad3dc391dd94f2d1592eb7220 (diff) | |
| download | mariadb-git-206ecb79a5f208547ac30ddd3fa108d208198eb0.tar.gz | |
Follow-up to MDEV-12289: Support innodb_undo_tablespaces=127
MySQL 5.7 reduced the maximum number of innodb_undo_tablespaces
from 126 to 95 when it reserved 32 persistent rollback segments
for the temporary undo logs. Since MDEV-12289 restored all 128
persistent rollback segments for persistent undo logs, the
reasonable maximum value of innodb_undo_tablespaces is 127
(not 126 or 95). This is because out of the 128 rollback segments,
the first one will always be created in the system tablespace
and the remaining ones can be created in dedicated undo tablespaces.
Diffstat (limited to 'storage/innobase/trx/trx0sys.cc')
| -rw-r--r-- | storage/innobase/trx/trx0sys.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/storage/innobase/trx/trx0sys.cc b/storage/innobase/trx/trx0sys.cc index 80aab87edaf..1ce9f49ba30 100644 --- a/storage/innobase/trx/trx0sys.cc +++ b/storage/innobase/trx/trx0sys.cc @@ -879,7 +879,7 @@ trx_sys_create_rsegs() srv_undo_logs determines how many of the srv_available_undo_logs rollback segments may be used for logging new transactions. */ - ut_ad(srv_undo_tablespaces < TRX_SYS_N_RSEGS); + ut_ad(srv_undo_tablespaces <= TRX_SYS_MAX_UNDO_SPACES); ut_ad(srv_undo_logs <= TRX_SYS_N_RSEGS); if (srv_read_only_mode) { |