| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "pajai" <patrick(dot)jayet(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: limit over attribute size if index over it exists |
| Date: | 2006-06-26 20:25:10 |
| Message-ID: | 22568.1151353510@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"pajai" <patrick(dot)jayet(at)gmail(dot)com> writes:
> I have got an issue with PostgreSQL. There is a limitation on the
> column length of a tuple, in case there is an index over it. In the
> actual project I am working on, I meet such a situation. I have got an
> attribute over which I am doing a search (that is, I need an index over
> it), but this attribute can be in some cases very large (100KB+).
It sounds to me a lot like you may be in need of full-text-index code ---
see contrib/tsearch2. If you were not trying to roll-your-own text
searcher, please give more details. I can hardly imagine a situation in
which it is useful to make a btree index on 100KB values.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Broersma Jr | 2006-06-26 20:45:55 | Re: inheritance and table |
| Previous Message | Tom Lane | 2006-06-26 20:19:40 | Re: list or regular expressions |