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: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
- Re: [HACKERS] How to get aroun... The Hermit Hacker
- Re: [HACKERS] How to get around LI... Philip Warner
- Re: [HACKERS] How to get aroun... The Hermit Hacker
- Re: [HACKERS] How to get around LIKE ineffi... Bruce Momjian
- Re: [HACKERS] How to get around LIKE in... Tom Lane
- Re: [HACKERS] How to get around LI... Bruce Momjian
- Re: [HACKERS] How to get aroun... The Hermit Hacker
- Re: [HACKERS] How to get aroun... Bruce Momjian
- Re: [HACKERS] How to get aroun... Tom Lane
- Re: [HACKERS] How to get aroun... Bruce Momjian
- Re: [HACKERS] How to get around LIKE inefficiencies... The Hermit Hacker
- Re: [HACKERS] How to get around LIKE inefficiencies? Ron Chmara
- Re: [HACKERS] How to get around LIKE inefficiencies? Tatsuo Ishii