Received: from tomts17-srv.bellnexxia.net (tomts17.bellnexxia.net [209.226.175.71]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0BJJ1B00792 for ; Fri, 11 Jan 2002 14:19:01 -0500 (EST) (envelope-from fbax@sympatico.ca) Received: from ACER ([65.93.1.15]) by tomts17-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with SMTP id <20020111191901.EXRT16289.tomts17-srv.bellnexxia.net@ACER>; Fri, 11 Jan 2002 14:19:01 -0500 Message-Id: <3.0.6.32.20020111141809.021c4eb0@pop6.sympatico.ca> X-Sender: b1wudu74@pop6.sympatico.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 11 Jan 2002 14:18:09 -0500 To: Chester Carlton Young From: Frank Bax Subject: Re: Resources Cc: pgsql-sql@postgresql.org In-Reply-To: <20020111173943.69680.qmail@web12703.mail.yahoo.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Archive-Number: 200201/101 X-Sequence-Number: 6190 Or you could create a function to extract the data from an existing field, then index on the function? At 09:39 AM 1/11/02 -0800, Chester Carlton Young wrote: >In regards to not being able to change tables, a common trick (eg, in >data warehousing) where tables are read only, is to have a trigger on >the table populate a secondary table with good index info (like ripping >street name out of the address) and the oid of the original row. The >query is a little more complex, but very good performance. > > >> You mention that it may be too late to change the tables, but I guess >> that's where I'd look next- I once had a similar situation when I >> worked for an electric utility & we ended up parsing the address lines >> to find road names & numbers and then loading them into special indexed >> fields just used for sorting. If you control the input app, maybe you >> could even have the user enter the fields you want to query on separately. >> >> -Nick