I'm trying to identify parts of a MySQL DB that take most space in GZipped dumps that I need to frequently save and restore so that I can archive some tables partially.
I have a suspicion that different tables are compressed better or worse depending on their content so their uncompressed size is not very relevant here.
Is there any way I can map
CREATE TABLE
or INSERT
statements in the DB dump to the file positions in the .sql.gz
file? Something like
gunzip
where {0}
is the current position of the db.sql.gz
file that gunzip is reading from
Asked by Anton Duzenko
(149 rep)
Oct 9, 2024, 01:05 PM
Last activity: Oct 11, 2024, 03:24 PM
Last activity: Oct 11, 2024, 03:24 PM