Re: Incremental sort for access method with ordered scan support (amcanorderbyop)
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Richard Guo <guofenglinux@gmail.com>
Cc: Miroslav Bendik <miroslav.bendik@gmail.com>, pgsql-hackers@postgresql.org
Date: 2023-07-04T11:15:45Z
Lists: pgsql-hackers
On Tue, 4 Jul 2023 at 20:12, Richard Guo <guofenglinux@gmail.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
Commits
-
Allow Incremental Sorts on GiST and SP-GiST indexes
- 625d5b3ca096 17.0 landed
-
Fix list_copy_head() with empty Lists
- 63a03aea6bc8 15.3 landed
- e35ded29566f 16.0 landed