On Sun, Jul 08, 2018 at 07:48:34PM +0300, Vladimir Davydov wrote:
vy_mem_iterator_next is as effecient as the current implementation of
vy_point_lookup_scan_mem, because it doesn't copy statements anymore
(see commit 1e1c1fdbedd vinyl: make read iterator always return newest
tuple version). Let's use it instead of open-coding vy_mem tree lookup.
---
src/box/vy_point_lookup.c | 47
+++++++++--------------------------------------
1 file changed, 9 insertions(+), 38 deletions(-)
