Audit Log breaks database exports

  • Resolved Adam Nowak

    (@adam320)


    1 year, 8 months ago

    I was using WP migrate DB to export the site database and the audit log serialized data was exhausting the allowed memory. Letting you know fist but will let WP migrate DB know about the issue if it’s not on your end. I simply deleted the audit log and the export worked fine. It gets stuck when exporting that table. Allowed memory size of 134217728 bytes exhausted

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support aporter

    (@aporter)

    Hi Adam,

    Thanks for the report.

    Did you notice how many entires/rows you had in the audit log table before you cleared it?

    I’ll try and reproduce the issue, but I have a feeling it’s going to be an issue WP migrate DB needs to resolve.

    We could add something to prevent recording the serialized stacktraces when turned on.

    Best Wishes,

    Ashley

    Plugin Author David Anderson

    (@davidanderson)

    One serialized stack trace is a tiny amount of data. So, most likely the issue is that WP Migrate DB needs a better algorithm for deciding how many rows to fetch at once – presumably, based on the description above, it fetches more rows than can fit into available memory. Do you get the same issue if you attempt a different plugin? (I authored the algorithm in UpdraftPlus for fetching rows without advanced knowledge of what they might contain and am always interest if someone finds a case that doesn’t work).

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Audit Log breaks database exports’ is closed to new replies.