Install a search tree depth limit in GIN bulk-insert operations, to prevent
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 24 Mar 2009 22:06:03 +0000 (22:06 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 24 Mar 2009 22:06:03 +0000 (22:06 +0000)
them from degrading badly when the input is sorted or nearly so.  In this
scenario the tree is unbalanced to the point of becoming a mere linked list,
so insertions become O(N^2).  The easiest and most safely back-patchable
solution is to stop growing the tree sooner, ie limit the growth of N.  We
might later consider a rebalancing tree algorithm, but it's not clear that
the benefit would be worth the cost and complexity.  Per report from Sergey
Burladyan and an earlier complaint from Heikki.

Back-patch to 8.2; older versions didn't have GIN indexes.

src/backend/access/gin/ginfast.c
src/backend/access/gin/gininsert.c
src/include/access/gin.h

index 0c3ee2577cb1f41f0d7cea1c91333f72e3daa326..bad62ad81e42c2150b0021b4ca5daa1770142a69 100644 (file)
@@ -749,9 +749,10 @@ ginInsertCleanup(Relation index, GinState *ginstate,
                 * XXX using up maintenance_work_mem here is probably unreasonably
                 * much, since vacuum might already be using that much.
                 */
-               if ( GinPageGetOpaque(page)->rightlink == InvalidBlockNumber ||
-                        ( GinPageHasFullRow(page) &&
-                          accum.allocatedMemory > maintenance_work_mem * 1024L ) )
+               if (GinPageGetOpaque(page)->rightlink == InvalidBlockNumber ||
+                       (GinPageHasFullRow(page) &&
+                        (accum.allocatedMemory >= maintenance_work_mem * 1024L ||
+                         accum.maxdepth > GIN_MAX_TREE_DEPTH)))
                {
                        ItemPointerData    *list;
                        uint32                  nlist;
index b1ecc127a6d6858715dca82edf7dd522fd1ee139..0190b2508f9a343151c2e81e0071305b4e17ca45 100644 (file)
@@ -245,7 +245,9 @@ ginBuildCallback(Relation index, HeapTuple htup, Datum *values,
                                                                                                                &htup->t_self);
 
        /* If we've maxed out our available memory, dump everything to the index */
-       if (buildstate->accum.allocatedMemory >= maintenance_work_mem * 1024L)
+       /* Also dump if the tree seems to be getting too unbalanced */
+       if (buildstate->accum.allocatedMemory >= maintenance_work_mem * 1024L ||
+               buildstate->accum.maxdepth > GIN_MAX_TREE_DEPTH)
        {
                ItemPointerData *list;
                Datum           entry;
index 346597867dc1023976a6e86b455273444323b25e..3bec7071b6e0933dd851154a3bcfe3ceebe4a241 100644 (file)
 #define GIN_COMPARE_PARTIAL_PROC          5
 #define GINNProcs                                         5
 
+/*
+ * Max depth allowed in search tree during bulk inserts.  This is to keep from
+ * degenerating to O(N^2) behavior when the tree is unbalanced due to sorted
+ * or nearly-sorted input.  (Perhaps it would be better to use a balanced-tree
+ * algorithm, but in common cases that would only add useless overhead.)
+ */
+#define GIN_MAX_TREE_DEPTH 100
+
 /*
  * Page opaque data in a inverted index page.
  *
@@ -434,12 +442,9 @@ extern IndexTuple ginPageGetLinkItup(Buffer buf);
 
 /* gindatapage.c */
 extern int     compareItemPointers(ItemPointer a, ItemPointer b);
-extern void
-MergeItemPointers(
-                                 ItemPointerData *dst,
+extern void MergeItemPointers(ItemPointerData *dst,
                                  ItemPointerData *a, uint32 na,
-                                 ItemPointerData *b, uint32 nb
-);
+                                 ItemPointerData *b, uint32 nb);
 
 extern void GinDataPageAddItem(Page page, void *data, OffsetNumber offset);
 extern void PageDeletePostingItem(Page page, OffsetNumber offset);