On Fri, Mar 11, 2016 at 1:31 PM, Peter Geoghegan <p...@heroku.com> wrote: > You could have a race, where > there was a concurrent page deletion of the left sibling of the child > page, then a concurrent insertion into the newly expanded keyspace of > the parent. Therefore, the downlink in the parent (which is the > "target", to use the patch's terminology) would not be a lower bound > on items in the page.
Excuse me: I meant the newly expanded keyspace of the *child*. (The parent's keyspace would have covered everything. It's naturally far larger than either child's keyspace, since it typically has several hundred pages.) -- 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
