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

From Tom Lane
Subject Re: index row size exceeds btree maximum, 2713 - Solutions?
Date
Msg-id 16848.1121719242@sss.pgh.pa.us
Whole thread Raw
In response to Re: index row size exceeds btree maximum, 2713 - Solutions?  (Dan Armbrust <daniel.armbrust.list@gmail.com>)
List pgsql-general
Dan Armbrust <daniel.armbrust.list@gmail.com> writes:
> The index that is failing is CREATE INDEX i1 ON conceptproperty USING
> btree (codingschemename, property, propertyvalue).<br>
> <br>
> Usually, the 'propertyValue' field is fairly short - 100 chars or
> less.  And in those cases, I need to be able to do an indexed search on
> it.

You do realize that the above index has nothing whatever to do with
searches on propertyvalue?  (Or at least not propertyvalue alone.)

My advice is to drop propertyvalue from the index and see what
performance you get.

You could possibly do something with a partial index, eg
    create index ... where length(propertyvalue) < 2000
but that'd probably require modifying your queries, so I suspect it's
not really very practical.

            regards, tom lane

pgsql-general by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: index row size exceeds btree maximum, 2713 - Solutions?
Next
From: "Guy Rouillier"
Date:
Subject: Re: How to find the number of rows deleted