From: Tom Lane <tgl@sss.pgh.pa.us>
To: jason@starnull.net
cc: pgsql-docs@lists.postgresql.org
Subject: Re: SELECT List with/without parentheses
In-reply-to: <175702516430.356921.959597202664413151@wrigleys.postgresql.org>
References: <175702516430.356921.959597202664413151@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Thu, 04 Sep 2025 22:32:44 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1529414.1757107022.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 05 Sep 2025 17:17:02 -0400
Message-ID: <1529415.1757107022@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1529415.1757107022%40sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> There is no mention of the difference in PostgreSql behavior if the sele=
ct
> list of columns is surrounded by parentheses or not.

What you've written there is an implicit row constructor, that is
"(a,b,...)" is taken as "ROW(a,b,...)".  These are documented at [1],
but it would be quite unwieldy to point out the possibility of this
for every context in which it could be written.

Personally I think implicit row constructors were one of the SQL
committee's worst ideas, precisely because of the surprise factor.
But it's in the standard so we're stuck with it.

			regards, tom lane

[1] https://www.postgresql.org/docs/current/sql-expressions.html#SQL-SYNTA=
X-ROW-CONSTRUCTORS