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 ) id 1u0DHU-00EXsd-4O for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Apr 2025 05:38:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u0DHS-003IHI-Ri for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Apr 2025 05:38:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u0DHS-003IHA-CR for pgsql-hackers@lists.postgresql.org; Thu, 03 Apr 2025 05:38:22 +0000 Received: from mail.postgrespro.ru ([93.174.132.70]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u0DHP-0036Em-2p for pgsql-hackers@lists.postgresql.org; Thu, 03 Apr 2025 05:38:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1743658698; bh=7sKRSPE0RlhksUh3vcL6RfurESoCxFRH3pIICclge3c=; h=Date:From:To:Cc:Subject:In-Reply-To:References:Message-ID:From; b=06RTTJgEEQdKPz4/9exM7lebBoHgGGkBnrc+Yufd4q0e8yKDJP2tx6Yxj4yXIZLf8 6N38uF3RvIvsL5HaXkMCZMXNCARdiYCxR+kJnPhy05FWioGDf8kxRZzJ+fPARJOzor 2psUL0uxWzCqJogajAImnLCVR4D6qvbhRnKbr5z60PMpHHWlxqIJFx9+ErLDFedTf2 jb+yJsqkRyPZZX06j89L7XDwrNeTcmR6g4znONz075Oa6ct5MDMpErJG5m7XoY0Tcd 26s3HX7CfQIKKcdR6hEB2pdeSkgWoXbI/QL6T/sTch3nDyluehkrmrLsDGBSGSgQSP umKzDKXdN9A5g== Received: from mail.postgrespro.ru (webmail-slave-mstn.l.postgrespro.ru [192.168.2.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: a.pyhalov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 7345B606B1; Thu, 3 Apr 2025 08:38:18 +0300 (MSK) MIME-Version: 1.0 Date: Thu, 03 Apr 2025 08:38:18 +0300 From: Alexander Pyhalov To: Tom Lane Cc: Pavel Stehule , Alexander Korotkov , pgsql-hackers@lists.postgresql.org, Ronan Dunklau Subject: Re: SQLFunctionCache and generic plans In-Reply-To: <1101294.1743617356@sss.pgh.pa.us> References: <8216639.NyiUUSuA9g@aivenlaptop> <3084885.1675783797@sss.pgh.pa.us> <758251661a3e8760ff52dd5c672a7505@postgrespro.ru> <30f02ca545915627905fbe3f23d93ec1@postgrespro.ru> <2275997.1737138456@sss.pgh.pa.us> <51ebc5f3b846ce279b75ac4f5e5ac33f@postgrespro.ru> <401652.1738598448@sss.pgh.pa.us> <445556.1738612687@sss.pgh.pa.us> <464677.1738620525@sss.pgh.pa.us> <1fc18af56d5fb27bf3e153ffaa2ed70d@postgrespro.ru> <2615770.1740688857@sss.pgh.pa.us> <448c63cf9b4f917c01802309b9c29eb9@postgrespro.ru> <2827970.1741890560@sss.pgh.pa.us> <337e011069b6831e063bfa346f49bb46@postgrespro.ru> <3344719.1741985546@sss.pgh.pa.us> <2691107.1743257329@sss.pgh.pa.us> <3605427.1743351017@sss.pgh.pa.us> <248291.1743463745@sss.pgh.pa.us> <1101294.1743617356@sss.pgh.pa.us> Message-ID: X-Sender: a.pyhalov@postgrespro.ru Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-KSMG-AntiPhishing: NotDetected X-KSMG-AntiSpam-Interceptor-Info: not scanned X-KSMG-AntiSpam-Status: not scanned, disabled by settings X-KSMG-AntiVirus: Kaspersky Secure Mail Gateway, version 2.1.0.7854, bases: 2025/04/03 03:59:00 #27851158 X-KSMG-AntiVirus-Status: NotDetected, skipped X-KSMG-LinksScanning: not scanned, disabled by settings X-KSMG-Message-Action: skipped X-KSMG-Rule-ID: 1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Tom Lane писал(а) 2025-04-02 21:09: > 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 Hi. I've looked through the latest patch series, but didn't have much time to examine them thoroughly. Haven't found any issue so far. From cosmetic things I've noticed - I would set func->pcontext to NULL in sql_delete_callback() to avoid dangling pointer if we error out early (but it seems only to be a matter of taste). -- Best regards, Alexander Pyhalov, Postgres Professional