From f0e766bd7f77774075297526bd2da8f3de226c1f Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 15 Apr 2016 00:02:26 -0400 Subject: [PATCH] Fix memory leak in GIN index scans. The code had a query-lifespan memory leak when encountering GIN entries that have posting lists (rather than posting trees, ie, there are a relatively small number of heap tuples containing this index key value). With a suitable data distribution this could add up to a lot of leakage. Problem seems to have been introduced by commit 36a35c550, so back-patch to 9.4. Julien Rouhaud --- src/backend/access/gin/ginget.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/backend/access/gin/ginget.c b/src/backend/access/gin/ginget.c index b79ba1e62af..610829852a6 100644 --- a/src/backend/access/gin/ginget.c +++ b/src/backend/access/gin/ginget.c @@ -281,6 +281,7 @@ collectMatchBitmap(GinBtreeData *btree, GinBtreeStack *stack, ipd = ginReadTuple(btree->ginstate, scanEntry->attnum, itup, &nipd); tbm_add_tuples(scanEntry->matchBitmap, ipd, nipd, false); scanEntry->predictNumberResult += GinGetNPosting(itup); + pfree(ipd); } /*