Tom Lane wrote:
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
The beef of the patch is two new optional indexam API functions:
amprepareinsert and amfinishinsert. amprepareinsert is called before
inserting the heap tuple. It descends the tree and finds and pins the
right leaf page to insert to, and returns a suggestion on where the heap
tuple should be inserted. amfinishinsert is called after inserting the
heap tuple to actually insert the index tuple. Documentation for these
functions need to be added indexam.sgml, I noticed that that's not done yet.
What happens when there's more than one index?
You can only cluster a table on one index. The other index inserts will
use the aminsert-function, after inserting the heap tuple as usual.
Is there a risk of deadlock during concurrent insertions (from different
processes trying to lock the same buffers in different orders)?
No, should be ok. btprepareinsert function will release locks (but not
the pin) after descending the tree, and btfinishinsert will reacquire
them. The locking order is the same as today.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
