From: Tom Lane <tgl@sss.pgh.pa.us>
To: ariel@mashraki.co.il
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18117: View definitions were changed in version 16 (missing
 column qualifiers)
In-reply-to: <18117-972f125de280aa93@postgresql.org>
References: <18117-972f125de280aa93@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Wed, 20 Sep 2023 09:08:31 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <523985.1695219612.1@sss.pgh.pa.us>
Date: Wed, 20 Sep 2023 10:20:12 -0400
Message-ID: <523986.1695219612@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/523986.1695219612%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I'm not sure if this change was intentional since it wasn't mentioned in the
> release notes, or at least, I couldn't find it there. Running the three
> statements below in version 16 produces ~different results from those in all
> versions before 16. I checked this against versions 11, 12, ... 15

> Statements:
> create table t(c int);
> create view v(c) as select c from t;
> select view_definition from information_schema.views where table_name='v';

Yeah, that was intentional, cf

https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=47bb9db75

I don't see any corresponding entry in the v16 release notes,
but it doesn't surprise me that Bruce would have deemed this
an internal change not worth documenting.  Minor cosmetic
changes in the output of view deparsing are very common.

			regards, tom lane