From: Tom Lane <tgl@sss.pgh.pa.us>
To: alexandrebailly1955@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19003: A SELECT that does not return a valid table
In-reply-to: <19003-17a559220b959ea1@postgresql.org>
References: <19003-17a559220b959ea1@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Wed, 30 Jul 2025 19:20:14 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1675173.1753911281.1@sss.pgh.pa.us>
Date: Wed, 30 Jul 2025 17:34:41 -0400
Message-ID: <1675174.1753911281@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1675174.1753911281%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> SELECT 'John' AS nom,'James' AS nom
> returns a table with attributes nom and nom that I can see in the output.
> Returning a table that contains twice the same column should not be
> permitted.

There is pretty much zero chance that we will enforce that
restriction.  It would break too much application code.
Also, it looks to me like there is no such requirement in
the SQL standard.

			regards, tom lane