Re: Speeding up Aggregates

From: Rod Taylor <rbt(at)rbt(dot)ca>
To: Dror Matalon <dror(at)zapatec(dot)com>
Cc: Postgresql Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Speeding up Aggregates
Date: 2003-10-03 22:10:29
Message-ID: 1065219028.91586.8.camel@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, 2003-10-03 at 17:53, Dror Matalon wrote:
> On Fri, Oct 03, 2003 at 05:44:49PM -0400, Rod Taylor wrote:
> > > item_max_date() looks like this:
> > > select max(dtstamp) from items where channel = $1 and link = $2;
> >
> > It is too bad the (channel, link) index doesn't have dtstamp at the end
> > of it, otherwise the below query would be a gain (might be a small one
> > anyway).
> >
> > select dtstamp
> > from items
> > where channel = $1
> > and link = $2
> > ORDER BY dtstamp DESC
> > LIMIT 1;

It didn't make a difference even with the 3 term index? I guess you
don't have very many common values for channel / link combination.

How about the below? Note the word STABLE on the end.

CREATE or REPLACE FUNCTION item_max_date (int4, varchar) RETURNS
timestamptz AS '
select max(dtstamp) from items where channel = $1 and link = $2;
' LANGUAGE 'sql' STABLE;

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Neil Conway 2003-10-03 22:11:45 Re: reindex/vacuum locking/performance?
Previous Message Dror Matalon 2003-10-03 22:03:58 Re: Speeding up Aggregates