From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Improve nbtree skip scan primitive scan scheduling. |
Date: | 2025-04-27 17:06:22 |
Message-ID: | CAHgHdKuWD2h3n6MHv2SOp8VLcKsKM1R+tLBHZrnE_WDOmDaqPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Sat, Apr 26, 2025 at 8:53 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Sat, Apr 26, 2025 at 10:39 PM Mark Dilger
> <mark(dot)dilger(at)enterprisedb(dot)com> wrote:
> > Peter, Matthias, thanks kindly for the good work on skipscans!
>
> Thanks!
>
> > I found a test case which fails after commit
> 21a152b37f36c9563d1b0b058fe1436baf578b4c. Please find a reproducible test
> case, attached.
>
> The bug isn't actually in commit
> 21a152b37f36c9563d1b0b058fe1436baf578b4c -- it's just an accident that
> the mechanism added by that commit happens to make your test case
> fail. The underlying issue was introduced in commit 8a510275, "Further
> optimize nbtree search scan key comparisons".
>
> This looks to have been a silly oversight in our handling of NULL
> tuple datums within _bt_check_compare. Attached provisional fix makes
> your test case pass.
>
> --
> Peter Geoghegan
>
I can confirm that your patch fixes the problem, having spent some four
hours trying to find other test cases which still fail, finding none.
Thank you for the quick reply, and again for the work on btree.
--
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-04-27 17:23:25 | pgsql: Don't use double-quotes in #include's of system headers, redux. |
Previous Message | Peter Geoghegan | 2025-04-27 15:50:02 | Re: clang-tidy complaints |