Re: when the IndexScan reset to the next ScanKey for in operator

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Alex <zhihui(dot)fan1213(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: when the IndexScan reset to the next ScanKey for in operator
Date: 2019-08-23 05:14:03
Message-ID: CAH2-WzkPXVGW7U-0PAfk1_cnH0snTsjKitOwY5mWXHbcJr07xw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 21, 2019 at 6:24 AM Alex <zhihui(dot)fan1213(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Nancarrow 2019-08-23 05:29:00 Re: Procedure support improvements
Previous Message Michael Paquier 2019-08-23 04:40:12 Re: Cleanup isolation specs from unused steps