On Tue, Mar 18, 2014 at 4:12 AM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
When inserting into a B-tree index, all the pages are read-locked when
descending the tree. When we reach the leaf page, the read-lock is exchanged
for a write-lock.
There's nothing wrong with that, but why
On 18 March 2014 11:12, Heikki Linnakangas hlinnakan...@vmware.com wrote:
When inserting into a B-tree index, all the pages are read-locked when
descending the tree. When we reach the leaf page, the read-lock is exchanged
for a write-lock.
There's nothing wrong with that, but why don't we
When inserting into a B-tree index, all the pages are read-locked when
descending the tree. When we reach the leaf page, the read-lock is
exchanged for a write-lock.
There's nothing wrong with that, but why don't we just directly grab a
write-lock on the leaf page? When descending, we know
On Tue, Mar 18, 2014 at 4:12 AM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
See attached patch. The new contract of _bt_getroot is a bit weird: it locks
the returned page in the requested lock-mode, shared or exclusive, if the
root page was also the leaf page. Otherwise it's locked in
On Tue, Mar 18, 2014 at 4:42 PM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
When inserting into a B-tree index, all the pages are read-locked when
descending the tree. When we reach the leaf page, the read-lock is exchanged
for a write-lock.
There's nothing wrong with that, but why
