On Thu, 8 Nov 2001, Bob Okumura wrote: > splitting into separate databases won't help if I still run > out of memory in htmerge when putting them back > together again.
Yes, this is correct. > > Certainly the htmerge phase, which in 3.1.x consumes a > > *lot* of memory for some people isn't needed. > > Are you saying that running htmerge in 3.1.x is not > needed? I doubt that you did, but was wondering what No, sorry if that was misleading. You were asking about the memory consumption of 3.2. The htdig indexing requires more memory in 3.2, but it's building the databases as it goes, so you don't need to sort. (In fact, htmerge in 3.2.0b3 and later is not used except to merge databases. Instead the htpurge utility will "clean out" unused/unreachable documents.) > On a different tack, using 3.1.5, can I run htsearch to > simultaneously search through multiple databases in one > query? Hmm. I seem to remember that a patch for "collections" support was posted for 3.1.x before it was ported to 3.2.x betas. But I can't find it in the patch archive or the list archives. > If all else, and the above fails, again does anyone have > any clues for getting past the 3.2.0b3 compile errors I > mentioned earlier? If multiple database querying is I'm sorry, I don't remember those particular errors. But I'd suggest grabbing a snapshot of 3.2.0b4 before trying 3.2.0b3. <http://www.htdig.org/files/snapshots/> -- -Geoff Hutchison Williams Students Online http://wso.williams.edu/ _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
