From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> |
Cc: | PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: count(*) of zero rows returns 1 |
Date: | 2013-01-13 21:43:28 |
Message-ID: | 12414.1358113408@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> writes:
> Can somebody explain why a standalone count(*) returns 1?
> postgres=# select count(*);
> count
> -------
> 1
> (1 row)
The Oracle equivalent of that would be "SELECT count(*) FROM dual".
Does it make more sense to you thought of that way?
> I agree it's an odd thing for someone to query, but I feel it should return
> 0, and not 1.
For that to return zero, it would also be necessary for "SELECT 2+2"
to return zero rows. Which would be consistent with some views of the
universe, but not particularly useful. Another counterexample is
regression=# select sum(42);
sum
-----
42
(1 row)
which by your argument would need to return NULL, since that would be
SUM's result over zero rows.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2013-01-13 21:50:10 | Re: pgcrypto seeding problem when ssl=on |
Previous Message | Tom Lane | 2013-01-13 21:37:53 | Re: erroneous restore into pg_catalog schema |