Thomas Carroll wrote: > We have a situation where a long-persistent Postgres connection consumes more > and more memory. If ignored, we eventually get “Cannot allocate memory” > errors in the Postgres log. If still ignored, the box will eventually crash. > This takes about 3 weeks to happen. It issues a call to a single function > about once every 15 seconds. What can I do to prevent this outcome? There should be a memory context dump in the log file. What does it look like? Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com
