From: | Kevin Way <kevin(dot)way(at)overtone(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: aggregate functions, COUNT |
Date: | 2001-10-03 02:54:41 |
Message-ID: | 20011003025441.C36630@bean.overtone.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [02-10-01 18:02]:
> Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> > I think you could use EXISTS for that,
> > select EXISTS (<query>); should give a true/false on whether the
> > query returned any rows. I'm not sure if it stops after one row
> > or not, but if it doesn't you can add a limit 1 to the query.
>
> Yes it does stop after one row; and furthermore, the planner knows to
> generate a fast-start plan for it. (Or at least it's supposed to
> ... hmm, this seems to be broken in current sources ...) Anyway,
> there's no need for LIMIT 1 inside an EXISTS, because the planner
> assumes that automatically.
Thank you muchly, I did some profiling and SELECT EXISTS is indeed
exactly what I wanted.
-Kevin Way
--
Kevin Way <kevin(dot)way(at)overtone(dot)org>
http://www.overtone.org/
From | Date | Subject | |
---|---|---|---|
Next Message | postgresql | 2001-10-03 13:55:23 | |
Previous Message | Barry Lind | 2001-10-03 01:18:54 | Re: jdbc driver |