Horton

Re: why do we need two snapshots per query?

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: Dimitri Fontaine <dimitri@2ndquadrant.fr>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-11-11T22:04:59Z
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.

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 don't think this has a lot to do with what Robert is on about, since
in any situation where a plan is cached for later, we surely are not
going to use the same snapshot to execute it.

			regards, tom lane