On Sat, Dec 11, 2004 at 03:17:13PM +0100, Tomas Skäre wrote:
> select c.* from cjm_object c
>  inner join
>   (select max(timestamp) as timestamp,objectid,field from cjm_object
>    group by objectid,field) t
>   using(timestamp,objectid,field)
>  where 1=1 and data is not null
>  order by objectid,field;

Usually, SELECT max(field) FROM table is better written in PostgreSQL as
SELECT field FROM table ORDER field DESC LIMIT 1.

I don't see the point of "where 1=1", though...

/* Steinar */
-- 
Homepage: http://www.sesse.net/

In response to

• Re: Query is not using index when it should at 2004-12-11 14:17:13 from Tomas =?iso-8859-1?q?Sk=E4re?=

Responses

• Re: [GENERAL] Query is not using index when it should at 2004-12-11 16:25:39 from Michael Fuhr
• Re: [GENERAL] Query is not using index when it should at 2004-12-12 08:32:25 from Tomas =?iso-8859-1?q?Sk=E4re?=

pgsql-performance by date

Next:	From: Mike Rylander	Date: 2004-12-11 14:37:15
	Subject: Re: LIMIT causes SEQSCAN in subselect
Previous:	From: Tomas =?iso-8859-1?q?Sk=E4re?=	Date: 2004-12-11 14:17:13
	Subject: Re: Query is not using index when it should

pgsql-sql by date

Next:	From: Stephan Szabo	Date: 2004-12-11 15:47:51
	Subject: Re: replacing mysql enum
Previous:	From: Tomas =?iso-8859-1?q?Sk=E4re?=	Date: 2004-12-11 14:17:13
	Subject: Re: Query is not using index when it should

pgsql-general by date

Next:	From: Ioannis Theoharis	Date: 2004-12-11 15:27:02
	Subject: Clustering in the presence of hierarchies (fwd)
Previous:	From: Tomas =?iso-8859-1?q?Sk=E4re?=	Date: 2004-12-11 14:17:13
	Subject: Re: Query is not using index when it should