Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for "Storing InnoDB Undo Logs in Separate Tablespaces" #41

Open
ShahriyarR opened this issue Nov 23, 2016 · 3 comments
Open
Assignees

Comments

@ShahriyarR
Copy link
Contributor

Update PTB to use -> https://dev.mysql.com/doc/refman/5.7/en/innodb-undo-tablespace.html

This feature involves the following new or renamed configuration options:

innodb_undo_tablespaces

innodb_undo_directory

innodb_rollback_segments becomes innodb_undo_logs. The old name is still available for compatibility. 
@ShahriyarR
Copy link
Contributor Author

So the decided values is:

innodb_undo_tablespaces=10
innodb_undo_directory -> will not specify. By default path is datadir.
innodb_undo_logs=128(max value)

ShahriyarR pushed a commit that referenced this issue Dec 19, 2016
@ShahriyarR
Copy link
Contributor Author

Implemented. Fixed.

@RoelVdP
Copy link
Contributor

RoelVdP commented Jan 9, 2017

One question; with innodb_undo_logs=128 (max value) - is the performance about the same? If the queries per second (qps) is much lower, then the testing coverage is more limited, for example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants