pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: RekGRpth <rekgrpth@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16974: memory leak
Date: Wed, 21 Apr 2021 09:27:06 -0400
Message-ID: <755577.1619011626@sss.pgh.pa.us> (raw)
In-Reply-To: <CAPgh2mJdrPZFQF-+WyVn0tVgCO1rwkov_T1xTPosuQomtwyzXA@mail.gmail.com>
References: <16974-4f1a4803e727c3cf@postgresql.org>
	<523763.1618929168@sss.pgh.pa.us>
	<CAPgh2mJdrPZFQF-+WyVn0tVgCO1rwkov_T1xTPosuQomtwyzXA@mail.gmail.com>

RekGRpth <rekgrpth@gmail.com> writes:
> The backend's "SHR" memory size increase from ~20Mb on startup to
> ~150Mb by one day (with inserts and updates into table)

As I said, that proves little and indeed is expected ... especially
if your shared_buffers setting is around that.  There's no leak
unless you see VIRT increasing significantly.

			regards, tom lane





view thread (5+ messages)  latest in thread

Message-ID: <755577.1619011626@sss.pgh.pa.us>
Permalink:  ../755577.1619011626@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/755577.1619011626@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-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, rekgrpth@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16974: memory leak
  In-Reply-To: <755577.1619011626@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