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 1u9pHO-006kly-AJ for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Apr 2025 18:02:02 +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 1u9pHM-009B1z-75 for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Apr 2025 18:02:01 +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 1u9pHL-009B1r-TZ for pgsql-hackers@lists.postgresql.org; Tue, 29 Apr 2025 18:02:00 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u9pHL-000Dpz-0B for pgsql-hackers@lists.postgresql.org; Tue, 29 Apr 2025 18:02:00 +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 53TI1sqc1055454; Tue, 29 Apr 2025 14:01:54 -0400 From: Tom Lane To: Nathan Bossart cc: Nisha Moond , Euler Taveira , Michael Paquier , Amit Kapila , Alexander Lakhin , "Jonathan S. Katz" , PostgreSQL Hackers Subject: Re: Large expressions in indexes can't be stored (non-TOASTable) In-reply-to: References: <1503201.1745444021@sss.pgh.pa.us> <905635.1745876108@sss.pgh.pa.us> <910625.1745878759@sss.pgh.pa.us> Comments: In-reply-to Nathan Bossart message dated "Tue, 29 Apr 2025 12:39:58 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1055452.1745949714.1@sss.pgh.pa.us> Date: Tue, 29 Apr 2025 14:01:54 -0400 Message-ID: <1055453.1745949714@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Nathan Bossart writes: > Thanks. I'll stash this away for July unless someone wants to argue that > it's fair game for v18. IMHO this isn't nearly urgent enough for that, and > the bugs will continue to exist on older major versions regardless. I'm inclined to argue that it's a bug fix and therefore still in-scope for v18. The fact that we can't back-patch such a change is all the more reason to not let it slide another year. But probably the RMT should make the call. regards, tom lane