From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | rekgrpth(at)gmail(dot)com |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16974: memory leak |
Date: | 2021-04-20 14:32:48 |
Message-ID: | 523763.1618929168@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2021-04-20 15:27:29 | BUG #16975: Not able to integrate and run Pgroonga Text search module |
Previous Message | PG Bug reporting form | 2021-04-20 10:34:47 | BUG #16974: memory leak |