pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Cheston <ccheston@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: How to create an index for type timestamp column using rtree?
Date: Tue, 13 Jul 2004 00:56:02 -0700
Message-ID: <e071108e04071300564c0c5379@mail.gmail.com> (raw)
In-Reply-To: <40F3824C.8090607@familyhealth.com.au>
References: <e071108e040712225174cda991@mail.gmail.com>
	<40F3824C.8090607@familyhealth.com.au>

Thanks,  Chris and Tom.
I had read *incorrectly* that rtrees are better for <= and >= comparisons.

Chris

On Tue, 13 Jul 2004 14:33:48 +0800, Christopher Kings-Lynne
<chriskl@familyhealth.com.au> wrote:
> > I'm storing some timestamps as integers (UTF) in a table and I want to
> > query by <= and >= for times between a certain period.  The table has
> > gotten quite large and is now very slow in querying.
> >
> > I think it's time to create an index for the timestamp column.
> 
> Uh, yeah.
> 
> > I tried using an rtree (for <= and >= optimization):
> 
> Bad idea.
> 
> > Do I have to create an rtree type for my timestamp integer column?
> 
> Why do you want an rtree index?  They're for multidimensional polygonal
> data and stuff.  Just create a normal index...
> 
> Chris
> 
>



view thread (4+ messages)

Message-ID: <e071108e04071300564c0c5379@mail.gmail.com>
Permalink:  ../e071108e04071300564c0c5379@mail.gmail.com/
Also on:    postgresql.org/message-id/e071108e04071300564c0c5379@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: ccheston@gmail.com
  Subject: Re: How to create an index for type timestamp column using rtree?
  In-Reply-To: <e071108e04071300564c0c5379@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox