pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Dinesh Pandey <dpandey@secf.com>
Cc: Ramakrishnan Muralidharan <ramakrishnanm@pervasive-postgres.com>
Cc: pgsql-general@postgresql.org, 'PostgreSQL' <pgsql-sql@postgresql.org>
Subject: Re: index row size 2728 exceeds btree maximum, 2713
Date: Thu, 2 Jun 2005 07:35:20 -0500
Message-ID: <20050602123520.GC6785@wolff.to> (raw)
In-Reply-To: <20050602122321.17F4F52825@svr1.postgresql.org>
References: <02767D4600E59A4487233B23AEF5C5992A4090@blrmail1.aus.pervasive.com>
	<20050602122321.17F4F52825@svr1.postgresql.org>

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.



view thread (18+ messages)  latest in thread

Message-ID: <20050602123520.GC6785@wolff.to>
Permalink:  ../20050602123520.GC6785@wolff.to/
Also on:    postgresql.org/message-id/20050602123520.GC6785@wolff.to

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: bruno@wolff.to, dpandey@secf.com, ramakrishnanm@pervasive-postgres.com
  Subject: Re: index row size 2728 exceeds btree maximum, 2713
  In-Reply-To: <20050602123520.GC6785@wolff.to>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox