[Closed] Can I truncate this row? easyblog_revisions
By Rob on Saturday, 28 November 2015
Posted in General Issues
Likes 0
Views 468
Votes 0
Helllo,

I am pruning the DB and I noticed a few tables that I have questions on.

easyblog_feeds_history
easyblog_oauth_posts
easyblog_post
easyblog_post_category
easyblog_revisions

I realize that the posts are for the articles that are there but some of them are getting over 20,000 entries.

Could you help advise to a good way for DB maintenance with EasyBlog. I mean is it safe to truncate the heavy rows such as feeds history and revisions rows?

Thank you for your time and Happy Holidays!

Regards,
Rob
Hi Rob,

I am sorry for the delay of this reply.

To be frank, we don' really run any optimisation to our DB except adding some extra table indexes to improve the sql performance for our forum. However, we do run the below command once awhile or when we detect the table has large overhead.



repair table jos_your_table_name;

optimize table jos_your_table_name;



Because I was testing my DB and when a post publishes I get a lot of table level locks - see image.


Regarding the above, do you mean when you publish a blog post from EasyBlog, you get the table lock? If yes, thats really strange. updating jos_easyblog_post publishing status shouldn't lock up the table. Maybe you can pass me your phpmyadmin access to your site so that i can take a look at your this issue? Also, i will need your site's Joomla backend admin access and your ftp account

Please advise.
Sam
·
Monday, 07 December 2015 11:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

#1. easyblog_post
#2. easyblog_revisions

Unfortunately you can't truncate this 2 table data is because all the post is depend on the revision id, if the revision id is missing, so that will some issue when you load the post in your frontend.

#3. easyblog_feeds_history

#4. easyblog_oauth_posts

You can truncate this 2 table data but you have to make sure you have to delete your feed URL from backend > Easyblog > feed importer is because this 2 table is actually stored which feed post already imported in your site, if you truncated the data from this table `easyblog_feeds_history`, it will auto import these feed in your site again.

This table `easyblog_oauth_posts` will stored these post data which already autopost to your social network page.

#5. easyblog_post_category

Unfortunately you can't truncate this table is because all of your existing post was already created under these categories.

Hope this explanation will help.
Arlex Wong
·
Monday, 30 November 2015 11:52
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Arlex,

Thank you my friend for an awesome explanation. Could you offer any advice as to what methods you use to optimize your DB to keep them in good operation? I already use a methodology but was wondering if you could offer anything else that could be done for the fantastic EasyBlog DB.

Because I was testing my DB and when a post publishes I get a lot of table level locks - see image.

Thanks you again very much for your time.

Regards,
Rob
Rob
·
Sunday, 06 December 2015 22:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Sam,

That's okay I got it under control I just thought maybe you may have done something else to keep the DB in top performance. Now the table locks don't happen all the time only once in a while. Thanks again.

Regards,
Rob
Rob
·
Monday, 07 December 2015 21:23
·
0 Likes
·
0 Votes
·
0 Comments
·
You are most welcome Rob
Mark
·
Tuesday, 08 December 2015 01:29
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post