From: | Matthew Wakeling <matthew(at)flymine(dot)org> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Very specialised query |
Date: | 2009-03-27 12:45:40 |
Message-ID: | alpine.DEB.2.00.0903271242250.21772@aragorn.flymine.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, 26 Mar 2009, I wrote:
> release-16.0-preview-14-mar=# \d location
> Table "public.location"
> Column | Type | Modifiers
> -----------------+---------+-----------
> end | integer |
> start | integer |
> objectid | integer |
> id | integer | not null
> Indexes:
> "location__object" btree (objectid, id)
> "location__start" btree (start)
> "location_bioseg" gist (bioseg_create(intermine_start, intermine_end))
So, it would be useful if we could make the location_bioseg index a
multi-column index, like this:
CREATE INDEX location_bioseg3 ON location USING GIST (objectid, bioseg_create(intermine_start, intermine_end));
However, I get the following error message:
ERROR: data type integer has no default operator class for access method "gist"
HINT: You must specify an operator class for the index or define a default operator class for the data type.
Is there an operator class for integer for gist indexes that I can use?
Matthew
--
And why do I do it that way? Because I wish to remain sane. Um, actually,
maybe I should just say I don't want to be any worse than I already am.
- Computer Science Lecturer
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-03-27 14:30:02 | Re: Very specialised query |
Previous Message | Scott Carey | 2009-03-26 22:02:08 | Re: Raid 10 chunksize |