Re: On conflict update & hint bits - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: On conflict update & hint bits
Date
Msg-id CAM3SWZRo482iT696EzNaYpJoyNf7oX1xD_=xq1S0wQj78PDR5g@mail.gmail.com
Whole thread Raw
In response to On conflict update & hint bits  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: On conflict update & hint bits  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
List pgsql-hackers
On Fri, Sep 30, 2016 at 5:33 PM, Konstantin Knizhnik
<k.knizhnik@postgrespro.ru> wrote:
> Later we try to check tuple visibility:
>
>     ExecCheckHeapTupleVisible(estate, &tuple, buffer);
>
> and inside HeapTupleSatisfiesMVCC try to set hint bit.

So, you're using repeatable read or serializable isolation level?

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: PoC: Make it possible to disallow WHERE-less UPDATE and DELETE
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] pg_upgrade from 9.5 to 9.6 fails with "invalid argument"