From: | "Erik Forsberg" <forsberg(at)efod(dot)se> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Example on difference between CREATE MATERIALIZED VIEW and standard VIEW has typo |
Date: | 2025-08-23 09:12:24 |
Message-ID: | 641a21c9-ab47-4213-961f-f83c0c220b3a@app.fastmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Fri, Aug 22, 2025, at 23:40, David G. Johnston wrote:
> On Fri, Aug 22, 2025 at 2:23 PM PG Doc comments form <noreply(at)postgresql(dot)org> wrote:
>> Unless I'm completely mistaken, the second code example on
>> https://www.postgresql.org/docs/current/rules-materializedviews.html, i.e
>> this:
>>
>> CREATE TABLE mymatview AS SELECT * FROM mytab;
>>
>> Should instead by
>>
>> CREATE VIEW mymatview AS SELECT * FROM mytab;
>
> No, the example's intent is to compare a true "materialized view" with a table that is simply populated from a query. The comment "the materialized view cannot subsequently be directly updated" only makes sense as a counterpoint to a physical table.
>
> David J.
>
Right, I stand corrected, and realize I don't know enough about standard view.
Maybe its the naming of the example *table* with the suffix *view* that completely mess up my brain, but I guess given the intent that's how it should be.
Thanks,
Erik
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2025-08-24 09:48:45 | Re: Initcap works differently with different locale providers |
Previous Message | David G. Johnston | 2025-08-22 21:40:33 | Re: Example on difference between CREATE MATERIALIZED VIEW and standard VIEW has typo |