Reduce core_log table size (20GB)

[Il_Picasso]

Hello! I would like some help on how to fix the size of my database which is 20GB but in fact it only has 6 entries at the moment

 

[Mark H]

You're looking at the physical files on disk for the database, but please do not attempt to directly edit or alter those files in any way, that's truly asking for trouble. 🙂

Instead use phpMyAdmin and examine the database. If the core_log table is huge but you only have a few topics and posts, then check a few of the rows in that table to see if they are error entries of some sort.

Once you determine that, and correct the problem causing the table to fill so quickly, you can safely TRUNCATE (empty, not delete) that table to reduce its size.

If you cannot find a valid reason for that table filling up so quickly, please submit a ticket to support and we'll be glad to take a look for you.

[bfarber]

Also, you showed "x_utf_core_log" in your screenshot, which is typically the pre-UTF8 conversion copies of the tables (and not the actual tables your live site is using). Unless your sql_prefix in conf_global.php is set to "x_utf_", you can safely delete any and all tables that are prefixed as x_utf_ entirely (as Mark suggested, use phpmyadmin or a similar tool for this, do not just delete the files on disk).

[Il_Picasso]

I truncated it directly from the commandline, it has not filled anymore

 

Just found it crazy that with 66 entries in that table the size of the DB would reach 20GB, now it is 2GB big, which is normal 

 

51 minutes ago, bfarber said:

Also, you showed "x_utf_core_log" in your screenshot, which is typically the pre-UTF8 conversion copies of the tables (and not the actual tables your live site is using). Unless your sql_prefix in conf_global.php is set to "x_utf_", you can safely delete any and all tables that are prefixed as x_utf_ entirely (as Mark suggested, use phpmyadmin or a similar tool for this, do not just delete the files on disk).

That is the case.

 

Thanks everyone