Re: BUG #15378: SP-GIST memory context screwup?
Andrew Gierth <andrew@tao11.riddles.org.uk>
From: Andrew Gierth <andrew@tao11.riddles.org.uk>
To: Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: pgsql-bugs@lists.postgresql.org, Teodor Sigaev <teodor@sigaev.ru>
Date: 2018-09-11T15:47:37Z
Lists: pgsql-bugs
>>>>> "Alexander" == Alexander Korotkov <a.korotkov@postgrespro.ru> writes: >> So this logic was added in ccd6eb49a and was wrong from the start. >> Testing suggests that removing the offending pfree does indeed fix >> the issue; any objections? Alexander> No objections from me. But it turns out that removing the pfree will cause transient leakage within the scan, since ScanStackEntry objects are also freed retail during a walk. ugh. So the simplest fix would be to move the memory context reset to just after the freeScanStack in resetSpGistScanOpaque. And with retail freeing going on during the scan, it makes less sense to try and avoid it during rescan, double ugh. -- Andrew (irc:RhodiumToad)
Commits
-
Repair double-free in SP-GIST rescan (bug #15378)
- 84a3a1e55c86 9.6.11 landed
- c02b56869439 10.6 landed
- e331d6712f02 11.0 landed
- 500d49794f1f 12.0 landed