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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 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
Date: 2022-10-11 14:58:19
Message-ID: 311953.1665500299@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-10-11 15:07:45 Re: BUG #17633: Define rule on views which do insert to another relation trigger cache lookup failed error.
Previous Message Japin Li 2022-10-11 14:35:50 Re: BUG #17633: Define rule on views which do insert to another relation trigger cache lookup failed error.