On Tue, 3 Feb 2026 at 23:39, Álvaro Herrera <[email protected]> wrote: > > On 2025-Apr-25, Matthias van de Meent wrote: > > > Hi, > > > > In the original thread [0] we established that GIST and SP-GiST > > support index-only scans, but don't have sufficient interlocking to > > prevent dead tuples from being revived for their scan by vacuum. > > Hello, > > This commitfest entry > https://commitfest.postgresql.org/patch/5721/ > is stale. I would have brought it forward because it's tagged as a bug > fix, but the patches look a bit intimidating to consider it a > backpatchable bug fix. So, what's the status here?
Sorry for the delay. I've finally gotten back to this patch, as it's the simpler option vs the patch in the original thread, even if it may have a higher performance impact for GIST and SP-GIST IOS scans. Attached is v02, which is a simple rebase with some language and wrapping changes in comments, as well as some fixes for assert-enabled builds. Kind regards, Matthias van de Meent Databricks (https://www.databricks.com)
v02-0002-GIST-Fix-visibility-issues-in-IOS.patch
Description: Binary data
v02-0001-Expose-visibility-checking-shim-for-index-usage.patch
Description: Binary data
v02-0003-SP-GIST-Fix-visibility-issues-in-IOS.patch
Description: Binary data
v02-0004-Test-for-IOS-Vacuum-race-conditions-in-index-AMs.patch
Description: Binary data
