jrgemignani commented on issue #2020: URL: https://github.com/apache/age/issues/2020#issuecomment-2296854488
@vladiksun There are some other memory leaks, for example #2046 which I am currently working on, that could be contributing factors. That particular one highlights quite a few other areas that **need** corrective action as well. This week I will be focusing on getting patches out to deal with those. I am hesitant to suggest that this will, or will not, fix issues, due to the complexity of PostgreSQL memory system (contexts and caches). However, I will note that in my debugging of these memory leaks, I have found that PostgreSQL doesn't like to give back memory even after it is freed. It seems that once it gets it from the system, it may hold onto it for a while, just in case. Also, keep in mind that PostgreSQL itself will cache items if it feels caching will improve performance. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
