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 <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1qFEPN-0003wX-QI
	for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Jun 2023 13:43:33 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1qFEPM-000432-BE
	for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Jun 2023 13:43:32 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1qFEPM-00042t-2t
	for pgsql-bugs@lists.postgresql.org; Fri, 30 Jun 2023 13:43:32 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.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 1qFEPJ-001HtR-OS
	for pgsql-bugs@lists.postgresql.org; Fri, 30 Jun 2023 13:43:30 +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 35UDhOlM1749276;
	Fri, 30 Jun 2023 09:43:24 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
cc: Andres Freund <andres@anarazel.de>, exclusion@gmail.com,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17994: Invalidating relcache corrupts tupDesc inside
 ExecEvalFieldStoreDeForm()
In-reply-to: <cf24e075-0809-b9b8-4c73-48eed105b9a9@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>
 <e52f6028-7196-8545-9726-a17a50ea14a3@dunslane.net>
 <e6cbff03-32c3-4048-78b6-54d2907ba852@dunslane.net>
 <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>
 <1610276.1688078516@sss.pgh.pa.us>
 <5316ba5d-ab3b-4ae2-6f6b-f22760932d99@dunslane.net>
 <1742513.1688129204@sss.pgh.pa.us>
 <cf24e075-0809-b9b8-4c73-48eed105b9a9@dunslane.net>
Comments: In-reply-to Andrew Dunstan <andrew@dunslane.net>
	message dated "Fri, 30 Jun 2023 09:23:13 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1749274.1688132604.1@sss.pgh.pa.us>
Date: Fri, 30 Jun 2023 09:43:24 -0400
Message-ID: <1749275.1688132604@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/1749275.1688132604%40sss.pgh.pa.us>
Precedence: bulk

Andrew Dunstan <andrew@dunslane.net> writes:
> OK, I get it. Do we have a routine to wrap a Datum in a bytea, or do I 
> need to write one?

I don't recall that functionality being exported anywhere,
but it'd only be a couple lines of code in any case.

(Whether it's actually worth doing, I'm not sure about.
It only helps if it lets you use existing hashtable support
routines, but I'm not quite sure that any of those exist
for bytea either.)

			regards, tom lane