| From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Edwin Groothuis <postgresql(at)mavetju(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit |
| Date: | 2008-03-07 06:14:09 |
| Message-ID: | 47D0DD31.2090908@timbira.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs 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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-07 06:52:24 | Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit |
| Previous Message | ykhuang | 2008-03-07 03:27:35 | Error during hash index scans can cause postgres halt! |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-07 06:52:24 | Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit |
| Previous Message | Bruce Momjian | 2008-03-07 01:40:56 | Re: Terminating a backend |