Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1rOP2U-003sa1-Qk
	for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Jan 2024 21:26:07 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1rOP2S-005irF-Vg
	for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Jan 2024 21:26:04 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1rOP2S-005ipx-L2
	for pgsql-hackers@lists.postgresql.org; Fri, 12 Jan 2024 21:26:04 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1rOP2L-001F1d-RE
	for pgsql-hackers@postgresql.org; Fri, 12 Jan 2024 21:26:03 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 40CLPrJk810951;
	Fri, 12 Jan 2024 16:25:53 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
cc: Michael Banck <mbanck@gmx.net>,
        PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: plpgsql memory leaks
In-reply-to: <CAFj8pRCMjozEaBxuLRXB50CYkPoui4WtbX6XaRKvOYPp+76Zcg@mail.gmail.com>
References: <CAFj8pRCWZBS4pXSZd8ibsSivVkzsUn1d8eX0y4jOYmRB+Cw2yg@mail.gmail.com> <CAFj8pRATsUvX0j8g9GcXC8N_9w-igEwuBqjAcbrZhL8Jq6uDZw@mail.gmail.com> <65a11a66.170a0220.fd97.5da6@mx.google.com> <CAFj8pRB132dKbwZtdEZtxnzXmEW9qrOmnuEpk2rxm9V3fpDFcw@mail.gmail.com> <65a14469.050a0220.fead0.7c6d@mx.google.com> <CAFj8pRCMjozEaBxuLRXB50CYkPoui4WtbX6XaRKvOYPp+76Zcg@mail.gmail.com>
Comments: In-reply-to Pavel Stehule <pavel.stehule@gmail.com>
	message dated "Fri, 12 Jan 2024 20:09:14 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <810949.1705094753.1@sss.pgh.pa.us>
Date: Fri, 12 Jan 2024 16:25:53 -0500
Message-ID: <810950.1705094753@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: <https://www.postgresql.org/message-id/810950.1705094753%40sss.pgh.pa.us>
Precedence: bulk

Pavel Stehule <pavel.stehule@gmail.com> writes:
> default master branch - res 190MB ram
> jit_inline_above_cost = -1 doesn't helps
> disabling JIT doesn't helps too,

> so it looks like the wrong hypothesis , and the problem is maybe somewhere
> else :-/

I see no leak with these examples on HEAD, either with or without
--enable-llvm --- the process size stays quite stable according
to "top".  I wonder if you are using some extension that's
contributing to the problem.

			regards, tom lane