Hello, anyone here have some advice for my problem?
So, my TimescaleDB Master memory spiking and Not Released after daily backup process that is run every 2am in the morning. To avoid issue we have a cron to restart the timescaleDB.
Hi @yoyo , what version of Timescaledb, PG are you using? I see it’s kubernetes, is it through some operator? Can you replicate your scenario without the timescaledb and confirm that the memory leakage is related to timescaledb extension?
Consider run VACUUM ANALYZE after the backup to help update statistics and check if it potentially free up memory.
Another idea is also use pg_stat_statements to identify any long-running or resource-intensive queries that might be interfering with memory release.
Hi @jonatasdp , i really appreciate for the fast response 
We currently using timescaledb version 2.14.2 with PG version 16.2. And yes we’re using kubernetes operator called StackGres, i think we can look deeper to this if this is could be the cause.
Thank you once more for your insight and recommendation! Will try it.