Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit - Mailing list pgsql-patches

From Euler Taveira de Oliveira
Subject Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit
Date
Msg-id 47D0DD31.2090908@timbira.com
Whole thread Raw
In response to Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Tom Lane wrote:

> I don't think that follows.  A tsearch index is lossy anyway, so there's
> no hard and fast reason why it should reject entries that it can't index
> completely.  I think it would be more useful to index whatever it can
> (probably just the words in the first N bytes of the document) than to
> prevent you from storing the document.
>
The problem with this approach is how to select the part of the document
to index. How will you ensure you're not ignoring the more important
words of the document?
IMHO Postgres shouldn't decide it; it would be good if an user could set
it runtime and/or on postgresql.conf.


--
   Euler Taveira de Oliveira
   http://www.timbira.com/

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit