Re: GiST wal_consistency_checking issue

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: GiST wal_consistency_checking issue
Date: 2026-08-16 00:15:23
Message-ID: CAH2-Wzm+e-soPqiPOCU7rqp=-gVukEs8eaXJbF6t_w8xKjrtgw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Aug 15, 2026 at 7:53 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> 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.

We already have test coverage for LP_DEAD marking GiST index tuples in
src/test/modules/index/specs/killtuples.spec (plus coverage for all
other index AMs that support this optimization). What we lack is test
coverage for the code that deals with subsequent deletion of those
LP_DEAD-marked tuples by gistprunepage (and so gistRedoDeleteRecord,
its REDO routine, also isn't tested).

Attached v2 adds this missing test coverage.

I verified that hash already has the same coverage for its
corresponding deletion routines.

--
Peter Geoghegan

Attachment Content-Type Size
v2-0001-GiST-Deprecate-F_TUPLES_DELETED.patch application/octet-stream 5.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2026-08-16 00:21:00 Re: Add a pg_wal_preallocate() SQL function to eagerly create future WAL segments
Previous Message Michael Paquier 2026-08-15 23:53:10 Re: GiST wal_consistency_checking issue