Horton

Re: why do we need two snapshots per query?

Simon Riggs <simon@2ndquadrant.com>

View thread
From: Simon Riggs <simon@2ndQuadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Dimitri Fontaine <dimitri@2ndquadrant.fr>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-11-13T07:47:06Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix copyright notices, other minor editing in new range-types code.

  2. Redesign the plancache mechanism for more flexibility and efficiency.

On Fri, Nov 11, 2011 at 10:04 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> Tom, in that earlier thread you said you'd be doing something in this
>> release about that. Can you say more about what that was, and will you
>> be doing it still?
>
> http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=e6faf910d75027bdce7cd0f2033db4e912592bcc
>
> I think that largely supersedes what I understood your notion of a
> one-shot plan to be about, though perhaps I missed something?

I was looking at other use cases, specifically partitioning/partial indexes.

If we could be certain that a query was being executed immediately
then it would be possible to simplify expressions using stable
functions as if they were constants. My earlier patch did exactly
that.

-- 
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services