Re: Adding an LWLockHeldByMe()-like function that reports if anybuffer content lock is held - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Adding an LWLockHeldByMe()-like function that reports if anybuffer content lock is held
Date
Msg-id CAH2-WznbrnEHXPAK0xx8vhPtdUE7yXqtNYdbbR4=Dn_pgzv94g@mail.gmail.com
Whole thread Raw
In response to Re: Adding an LWLockHeldByMe()-like function that reports if anybuffer content lock is held  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Wed, Apr 18, 2018 at 6:53 PM, Michael Paquier <michael@paquier.xyz> wrote:
>> I'm curious about what we'll find by just by adding
>> Assert(!AnyBufferLockHeldByMe()) to the top of
>> heap_tuple_fetch_attr(). AssertNotInCriticalSection() certainly found
>> several bugs when it was first added.
>
> Yep.

I wrote a simple prototype of this. No assertion failed during a "make
installcheck". Assertions were added to heap_tuple_fetch_attr(), and a
couple of other places.

-- 
Peter Geoghegan


pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: VM map freeze corruption
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Postgres 10 problem with UNION ALL of null value in "subselect"