Re: BUG #16974: memory leak - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16974: memory leak
Date
Msg-id 523763.1618929168@sss.pgh.pa.us
Whole thread Raw
In response to BUG #16974: memory leak  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16974: memory leak  (RekGRpth <rekgrpth@gmail.com>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16974: memory leak
Next
From: PG Bug reporting form
Date:
Subject: BUG #16975: Not able to integrate and run Pgroonga Text search module