Re: Different execution plans for semantically equivalent queries - Mailing list pgsql-performance

From Tom Lane
Subject Re: Different execution plans for semantically equivalent queries
Date
Msg-id 15642.1297027741@sss.pgh.pa.us
Whole thread Raw
In response to Different execution plans for semantically equivalent queries  (Mikkel Lauritsen <renard@tala.dk>)
Responses Re: Different execution plans for semantically equivalent queries  (Mikkel Lauritsen <renard@tala.dk>)
List pgsql-performance
Mikkel Lauritsen <renard@tala.dk> writes:
> I would like to do a query which retrieves the newest record for each
> type, and the persistence framework that I'm using does something
> which is structurally like

> SELECT * FROM table t1 WHERE 0 = (SELECT COUNT(*) FROM table t2 WHERE
>     t2.type = t1.type AND t2.timestamp > t1.timestamp)

I suspect that *any* database is going to have trouble optimizing that.
You'd be well advised to lobby the persistence framework's authors to
produce less brain-dead SQL.  The NOT EXISTS formulation seems to
express what's wanted much less indirectly.

            regards, tom lane

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Does auto-analyze work on dirty writes? (was: Re: [HACKERS] Slow count(*) again...)
Next
From: Linos
Date:
Subject: Re: general hardware advice