Re: index row requires 10040 bytes, maximum size is 8191

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: akp geek <akpgeek(at)gmail(dot)com>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, jd(at)commandprompt(dot)com, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: index row requires 10040 bytes, maximum size is 8191
Date: 2010-11-15 19:36:17
Message-ID: 5018.1289849777@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

akp geek <akpgeek(at)gmail(dot)com> writes:
> What we do with the text that I have mentioned is, we have
> search functionality on the text. The user enters some keywords and then the
> application should be able to search for all the text that matches the key
> word.

Well, a btree index on the entire string is approximately useless for
that anyway. Look into the text search functionality.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-11-15 19:52:16 Re: Backends "hanging" with strace showing selects?
Previous Message hubert depesz lubaczewski 2010-11-15 19:35:46 Backends "hanging" with strace showing selects?