ExecAgg() failed to finish running out set-returning functions in the last

aggregated tuple of a run.  Per report from Laurenz Albe.  This is a new
bug in 8.4, but only because prior versions rejected SRFs in an Agg plan
node altogether.

diff --git a/src/backend/executor/nodeAgg.c b/src/backend/executor/nodeAgg.c
index b48896c620229203ad6b534d1f8926f4fa8338b9..cf0c242245257a1c98c80d8c06a0f6fec8d64782 100644 (file)
--- a/src/backend/executor/nodeAgg.c
+++ b/src/backend/executor/nodeAgg.c
@@ -811,9 +811,6 @@ lookup_hash_entry(AggState *aggstate, TupleTableSlot *inputslot)
 TupleTableSlot *
 ExecAgg(AggState *node)
 {
-       if (node->agg_done)
-               return NULL;
-
        /*
         * Check to see if we're still projecting out tuples from a previous agg
         * tuple (because there is a function-returning-set in the projection
@@ -831,6 +828,15 @@ ExecAgg(AggState *node)
                node->ss.ps.ps_TupFromTlist = false;
        }
 
+       /*
+        * Exit if nothing left to do.  (We must do the ps_TupFromTlist check
+        * first, because in some cases agg_done gets set before we emit the
+        * final aggregate tuple, and we have to finish running SRFs for it.)
+        */
+       if (node->agg_done)
+               return NULL;
+
+       /* Dispatch based on strategy */
        if (((Agg *) node->ss.ps.plan)->aggstrategy == AGG_HASHED)
        {
                if (!node->table_filled)