aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistsplit.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-06-23 10:55:59 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-06-23 10:55:59 -0400
commitbd1693e89e7e6c458d0563f6cc67a7c99a45251a (patch)
tree01fe3bc1b0b99b42348bb1e15dcd609a84edb1c3 /src/backend/access/gist/gistsplit.c
parent2d673424faf3e33c5fcca926fbe3f21e16dd0fef (diff)
downloadpostgresql-bd1693e89e7e6c458d0563f6cc67a7c99a45251a.tar.gz
postgresql-bd1693e89e7e6c458d0563f6cc67a7c99a45251a.zip
Fix small memory leak in partial-aggregate deserialization functions.
A deserialize function's result is short-lived data during partial aggregation, since we're just going to pass it to the combine function and then it's of no use anymore. However, the built-in deserialize functions allocated their results in the aggregate state context, resulting in a query-lifespan memory leak. It's probably not possible for this to amount to anything much at present, since the number of leaked results would only be the number of worker processes. But it might become a problem in future. To fix, don't use the same convenience subroutine for setting up results that the aggregate transition functions use. David Rowley Report: <10050.1466637736@sss.pgh.pa.us>
Diffstat (limited to 'src/backend/access/gist/gistsplit.c')
0 files changed, 0 insertions, 0 deletions