After switching to HPOS and turning off compatibility mode, i wanted to clean up the database as per the native function in Status->Tools. This does not seem to function.

Eg, in the wp_postmeta table I’m seeing these entries (portfolio and style are pods custom post types with table storage):

| Edit  | Copy  | Delete | 58681 | 170 | _pods_portfolio  | a:1:{i:0;i:64;} |
| Edit  | Copy  | Delete | 58682 | 170 | _portfolio       | 64     |
| Edit  | Copy  | Delete | 58683 | 64  | _style           | 162    |
| Edit  | Copy  | Delete | 58684 | 64  | _style           | 243    |
| Edit  | Copy  | Delete | 58685 | 64  | _style           | 251    |
| Edit  | Copy  | Delete | 58686 | 64  | _style           | 252    |
| Edit  | Copy  | Delete | 58687 | 64  | _style           | 170    |

And the podsrel table:

| Edit | Copy | Delete | 89  | 43 | 144 | 64 | 135 | 138 | 162 | 0 |
| Edit | Copy | Delete | 249 | 43 | 144 | 64 | 135 | 138 | 251 | 2 |
| Edit | Copy | Delete | 95  | 43 | 129 | 64 | 47  | 130 | 164 | 1 |
| Edit | Copy | Delete | 248 | 43 | 144 | 64 | 135 | 138 | 243 | 1 |
| Edit | Copy | Delete | 94  | 43 | 129 | 64 | 47  | 130 | 165 | 0 |
| Edit | Copy | Delete | 250 | 43 | 144 | 64 | 135 | 138 | 252 | 3 |
| Edit | Copy | Delete | 76  | 43 | 129 | 64 | 47  | 130 | 157 | 2 |

I thought table storage meant these relationships would be stored in wp_podsrel? Would love some clarity on this.

sometime in May, my automatic and manual backups stopped working. I always get the message “Unable to export – Cannot run export. Please refresh the page and try again”
By the elimination method I found the following:

1. The error is caused by the wp_postmeta table.
2. If I export the entire site and intentionally omit wp_postmeta, the export is successful. If I export only the wp_postmeta table or include this table in the overall backup, the export will end with the above error message.
3. Apparently the error is not caused by the script run time – the wp_postmeta table is the largest size in the database, but it does not have the most rows. If I export the whole site without wp_postmeta, I can download a 2 GB file without any difficulties.

I suspect that the All-in-One WP Migration and Backup plugin doesn’t like the contents of that table.

I use the following:
WordPress 6.6.2
All-in-One WP Migration 7.86
All-in-One WP Migration OneDrive Extension 1.74
All-in-One WP Migration Unlimited Extension 2.60

Does anyone have the same problem? Do you know how I can get the full backup to work?

Thank you very much
-Petr

We have a multilingual WordPress website using WPML with over 52,000 posts across 8+ languages. We are encountering performance issues and site slowness, which seem to be related to the size of several database tables.

Here is an overview of the large database tables:

• wp_icl_translate: 1859.59 MB
• wp_icl_translation_status: 1196.06 MB
• wp_postmeta: 1095.48 MB
• wp_posts: 570.16 MB
• wp_icl_string_translations: 260.89 MB

To address these issues, we have optimized the database using the WP Rocket plugin, clearing out unnecessary data like post revisions, transients, and auto drafts. Additionally, we have set WP_POST_REVISIONS to 3.

I came across the suggestion to split large tables into multiple tables as a potential optimization. Could anyone share their experience with this approach?

Moreover, I would appreciate any recommendations on further improving site performance, especially with regard to the database, queries, and overall request handling.

Thank you in advance for your assistance.

Best regards,
Vimal Roy

my wp_postmeta is 3.6gb – the sm_cloud table is approx 2GB

Is it safe to delete the sm_cloud table if the plugin is deleted or is there a different approach I can use to reduce the size of sm_sloud?

We have deleted all products in the store and are planning to ulpload them again once our database is fully optimized

I am reaching out to discuss an issue I am encountering with my website, specifically concerning the WooCommerce Advanced Product Labels plugin.

The problem lies with the database size, which has become quite large due to numerous “br_labels” records in the “wp_postmeta” table. I sought assistance from my hosting support, and they advised against outright removing these records. They explained that doing so may result in the removal of labels associated with products on my site.

I would appreciate it if you could provide more information about these records. Is it possible to delete them without causing any problems for my website? Additionally, I am curious if there is a way to modify the plugin settings to limit the number of records created, as my site has a growing number of products.

Thank you in advance for your assistance.

Best regards

I use the following code to add the contents of some custom checkout fields to my invoices and packing slips:

function custom_order_info_fields( $fields, $order ) {

	$custom_fields = array(
        array(
            'label' => 'Vergi Dairesi:',
	    'value' => get_post_meta( $order->get_id(), '_billing_vergidairesi', true ),
        ),
        array(
            'label' => 'T.C./Vergi No:',
			'value' => get_post_meta( $order->get_id(), '_billing_tckimlik_vergino', true ),
        ),
    );

    $fields = array_merge( $fields, $custom_fields );
    return $fields;
}

add_filter( 'wcdn_order_info_fields', 'custom_order_info_fields', 10, 2 );

The code works as intended except it gives empty values for the custom fields. There are no errors in debug logs, and when I dump some variables with:

var_dump(get_post_meta( $order->get_id(), '', false ));

I see the get_post_meta() returns data from my db table wp_postmeta instead of wp_wc_orders_meta where the custom fields are stored. wp_postmeta does have entries for every orderID that has a successful payment, because my payment gateway plugin stores them there, I’m not sure how or why.

Why does this happen and how do I make get_post_meta() return custom checkout fields?

Everything else seems to work fine. Below is my related config:

• WordPress 6.4.3
• WooCommerce 8.5.2
• Checkout Field Editor for WooCommerce 2.0.0
• Raft 1.1.1 (theme)
• Code Snippets 3.6.2
• Print Invoice & Delivery Notes for WooCommerce 4.8.1

On one of my websites an error occurs when I just open the Maintenance plugin settings page. I can put the website in the maintenance mode and back, but the bottom of the settings page is not loaded (or/and I cannot apply another background image for the maintenance mode). The debug.log shows me the following error:

Got error 'PHP message: PHP Fatal error: Allowed memory size of 4294967296 bytes exhausted (tried to allocate 1052672 bytes) in /web/alarmaa.de/wp-includes/meta.php on line 1194'

I found out that this comes from having more than 3 million wp_postmeta entries. And yes, they are important for my website, this is ok. Now I reprogram my code to store this huge amount of data in a separate database table.

But maybe you are interested in this behavior and maybe you want to (if there is a need for) optimize your code for that nice plugin Or maybe some other users get this error and want to know what is wrong …

Best wishes,
Wasilij