From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | kgrittn(at)ymail(dot)com |
Cc: | ishii(at)postgresql(dot)org, stark(at)mit(dot)edu, ants(at)cybertec(dot)at, hlinnakangas(at)vmware(dot)com, robertmhaas(at)gmail(dot)com, michael(dot)paquier(at)gmail(dot)com, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Materialized views WIP patch |
Date: | 2013-03-06 22:45:22 |
Message-ID: | 20130307.074522.1755169086862119106.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
> Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
>> Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>>
>>> Was the remaining work on docs done? I would like to test MVs and
>>> am waiting for the docs completed.
>>
>> I think they are done. If you notice anything missing or in need
>> of clarification please let me know. At this point missing docs
>> would be a bug in need of a fix.
Ok.
> I decided to take another pass through to try to spot anyplace I
> might have missed. I found that I had missed documenting the new
> pg_matviews system view, so I have just pushed that.
>
> I also think that something should be done about the documentation
> for indexes. Right now that always refers to a "table". It would
> clearly be awkward to change that to "table or materialized view"
> everywhere. I wonder if most of thosse should be changed to
> "relation" with a few mentions that the relation could be a table
> or a materialized view, or whether some less intrusive change would
> be better. Opinions welcome.
You might want to add small description about MVs to Tutorial
documentation "3.2 Views". Here is the current description of views in
the doc.
---------------------------------------------------------------------
3.2. Views
Refer back to the queries in Section 2.6. Suppose the combined listing
of weather records and city location is of particular interest to your
application, but you do not want to type the query each time you need
it. You can create a view over the query, which gives a name to the
query that you can refer to like an ordinary table:
CREATE VIEW myview AS
SELECT city, temp_lo, temp_hi, prcp, date, location
FROM weather, cities
WHERE city = name;
SELECT * FROM myview;
Making liberal use of views is a key aspect of good SQL database
design. Views allow you to encapsulate the details of the structure of
your tables, which might change as your application evolves, behind
consistent interfaces.
Views can be used in almost any place a real table can be
used. Building views upon other views is not uncommon.
---------------------------------------------------------------------
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-03-06 23:16:48 | pgsql: WAL-log the extension of a new empty MV heap which is being popu |
Previous Message | David E. Wheeler | 2013-03-06 22:28:29 | Re: Materialized views WIP patch |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2013-03-06 23:00:32 | Re: Enabling Checksums |
Previous Message | David E. Wheeler | 2013-03-06 22:28:29 | Re: Materialized views WIP patch |