Re: On conflict update & hint bits

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: On conflict update & hint bits
Date: 2016-09-30 16:37:35
Message-ID: CAM3SWZRo482iT696EzNaYpJoyNf7oX1xD_=xq1S0wQj78PDR5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 30, 2016 at 5:33 PM, Konstantin Knizhnik
<k(dot)knizhnik(at)postgrespro(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-09-30 16:38:51 Re: [GENERAL] pg_upgrade from 9.5 to 9.6 fails with "invalid argument"
Previous Message Julien Rouhaud 2016-09-30 16:37:17 Re: PoC: Make it possible to disallow WHERE-less UPDATE and DELETE