X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0775452875 for ; Thu, 2 Jun 2005 09:36:16 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 84120-10 for ; Thu, 2 Jun 2005 12:36:14 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.197.194]) by svr1.postgresql.org (Postfix) with SMTP id 6822652825 for ; Thu, 2 Jun 2005 09:36:12 -0300 (ADT) Received: (qmail 7866 invoked by uid 500); 2 Jun 2005 12:35:20 -0000 Date: Thu, 2 Jun 2005 07:35:20 -0500 From: Bruno Wolff III To: Dinesh Pandey Cc: 'Ramakrishnan Muralidharan' , pgsql-general@postgresql.org, 'PostgreSQL' Subject: Re: index row size 2728 exceeds btree maximum, 2713 Message-ID: <20050602123520.GC6785@wolff.to> Mail-Followup-To: Bruno Wolff III , Dinesh Pandey , 'Ramakrishnan Muralidharan' , pgsql-general@postgresql.org, 'PostgreSQL' References: <02767D4600E59A4487233B23AEF5C5992A4090@blrmail1.aus.pervasive.com> <20050602122321.17F4F52825@svr1.postgresql.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050602122321.17F4F52825@svr1.postgresql.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.008 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/87 X-Sequence-Number: 78795 On Thu, Jun 02, 2005 at 17:48:47 +0530, Dinesh Pandey 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.