Re: For full text indexing, which is better, tsearch2 or
От
Steve Atkins
Тема
Re: For full text indexing, which is better, tsearch2 or
Дата
Msg-id
20031127051230.GA6212@gp.word-to-the-wise.com
Ответ на
Re: For full text indexing, which is better, tsearch2 or (Christopher Kings-Lynne)
Список
Дерево обсуждения
For full text indexing, which is better, tsearch2 or fulltextindex LIANHE SHAO <lshao2@jhmi.edu>
Re: For full text indexing, which is better, tsearch2 or Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: For full text indexing, which is better, tsearch2 or Dror Matalon <dror@zapatec.com>
Re: For full text indexing, which is better, tsearch2 or Steve Atkins <steve@blighty.com>
Re: For full text indexing, which is better, tsearch2 or Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: For full text indexing, which is better, tsearch2 or Steve Atkins <steve@blighty.com>
Re: For full text indexing, which is better, tsearch2 or Steve Atkins <steve@blighty.com>
Re: For full text indexing, which is better, tsearch2 or Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: For full text indexing, which is better, tsearch2 or Steve Atkins <steve@blighty.com>
Re: For full text indexing, which is better, tsearch2 or Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: For full text indexing, which is better, tsearch2 or Christopher Kings-Lynne <chriskl@familyhealth.com.au>
On Thu, Nov 27, 2003 at 12:41:59PM +0800, Christopher Kings-Lynne wrote: > >Does anyone have any metrics on how fast tsearch2 actually is? > > > >I tried it on a synthetic dataset of a million documents of a hundred > >words each and while insertions were impressively fast I gave up on > >the search after 10 minutes. > > > >Broken? Unusable slow? This was on the last 7.4 release candidate. > > I just created a 1.1million row dataset by copying one of our 30000 row > production tables and just taking out the txtidx column. Then I > inserted it into itself until it had 1.1 million rows. > > Then I created the GiST index - THAT took forever - seriously like 20 > mins or half an hour or something. > > Now, to find a word: > > select * from tsearchtest where ftiidx ## 'curry'; > Time: 9760.75 ms > So, I have no idea why you think it's slow? Perhaps you forgot the > 'create index using gist' step? No, it was indexed. Thanks, that was the datapoint I was looking for. It _can_ run fast, so I just need to work out what's going on. (It's hard to diagnose a slow query when you've no idea whether it's really 'slow'). Cheers, Steve
В списке pgsql-performance по дате отправления
От: Christopher Kings-Lynne
Дата: