pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Davlet Panech <dpanech@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Abnormally high memory usage/OOM triggered
Date: Wed, 17 Jan 2018 19:15:20 -0500
Message-ID: <3138.1516234520@sss.pgh.pa.us> (raw)
In-Reply-To: <4d52fee7-73ba-16a9-9c27-8ae5107ee6ae@gmail.com>
References: <4d52fee7-73ba-16a9-9c27-8ae5107ee6ae@gmail.com>

Davlet Panech <dpanech@gmail.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




view thread (8+ messages)  latest in thread

Message-ID: <3138.1516234520@sss.pgh.pa.us>
Permalink:  ../3138.1516234520@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3138.1516234520@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, dpanech@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Abnormally high memory usage/OOM triggered
  In-Reply-To: <3138.1516234520@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox