From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: How to get around LIKE inefficiencies? |
Date: | 2000-11-06 03:01:37 |
Message-ID: | Pine.BSF.4.21.0011052300190.928-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
yowch ... removing that one index makes my 'test' search (mvcc) come back
as:
[97366] SQL 0.05s: SELECT ndict.url_id,ndict.intag FROM ndict,url WHERE ndict.word_id=572517542 AND url.rec_id=ndict.url_id AND (url.url LIKE 'http://www.postgresql.org/%')
vs what we were doing before ... now, let's see how increasing the number
of docs indexed changes this ...
thanks ...
On Sun, 5 Nov 2000, Tom Lane wrote:
> A brute-force answer would be to remove the url_url index ;-)
> dunno if that would slow down other queries, however.
>
> regards, tom lane
>
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Warner | 2000-11-06 03:10:36 | Re: How to get around LIKE inefficiencies? |
Previous Message | Tom Lane | 2000-11-06 02:59:03 | Re: How to get around LIKE inefficiencies? |