Re: Materialized views WIP patch
David Fetter <david@fetter.org>
From: David Fetter <david@fetter.org>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Kevin Grittner <kgrittn@mail.com>, Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2012-11-26T15:24:56Z
Lists: pgsql-hackers
On Mon, Nov 26, 2012 at 09:46:33AM -0500, Peter Eisentraut wrote: > On 11/14/12 9:28 PM, Kevin Grittner wrote: > > 17. Since the data viewed in an MV is not up-to-date with the > > latest committed transaction, > > So, the way I understand it, in Oracle terms, this feature is a > "snapshot", not a materialized view. Maybe that's what it should be > called then. "Snapshot" is one of the options for refreshing an Oracle materialized view. There are others, which we'll eventually add if past is any prologue :) I hate to add to the bike-shedding, but we should probably add REFRESH SNAPSHOT as an optional piece of the grammar, with more REFRESH options to come. Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Preserve intermediate .c files in coverage mode
- 4af3dda13601 9.3.0 cited