On Mon, Mar 14, 2016 at 11:48 PM, Amit Langote <langote_amit...@lab.ntt.co.jp> wrote: >> Dunno about that. It's defining characteristic is that it checks child >> pages against their parent IMV. Things are not often defined in terms >> of their locking requirements. > > At the risk of sounding a bit verbose, do bt_check_level() for a check > that inspects a level at a time and bt_check_multi_level() for a check > that spans levels sound descriptive?
Hmm. But all functions verify multiple levels. What distinguishes bt_index_parent_check()'s verification is that the downlinks in internal pages are checked against actual child pages (every item in the child page, in fact). It's the parent/child relationship that is verified in addition to the standard checks of every page on and across (not between) every level. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
