Re: Materialized views WIP patch
David Johnston <polobo@yahoo.com>
From: David Johnston <polobo@yahoo.com>
To: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
Cc: Peter Eisentraut <peter_e@gmx.net>, Kevin Grittner <kgrittn@mail.com>, Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2012-11-27T14:17:14Z
Lists: pgsql-hackers
On Nov 27, 2012, at 5:25, Dimitri Fontaine <dimitri@2ndQuadrant.fr> wrote: > > So my proposal for the current feature would be: > > ALTER MATERIALIZED VIEW mv UPDATE [ CONCURRENTLY ]; > UPDATE MATERIALIZED VIEW mv; > > The choice of keywords and syntax here hopefully clearly hint the user > about the locking behavior of the commands, too. And as we said, the > bare minimum for this patch does *not* include the CONCURRENTLY option, > which we still all want to have (someday). :) > I dislike using ALTER syntax to perform a data-only action. The other advantage of non-functional syntax is that you could more easily supply some form of where clause should you only want to perform a partial refresh. With a function call that becomes more obtuse. David J.
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