| From: | Jonathan Lemig <jtlemig(at)gmail(dot)com> |
|---|---|
| To: | Erik Wienhold <ewie(at)ewie(dot)name> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Views "missing" from information_schema.view_table_usage |
| Date: | 2022-12-02 22:14:54 |
| Message-ID: | CABR8q_9-sN65XQqDMwB=-7o8b7igpOVDZKFbGS4BaoFLFivhiQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
Hi Erik - sorry I missed your reply when I replied to David's. That is
indeed the issue. The object that the view is querying is a materialized
view.
Thanks for the link.
Jon
On Fri, Dec 2, 2022 at 3:33 PM Erik Wienhold <ewie(at)ewie(dot)name> wrote:
> > On 02/12/2022 21:51 CET Jonathan Lemig <jtlemig(at)gmail(dot)com> wrote:
> >
> > Has anybody ever encountered this, and if so, did you find a resolution?
> > Or perhaps there other limitations with the VTU that I'm unaware of?
>
> Is the one view you cannot find in view_table_usage a materialized view?
> Because those are not covered by view_table_usage[1].
>
> [1]
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/catalog/information_schema.sql;h=18725a02d1fb6ffda3d218033b972a0ff23aac3b;hb=HEAD#l2605
>
> --
> Erik
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Lemig | 2022-12-02 22:22:13 | Re: Views "missing" from information_schema.view_table_usage |
| Previous Message | Erik Wienhold | 2022-12-02 22:14:05 | Re: Views "missing" from information_schema.view_table_usage |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | raf | 2022-12-02 22:18:52 | Re: Stored procedure code no longer stored in v14 and v15, changed behaviour |
| Previous Message | Erik Wienhold | 2022-12-02 22:14:05 | Re: Views "missing" from information_schema.view_table_usage |