On Thu, May 10, 2012 at 12:36 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Chris Angelico <rosuav@gmail.com> writes:
>> On Wed, May 9, 2012 at 2:52 PM, Tom Lane <tgl@sss.pgh.pa.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.
Thank you! Much appreciated.
ChrisA