From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alex Balashov <abalashov@evaristesys.com>
cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Unexplained rapid growth in memory usage of idle backends
In-reply-to: <2D17E15D-8D5B-4DF7-A238-12455C2731D8@evaristesys.com>
References: <2D17E15D-8D5B-4DF7-A238-12455C2731D8@evaristesys.com>
Comments: In-reply-to Alex Balashov <abalashov@evaristesys.com>
	message dated "Fri, 12 May 2023 18:12:10 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1634072.1683942775.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 12 May 2023 21:52:55 -0400
Message-ID: <1634073.1683942775@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1634073.1683942775%40sss.pgh.pa.us>
Precedence: bulk

Alex Balashov <abalashov@evaristesys.com> writes:
> Occasionally, about once every 2 months, we'll get a slow-motion implosi=
on over a period of about 24 hours, where the resident memory size of some=
 of the backends shoots up from a reasonable few hundred MB to several gig=
s -- and will keep growing, e.g.

I'm a little suspicious that the excess memory consumption is a
consequence of JIT-compiled code not getting recycled promptly.
Do you have JIT enabled, and if so are you relying on it too much
to turn it off?

I don't have any concrete idea of why JIT code management would work
fine and then stop working fine, but we do have other reports of
memory leaks from that.

			regards, tom lane