| 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 12:11:27 |
| Message-ID: | 5316ba5d-ab3b-4ae2-6f6b-f22760932d99@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2023-06-29 Th 18:41, Tom Lane wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)net> 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?
Yes, the value we get back for byval types isn't a pointer that might
disappear.
> Why not make the hash key be the value
> itself? Wrap it in a bytea perhaps to avoid needing a bespoke
> hash function.
>
>
Not sure I understand.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2023-06-30 12:13:10 | Re: BUG #17946: LC_MONETARY & DO LANGUAGE plperl - BUG |
| Previous Message | PG Bug reporting form | 2023-06-30 09:44:58 | BUG #18008: SSL certificate error for Stackbuilder 4.2.1 |