I have 7.2.4 running on a Sun box, so I tried that too, with similar
results. tsearch just doesn't seem to work very well on this dataset
(or any other large dataset I've tried).
Well, as I've shown - works fine for me...
I strongly suggest you repost your problem report to -hackers, since the
On Fri, Nov 28, 2003 at 01:18:48PM +0800, Christopher Kings-Lynne wrote:
Any thoughts?
Actually, I ran my tests using tsearch V1. I wonder if there has been
some weird regression between tsearch 1 and 2?
Maybe. tsearch2 doesn't seem production ready in other respects
(untsearch2.sql
Any thoughts?
Actually, I ran my tests using tsearch V1. I wonder if there has been
some weird regression between tsearch 1 and 2?
hris
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
On Wed, Nov 26, 2003 at 09:12:30PM -0800, Steve Atkins wrote:
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
On Thu, Nov 27, 2003 at 08:51:14AM +0800, Christopher Kings-Lynne wrote:
Which one is better (performance/easier to use),
tsearch2 or fulltextindex?
there is an example how to use fulltextindex in the
techdocs, but I checked the contrib/fulltextindex
package, there is a WARNING that
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.
