Re: BUG #15378: SP-GIST memory context screwup? - Mailing list pgsql-bugs

From Andrew Gierth
Subject Re: BUG #15378: SP-GIST memory context screwup?
Date
Msg-id 87y3c8oy1g.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: BUG #15378: SP-GIST memory context screwup?  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Responses Re: BUG #15378: SP-GIST memory context screwup?  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List 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)


pgsql-bugs by date:

Previous
From: kalyani kaniganti
Date:
Subject: Re: BUG #15376: Postgres sql 9.4.19 pg_upgrade stops with error Thesource cluster was not shut down cleanly.
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #15376: Postgres sql 9.4.19 pg_upgrade stops with error Thesource cluster was not shut down cleanly.