Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm() - Mailing list pgsql-bugs

From Andrew Dunstan
Subject Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
Date
Msg-id e56b9c00-291b-dac0-6260-74137fdaffa5@dunslane.net
Whole thread Raw
In response to Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs


On 2023-06-30 Fr 09:43, Tom Lane wrote:
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.)
			


Me either. I think this might call for too much invention so I'm going to revert to plan A. The invalidation code won't be very much, and it should be a fairly rare event, so it doesn't need to be very clever.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: Chandy G
Date:
Subject: Toasted column values during replication. (Enhancement)
Next
From: Tom Lane
Date:
Subject: Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()