From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: How to get around LIKE inefficiencies? |
Date: | 2000-11-06 03:18:34 |
Message-ID: | 3.0.5.32.20001106141834.02884c20@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 23:12 5/11/00 -0400, The Hermit Hacker wrote:
>
>Except, if we are telling it to get rid of using the index, may as well
>get rid of it altogether, as updates/inserts would be slowed down by
>having to update that too ...
>
So long as you don't ever need the index for anything else, then getting
rid of it is by far the best solution. But, eg, if you want to check if a
page is already indexed you will probably end up with a sequential search.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Chmara | 2000-11-06 03:19:21 | Re: How to get around LIKE inefficiencies? |
Previous Message | Tom Lane | 2000-11-06 03:17:21 | Re: How to get around LIKE inefficiencies? |