From: Tom Lane <tgl@sss.pgh.pa.us>
To: rekgrpth@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16974: memory leak
Date: Tue, 20 Apr 2021 10:32:48 -0400
Message-ID: <523763.1618929168@sss.pgh.pa.us> (raw)
In-Reply-To: <16974-4f1a4803e727c3cf@postgresql.org>
References: <16974-4f1a4803e727c3cf@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> ...
> 7) in opened psql execute above two files periodically
> \i sql/update.sql
> \i sql/timeout.sql
> 8) the memory (using by corresponded postgres backend) is increasing
> constantly
I tried this, and I don't see any evidence of a leak, not even
after I inserted some data into "task" so that the queries were
actually doing something.
The backend's "SHR" memory size will increase for awhile, but
that's just evidence of it touching more and more of the shared
buffer pool over time. The total virtual memory size ("VIRT"
column in top) is rock-solid steady, so there's no actual
accumulation of leaked memory.
Perhaps there's an issue here somewhere, but if so, you haven't
given a sufficient description of how to reproduce it.
regards, tom lane
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: <523763.1618929168@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