Re: Request to modify view_table_usage to include materialized views

From: Jonathan Lemig <jtlemig(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 18:16:03
Message-ID: CABR8q_-+iLu2yRS66MfqcN3sozZuSQaGM8RpdXF7ybqYRXE2mg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-12-05 18:30:07 Re: WAL Insertion Lock Improvements (was: Re: Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish())
Previous Message Andres Freund 2022-12-05 18:14:49 Re: [PATCH] Add native windows on arm64 support