aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2019-03-14 12:03:31 -0400
committerRobert Haas <rhaas@postgresql.org>2019-03-14 12:14:47 -0400
commit2455ab48844c90419714e27eafd235a85de23232 (patch)
treefc6755562d7594fdca476020db6bf47291a943a2 /src/backend/executor/nodeModifyTable.c
parentc6ff0b892c30122b75d32c524109d16ee3c973f0 (diff)
downloadpostgresql-2455ab48844c90419714e27eafd235a85de23232.tar.gz
postgresql-2455ab48844c90419714e27eafd235a85de23232.zip
Defend against leaks into RelationBuildPartitionDesc.
In normal builds, this isn't very important, because the leaks go into fairly short-lived contexts, but under CLOBBER_CACHE_ALWAYS, this can result in leaking hundreds of megabytes into MessageContext, which probably explains recent failures on hyrax. This may or may not be the best long-term strategy for dealing with this leak, but we can change it later if we come up with something better. For now, do this to make the buildfarm green again (hopefully). Commit 898e5e3290a72d288923260143930fb32036c00c seems to have exacerbated this problem for reasons that are not quite clear, but I don't believe it's actually the cause. Discussion: http://postgr.es/m/CA+TgmoY3bRmGB6-DUnoVy5fJoreiBJ43rwMrQRCdPXuKt4Ykaw@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions