You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This should help for a few reasons. 1) it wouldn't take too much packet data to overwhelm the maximum size of the merge table. 2) InnoDB is capable of non-blocking writes. 3) partitions should be faster than merges.
It's frankly tempting to just not keep a merged table and just pull queries over multiple days out of multiple tables.
The text was updated successfully, but these errors were encountered:
Change from using:
MyISAM's merge to InnoDB partitions.
This should help for a few reasons. 1) it wouldn't take too much packet data to overwhelm the maximum size of the merge table. 2) InnoDB is capable of non-blocking writes. 3) partitions should be faster than merges.
It's frankly tempting to just not keep a merged table and just pull queries over multiple days out of multiple tables.
The text was updated successfully, but these errors were encountered: