Re: Ignoring BRIN for HOT updates (was: -udpates seems broken)

Tomas Vondra <tomas.vondra@enterprisedb.com>

From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-03-20T10:11:27Z
Lists: pgsql-hackers
On 3/14/23 15:41, Matthias van de Meent wrote:
> On Tue, 14 Mar 2023 at 14:49, Tomas Vondra
> <tomas.vondra@enterprisedb.com> wrote:
>>
>>> ...
> 
>> If you agree with these changes, I'll get it committed.
> 
> Yes, thanks!
> 

I've tweaked the patch per the last round of comments, cleaned up the
commit message a bit (it still talked about unused bit in tuple header
and so on), and pushed it.

Thanks for fixing the issues that got the patch reverted last year!


regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Ignore BRIN indexes when checking for HOT updates

  2. Revert changes in HOT handling of BRIN indexes

  3. Ignore BRIN indexes when checking for HOT udpates