[Xapian-discuss] "Value in posting list too large" error with 1.1.4 (chert and brass, not flint)

[Olly Betts]

On Sun, Mar 07, 2010 at 05:14:18PM -0500, Jason Tackaberry wrote:
> A bit more digging reveals that if I strip out all non-word characters
> from the query I was periodically performing, the problem goes away.
> 
> I _was_ using the query parser.  I'm now constructing the query directly
> (it's a phrase search), which is obviously better anyway.
> 
> But it appears there might be something about non-word characters that
> isn't being handled robustly in chert and brass.

It seems to me this is certain to be a red-herring.  Except for zero bytes
the characters in a term just a string of bytes to the backend.

So it's just coincidence that changing the query avoids the problem.

Cheers,
    Olly