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
somepoint.
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