Re: Bug in nbtree optimization to skip > operator comparisons (or < comparisons in backwards scans)
Alexander Korotkov <aekorotkov@gmail.com>
From: Alexander Korotkov <aekorotkov@gmail.com>
To: Maxim Orlov <orlovmg@gmail.com>
Cc: "Anton A. Melnikov" <a.melnikov@postgrespro.ru>,
Pavel Borisov <pashkin.elfe@gmail.com>, Peter Geoghegan <pg@bowt.ie>, Heikki Linnakangas <hlinnaka@iki.fi>, Matthias van de Meent <boekewurm+postgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-03-22T13:26:47Z
Lists: pgsql-hackers
On Fri, Mar 22, 2024 at 11:58 AM Maxim Orlov <orlovmg@gmail.com> wrote: > I've noticed this patch and had a quick look at it. As far as I understand, this bug > does not lead to an incorrect matching, resulting only in degradation in speed. > Anyway, consider this patch useful, hope it will be committed soon. Pushed. Thanks to Maxim and Pavel. ------ Regards, Alexander Korotkov
Commits
-
Fix an oversight in refactoring in 06b10f80ba4.
- b670b93a66fc 17.0 landed
-
Make RangeTblEntry dump order consistent
- b4080fa3dcf6 17.0 cited
-
Improvements and fixes for e0b1ee17dc
- 7e6fb5da41d8 17.0 landed
-
Remove BTScanOpaqueData.firstPage
- 06b10f80ba4d 17.0 landed
-
Optimize nbtree backward scan boundary cases.
- c9c0589fda0e 17.0 cited
-
Skip checking of scan keys required for directional scan in B-tree
- e0b1ee17dc3a 17.0 cited