Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
Дата
Msg-id 5316ba5d-ab3b-4ae2-6f6b-f22760932d99@dunslane.net
обсуждение исходный текст
Ответ на Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs


On 2023-06-29 Th 18:41, Tom Lane wrote:
Andrew Dunstan <andrew@dunslane.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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #18008: SSL certificate error for Stackbuilder 4.2.1
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()