From: | "Travis Whitton" <tinymountain(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Grabbing Newest Records From Duplicates |
Date: | 2007-03-16 15:55:33 |
Message-ID: | cf9b4f3e0703160855q537eafe6yf3c3bbea090e5b6e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
One last question, using the "weather report" example, is it going to
improve performance for the DISTINCT ON query to add an index to the
location and time columns?
Thanks a lot,
Travis
On 3/16/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Travis Whitton" <tinymountain(at)gmail(dot)com> writes:
> > Given the following test table, I want to grab only the newest record
> and
> > disregard any older duplicates based on name. Is this the most efficient
> way
> > to do it?
>
> No, it's gonna be pretty awful. The best way I know of involves
> DISTINCT ON (see the "weather reports" example in the SELECT reference
> page). Unfortunately that's a Postgres-only construct. If you want
> something portable then you'll need something messy with subqueries...
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-03-16 16:17:41 | Re: Grabbing Newest Records From Duplicates |
Previous Message | Gerardo Herzig | 2007-03-16 15:50:32 | log file permissions? |