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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1pdyl7-0007vF-Kc
	for pgsql-hackers@arkaria.postgresql.org; Sun, 19 Mar 2023 19:32:01 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1pdyl5-0003dU-Rt
	for pgsql-hackers@arkaria.postgresql.org; Sun, 19 Mar 2023 19:31:59 +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 <pryzby@telsasoft.com>)
	id 1pdyl5-0003dK-EQ
	for pgsql-hackers@lists.postgresql.org; Sun, 19 Mar 2023 19:31:59 +0000
Received: from mail-io1-xd31.google.com ([2607:f8b0:4864:20::d31])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.92)
	(envelope-from <pryzby@telsasoft.com>)
	id 1pdyl1-0005NR-OZ
	for pgsql-hackers@lists.postgresql.org; Sun, 19 Mar 2023 19:31:58 +0000
Received: by mail-io1-xd31.google.com with SMTP id q6so4596910iot.2
        for <pgsql-hackers@lists.postgresql.org>;
 Sun, 19 Mar 2023 12:31:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=telsasoft-com.20210112.gappssmtp.com; s=20210112; t=1679254313;
        h=in-reply-to:content-disposition:mime-version:references:message-id
         :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to;
        bh=CoJ6ZjUPxV2ubzNjiNcGUiH55CbX7k86eUtDnhmwE1k=;
        b=Qz3+vwT3EwqsLBLyeESHuJ5Rty1+RkTWU9puual7TQ7T4zV2fwOspmhemX1W1xwulG
         pOImL9H5kwgYcXheE0HCDqI+FM7gZT1tY72WCVl/6sIcGe4UgXAn4zFZAkNgefKSEI/v
         DpmnShp+bDXKkVs8p4CuAX0025qxzG6GOVSCbBC9C/Vc0W6pBNVvrab4a3LRg0ZurA14
         eUAHbLCnyN/gQzqhUUls2szKNBrEP8DofOMHpo6Hr+CRQeagArT44rcBLqxgRjlZJBBd
         jFsyYfXb7nfScBowEFaFskoPgPq7zvh0lYIb3MS+w3oG+ZrLQhjhThlhOecapWDi+JHf
         H89w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112; t=1679254313;
        h=in-reply-to:content-disposition:mime-version:references:message-id
         :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date
         :message-id:reply-to;
        bh=CoJ6ZjUPxV2ubzNjiNcGUiH55CbX7k86eUtDnhmwE1k=;
        b=5iqePyXS8+KWLMAxl3Mxsket5XXkrCk7wIxidsTGk+p+DAY4miaPQMajXROJks5FZA
         tk5Oj0n690LrLv0O3hUXEUDzjREJgYPp5Mq4NvkBVc/f848FGfwGsqXwPuYrwnsbFLmt
         oZA1x8rDMVxbUa+j2j3nzuEfDGQl98OoY+FwSAZR1YaT7ZQ1clQd+mxriksM46/rqjk1
         Py+cVHJtZWS2IMPfd+MG794ECkzPF9Boe2KTUju3GnFUERCMUUwuv0gEiAkYiOlj2Arx
         98QlJ7OiEuaY9PpzDvzY8kodNIxN/UMHqDYVK3c7vaIC5ewO7eUJbZwOCVRCnq3dogPi
         X6mQ==
X-Gm-Message-State: AO0yUKVe+l6RdyzEtwqEZPhbRIl5qfhlhX/l89ZKkj2ZySNf9WFnCcZE
	fahKLqHpZujo3Yet2oldaKOd+g==
X-Google-Smtp-Source: 
 AK7set8ClAAmbV3tH9KiAALRIv5kmoBiqIv+4s4n1ZvkIaeQtxXE3+LDeLWjSnLI8wwSeih8JTXS4A==
X-Received: by 2002:a5d:9a98:0:b0:752:e2e8:e558 with SMTP id
 c24-20020a5d9a98000000b00752e2e8e558mr3667518iom.15.1679254313253;
        Sun, 19 Mar 2023 12:31:53 -0700 (PDT)
Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1])
        by smtp.gmail.com with ESMTPSA id
 e4-20020a5ede04000000b00746c717e922sm2325604iok.43.2023.03.19.12.31.52
        (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
        Sun, 19 Mar 2023 12:31:52 -0700 (PDT)
Received: by pryzbyj.telsasoft (Postfix, from userid 1000)
	id CE55B800BC8; Sun, 19 Mar 2023 14:31:51 -0500 (CDT)
Date: Sun, 19 Mar 2023 14:31:51 -0500
From: Justin Pryzby <pryzby@telsasoft.com>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>,
	pgsql-hackers@lists.postgresql.org,
	Melanie Plageman <melanieplageman@gmail.com>
Subject: Re: Memory leak from ExecutorState context?
Message-ID: <ZBdjJ8l3CNmBZUg0@telsasoft.com>
References: <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>
 <dbae24d7-0dda-18aa-5e08-8138ac1caef9@enterprisedb.com>
 <20230310195114.6d0c5406@karst>
 <20230317091834.22e97642@karst>
 <ae017eef-79d5-fcd6-b865-b7e55ac5290b@enterprisedb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ae017eef-79d5-fcd6-b865-b7e55ac5290b@enterprisedb.com>
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/ZBdjJ8l3CNmBZUg0%40telsasoft.com>
Precedence: bulk

On Fri, Mar 17, 2023 at 05:41:11PM +0100, Tomas Vondra wrote:
> >> * Patch 2 is worth considering to backpatch
> 
> I'm not quite sure what exactly are the numbered patches, as some of the
> threads had a number of different patch ideas, and I'm not sure which
> one was/is the most promising one.

patch 2 is referring to the list of patches that was compiled
https://www.postgresql.org/message-id/20230310195114.6d0c5406%40karst