- Notifications
You must be signed in to change notification settings - Fork28
Commit601084e
committed
Fix unsafe memory management in CloneRowTriggersToPartition().
It's not really supported to call systable_getnext() in a differentmemory context than systable_beginscan() was called in, and it's*definitely* not safe to do so and then reset that context betweencalls. I'm not very clear on how this code survivedCLOBBER_CACHE_ALWAYS testing ... but Alexander Lakhin found a casethat 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.org1 parent3c461d5 commit601084e
1 file changed
+7
-7
lines changedLines changed: 7 additions & 7 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
15082 | 15082 |
| |
15083 | 15083 |
| |
15084 | 15084 |
| |
15085 |
| - | |
15086 |
| - | |
| 15085 | + | |
15087 | 15086 |
| |
15088 | 15087 |
| |
15089 | 15088 |
| |
| |||
15093 | 15092 |
| |
15094 | 15093 |
| |
15095 | 15094 |
| |
15096 |
| - | |
15097 | 15095 |
| |
15098 | 15096 |
| |
15099 | 15097 |
| |
15100 |
| - | |
| 15098 | + | |
15101 | 15099 |
| |
15102 | 15100 |
| |
15103 | 15101 |
| |
15104 | 15102 |
| |
15105 | 15103 |
| |
15106 |
| - | |
15107 |
| - | |
| 15104 | + | |
15108 | 15105 |
| |
15109 | 15106 |
| |
15110 | 15107 |
| |
| |||
15123 | 15120 |
| |
15124 | 15121 |
| |
15125 | 15122 |
| |
| 15123 | + | |
| 15124 | + | |
| 15125 | + | |
15126 | 15126 |
| |
15127 | 15127 |
| |
15128 | 15128 |
| |
| |||
15186 | 15186 |
| |
15187 | 15187 |
| |
15188 | 15188 |
| |
| 15189 | + | |
15189 | 15190 |
| |
15190 | 15191 |
| |
15191 | 15192 |
| |
15192 |
| - | |
15193 | 15193 |
| |
15194 | 15194 |
| |
15195 | 15195 |
| |
|
0 commit comments
Comments
(0)