Re: index row size 2728 exceeds btree maximum, 2713 - Mailing list pgsql-sql

From Bruno Wolff III
Subject Re: index row size 2728 exceeds btree maximum, 2713
Date
Msg-id 20050602123520.GC6785@wolff.to
Whole thread Raw
In response to Re: index row size 2728 exceeds btree maximum, 2713  ("Dinesh Pandey" <dpandey@secf.com>)
List pgsql-sql
On Thu, Jun 02, 2005 at 17:48:47 +0530,
  Dinesh Pandey <dpandey@secf.com> wrote:
> Yes I am storing some "error messages" in data column, and the PK columns
> are party of search criteria.

If you need to be able to search based on the entire stored error message,
than you might try adding an indexed hash column to the table and using that
to speed up searches. You can still compare the full string in case you
have a hash collision, but those should be very rare.

pgsql-sql by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: [GENERAL] index row size 2728 exceeds btree maximum, 27
Next
From: Richard Huxton
Date:
Subject: Re: [GENERAL] index row size 2728 exceeds btree maximum, 27