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

From Tom Lane
Subject Re: Review: Fix snapshot taking inconsistencies
Date
Msg-id 26603.1298917365@sss.pgh.pa.us
Whole thread Raw
In response to Re: Review: Fix snapshot taking inconsistencies  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
Responses Re: Review: Fix snapshot taking inconsistencies  (Robert Haas <robertmhaas@gmail.com>)
Re: Review: Fix snapshot taking inconsistencies  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
List pgsql-hackers
Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi> writes:
> [ latest version of snapshot-taking patch ]

I started to look at this, and find myself fairly confused as to what
the purpose is anymore.  Reviewing the thread, there has been a lot of
discussion of refactoring the API of pg_parse_and_rewrite and related
functions exported by postgres.c; but the current patch seems to have
abandoned that goal (except for removing pg_parse_and_rewrite itself,
which doesn't seem to me to have a lot of point except as part of a
more general refactoring).  With respect to the issue of changing
snapshot timing, most of the discussion around that seemed to start
from assumptions about the behavior of wCTEs that we've now abandoned.
And there was some discussion about rule behavior too, but it's not
clear to me whether this patch intends to change that or not.  The
lack of any documentation change doesn't help here.

So: exactly what is the intended behavioral change as of now, and what
is the argument supporting that change?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Why our counters need to be time-based WAS: WIP: cross column correlation ...
Next
From: Robert Haas
Date:
Subject: Re: Why our counters need to be time-based WAS: WIP: cross column correlation ...