Re: Recovering from detoast-related catcache invalidations - Mailing list pgsql-hackers

From Xiaoran Wang
Subject Re: Recovering from detoast-related catcache invalidations
Date
Msg-id CAGjhLkMN1ZnYdyhmHxBtXV9=QhRCEQR=TQecibC1Y9uT0aytqA@mail.gmail.com
Whole thread Raw
In response to Re: Recovering from detoast-related catcache invalidations  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Recovering from detoast-related catcache invalidations
List pgsql-hackers
Great! That's what exactly we need.

The patch LGTM,  +1


Tom Lane <tgl@sss.pgh.pa.us> 于2024年1月13日周六 04:47写道:
I wrote:
> This is uncomfortably much in bed with the tuple table slot code,
> perhaps, but I don't see a way to do it more cleanly unless we want
> to add some new provisions to that API.  Andres, do you have any
> thoughts about that?

Oh!  After nosing around a bit more I remembered systable_recheck_tuple,
which is meant for exactly this purpose.  So v4 attached.

                        regards, tom lane

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Synchronizing slots from primary to standby
Next
From: Pavel Stehule
Date:
Subject: Re: plpgsql memory leaks