Re: GiST wal_consistency_checking issue

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: GiST wal_consistency_checking issue
Date: 2026-08-15 23:53:10
Message-ID: aoD75uijRV-oATBu@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Aug 15, 2026 at 07:31:01PM -0400, Peter Geoghegan wrote:
> The purpose of XLOG_GIST_DELETE relates in some way to old style
> VACUUM FULL. It's obviously useless now: there are 3 places that set
> F_TUPLES_DELETED, but nothing ever tests whether it is set in any GiST
> page's opaque area's flags field (barring pageinspect).
>
> Attached patch marks F_TUPLES_DELETED deprecated, removes all of its
> helper function-style macros, and removes all remaining callers of
> those macros.

batta tests wal_consistency_checking (maybe it's the only buildfarm
member doing so), and did not detect anything:
https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=batta&br=master

Your patch is not adding any tests, and I am pretty sure that recovery
test 027 would fail because standbys stop on an inconsistency.

Shouldn't the tests be expanded in some way, then? Your patch does
not do any of that. You could hide an extra expensive test script
under a conditional wal_consistency_checking, for example.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2026-08-16 00:15:23 Re: GiST wal_consistency_checking issue
Previous Message Michael Paquier 2026-08-15 23:50:08 Re: gistkillitems can LP_DEAD-mark the wrong tuples on a rescan