--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Fecha: Jueves, 17 de Julio de 2003 04:23:23 p.m.
A: Marvin
Asunto: Re: [ADMIN] Sub-Select problem
I executed this same query and all the rows have been showed. The onlyproblem was I had to include field2 in the group by statement.I am running postgresql 7.2.3-5.80 over Red Hat 8.- Original Me
I was trying to do something like this.
Select Field1, Field2, Total
FROM
(Select Field1, Field2, SUM(Field3) as Total
From TableA
Where DateHired <= CAST('08/01/2003' AS DATE)
GROUP BY Field1) as MyTable;
The sub-select query tested alone returns me a lot of rows,
howeve
On Wed, 25 Sep 2002, Waruna Geekiyanage wrote:
> I have a select query with 2 sub selects.
> When I run that query CPU usage goes to 98% for postgres.
> Does sub selects eat more resources and slower the queries?
> Is there any alternatives to sub selects?
It depends on what you're doing. The
I have a select query with 2 sub
selects.
When I run that query CPU usage goes to 98%
for postgres.
Does sub selects eat more resources and slower
the queries?
Is there any alternatives to sub
selects?
Jodi Kanter <[EMAIL PROTECTED]> writes:
> select usf_fk from am_spots where ams_pk in (select min(ams_pk), max(ams_pk=
> ) from am_spots where am_fk>135);
> I received an error saying that my subselect has too many fields. Did I use=
> the wrong syntax or is it just a postgres rule that you can'