diff options
| author | Neil Conway <neilc@samurai.com> | 2006-01-12 22:04:02 +0000 |
|---|---|---|
| committer | Neil Conway <neilc@samurai.com> | 2006-01-12 22:04:02 +0000 |
| commit | d3a4d63387b633abb78b57e67c9be6076255a157 (patch) | |
| tree | 4105bdd14f76f71b9e18b9c69991d6b491647864 /src/backend/access/gist/gistget.c | |
| parent | 25b9b1b0425910a8503979ddcd974a0a32998791 (diff) | |
| download | postgresql-d3a4d63387b633abb78b57e67c9be6076255a157.tar.gz postgresql-d3a4d63387b633abb78b57e67c9be6076255a157.zip | |
mbutils was previously doing some allocations, including invoking
fmgr_info(), in the TopMemoryContext. I couldn't see that the code
actually leaked, but in general I think it's fragile to assume that
pfree'ing an FmgrInfo along with its fn_extra field is enough to
reclaim all the resources allocated by fmgr_info(). I changed the
code to do its allocations in a new child context of
TopMemoryContext, MbProcContext. When we want to release the
allocations we can just reset the context, which is cleaner.
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions