Re: Incremental sort for access method with ordered scan support (amcanorderbyop)

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Miroslav Bendik <miroslav(dot)bendik(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Incremental sort for access method with ordered scan support (amcanorderbyop)
Date: 2023-07-04 08:12:39
Message-ID: CAMbWs48RiJcmA7RhzdxyjEVYfCrf6Z3JLzQWfiGWAFVcnuph+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jul 2, 2023 at 12:02 PM Miroslav Bendik <miroslav(dot)bendik(at)gmail(dot)com>
wrote:

> Thanks, for suggestions.
>
> On Sun 02. 07. 2023 at 10:18 Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> > 1. For comment "On success, the result list is ordered by pathkeys.", I
> > think it'd be more accurate if we say something like "On success, the
> > result list is ordered by pathkeys or a prefix list of pathkeys."
> > considering the possibility of incremental sort.
> >
> > 2. The comment below is not true anymore.
> >
> > /*
> > * Note: for any failure to match, we just return NIL immediately.
> > * There is no value in matching just some of the pathkeys.
> > */
> > We should either remove it or change it to emphasize that we may return
> > a prefix of the pathkeys for incremental sort.
>
> Comments are updated now.
>
> > BTW, would you please add the patch to the CF to not lose track of it?
>
> Submitted <https://commitfest.postgresql.org/43/4433/>

The v4 patch looks good to me (maybe some cosmetic tweaks are still
needed for the comments). I think it's now 'Ready for Committer'.

Thanks
Richard

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Japin Li 2023-07-04 08:50:33 Re: Extension Enhancement: Buffer Invalidation in pg_buffercache
Previous Message Will Mortensen 2023-07-04 08:11:05 Re: Exposing the lock manager's WaitForLockers() to SQL