From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jonathan Lemig <jtlemig(at)gmail(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Request to modify view_table_usage to include materialized views |
Date: | 2022-12-05 17:53:49 |
Message-ID: | 3322650.1670262829@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jonathan Lemig <jtlemig(at)gmail(dot)com> writes:
> Would it be possible to modify the information_schema.view_table_usage
> (VTU) to include materialized views?
Is it physically possible? Sure, it'd just take adjustment of some
relkind checks.
However, it's against project policy. We consider that because the
information_schema views are defined by the SQL standard, they should
only show standardized properties of standardized objects. If the
standard ever gains materialized views, we'd adjust those views to
show them. In the meantime, they aren't there.
It would make little sense in any case to adjust only this one view.
But if we were to revisit that policy, there are a lot of corner
cases that would have to be thought through --- things that almost
fit into the views, or that might appear in a very misleading way,
etc.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2022-12-05 17:56:44 | Re: ANY_VALUE aggregate |
Previous Message | Andrew Dunstan | 2022-12-05 17:51:49 | Re: Error-safe user functions |