Internet of Things Integration Platform
Remote Monitoring, M2M and Device Management Software Platform

Correct way of database data shrinking

Questions related to relational databases, key-value databases, NoSQL databases, round-robin databases, and file-based storage.

Correct way of database data shrinking

Postby imoskovko/gmail_com » Fri Sep 29, 2017 12:19 pm

Hello

We noticed that our postgress DB grew up to 12 TB. Looks like some devices have too short sync period.
I have trancated largest tables with *_change suffix using pgadmin4 GUI tool.

Waht is correct way of housekeeping database? Can history change data be discarded using Aggregate tools or commands?

Regards,
Igor
imoskovko/gmail_com
 
Posts: 16
Joined: Wed Aug 30, 2017 9:39 am

Re: Correct way of database data shrinking

Postby sergey_eritsyan/tibbo_com » Fri Oct 06, 2017 2:56 pm

Hi, Igor!

You can see statistics in DB and find out the most loaded tables.
For DB housekeeping you should make VACUUM LO operation using DB tools. It will clean up and compress data.

Best regards, AggreGate support team.
sergey_eritsyan/tibbo_com
 
Posts: 26
Joined: Fri Jul 07, 2017 10:42 am

Re: Correct way of database data shrinking

Postby imoskovko/gmail_com » Tue Oct 10, 2017 7:23 pm

I found it in Aggregate manuals
It helps

http://aggregate.tibbo.com/docs/en/ls_d ... b=vacuumlo


yum install postgresql-contrib

su - postgres
vacuumlo -U postgres -v -w aggregate
vacuumdb -fav -w
imoskovko/gmail_com
 
Posts: 16
Joined: Wed Aug 30, 2017 9:39 am

Re: Correct way of database data shrinking

Postby sergey_eritsyan/tibbo_com » Fri Oct 13, 2017 10:40 am

Thank you for feedback.
sergey_eritsyan/tibbo_com
 
Posts: 26
Joined: Fri Jul 07, 2017 10:42 am


Return to Data Storage

Who is online

Users browsing this forum: No registered users and 2 guests