Skip site navigation (1) Skip section navigation (2)

max(*)

From: Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: max(*)
Date: 2006-05-26 08:22:21
Message-ID: 4476BABD.4080100@zigo.dhs.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Shouldn't

   SELECT max(*) FROM foo;

give an error? Instead it's executed like

   SELECT max(1) FROM foo;

Just like count(*) is executed as count(1).

Something for the TODO or is it a feature?

ps. I know it's not an important case since no one sane would try to 
calculate max(*), but still.

/Dennis

Responses

  • Re: max(*) at 2006-05-26 10:09:48 from Simon Riggs

pgsql-hackers by date

Next:From: Simon RiggsDate: 2006-05-26 09:59:37
Subject: Re: XLogArchivingActive
Previous:From: Teodor SigaevDate: 2006-05-26 08:08:54
Subject: Re: GIN stuck in loop during PITR

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group