[Maria-discuss] DELETE Operations in MariaDB 5.5.30 do not reduce size of table files
To anyone who knows how the MyISAM engine works (or maybe this is independent of the DB engine), here’s my scenario: * I have a table with 180,000 rows * I delete 170,000 rows with a DELETE and subsequent COMMIT statement * The MYI table file is still the same size it was before the 170k rows were deleted I saw there’s an administrative PURGE command, but it looks like that is just for purging data from binary logs, if you’ve even turned on the option for keeping binary logs. In MariaDB 5.5.30 or later, how do I run a purge operation to compress the deleted rows of data out of my physical table files and cause the reindexing to happen for the data that is still in my tables? Thanks, Steve
optimize table xxxxx will "clean" the "deleted records" 2013/10/9 Steve Afrin <safrin@yahoo.com>
To anyone who knows how the MyISAM engine works (or maybe this is independent of the DB engine), here’s my scenario:
- I have a table with 180,000 rows - I delete 170,000 rows with a DELETE and subsequent COMMIT statement - The MYI table file is still the same size it was before the 170k rows were deleted
I saw there’s an administrative PURGE command, but it looks like that is just for purging data from binary logs, if you’ve even turned on the option for keeping binary logs.
In MariaDB 5.5.30 or later, how do I run a purge operation to compress the deleted rows of data out of my physical table files and cause the reindexing to happen for the data that is still in my tables?
Thanks, Steve
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
-- Roberto Spadim SPAEmpresarial
participants (2)
-
Roberto Spadim -
Steve Afrin