Memory leak in PostgreSQL12 and workaround

Date 2020/2/20 15:41:45 | Topic: Announcements

Recently (in December 2019) I have upgraded the FGTracker database from 11 to 12. Unforturnately it appears that there is memory leak in postgres instance:

I have tried to submit a bug report to pgsql-bugs but unforturnately I am not able to produce a replication steps simple enough for a decent bug report, and the bug report is closed.

In this connection, I have to make necessary arrangements to mitigate the memory leak by reducing the frequency on running the batch job. What the batch job does is to update the ranking, to update the start/end airport and to claculate effective flight time.

With immediate effect, the frequency is changed from 300 seconds to 1800 seconds.




This article comes from FG Tracker & Planner
https://fgtracker.ml

The URL for this story is:
https://fgtracker.ml/modules/news/article.php?storyid=31