Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pd5Jj-0006Bn-QZ for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Mar 2023 08:20:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pd5Ji-0002xf-8b for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Mar 2023 08:20:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pd5Jh-0002xV-Tu for pgsql-hackers@lists.postgresql.org; Fri, 17 Mar 2023 08:20:01 +0000 Received: from mail1.dalibo.net ([51.159.93.128] helo=mail.dalibo.com) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pd5Jb-0003LE-9n for pgsql-hackers@lists.postgresql.org; Fri, 17 Mar 2023 08:20:01 +0000 Received: from karst (larco.ioguix.net [78.202.0.6]) by mail.dalibo.com (Postfix) with ESMTPSA id 205F2201ED; Fri, 17 Mar 2023 09:18:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dalibo.com; s=a; t=1679041115; bh=07b70f8R2QOQZWDHTkNIZpvgYHA5+Nsw5jqxdLRF4fs=; h=Date:From:To:Subject:In-Reply-To:References:From; b=Oeq+MjbMllJ8ZFkU5R1sYkIUHxazHe3y9zHWfywig9dkOYKQvSdI56hWw9ma6ax71 AMpkchRa2slUGZo07Tc1F5tMQ+n85Ai7Ll4UbNmNt4ErjWSuirx8vVlNIHLbR0JuAo hJ+HSBocC67Eo1+x/UZXRwPN8JRrwF2y+grBIPEk= Date: Fri, 17 Mar 2023 09:18:34 +0100 From: Jehan-Guillaume de Rorthais To: pgsql-hackers@lists.postgresql.org, Tomas Vondra , Melanie Plageman Subject: Re: Memory leak from ExecutorState context? Message-ID: <20230317091834.22e97642@karst> In-Reply-To: <20230310195114.6d0c5406@karst> References: <20230228190643.1e368315@karst> <45d453c8-b2d3-b477-36eb-32fdf4455f3c@enterprisedb.com> <20230301184840.0a897a80@karst> <3013398b-316c-638f-2a73-3783e8e2ef02@enterprisedb.com> <20230302001827.66e95dc3@karst> <41c5766d-ed71-b70c-bbbc-d3396c462d62@enterprisedb.com> <20230302130838.717e888d@karst> <77a96d42-00cb-2448-465a-aa1e92d00cac@enterprisedb.com> <20230302191530.781909fe@karst> <20230310195114.6d0c5406@karst> Organization: Dalibo MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi there, On Fri, 10 Mar 2023 19:51:14 +0100 Jehan-Guillaume de Rorthais wrote: > > So I guess the best thing would be to go through these threads, see what > > the status is, restart the discussion and propose what to do. If you do > > that, I'm happy to rebase the patches, and maybe see if I could improve > > them in some way. > > [...] > > > I was hoping we'd solve this by the BNL, but if we didn't get that in 4 > > years, maybe we shouldn't stall and get at least an imperfect stop-gap > > solution ... > > Indeed. So, to sum-up: > > * Patch 1 could be rebased/applied/backpatched Would it help if I rebase Patch 1 ("move BufFile stuff into separate context")? > * Patch 2 is worth considering to backpatch Same question. > * Patch 3 seemed withdrawn in favor of BNLJ > * Patch 4 is waiting for some more review and has some TODO > * discussion 5 worth few minutes to discuss before jumping on previous topics These other patches needs more discussions and hacking. They have a low priority compare to other discussions and running commitfest. However, how can avoid losing them in limbo again? Regards,