Re: index row size exceeds btree maximum, 2713 - - Mailing list pgsql-general

From Scott Marlowe
Subject Re: index row size exceeds btree maximum, 2713 -
Date
Msg-id 1121790031.8208.369.camel@state.g2switchworks.com
Whole thread Raw
In response to Re: index row size exceeds btree maximum, 2713 -  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: index row size exceeds btree maximum, 2713 -
List pgsql-general
On Tue, 2005-07-19 at 10:25, Tom Lane wrote:
> Scott Marlowe <smarlowe@g2switchworks.com> 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.

pgsql-general by date:

Previous
From: Samuel Thoraval
Date:
Subject: Re: Hot to restrict access to subset of data
Next
From: Tom Lane
Date:
Subject: Re: index row size exceeds btree maximum, 2713 -