From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dan Armbrust <daniel(dot)armbrust(dot)list(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: index row size exceeds btree maximum, 2713 - Solutions? |
Date: | 2005-07-18 20:40:42 |
Message-ID: | 16848.1121719242@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dan Armbrust <daniel(dot)armbrust(dot)list(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2005-07-18 20:55:46 | Re: index row size exceeds btree maximum, 2713 - |
Previous Message | Guy Rouillier | 2005-07-18 20:40:37 | Re: How to find the number of rows deleted |