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

From Alexander Korotkov
Subject Re: BUG #15378: SP-GIST memory context screwup?
Date
Msg-id CAPpHfdudnGJFcbh76OjgMy2sBCGm8pMsBgZbiL4i7Vzc44kZ1g@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15378: SP-GIST memory context screwup?  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-bugs
On Tue, Sep 11, 2018 at 6:47 PM Andrew Gierth <andrew@tao11.riddles.org.uk> wrote:
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.

Right, I've missed code path freeScanStackEntry() call from spgWalk().

On Tue, Sep 11, 2018 at 9:59 PM Andrew Gierth <andrew@tao11.riddles.org.uk> wrote:
 Andrew> Proposed patch attached.

Pushed this.

Pushed version looks correct to me.  Thank you!

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

pgsql-bugs by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: BUG #15378: SP-GIST memory context screwup?
Next
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.