Re: Review: Fix snapshot taking inconsistencies - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: Review: Fix snapshot taking inconsistencies
Date
Msg-id 4D6BF51F.6080906@cs.helsinki.fi
Whole thread Raw
In response to Re: Review: Fix snapshot taking inconsistencies  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Review: Fix snapshot taking inconsistencies  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2011-02-28 9:03 PM, Tom Lane wrote:
> Marko Tiikkaja<marko.tiikkaja@cs.helsinki.fi>  writes:
>> On 2011-02-28 8:22 PM, Tom Lane wrote:
>>> So: exactly what is the intended behavioral change as of now, and what
>>> is the argument supporting that change?
>
>> The only intended change is what I was wondering in the original post:
>> snapshot handling between normal execution and EXPLAIN ANALYZE when a
>> query expands to multiple trees because of rewrite rules.  Like I said
>> earlier, this is just a bugfix now that wCTEs don't need it anymore.
>
> OK, and which behavior is getting changed, to what?  I am not interested
> in trying to reverse-engineer a specification from the patch.

My recollection is (and the archives seem to agree) that normal 
execution and SQL functions were changed to only advance the CID instead 
of taking a new snapshot.  EXPLAIN ANALYZE and SPI (not exactly sure 
about this one) did that already so they were just changed to use the 
new API.


Regards,
Marko Tiikkaja


pgsql-hackers by date:

Previous
From: Andrew Hammond
Date:
Subject: Re: mysql2pgsql.perl update
Next
From: David Fetter
Date:
Subject: Re: EXPLAIN doesn't show sufficient info for wCTE cases