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 ) id 1qF0L5-0000ns-Gp for pgsql-bugs@arkaria.postgresql.org; Thu, 29 Jun 2023 22:42:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qF0L3-0000kk-Pg for pgsql-bugs@arkaria.postgresql.org; Thu, 29 Jun 2023 22:42:09 +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 ) id 1qF0L3-0000kb-HA for pgsql-bugs@lists.postgresql.org; Thu, 29 Jun 2023 22:42:09 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qF0Kw-001FSH-NC for pgsql-bugs@lists.postgresql.org; Thu, 29 Jun 2023 22:42:08 +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 35TMfukm1610277; Thu, 29 Jun 2023 18:41:56 -0400 From: Tom Lane To: Andrew Dunstan cc: Andres Freund , exclusion@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm() In-reply-to: <326723ee-ee05-35bf-06fd-e4f3afc61654@dunslane.net> References: <17994-5c7100b51b4790e9@postgresql.org> <1306569.1687978174@sss.pgh.pa.us> <20230628194446.uu47f4vyfyjfl7dd@awork3.anarazel.de> <1314841.1687981948@sss.pgh.pa.us> <20230628205443.6gu5bmcck6t4pgyv@awork3.anarazel.de> <1509402.1688048784@sss.pgh.pa.us> <7ae37634-7626-8977-4d89-20603f0d1dcf@dunslane.net> <1583514.1688066735@sss.pgh.pa.us> <326723ee-ee05-35bf-06fd-e4f3afc61654@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Thu, 29 Jun 2023 16:30:21 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1610275.1688078516.1@sss.pgh.pa.us> Date: Thu, 29 Jun 2023 18:41:56 -0400 Message-ID: <1610276.1688078516@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > On 2023-06-29 Th 15:25, Tom Lane wrote: >> Maybe we should bite the bullet and provide >> invalidation based on a pg_type inval callback. > Yeah, Robert has just convinced me, so I'll do it like that. It doesn't > look too hard. Oh, I have a better idea. We're only going to need all this for pass-by-ref types, right? Why not make the hash key be the value itself? Wrap it in a bytea perhaps to avoid needing a bespoke hash function. regards, tom lane