pgsql: Add very basic test for kill_prior_tuples

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Add very basic test for kill_prior_tuples
Date: 2025-08-13 19:38:11
Message-ID: E1umHIZ-000P7e-13@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Add very basic test for kill_prior_tuples

Previously our tests did not exercise kill_prior_tuples for hash and gist. For
gist some related paths were reached, but gist's implementation seems to not
work if all the dead tuples are on one page (or something like that). The
coverage for other index types was rather incidental.

Thus add an explicit test ensuring kill_prior_tuples works at all.

Reviewed-by: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Discussion: https://postgr.es/m/lxzj26ga6ippdeunz6kuncectr5gfuugmm2ry22qu6hcx6oid6@lzx3sjsqhmt6

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/377b7ab1452418a90d6c46dcef2d4a2d4a4517af

Modified Files
--------------
src/test/isolation/expected/index-killtuples.out | 355 +++++++++++++++++++++++
src/test/isolation/isolation_schedule | 1 +
src/test/isolation/specs/index-killtuples.spec | 127 ++++++++
3 files changed, 483 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2025-08-13 20:26:59 pgsql: ci: windows: Stop using DEBUG:FASTLINK
Previous Message Tom Lane 2025-08-13 16:00:15 pgsql: Don't treat EINVAL from semget() as a hard failure.