Backup (Mysqldump error) with Brizy database table wp_brizy_logs

Pedro Paquemar

• August 24, 2020 21:08
• Edited

Hi,

I am having an issue since a while where many backups fail because of the error bellow. You may want to look at this:

mysqldump: Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."number-of-buckets-specified"') FROM information_schema.COLUMN_STATISTICS WHERE SCHEMA_NAME = 'wordpress' AND TABLE_NAME = 'wp_brizy_logs';': Unknown table 'COLUMN_STATISTICS' in information_schema (1109)

Regards,

Pedro

0

• 

  Sandra Prunici

  • August 25, 2020 11:08

  Hi,

  When did you encounter this problem? What were your previous actions? How did you make the backup and how did you restore it? What visual problem did you have? Do you have the later version for Brizy Free (2.0.6) and Brizy Pro (2.0.4)?

  Thanks!

  Best regards,
  Sandra

  0
• 

  Pedro Paquemar

  • August 25, 2020 12:17

  Thank you for your reply Sandra. I do appreciate if you could share this with your dev team.

  We initially wanted to share the issue on Github, but the replies being slow there I thought it would be better to share this issue here for the sake of having a follow-up from your team.

  1. When did you encounter this problem?
     I am having this issue since Version 2.0. As you can see in the error log I am just exporting the database Reference.
     
     
  2. How did you make the backup and how did you restore it?
     The backup is made through a simple mysqldump, as seen in the error report.
     This is what most WordPress plugins use to backup WordPress tables, hence the reason why I am sharing this report here. This error can be reproduced easily on the following database systems Mariadb, Mysql, Amazon Aurora.
     
     
  3. What visual problem did you have?
     I am not sure I understand this question in the context of the error that is being reported. This table COLUMN_STATISTICS is referred to in your database information_schema but is not used anymore and not part of the tables that are created by default for Brizy. So when you export the database for backups or migrations, mysql simply throw the error reported in this thread.
     
     
  4. Do you have the later version for Brizy Free (2.0.6) and Brizy Pro (2.0.4)?
     Yes this have been tested also on the latest versions of the Pro plugins and Free plugin. Our team have seen in your change logs that this issue have not been addressed since 2.0 so we wanted to raise it to your attention.

  I hope you find this information helpful. Please let me know if you need any additional relevant information.

  Best regards,
  Pedro

   

  0
• 

  Sandra Prunici

  • August 26, 2020 12:21

  Hi,

  Could you please try to delete the table "wp_brizy_logs" from PHPMyAdmin? Or you can try to disable Brizy Free and Pro and after some seconds to activate them again. We recommend the first method. After this try to generate the backup.

  Thanks!

  Best regards,
  Sandra

  0
• 

  Pedro Paquemar

  • August 26, 2020 15:35

  Thank you so much for your help! Deleting the table fixes the issue!

   

  Best regards,

  Pedro

  0
• 

  Sandra Prunici

  • August 26, 2020 15:49

  Thank you too! 
  Let us know if we can help you with something else.

  Best regards,
  Sandra

  0

Please sign in to leave a comment.