From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | alexandrebailly1955(at)gmail(dot)com, PostgreSQL Bug List <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #19003: A SELECT that does not return a valid table |
Date: | 2025-07-30 21:38:16 |
Message-ID: | CAKFQuwb9W-Qq7dRkptnW217nfXhPpf_U54_G8Pbwj25qW4_PZw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Jul 30, 2025, 12:50 PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 19003
> Logged by: Alexandre Bailly
> Email address: alexandrebailly1955(at)gmail(dot)com
> PostgreSQL version: 17.5
> Operating system: Windows
> Description:
>
> Returning a table that contains twice the same column should not be
> permitted. It should be a nice mathematical property (closure) if a SELECT
> always returns a valid table.
>
>
This isn't a bug. And at this point, regardless of such purity concerns,
there is no way we are going to change this behavior and break
well-functioning applications.
A query result is not a table. It just has a tabular form (rows and
columns). It is also not a set though set-theory did inspire various
aspects of SQL.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2025-07-31 02:39:31 | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |
Previous Message | Tom Lane | 2025-07-30 21:34:41 | Re: BUG #19003: A SELECT that does not return a valid table |