Hi @zimbo000, thanks for contacting us!
I understand you need to reduce the size of your database for MailPoet tables. We have documented our recommendations on how to safely approach that here: https://kb.mailpoet.com/article/402-reducing-database-size-for-mailpoet-tables
Feel free to get back to us in case you have any additional questions!
Thanks – is it documented anywhere what function each of those referenced tables does, e.g. I need to reduce wp_mailpoet_scheduled_task_subscribers (and others) in size but I don’t know what that table does, so am unsure how far back in time to delete.
Hi @zimbo000,
The wp_mailpoet_scheduled_task_subscribers table tracks which subscribers were sent each newsletter. A row is created per subscriber per send, and marked as processed once complete. After that, the data is only used by the Inactive Subscribers feature.
So how far back to keep depends on that:
- Not using Inactive Subscribers? You can safely delete all older processed data.
- Using it? Keep data at least as far back as the inactivity period you’ve set in MailPoet → Settings → Advanced.
The other large tables are mostly statistics — _statistics_opens, _statistics_clicks, _statistics_newsletters track email engagement, while _sending_queues stores email content for each send job, and _newsletter_links tracks links in your emails. You can apply the same date-based cleanup approach from the KB article to any of them.
Just remember to back up first before making any changes on your database.
Feel free to get back to us in case you have any additional questions!
