Re: BUG #5914: locking error in heap_fetch

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: YAMAMOTO Takashi <yamt(at)mwd(dot)biglobe(dot)ne(dot)jp>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5914: locking error in heap_fetch
Date: 2011-03-04 13:52:05
Message-ID: 4D70EE85.6010904@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 04.03.2011 10:34, YAMAMOTO Takashi wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5914
> Logged by: YAMAMOTO Takashi
> Email address: yamt(at)mwd(dot)biglobe(dot)ne(dot)jp
> PostgreSQL version: 9.1devel
> Operating system: NetBSD
> Description: locking error in heap_fetch
> Details:
>
> heap_fetch calls CheckForSerializableConflictOut without buffer locked.
> it ends up an assertion failure in SetBufferCommitInfoNeedsSave.

Thanks, applied. I also added a comment to
CheckForSerializableConflictOut, noting that the caller must hold a lock
on the page.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-03-04 14:55:35 Re: Possible regression: libpq + SSL aborts when user has no home directory
Previous Message Torsten Zühlsdorff 2011-03-04 13:49:42 Re: Missing Bug-Report #5904?