Re: BUG #16707: Memory leak - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16707: Memory leak
Date
Msg-id 2002012.1604960437@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #16707: Memory leak  (Kurt Roeckx <kurt@roeckx.be>)
Responses Re: BUG #16707: Memory leak
Re: BUG #16707: Memory leak
List pgsql-bugs
Kurt Roeckx <kurt@roeckx.be> writes:
> On Mon, Nov 09, 2020 at 04:34:33PM -0500, Tom Lane wrote:
>> * look in postmaster log for memory dump

> ...
> Grand total: 3575000 bytes in 533 blocks; 596232 free (450 chunks); 2978768 used

> Which was for this process:
> USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
> postgres 10000  2.6 16.3 5547172 5374656 ?     Ss   Nov08  54:10 postgres: synapse synapse [local] idle

Hm.  It would seem that whatever you're leaking was not allocated via
palloc.  Have you got any extensions loaded into that backend?

It's also worth noting that if you've got 4GB of shared buffers,
a total process vsize of 5.3GB doesn't seem all that far out of
line.  I'm not quite convinced that you have a leak at all,
as opposed to processes gradually touching more and more of the
shared buffer arena.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Kurt Roeckx
Date:
Subject: Re: BUG #16707: Memory leak
Next
From: "Burgess, Freddie"
Date:
Subject: Re: pg_dump error attempting to upgrade from PostgreSQL 10 to PostgreSQL 12