[PERFORM] Index row requires 9324 bytes maximum size is 8191
solAris23
Hello,
I am trying to index a field in my database of size about 16K rows, but i m
getting this error.
" Index row requires 9324 bytes maximum size is 8191 "
Can anyone please guide me how to remove this error....
Also, average time to search for a query in a table is taking about 15
seconds. I have done indexing but the time is not reducing.....
Is there any way to reduce the time to less than 1 sec ???
The type of indexing which I am performing on the field is btree... My field
contains large text. Is there any more suitable indexing type ??
--
View this message in context: http://www.nabble.com/Index-row-requires-9324-bytes-maximum-size-is-8191-tp25511356p25511356.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
--
Sent via pgsql-performance mailing list (pgsql-pe...@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Euler Taveira de Oliveira
> I am trying to index a field in my database of size about 16K rows, but i m
> getting this error.
>
> " Index row requires 9324 bytes maximum size is 8191 "
>
That is a known limitation; but even if it would be possible I don't think it
would be a good idea. Why on Earth would I search using a big field?
What kind of content are you trying to index?
--
Euler Taveira de Oliveira
http://www.timbira.com/
Pavel Stehule
2009/9/18 solAris23 <vikas...@dolcera.com>:
>
>
> Hello,
>
> I am trying to index a field in my database of size about 16K rows, but i m
> getting this error.
>
> " Index row requires 9324 bytes maximum size is 8191 "
>
> Can anyone please guide me how to remove this error....
>
> Also, average time to search for a query in a table is taking about 15
> seconds. I have done indexing but the time is not reducing.....
> Is there any way to reduce the time to less than 1 sec ???
> The type of indexing which I am performing on the field is btree... My field
> contains large text. Is there any more suitable indexing type ??
>
you can use hashing functions
regards
Pavel Stehule
Grzegorz Jaśkiewicz
http://gjsql.wordpress.com/2009/04/19/how-to-speed-up-index-on-bytea-text-etc/
instead.
Florian Weimer
> Also, average time to search for a query in a table is taking about 15
> seconds. I have done indexing but the time is not reducing.....
> Is there any way to reduce the time to less than 1 sec ???
How are your queries structured? Do you just compare values? Do you
perform range queries? Or something like "WHERE col LIKE '%string%')?
--
Florian Weimer <fwe...@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
solAris23
Euler Taveira de Oliveira-2 wrote:
>
> solAris23 escreveu:
>> I am trying to index a field in my database of size about 16K rows, but i
>> m
>> getting this error.
>>
> Why are you want to index such a big field? BTW, it'll be worthless.
>
>> " Index row requires 9324 bytes maximum size is 8191 "
>>
> That is a known limitation; but even if it would be possible I don't think
> it
> would be a good idea. Why on Earth would I search using a big field?
>
> What kind of content are you trying to index?
>
> Thanks for the feed back... Actually I want to index text field which is
> substantially big.
> As I already told in the post.. the searching takes too long.. so I want
> to index it....
>
> I went through gist and gin indexes but they are applicable for tsvector
> and tsquery i think...
>
> For me any option is fine... if i am able to get result within a
> second....
>
> Thanks.
>
>
> --
> Euler Taveira de Oliveira
> http://www.timbira.com/
>
> --
> Sent via pgsql-performance mailing list (pgsql-pe...@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>
>
--
View this message in context: http://www.nabble.com/Index-row-requires-9324-bytes-maximum-size-is-8191-tp25511356p25549641.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.