From: Tom Lane <tgl@sss.pgh.pa.us>
To: rekgrpth@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16974: memory leak
In-reply-to: <16974-4f1a4803e727c3cf@postgresql.org>
References: <16974-4f1a4803e727c3cf@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 20 Apr 2021 10:34:47 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <523762.1618929168.1@sss.pgh.pa.us>
Date: Tue, 20 Apr 2021 10:32:48 -0400
Message-ID: <523763.1618929168@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/523763.1618929168%40sss.pgh.pa.us>
Precedence: bulk

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