From: | CSN <cool_screen_name90001(at)yahoo(dot)com> |
---|---|
To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: index row size exceeds btree maximum |
Date: | 2005-09-21 20:12:20 |
Message-ID: | 20050921201221.66419.qmail@web52914.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
--- Scott Marlowe <smarlowe(at)g2switchworks(dot)com> wrote:
> On Wed, 2005-09-21 at 15:02, CSN wrote:
> > This appears related to my previous post:
> >
>
http://archives.postgresql.org/pgsql-general/2005-09/msg00809.php
> >
> > I setup a unique index using the title, yield, and
> > directions fields. Some inserts are causing this
> > error:
> >
> > DBD::Pg::st execute failed: ERROR: index row size
> > 2832 exceeds btree maximum, 2713
> > CONTEXT: SQL statement "insert into stuff (title,
> > yield, directions) values ( $1 , $2 , $3 )"
> >
> > What do I do?
>
> Don't insert such big values? :)
>
> Actually, the standard solution is to use an md5 of
> the three fields:
>
> create unique index threefieldindex on table1
> (md5(field1||field2||field3));
>
Ah, cool! Looks like using tsearch2 would be another
option, but I don't plan on searching through the
yield or directions fields (except at insert time).
CSN
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Yonatan Ben-Nes | 2005-09-21 20:24:20 | Re: Slow search.. quite clueless |
Previous Message | Greg Sabino Mullane | 2005-09-21 20:07:48 | YAPC::Israel looking for Perl/Database speakers |