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 1u7hk1-004Sl0-8g for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Apr 2025 21:34:49 +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 1u7hj0-00AZ5l-BJ for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Apr 2025 21:33:47 +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 1u7hj0-00AZ5c-13 for pgsql-hackers@lists.postgresql.org; Wed, 23 Apr 2025 21:33:46 +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 1u7hix-001fLm-1q for pgsql-hackers@lists.postgresql.org; Wed, 23 Apr 2025 21:33:46 +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 53NLXf371503202; Wed, 23 Apr 2025 17:33:41 -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: <4c2a6100-738e-48cc-8a11-2d85f95ae0ed@app.fastmail.com> <18a111db-9f31-449c-a14b-61779a69f344@app.fastmail.com> Comments: In-reply-to Nathan Bossart message dated "Wed, 23 Apr 2025 16:25:41 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1503200.1745444021.1@sss.pgh.pa.us> Date: Wed, 23 Apr 2025 17:33:41 -0400 Message-ID: <1503201.1745444021@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Nathan Bossart writes: > Here is a new version of the patch with this change. I don't see any comments in this patch that capture the real reason for removing pg_replication_origin's TOAST table, namely (IIUC) that we'd like to be able to access that catalog without a snapshot. I think it's important to record that knowledge, because otherwise somebody is likely to think they can undo this change for $whatever-reason. regards, tom lane