| From: | Frank Bax <fbax(at)sympatico(dot)ca> |
|---|---|
| To: | Chester Carlton Young <chestercyoung(at)yahoo(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Resources |
| Date: | 2002-01-11 19:18:09 |
| Message-ID: | 3.0.6.32.20020111141809.021c4eb0@pop6.sympatico.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank Bax | 2002-01-11 21:13:13 | Re: Resources |
| Previous Message | Chester Carlton Young | 2002-01-11 17:39:43 | Re: Resources |