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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Miroslav Bendik <miroslav(dot)bendik(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 11:15:45
Message-ID: CAApHDvqNHLGBbOYTLq00cGPDX9XCC_LvZdR2zoix6z2qSkqNCw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 4 Jul 2023 at 20:12, Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> 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'.

I agree. I went and hit the comments with a large hammer and while
there also adjusted the regression tests. I didn't think having "t" as
a table name was a good idea as it seems like a name with a high risk
of conflicting with a concurrently running test. Also, there didn't
seem to be much need to insert data into that table as the tests
didn't query any of it.

The only other small tweak I made was to not call list_copy_head()
when the list does not need to be shortened. It's likely not that
important, but if the majority of cases are not partial matches, then
we'd otherwise be needlessly making copies of the list.

I pushed the adjusted patch.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2023-07-04 11:23:58 Re: brininsert optimization opportunity
Previous Message Drouvot, Bertrand 2023-07-04 10:04:50 Re: Autogenerate some wait events code and documentation