From: Tom Lane <tgl@sss.pgh.pa.us>
To: pageorge@unice.fr
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17404: CREATE OR REPLACE VIEW does not properly change the
 COLLATION of an existing field.
In-reply-to: <17404-8a4a270ef30a6709@postgresql.org>
References: <17404-8a4a270ef30a6709@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 15 Feb 2022 08:51:11 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3049977.1644941552.1@sss.pgh.pa.us>
Date: Tue, 15 Feb 2022 11:12:32 -0500
Message-ID: <3049978.1644941552@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3049978.1644941552%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> create TABLE my_table (my_text TEXT);
> create VIEW my_view AS SELECT my_text COLLATE "C" FROM my_table;
> create OR REPLACE view my_view AS SELECT my_text COLLATE "en_US.utf8" FROM
> my_table;

> The COLLATION of "my_view"."my_text" should have been changed to
> "en_US.utf8".  
> - OR -
> I should have got an error message telling me that it is not possible.

Yeah, that's a bug, it should have thrown an error.

(Changing the collation is impractical for the same reasons that
changing the output datatype is impractical.)

			regards, tom lane