Oh ok. Not to cause confusion, but after I suggested I would request an
update to the docs, I thought maybe it would be better to ask if the VTU's
code could be modified to include MVs. So I sent a request to
pgsql-hackers (I think that's the list to use for feature requests). But
from what you'
It probably wouldn't hurt to have that added to the documentation.
I'll post a message to pgsql-docs. Thanks again!
Jon
On Fri, Dec 2, 2022 at 4:14 PM Jonathan Lemig wrote:
> Hi Erik - sorry I missed your reply when I replied to David's. That is
> indeed the issue. The
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 wrote:
> > On 02/12/2022 21:51 CET Jonathan Lemig wrote:
view_catalog | view_schema | view_name | table_catalog | table_schema |
table_name
--+-+-+---+--+
drps | event | tv_lineup_v | drps | event|
tv_lineup
I'll take a look at the VTU view's DDL and see what else I can find.
Thanks!
Jon
On Fri, Dec 2, 2022 at 3:15
Hi,
I am running Postgres 12.9 on FreeBSD.
I had a developer ask me the best way to determine a view's dependencies
(i.e. which tables/views are used in a view's query). In Oracle, I would
use the ALL_DEPENDENCIES dictionary view. I found a view called
information_schema.view_table_usage (VTU)
