| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Donghang Lin <donghanglin(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, benoit <benoit(at)hopsandfork(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Subject: | Re: Optimizing nbtree ScalarArrayOp execution, allowing multi-column ordered scans, skip scan |
| Date: | 2024-04-18 15:50:53 |
| Message-ID: | CAH2-WznnEQfsR4CH34Wh3UGR2Y00N2n6GBCcWTOKOWct2MpP+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 18, 2024 at 2:13 AM Donghang Lin <donghanglin(at)gmail(dot)com> wrote:
> It's triggered when a scankey's strategy is set to invalid. While for a descending ordered column,
> the strategy needs to get fixed to its commute strategy. That doesn't work if the strategy is invalid.
The problem is that _bt_fix_scankey_strategy shouldn't have been doing
anything with already-eliminated array scan keys in the first place
(whether or not they're on a DESC index column). I just pushed a fix
along those lines.
Thanks for the report!
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2024-04-18 15:57:40 | PostgreSQL 17 Beta 1 release date |
| Previous Message | Alvaro Herrera | 2024-04-18 15:39:31 | Re: pgsql: Fix restore of not-null constraints with inheritance |