simovesterinen81

Both reasons: OOM sometimes happen when there are multiple users and simultnious delete&load&query. The Get-query gets somehow infinite loop --> takes long time--> builds memory --> oom killer. The query...

No. It's a production environment. We are not able to reproduce this in development env. Maybe I could create the needed locking by using advisory locks.

Could there be better exception hanlind in IMCS side so that if OOM killer happens it would not restart the postgres server? It's a problem for us because we need...