| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Thomas Carroll <tomfecarroll(at)yahoo(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Memory exhaustion due to temporary tables? |
| Date: | 2018-12-10 20:04:41 |
| Message-ID: | 5039683d856d06b9cbfe20da029e274216558b26.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-12-10 20:45:27 | Re: Memory exhaustion due to temporary tables? |
| Previous Message | Thomas Carroll | 2018-12-10 19:26:36 | Memory exhaustion due to temporary tables? |