| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jonathan Lemig <jtlemig(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Views "missing" from information_schema.view_table_usage |
| Date: | 2022-12-02 21:14:47 |
| Message-ID: | CAKFQuwb3xQ5UbyFqW3TFDKBenBrngUXrA4152-3yT8Aeb1eSYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
On Fri, Dec 2, 2022 at 1:52 PM 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?
>
>
Well, the query itself is available in the source code if you want to
experiment on your own. Otherwise, I suggest you produce a self-contained
example that fails to produce one or more rows in view_table_usage that you
believe should be present. Whether it is a bug report or trying to point
out what you are misunderstanding, diagnosing this situation with the
information you've provided is not a productive activity.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Wienhold | 2022-12-02 21:33:27 | Re: Views "missing" from information_schema.view_table_usage |
| Previous Message | Jonathan Lemig | 2022-12-02 20:51:50 | Views "missing" from information_schema.view_table_usage |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pasi Oja-Nisula | 2022-12-02 21:15:33 | Re: Stored procedure code no longer stored in v14 and v15, changed behaviour |
| Previous Message | Jonathan Lemig | 2022-12-02 20:51:50 | Views "missing" from information_schema.view_table_usage |