Re: BUG #16707: Memory leak
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kurt Roeckx <kurt@roeckx.be>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2020-11-09T22:20:37Z
Lists: 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
Commits
-
llvmjit: Use explicit LLVMContextRef for inlining
- 3b991f81c457 12.18 landed
- 10912f7d4ff0 13.14 landed
- 75a20a4b4b44 14.11 landed
- aef521849b68 15.6 landed
- 2cf50585e54a 16.2 landed
- 9dce22033d5d 17.0 landed