Re: "SELECT FROM foo" acts like "SELECT COUNT(*) FROM foo"?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: "SELECT FROM foo" acts like "SELECT COUNT(*) FROM foo"?
Date: 2023-02-01 20:10:21
Message-ID: 1409990.1675282221@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ron <ronljohnsonjr(at)gmail(dot)com> writes:
> v12.13
> https://www.postgresql.org/docs/12/sql-select.html

> The docs say that one of these are required in the SELECT list.

> [ * |/|expression|/ [ [ AS ]/|output_name|/ ] [, ...] ]

Really? I don't see anything to that effect in either the syntax
synopsis or the text, plus there's this in the Compatibility section:

Empty SELECT Lists

The list of output expressions after SELECT can be empty, producing a
zero-column result table. This is not valid syntax according to the
SQL standard. PostgreSQL allows it to be consistent with allowing
zero-column tables. However, an empty list is not allowed when
DISTINCT is used.

We probably did say that before 9.4 or so, but if you still find it
in modern releases, please say exactly where.

> However, *not* mentioning anything also works, though acts like COUNT(*).

Well, you get some number of zero-column rows. psql's display of that is
a bit idiosyncratic, but nobody's bothered to improve it.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Siddharth Jain 2023-02-01 20:13:18 Re: FATAL: database "xxx" does not exist when it does
Previous Message David G. Johnston 2023-02-01 20:06:56 Re: "SELECT FROM foo" acts like "SELECT COUNT(*) FROM foo"?