From: Frank Bax <fbax@sympatico.ca>
To: Chester Carlton Young <chestercyoung@yahoo.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Resources
Date: Fri, 11 Jan 2002 14:18:09 -0500
Message-ID: <3.0.6.32.20020111141809.021c4eb0@pop6.sympatico.ca> (raw)
In-Reply-To: <20020111173943.69680.qmail@web12703.mail.yahoo.com>
References: <NEBBLAAHGLEEPCGOBHDGEEOKECAA.nickf@ontko.com>
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
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-sql@postgresql.org
Cc: fbax@sympatico.ca, chestercyoung@yahoo.com
Subject: Re: Resources
In-Reply-To: <3.0.6.32.20020111141809.021c4eb0@pop6.sympatico.ca>
* 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