There are cases where we need to implement MySQL
partitioning, or at least test if it is an option to solve an
issue. However, how are we able to test it when the table on our
production environment has hundreds of millions of rows, several
composite indexes and/or the size on disk is hundreds of
gigabytes?
Testing environments usually don’t have all the data
that production has and if they have, probably you are not
testing all the use-cases at a database level. Therefore, is it
possible to test MySQL Partitioning on production impacting
as less as possible?
When we execute pt-online-schema-change, it creates a table,
triggers, and then copies the data. As we are going to test
partitioning we are going to need both tables – with and without
partitioning – and we are going to use triggers to keep both
tables consistent. A good thing about changing a table to
use partitioning is that, usually, …
[Read more]