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 1u02Wh-00ASjy-Ap
	for pgsql-hackers@arkaria.postgresql.org; Wed, 02 Apr 2025 18:09:23 +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 1u02Wg-00GxMp-2H
	for pgsql-hackers@arkaria.postgresql.org; Wed, 02 Apr 2025 18:09:22 +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 1u02Wf-00GxMh-Oi
	for pgsql-hackers@lists.postgresql.org; Wed, 02 Apr 2025 18:09:21 +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.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1u02Wd-002b0d-2o
	for pgsql-hackers@lists.postgresql.org;
	Wed, 02 Apr 2025 18:09:20 +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 532I9GNU1101295;
	Wed, 2 Apr 2025 14:09:17 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Pyhalov <a.pyhalov@postgrespro.ru>
cc: Pavel Stehule <pavel.stehule@gmail.com>,
        Alexander Korotkov <aekorotkov@gmail.com>,
        pgsql-hackers@lists.postgresql.org,
        Ronan Dunklau <ronan.dunklau@aiven.io>
Subject: Re: SQLFunctionCache and generic plans
In-reply-to: <248291.1743463745@sss.pgh.pa.us>
References: <8216639.NyiUUSuA9g@aivenlaptop> <3084885.1675783797@sss.pgh.pa.us> <b69515864a7021505340f85476dc111e@postgrespro.ru> <CAPpHfdue9RVJKo33jKwrCeEXec0BTTH7CTxVcyXGMbfMExaGLA@mail.gmail.com> <758251661a3e8760ff52dd5c672a7505@postgrespro.ru> <CAFj8pRCoR9B+Ap70TQqWUa0PeeEk94D6VW20YbWN2Pm4b6-JMQ@mail.gmail.com> <30f02ca545915627905fbe3f23d93ec1@postgrespro.ru> <2275997.1737138456@sss.pgh.pa.us> <ad7296dd981c5f8eb76ff129913a55fd@postgrespro.ru> <51ebc5f3b846ce279b75ac4f5e5ac33f@postgrespro.ru> <CAFj8pRD2Fa84HoH_R_S5aKngyA6a+Au7U6NyidfBMrwEjFAc9g@mail.gmail.com> <401652.1738598448@sss.pgh.pa.us> <CAFj8pRC_4gEfmDoB5KbacNDdt3e6Tnf1z1BFK=MVp3+2kcDVqw@mail.gmail.com> <CAFj8pRA7MFTfUPwDDWtghaUvAjbrMHFUPbHyLSX3h8+FDw4WFg@mail.gmail.com> <445556.1738612687@sss.pgh.pa.us> <464677.1738620525@sss.pgh.pa.us> <1fc18af56d5fb27bf3e153ffaa2ed70d@postgrespro.ru> <2615770.1740688857@sss.pgh.pa.us> <448c63cf9b4f917c01802309b9c29eb9@postgrespro.ru> <CAFj8pRDWDeF2cC+pCjLHJno7KnK5kdtjYN-f933R!
 ! ! ! ! HS7UneArFw@mail.gmail.com> <CAFj8pRD0diy5VDP=8B9au5sk_yRknCWqZx35VniBtP_OA4aJNw@mail.gmail.com> <2827970.1741890560@sss.pgh.pa.us> <337e011069b6831e063bfa346f49bb46@postgrespro.ru> <3344719.1741985546@sss.pgh.pa.us> <fcc68b0ef570160cd6e88851eb244ccd@postgrespro.ru> <db42573039cc66815e80a48589eebea8@postgrespro.ru> <2691107.1743257329@sss.pgh.pa.us> <3605427.1743351017@sss.pgh.pa.us> <248291.1743463745@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Mon, 31 Mar 2025 19:29:05 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1101293.1743617356.1@sss.pgh.pa.us>
Date: Wed, 02 Apr 2025 14:09:16 -0400
Message-ID: <1101294.1743617356@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/1101294.1743617356%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> Anyway, I feel pretty good about this patch now and am quite content
> to stop here for PG 18.

Since feature freeze is fast approaching, I did a tiny bit more
cosmetic work on this patchset and then pushed it.  (There's still
plenty of time for adjustments if you have further comments.)

Thanks for working on this!  This is something I've wanted to see
done ever since we invented plancache.

			regards, tom lane