Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA02623; Mon, 28 Jun 93 16:22:16 -0700
Date: Mon, 28 Jun 93 16:22:16 -0700
Message-Id: <9306282322.AA02623@postgres.Berkeley.EDU>
From: bunting@pangaea.dme.nt.gov.au (Chris Bunting 61-89-895442)
Subject: Access Methods
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu

I have a problem and was wondering if anyone had any ideas on possible solutions.
It goes like this

I have a class
	create OBJECT( bbox     =     BOX, m_type   =     int4)

and it has the following indices 

define index obj_bbox on OBJECT using rtree (bbox box_ops)
define index obj_mtype on OBJECT using btree (m_type int4_ops)

the idea being to store the bounding box of spatial data of different types
hence the m_type.

The query optimiser seems to always give the rtree index a higher priority
than the btree and I want it to have the opposite behaviour.

Does anyone have any suggestions.

Thanks

Chris Bunting
Database Manager
NT Dept of Mines and Energy
PO Box 2901
DARWIN NT 0801
AUSTRALIA
email    bunting.dme.nt.gov.au
voice    61-89-895442
fax      61-89-817861