Re: Hash index bucket split bug - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Hash index bucket split bug
Date
Msg-id CAH2-WznKyrDzTA+wvBYw0zbUe9f2JyUOG-Jm368Cs03sgEB_1Q@mail.gmail.com
Whole thread
In response to Re: Hash index bucket split bug  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Hash index bucket split bug
List pgsql-hackers
On Thu, Jul 9, 2026 at 6:45 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> I am getting following regression diff even after applying the patch:
> -step s1_split: <... completed>
>  step s2_scan:
>      SELECT count(*) FROM hash_split_test
>       WHERE v = (SELECT k FROM hash_split_key);
> @@ -68,3 +67,4 @@
>     11
>  (1 row)

This is just a minor test flakiness issue with the isolation test.
Apparently, we need to force a deterministic report position by adding
a no-op step to the splitter's session.

Attached v2 has a more stable version of the isolation test (no other
changes compared to V1). Does this version work for you?

The isolation test is just for illustrative purposes. I don't think
that it's committable.

--
Peter Geoghegan

Attachment

pgsql-hackers by date:

Previous
From: Paul A Jungwirth
Date:
Subject: Re: [PATCH] Fix null pointer dereference in PG19
Next
From: "Greg Burd"
Date:
Subject: Re: Tepid: selective index updates for heap relations