I do the code review.
Now, it is first patch - v6-0001... dedicated to a logical duplicates
ordering.
Documentation is full and clear. All non-trivial logic is commented
accurately.
Patch applies cleanly on top of current master. Regression tests passed
and my "Retail Indextuple deletion" use cases works without mistakes.
But I have two comments on the code.
New BTScanInsert structure reduces parameters list of many functions and
look fine. But it contains some optimization part ('restorebinsrch'
field et al.). It is used very locally in the code -
_bt_findinsertloc()->_bt_binsrch() routines calling. May be you localize
this logic into separate struct, which will passed to _bt_binsrch() as
pointer. Another routines may pass NULL value to this routine. It is may
simplify usability of the struct.
Due to the optimization the _bt_binsrch() size has grown twice. May be
you move this to some service routine?
--
Andrey Lepikhov
Postgres Professional
https://postgrespro.com
The Russian Postgres Company
