Search Postgresql Archives

Re: index row size exceeds btree maximum, 2713 -

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2005-07-19 at 10:25, Tom Lane wrote:
> Scott Marlowe <smarlowe@xxxxxxxxxxxxxxxxx> writes:
> > On Tue, 2005-07-19 at 05:42, Dennis Bjorklund wrote:
> >> You can index text fields, but you can't insert values bigger then 
> >> BLOCKSIZE/3 when you have an index on that column.]
> 
> > Please note that the size limitation is for btree indexes, the most
> > common and well tested index types.
> > For hash you can have a much larger value, but only direct matching is
> > supported.
> > I don't know about GiST...
> 
> None of the index types support entries larger than BLOCKSIZE-less-a-bit,
> so switching to a different index type won't do more than push the
> problem out by a factor of about 3.

Are they compressed?  It would look to me like maybe they are, or
something strange like that.  When I fed highly compressable data into
an indexed field, it took a LOT of said text to get a failure method.

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux