RE: BUG #17634: Inconsistent view_definition in information_schema.views

Then perhaps the rule decompiler should be used when populating a column that implies it contains the view definition - because it is not the correct definition. No snark intended, just my thoughts. On a related note, having dependencies for all object (including functions and procedures) available in postgres would be awesome. You all provide a great product for us opensource users, and it's appreciated.

-----Original Message-----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Sent: Tuesday, October 11, 2022 9:58 AM
To: Blum, Kimber <kimber7(at)illinois(dot)edu>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17634: Inconsistent view_definition in information_schema.views

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> If I run my query against information_schema.views while my session is
> active in a schema that is referenced in my query,
> information_schema.views strips out that schema name. All other objects remain schema qualified.

This is not a bug, it's normal behavior of the rule decompiler:
object names are qualified only if necessary (where "necessary"
means "would not be found in a search_path search").

If you don't like it, set search_path to empty.

regards, tom lane