1
0
mirror of https://github.com/postgres/postgres.git synced 2025-08-22 21:53:06 +03:00
Files
postgres/src/backend/commands
Tom Lane 601084eb1a 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
2019-06-03 16:59:16 -04:00
..
2018-04-26 14:47:16 -04:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00
2018-07-18 16:17:42 +03:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00
2018-03-16 13:18:06 -04:00
2018-01-02 23:30:12 -05:00
2018-03-16 13:18:06 -04:00
2018-10-03 13:11:44 -07:00
2018-04-26 14:47:16 -04:00
2018-04-26 14:47:16 -04:00
2018-04-12 11:22:56 +01:00
2018-01-02 23:30:12 -05:00
2018-04-26 14:47:16 -04:00
2018-04-07 17:45:39 -04:00
2018-01-19 14:01:15 -05:00
2018-01-02 23:30:12 -05:00