Re: BUG #19003: A SELECT that does not return a valid table

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, alexandrebailly1955(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19003: A SELECT that does not return a valid table
Date: 2025-07-31 09:17:14
Message-ID: bd9a5a27-e020-4975-8c46-0c30a67bff50@postgresfriends.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On 30/07/2025 23:34, Tom Lane wrote:
> PG Bug reporting form<noreply(at)postgresql(dot)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.

Indeed.  In SQL:2023-1 (available free of charge at [1]) says in
Subclause 4.6, "Tables":

    "An operation that references zero or more base tables and returns
a table is called a *query*. The result of a query is called a *derived
table*."

and

    "Derived tables, other than viewed tables, may contain more than
one column with the same name."

So, not only is this not a bug we should fix, it is explicitly allowed
by the standard.

[1] https://www.iso.org/standard/76583.html

--

Vik Fearing

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexandre Bailly 2025-07-31 10:50:32 Re: BUG #19003: A SELECT that does not return a valid table
Previous Message Hayato Kuroda (Fujitsu) 2025-07-31 09:03:58 RE: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database