From: teknokrat <teknokrat@yahoo.com>
Subject: Re: indexing timestamp fields
Date: Wed, 15 Oct 2003 21:25:17 +0100
Organization: Hub.Org Networking Services
Lines: 20
Message-ID: <bmkafb$aiu$1@news.hub.org>
References: <bmjqo8$1hve$1@news.hub.org>
	<60wub6wjxf.fsf@dev6.int.libertyrms.info>
Reply-To: teknokrat@yahoo.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0+) Gecko/20020518
In-Reply-To: <60wub6wjxf.fsf@dev6.int.libertyrms.info>
To: pgsql-sql@postgresql.org

Christopher Browne wrote:

> teknokrat <teknokrat@yahoo.com> writes:
> 
>>Is it a good idea to index timestamp fields? what about date fields in
>>general?
> 
> 
> If you need to order by a timestamp, then it can be worthwhile.
> 
> If that timestamp can be null, and is rarely populated, then you might
> get a _big_ benefit from creating a partial index as with:
> 
>  create index by_some_date on my_table(some_date) where some_date is
>    not null;

I have a lot of queries of the " where timestamp < some date " type and 
was wondering if an index would improve performance. None of the 
timestamps are null and they are always populated