|
lhammond
|
November 19, 2018 at 4:21 am
After converting all my EE3 data to EE4, I was running a duplicator backup when I noticed that the esp_payment table is strangely large. It doesn’t seem like it should be so I’m wondering if something has gone wrong in my database. Can you confirm that this seems unusually large compared to the other tables and in consideration of the number of rows?
table number of rows data size index size Type
wp_esp_payment 4,716 11.5 MB 272.0 KB InnoDB
wp_esp_answer 16,884 1.5 MB 0 bytes InnoDB
wp_esp_registration 19,875 3.5 MB 8.4 MB InnoDB
wp_posts 14,172 51.5 MB 3.9 MB InnoDB
wp_postmeta 89,937 9.5 MB 8.0 MB InnoDB
Do you have any thoughts as to what would cause such a big discrepancy in the data size relative to the number of rows, compared to the other tables that have many more rows? What is actually stored in that table, and is it possible that it contains duplicated data from the data conversion somehow?
What do you recommend I do to fix the problem (if it really is a problem)? I cannot run optimize on the table because it’s InnoDB.
Thanks!
|
|
Josh
|
November 19, 2018 at 10:16 am
Hi Laura,
The reason for the larger amount of data is because there are some serialized objects stored in the PAY_details field of the wp_esp_payment table. Those do take more storage than a typical text field.
is it possible that it contains duplicated data from the data conversion somehow?
I don’t think so. Have you looked in the table to see if there is duplicated data?
Here’s a little tip for optimizing the database when it’s InnoDB:
https://perishablepress.com/wordpress-plugin-enable-database-tools/
|
