From: | Nicolas Barbier <nicolas(dot)barbier(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Documentation/help for materialized and recursive views |
Date: | 2013-06-27 08:56:04 |
Message-ID: | CAP-rdTbKr6Tu1h0tC+aOBrPT6YY9CN_+cQhixk_Ds-Jd7k+2Mw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2013/6/27 Magnus Hagander <magnus(at)hagander(dot)net>:
> Is there a particular reason why CREATE RECURSIVE VIEW is part of the
> help for CREATE VIEW, but CREATE MATERIALIZED VIEW doesn't show up
> there?
>
> I realize the technical reason (they're different man pages, and that
> also controls what's in \h in psql which is where I ran into it), but
> was there any particular reason to split those up in the first place?
Normal views are an abstraction layer, while materialized views
(despite containing the word “view”) are mainly a performance tool (in
a way similar to indexes).
The functionality of materialized views will (over time) totally swamp
that of normal views, so mixing all the corresponding documentation
with the documentation for normal views probably doesn’t make things
easier for people that are only interested in normal views.
Nicolas
--
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
From | Date | Subject | |
---|---|---|---|
Next Message | Szymon Guz | 2013-06-27 09:04:50 | Re: [PATCH] Fix conversion for Decimal arguments in plpython functions |
Previous Message | Pavel Stehule | 2013-06-27 08:47:20 | Re: FILTER for aggregates [was Re: Department of Redundancy Department: makeNode(FuncCall) division] |