pgsql: Fix a small memory leak in ExecReScanAgg() in the hashed

From: neilc(at)postgresql(dot)org (Neil Conway)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix a small memory leak in ExecReScanAgg() in the hashed
Date: 2008-10-16 19:26:01
Message-ID: 20081016192601.4B1A67545A5@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Teodor Sigaev 2008-10-17 17:02:21 pgsql: During repeated rescan of GiST index it's possible that scan key
Previous Message Neil Conway 2008-10-16 19:25:58 pgsql: Fix a small memory leak in ExecReScanAgg() in the hashed