diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-06-03 16:59:16 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-06-03 16:59:16 -0400 |
| commit | 601084eb1aa8f1ae5303d9cf130d5b8cc385b517 (patch) | |
| tree | 94287951e04d95b2c7d04f2ba81ac24103905775 /src/backend/access/gist/gistxlog.c | |
| parent | 3c461d510dc5af7a7c4d4947ad7c2ef703e3646c (diff) | |
| download | postgresql-601084eb1aa8f1ae5303d9cf130d5b8cc385b517.tar.gz postgresql-601084eb1aa8f1ae5303d9cf130d5b8cc385b517.zip | |
Fix unsafe memory management in CloneRowTriggersToPartition().
It's not really supported to call systable_getnext() in a different
memory context than systable_beginscan() was called in, and it's
*definitely* not safe to do so and then reset that context between
calls. I'm not very clear on how this code survived
CLOBBER_CACHE_ALWAYS testing ... but Alexander Lakhin found a case
that would crash it pretty reliably.
Per bug #15828. Fix, and backpatch to v11 where this code came in.
Discussion: https://postgr.es/m/15828-f6ddd7df4852f473@postgresql.org
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions