pgsql: Fix a small memory leak in ExecReScanAgg() in the hashed - Mailing list pgsql-committers

From neilc@postgresql.org (Neil Conway)
Subject pgsql: Fix a small memory leak in ExecReScanAgg() in the hashed
Date
Msg-id 20081016192601.4B1A67545A5@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix a small memory leak in ExecReScanAgg() in the hashed aggregation case.
In the previous coding, the list of columns that needed to be hashed on
was allocated in the per-query context, but we reallocated every time
the Agg node was rescanned. Since this information doesn't change over
a rescan, just construct the list of columns once during ExecInitAgg().

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
    pgsql/src/backend/executor:
        nodeAgg.c (r1.146.2.2 -> r1.146.2.3)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeAgg.c?r1=1.146.2.2&r2=1.146.2.3)

pgsql-committers by date:

Previous
From: neilc@postgresql.org (Neil Conway)
Date:
Subject: pgsql: Fix a small memory leak in ExecReScanAgg() in the hashed
Next
From: teodor@postgresql.org (Teodor Sigaev)
Date:
Subject: pgsql: During repeated rescan of GiST index it's possible that scan key