Re: Materialized views don't show up in information_schema

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Sehrope Sarkuni <sehrope(at)jackdb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Materialized views don't show up in information_schema
Date: 2014-10-17 20:12:03
Message-ID: 54417813.3060302@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/16/14 9:45 AM, Stephen Frost wrote:
> Alright, coming back to this, I have to ask- how are matviews different
> from views from the SQL standard's perspective? I tried looking through
> the standard to figure it out (and I admit that I probably missed
> something), but the only thing appears to be a statement in the standard
> that (paraphrased) "functions are run with the view is queried" and that
> strikes me as a relatively minor point..

To me, the main criterion is that you cannot DROP VIEW a materialized view.

Generally, if the information schema claims that a
view/table/function/etc. named "foo" exists, then I should be able to
operate on "foo" using the basic operations for a
view/table/function/etc. of that name. I think think DROP VIEW is a
basic operation for a view. Others might disagree.

More subtly, if we claim that a materialized view is a view, then we
cannot have asynchronously updated materialized views, because then we
have different semantics.

All of this is a judgement call in corner cases. But I don't think this
is a corner case at all.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2014-10-17 20:44:09 Re: json function volatility
Previous Message Andrew Dunstan 2014-10-17 20:03:10 json function volatility