| From: | Sehrope Sarkuni <sehrope(at)jackdb(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: Materialized views don't show up in information_schema |
| Date: | 2014-10-11 01:14:52 |
| Message-ID: | FAFBF0EA-980F-4902-8FCF-D9518974607F@jackdb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Another example is an ETL tool or ORM that queries the data dictionary to generate SQL or object models.
If mviews show up in the regular information_schema views (specifically the .columns view) then it'll just work as if it's a regular table or view (ex: like foreign tables).
If not, it's possible to use the internal pg_ catalog tables to get the column details but it'd require PG specific coding.
In our case I already plan on using the internal catalog tables to display mview metadata. I brought this up thinking about existing apps and tools being able to work with mviews without additional code changes.
Regards,
-- Sehrope Sarkuni
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2014-10-11 01:19:54 | Re: Wait free LW_SHARED acquisition - v0.9 |
| Previous Message | Peter Eisentraut | 2014-10-11 01:14:38 | Re: orangutan seizes up during isolation-check |