Re: Recovering from detoast-related catcache invalidations

From: Xiaoran Wang <fanfuxiaoran(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Recovering from detoast-related catcache invalidations
Date: 2024-01-13 05:16:52
Message-ID: CAGjhLkMN1ZnYdyhmHxBtXV9=QhRCEQR=TQecibC1Y9uT0aytqA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Great! That's what exactly we need.

The patch LGTM, +1

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2024-01-13 05:25:04 Re: plpgsql memory leaks
Previous Message Amit Kapila 2024-01-13 04:35:52 Re: Synchronizing slots from primary to standby