Re: Seeking performance advice: Index for "recent entries"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Angelico <rosuav(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Seeking performance advice: Index for "recent entries"
Date: 2012-05-09 14:36:33
Message-ID: 20217.1336574193@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Chris Angelico <rosuav(at)gmail(dot)com> writes:
> On Wed, May 9, 2012 at 2:52 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I think this falls under the rubric of "premature optimization is the
>> root of all evil". Just use a plain index on the timestamptz column
>> and be happy. Searches that only look at the extremal values of a
>> column work perfectly well with a full index, because they only need to
>> examine a small range of the index.

> The index is actually on two columns, an account ID followed by the
> effective date - I need to look up whether any particular account has
> recent entries. Does that make any difference?

Should still work all right, though you might want to check plans and
timings on some test data to be sure.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Angelico 2012-05-09 14:56:56 Re: Seeking performance advice: Index for "recent entries"
Previous Message Richard Harley 2012-05-09 14:34:55 Re: relpages sudden increase