Re: Remove extra Sort node above a btree-compatible Index Scan

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Alexandra Wang <alexandra(dot)wang(dot)oss(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove extra Sort node above a btree-compatible Index Scan
Date: 2025-02-28 05:30:54
Message-ID: CAH2-WzmiiZ6214VRrhFMbvc-AOTJxxOjP0m4OYxLEnOYAc5Azg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 28, 2025 at 12:23 AM Alexandra Wang
<alexandra(dot)wang(dot)oss(at)gmail(dot)com> wrote:
> While reviewing Mark Dilger’s patch series "Index AM API cleanup" [1],
> I noticed some unexpected plan diffs when running the xtree and treeb
> test modules. Specifically, an additional Sort node appears on top of
> an Index Only Scan, even when the index key and sort key are the same.
> For example:
>
> --- src/test/modules/xtree/expected/interval.out
> +++ src/test/modules/xtree/results/interval.out

What's the xtree module? There's no such test module?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Abhishek Chanda 2025-02-28 05:39:59 Re: Adding support for SSLKEYLOGFILE in the frontend
Previous Message Alexandra Wang 2025-02-28 05:22:21 Remove extra Sort node above a btree-compatible Index Scan