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

From RekGRpth
Subject Re: BUG #16974: memory leak
Date
Msg-id CAPgh2mJdrPZFQF-+WyVn0tVgCO1rwkov_T1xTPosuQomtwyzXA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16974: memory leak  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #16974: memory leak  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Yes,
The backend's "SHR" memory size increase from ~20Mb on startup to
~150Mb by one day (with inserts and updates into table)

вт, 20 апр. 2021 г. в 19:32, Tom Lane <tgl@sss.pgh.pa.us>:
>
> 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: Bharath Rupireddy
Date:
Subject: Re: BUG #16972: parameter parallel_leader_participation's category problem
Next
From: Thomas Munro
Date:
Subject: Re: postgres has no spinlock support on riscv rv64imafdc