Title: database table wp_option growing
Last modified: February 17, 2020

---

# database table wp_option growing

 *  Resolved [kennet1975](https://wordpress.org/support/users/kennet1975/)
 * (@kennet1975)
 * [6 years, 3 months ago](https://wordpress.org/support/topic/database-table-wp_option-growing/)
 * Hi Have you ever experienced database table wp_option growing and growing when
   using Mainwp and mainwp child?

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [sanjamainwp](https://wordpress.org/support/users/sanjamainwp/)
 * (@sanjamainwp)
 * [6 years, 3 months ago](https://wordpress.org/support/topic/database-table-wp_option-growing/#post-12450998)
 * Hi [@kennet1975](https://wordpress.org/support/users/kennet1975/),
 * Please open a [support ticket](https://mainwp.com/presale-query/) so we can check
   the issue.
 * Thanks,
    Sanja
 *  Plugin Author [mainwp](https://wordpress.org/support/users/mainwp/)
 * (@mainwp)
 * [6 years, 3 months ago](https://wordpress.org/support/topic/database-table-wp_option-growing/#post-12499797)
 * This problem should be solved in MainWP Child 4.0.7. If you still experience 
   this issue please feel free to open the [helpsdesk ticket](https://mainwp.com/support/).
 *  [pixelbrad](https://wordpress.org/support/users/pixelbrad/)
 * (@pixelbrad)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/database-table-wp_option-growing/#post-13295366)
 * I understand this is resolved, but wanted to chime in with my two cents anyway.
 * I have been using MainWP Child for 6+ months on my client’s website. They have
   a fairly busy ecommerce website with plenty of public and admin traffic.
 * I was just pulling my hair out about during a database migration because the `
   wp_options` table kept failing to import. I traced it down to a single row. The
   problematic row had an `option_name` of `mainwp_child_subpages` and a value **
   over 120 million characters in length**.
 * After browsing through MainWP Child’s code, it seems this option is unused in
   the current version. Excluding this row from my import allowed the import to 
   proceed unhindered.
 * Not too sure what this would have been used for, or how it grew to such a size,
   but my oh my did this ever give me a headache.
    -  This reply was modified 5 years, 9 months ago by [pixelbrad](https://wordpress.org/support/users/pixelbrad/).
    -  This reply was modified 5 years, 9 months ago by [pixelbrad](https://wordpress.org/support/users/pixelbrad/).

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘database table wp_option growing’ is closed to new replies.

 * ![](https://ps.w.org/mainwp-child/assets/icon-256x256.png?rev=2734948)
 * [MainWP Child - Securely Connects to the MainWP Dashboard to Manage Multiple Sites](https://wordpress.org/plugins/mainwp-child/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/mainwp-child/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/mainwp-child/)
 * [Active Topics](https://wordpress.org/support/plugin/mainwp-child/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/mainwp-child/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/mainwp-child/reviews/)

 * 3 replies
 * 4 participants
 * Last reply from: [pixelbrad](https://wordpress.org/support/users/pixelbrad/)
 * Last activity: [5 years, 9 months ago](https://wordpress.org/support/topic/database-table-wp_option-growing/#post-13295366)
 * Status: resolved