| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Materialized views don't show up in information_schema |
| Date: | 2014-10-17 21:27:54 |
| Message-ID: | 544189DA.7000903@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/17/14, 4:31 AM, David G Johnston wrote:
> Since the standard doesn't distinguish between read and write aspects of the
> object types there isn't a safe way to add matviews to the information
> schema that doesn't violate the intent of the provided view. If the
> application/users wants to support/use PostgreSQL specific features it/they
> have to be ready and able to use the catalog.
+1. If we add matviews to information_schema while they're not part of that standard then we're going to regret it at some point.
Perhaps the answer to this problem is to restart the old pg_newsysviews project.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-10-17 21:41:09 | Re: json function volatility |
| Previous Message | Alvaro Herrera | 2014-10-17 20:59:49 | Re: json function volatility |