Replies: 2 comments 2 replies
-
In the Postgres database itself, do you have Autovacuum enabled? Autovacuum needs to run regularly to remove dead tuples (updated or deleted rows) and reclaim space. If it is not running effectively, the database will continue growing even with pruning. |
Beta Was this translation helpful? Give feedback.
0 replies
-
yes, the Autovacuum is enabled for Psql Database And After setting the Pruning, the DB is growing constantly whenever the first pruning was run |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
we are using the Mirth Connect version is 4.3.0
The database of Mirth is Connected to Cloud SQL [PostgreSQL] in GCP [Google Cloud Platform] Which have a version of 12.16
So my concern is from last month onwards the mirth-connect database in PostgreSQL is growing rapidly day by day.
And also parallely, the Archived_wal_log is increasing and it's almost the double the size of original data
we have enabled the Automated backups & Point-in-time recovery & also enabled the Autoscaling of storage. So it increases the storage whenever the size of Database increases.
So after had a discussion and we have set the Data pruning at the Global level & Channel level
Here's the Settings for that
At the time of pruning, we observed the PostgreSQL Database storage is growing.
And also the archived_wal_log storage is increased mainly[For this one, i have attached screenshot before & after pruning started]
Then after completing the Pruning the Data storage is constant
Attached the Screenshots
Here's my question:
Can someone please help on this
Beta Was this translation helpful? Give feedback.
All reactions