| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm() |
| Date: | 2023-06-30 18:43:20 |
| Message-ID: | e56b9c00-291b-dac0-6260-74137fdaffa5@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2023-06-30 Fr 09:43, Tom Lane wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-06-30 19:08:05 | Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm() |
| Previous Message | Chandy G | 2023-06-30 17:10:25 | Toasted column values during replication. (Enhancement) |