On Wed, Mar 25, 2026, at 1:16 PM, Nathan Bossart wrote:
> I just spoke to Greg off-list and wanted to share my current thoughts on
> the list as well. In short, while we feel that the patch is in decent
> shape and seems to be performance neutral (or maybe even positive in some
> cases), it obviously doesn't accomplish $subject, and only a couple of
> folks have looked at it in depth. Furthermore, if this patch was committed
> and someone did find a problem, it'd be hard to justify anything except a
> revert. So, it's probably better to keep working on the full patch set and
> try to get $subject committed much earlier in the development cycle.
Thanks Nathan,
I 100% agree with that.
As I think about this thread and the current patch vs the goals in $subject, it's just not there yet. There are no
changesin the v38 set that enable HOT updates in new cases. What is in the v38 patch set is solid and does what it
claimsto do, has no performance regressions (I can find) and in cases where UPDATEs target many rows shows a
performanceimprovement, but is that enough? More so, is now the right time? It's the end of the development cycle and
we'reabout to freeze so I think the answer is obviously no.
I do have more of the work nearly ready to layer back on top of this the changes to HOT for expression indexes (and
more). And I'm confident that given the chance PHOT could layer on top of this as well. But those are not done yet.
:)
> If someone thinks that we should seriously consider committing this for
> v19, please let us know.
/me eats popcorn and waits for anyone interested to chime in...
> --
> nathan
If no one chimes in then I'll get this in shape for the first commit fest of the next cycle. :)
best.
-greg
