From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
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 19:54:33 |
Message-ID: | 20050718195433.GA23508@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jul 18, 2005 at 14:44:26 -0500,
Dan Armbrust <daniel(dot)armbrust(dot)list(at)gmail(dot)com> wrote:
> I'm trying to load some data into PostgreSQL 8.0.3, and I got the error
> message "index row size 2904 exceeds btree maximum, 2713". After a
> bunch of searching, I believe that I am getting this error because a
> value that I am indexing is longer than ~ 1/3 of the block size - or the
> BLCKSZ variable in the src/include/pg_config_manual.h file.
>
> Am I correct so far?
>
> I need to fix this problem. I cannot change the indexed columns. I
> cannot shorten the data value. And I cannot MD5 it, or any of those
> hashing types of solutions that I saw a lot while searching.
Can you explain how you are using the index now and what you are trying
to accomplish? It is hard to suggest alternatives without knowing what
you are really trying to do.
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Armbrust | 2005-07-18 20:17:35 | Re: index row size exceeds btree maximum, 2713 - Solutions? |
Previous Message | Andrus | 2005-07-18 19:47:54 | Re: How to find the number of rows deleted |