Re: when the IndexScan reset to the next ScanKey for in operator - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: when the IndexScan reset to the next ScanKey for in operator
Date
Msg-id CAH2-WzkPXVGW7U-0PAfk1_cnH0snTsjKitOwY5mWXHbcJr07xw@mail.gmail.com
Whole thread Raw
In response to when the IndexScan reset to the next ScanKey for in operator  (Alex <zhihui.fan1213@gmail.com>)
List pgsql-hackers
On Wed, Aug 21, 2019 at 6:24 AM Alex <zhihui.fan1213@gmail.com> wrote:
> suppose the executor  should scan 1 first,  If all the tuples for 1 has been scanned,  then **it should be reset to
100000** and scan again.
 

You might find my nbtree index scan test patch useful:

https://postgr.es/m/CAH2-WzmRT_0YbHF05axQb2OiTUQiQAkr0Lznntj8X3KADKZ-5g@mail.gmail.com

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Cleanup isolation specs from unused steps
Next
From: Thomas Munro
Date:
Subject: Re: POC: Cleaning up orphaned files using undo logs