Re: Incorrect visibility test function assigned to snapshot - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Incorrect visibility test function assigned to snapshot
Date
Msg-id 20180530132854.tkv37qiamepu3slh@alvherre.pgsql
Whole thread Raw
In response to Incorrect visibility test function assigned to snapshot  (Antonin Houska <ah@cybertec.at>)
Responses Re: Incorrect visibility test function assigned to snapshot  (Antonin Houska <ah@cybertec.at>)
Re: Incorrect visibility test function assigned to snapshot  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 2018-May-30, Antonin Houska wrote:

> In the header comment, SnapBuildInitialSnapshot() claims to set
> snapshot->satisfies to the HeapTupleSatisfiesMVCC test function, and indeed it
> converts the "xid" array to match its semantics (i.e. the xid items eventually
> represent running transactions as opposed to the committed ones). However the
> test function remains HeapTupleSatisfiesHistoricMVCC as set by
> SnapBuildBuildSnapshot().

Interesting.  While this sounds like an oversight that should have
horrible consequences, it's seems not to because the current callers
don't seem to care about the ->satisfies function.  Are you able to come
up with some scenario in which it causes an actual problem?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Geoff Winkless
Date:
Subject: Re: Is a modern build system acceptable for older platforms
Next
From: Ashutosh Bapat
Date:
Subject: Re: Microoptimization of Bitmapset usage in postgres_fdw