| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Davlet Panech <dpanech(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Abnormally high memory usage/OOM triggered |
| Date: | 2018-01-18 00:15:20 |
| Message-ID: | 3138.1516234520@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Davlet Panech <dpanech(at)gmail(dot)com> writes:
> I'm troubleshooting a problem with a Postgres installation (Linux): a
> client process got killed by OOM while executing an update statement,
> Is there a memory leak in there somewhere?
> I'm using Postgres 9.4.8 on x86_64-redhat-linux-gnu with 16GB of
> physical RAM and 8GB of swap space.
I see a possibly relevant entry in the 9.4.10 release notes:
Fix query-lifespan memory leak in a bulk UPDATE on a table
with a PRIMARY KEY or REPLICA IDENTITY index
Looking at the relevant commit (ae4760d66), it seems the leak was
just a few bytes per row, but if the update touches enough rows ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashwani Kumar B | 2018-01-18 09:31:51 | Starting Postgre DB in read write mode |
| Previous Message | scott ribe | 2018-01-17 22:57:33 | Re: Abnormally high memory usage/OOM triggered |