On Tue, Aug 11, 2026 at 3:29 AM Adam Brusselback <[email protected]> wrote: > +1 on the change. I have the same thing in the REFRESH ... WHERE patch > [1], so I'd like to see it go in on its own. > > One thing worth adding to the justification: the dead tuple isn't the > only cost. The CatalogTupleUpdate() also sends an SI message, so every > call invalidates the relcache entry for the MV in every backend, > including the caller's own, and that discards cached plans referencing > it. On an MV that gets refreshed often and is already populated, the > repeated invalidation costs more than the dead tuple does.
Thanks for the review and for sharing your analysis! I've pushed the patch. Regards, -- Fujii Masao
