Re: BUG #14668: BRIN open autosummarize=on , database will crash

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: digoal(at)126(dot)com, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14668: BRIN open autosummarize=on , database will crash
Date: 2017-05-31 00:44:01
Message-ID: CAEepm=1R696zMza9iEbpjoFUt5Pirzvu3Az181rAbraiWOVvEw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, May 31, 2017 at 10:19 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Pushed fix. Actually that's not correct either, because tuples returned
> by brinGetTupleForHeapBlock are not supposed to be freed at all since
> they are shared buffer items. The correct thing to do there was to
> release the buffer lock ...

Ugh, right, thanks. I'll blame the myopic analysis on jetlag and lack
of coffee.

--
Thomas Munro
http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message wangchuanting 2017-05-31 03:32:28 BUG #14680: startup process on standby encounter a deadlock of TwoPhaseStateLock when redo 2PC xlog
Previous Message Michael Paquier 2017-05-30 23:39:55 Re: [PATCH] Fixed malformed error message on malformed SCRAM message.