Re: Expanding HOT updates for expression and partial indexes - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Expanding HOT updates for expression and partial indexes
Date
Msg-id 3fba3f5671eddb221ba38f5a12acbe7cad27edf3.camel@j-davis.com
Whole thread Raw
In response to Re: Expanding HOT updates for expression and partial indexes  ("Greg Burd" <greg@burd.me>)
Responses Re: Expanding HOT updates for expression and partial indexes
List pgsql-hackers
On Mon, 2026-03-16 at 14:35 -0400, Greg Burd wrote:
> Now I want to rename ExecGetAllUpdatedCols() to
> ExecUpdateTargetedCols(), maybe I will.  And while I'm at it I'll
> change the single non-trigger use case in index_unchanged_by_update()
> to my new ExecUpdateTargetedCols() function which better matches that
> use anyway.

Does this mean a new bitmap of "actually changed values" that's a
subset of targeted columns?

If so it feels like quite a few bitmaps and we might need to expand
some comments to explain the subtle meanings of each, and when they are
valid, and what kinds of false positives they might contain (hopefully
none have false negatives).

Also, the "actually changed values" is only valid for a single tuple,
and it would be good to clarify that and make sure there's not a lot of
room for confusion there.

Regards,
    Jeff Davis





pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: Improve OAuth discovery logging
Next
From: Corey Huinker
Date:
Subject: Re: Add starelid, attnum to pg_stats and leverage this in pg_dump