Re: index row size exceeds btree maximum, 2713 -

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>
Cc: Jaime Casanova <systemguards(at)gmail(dot)com>, Dan Armbrust <daniel(dot)armbrust(dot)list(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: index row size exceeds btree maximum, 2713 -
Date: 2005-07-19 14:48:25
Message-ID: 1121784505.8208.358.camel@state.g2switchworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 2005-07-19 at 05:42, Dennis Bjorklund wrote:
> On Mon, 18 Jul 2005, Jaime Casanova wrote:
>
> > I don't think you could create indexes on text fields... there are
> > other type of indexes for that... tsearch2 for example
>
> 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...

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ilja Golshtein 2005-07-19 15:01:05 Re: Old question - failed to find conversion function from "unknown"
Previous Message Tom Lane 2005-07-19 14:44:37 Re: pg_dump and write locks