Yes, that is currently used for REFRESH, and will be used to drive the
incremental maintenance when that is added. Without it, CREATE
MATERIALIZED VIEW wouldn't be different from CREATE TABLE AS.
A materialized view is pretty much like a view, but with the results
materialized.
-Kevin
On Mon,
On Mon, Jun 3, 2013 at 3:59 PM, Kevin Grittner wrote:
> Dave Page wrote:
>> Kevin Grittner wrote:
>>> Dave Page wrote:
>
In playing with materialized views, I noticed that they still
seem to have an _RETURN rule implicitly created like a regular
view.
>
>>> A materialized view is
Dave Page wrote:
> Kevin Grittner wrote:
>> Dave Page wrote:
>>> In playing with materialized views, I noticed that they still
>>> seem to have an _RETURN rule implicitly created like a regular
>>> view.
>> A materialized view is pretty much like a view, but with the
>> results materialized.
>
Dave Page writes:
> On Mon, Jun 3, 2013 at 1:06 PM, Kevin Grittner
> wrote:
>> A materialized view is pretty much like a view, but with the results
>> materialized.
> Yeah, I get that, but what is confusing is that this now seems to be a
> special kind of relation where there is an ON SELECT DO
On Mon, Jun 3, 2013 at 1:06 PM, Kevin Grittner
wrote:
> Yes, that is currently used for REFRESH, and will be used to drive the
> incremental maintenance when that is added. Without it, CREATE MATERIALIZED
> VIEW wouldn't be different from CREATE TABLE AS.
OK.
> A materialized view is pretty muc
Hi
In playing with materialized views, I noticed that they still seem to
have an _RETURN rule implicitly created like a regular view. This
doesn't seem right to me - is there a reason?
viper:~ dpage$ /usr/local/pgsql-9.3/bin/psql -p 5433 -U postgres
psql (9.3beta1)
Type "help" for help.
postgres
