Re: Recovering from detoast-related catcache invalidations
| От | Noah Misch |
|---|---|
| Тема | Re: Recovering from detoast-related catcache invalidations |
| Дата | |
| Msg-id | 20240924212036.0a.nmisch@google.com обсуждение исходный текст |
| Ответ на | Re: Recovering from detoast-related catcache invalidations (Noah Misch <noah@leadboat.com>) |
| Ответы |
Re: Recovering from detoast-related catcache invalidations
|
| Список | pgsql-hackers |
On Sun, Jan 14, 2024 at 12:14:11PM -0800, Noah Misch wrote: > On Fri, Jan 12, 2024 at 03:47:13PM -0500, Tom Lane wrote: > > Oh! After nosing around a bit more I remembered systable_recheck_tuple, > > which is meant for exactly this purpose. So v4 attached. > > systable_recheck_tuple() is blind to heap_inplace_update(), so it's not a > general proxy for invalidation messages. The commit for $SUBJECT (ad98fb1) > doesn't create any new malfunctions, but I expect the systable_recheck_tuple() > part will change again before the heap_inplace_update() story is over > (https://postgr.es/m/flat/CAMp+ueZQz3yDk7qg42hk6-9gxniYbp-=bG2mgqecErqR5gGGOA@mail.gmail.com). Commit f9f47f0 (2024-06-27) addressed inplace updates here.
В списке pgsql-hackers по дате отправления: