Re: Request to modify view_table_usage to include materialized views - Mailing list pgsql-hackers

From Jonathan Lemig
Subject Re: Request to modify view_table_usage to include materialized views
Date
Msg-id CABR8q_-+iLu2yRS66MfqcN3sozZuSQaGM8RpdXF7ybqYRXE2mg@mail.gmail.com
Whole thread Raw
In response to Re: Request to modify view_table_usage to include materialized views  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hey Tom,

Thanks for the info.  I'll submit a document change request instead. 

Thanks!

Jon

On Mon, Dec 5, 2022 at 11:53 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Jonathan Lemig <jtlemig@gmail.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

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH] Add native windows on arm64 support
Next
From: Andres Freund
Date:
Subject: Re: WAL Insertion Lock Improvements (was: Re: Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish())