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 33419528C1; Thu, 2 Jun 2005 07:12:51 -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 35253-01; Thu, 2 Jun 2005 10:12:47 +0000 (GMT) Received: from svana.org (svana.org [203.20.62.76]) by svr1.postgresql.org (Postfix) with ESMTP id 68D3752825; Thu, 2 Jun 2005 07:12:44 -0300 (ADT) Received: from kleptog by svana.org with local (Exim 3.35 #1 (Debian)) id 1Ddmgm-00051y-00; Thu, 02 Jun 2005 20:12:36 +1000 Date: Thu, 2 Jun 2005 12:12:36 +0200 From: Martijn van Oosterhout To: Dinesh Pandey Cc: 'Ramakrishnan Muralidharan' , pgsql-general@postgresql.org, 'PostgreSQL' Subject: Re: [SQL] index row size 2728 exceeds btree maximum, 2713 Message-ID: <20050602101236.GC16799@svana.org> Reply-To: Martijn van Oosterhout Mail-Followup-To: Dinesh Pandey , 'Ramakrishnan Muralidharan' , pgsql-general@postgresql.org, 'PostgreSQL' References: <02767D4600E59A4487233B23AEF5C5992A408F@blrmail1.aus.pervasive.com> <20050602094845.E510852923@svr1.postgresql.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3uo+9/B/ebqu+fSQ" Content-Disposition: inline In-Reply-To: <20050602094845.E510852923@svr1.postgresql.org> User-Agent: Mutt/1.3.28i X-PGP-Key-ID: Length=1024; ID=0x0DC67BE6 X-PGP-Key-Fingerprint: 295F A899 A81A 156D B522 48A7 6394 F08A 0DC6 7BE6 X-PGP-Key-URL: X-Warning: Normally my messages are signed, but not on the ozTiVo list due to legacy application support X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/72 X-Sequence-Number: 78780 --3uo+9/B/ebqu+fSQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 01, 2004 at 03:13:48PM +0530, Dinesh Pandey wrote: > One of the columns in primary key is of type "TEXT". I am able to insert > with small data, but for around 3000 characters it's failing. How to hand= le > that? Easy, btree indexes can't handle data with more that 2713 bytes. You need to decide if having a single index on all your columns is actually what you want. Depending on your queries it may not even be used. Hope this helps, > From: Ramakrishnan Muralidharan > [mailto:ramakrishnanm@pervasive-postgres.com]=20 > Sent: Thursday, June 02, 2005 3:11 PM > To: dpandey@secf.com; pgsql-general@postgresql.org; PostgreSQL > Subject: RE: [SQL] index row size 2728 exceeds btree maximum, 2713 >=20 > =20 >=20 > Hi, >=20 > =20 >=20 > The issue looks like your Index width exceeds the maximum wi= dth > of the index key limit, Please review the keys used in the index. >=20 > =20 >=20 > Regards, >=20 > R.Muralidharan >=20 > =20 >=20 > =20 >=20 > -----Original Message----- > From: pgsql-sql-owner@postgresql.org > [mailto:pgsql-sql-owner@postgresql.org]On Behalf Of Dinesh Pandey > Sent: Thursday, June 02, 2005 12:35 PM > To: pgsql-general@postgresql.org; 'PostgreSQL' > Subject: [SQL] index row size 2728 exceeds btree maximum, 2713 >=20 > TABLE=20 >=20 > -----------+-----------------------+----------- >=20 > Column | Type =20 >=20 > -----------+-----------------------+----------- >=20 > scan_id | bigint =20 >=20 > host_ip | character varying(15)=20 >=20 > port_num | integer =20 >=20 > plugin_id | integer =20 >=20 > severity | character varying(50)=20 >=20 > data | text =20 >=20 > Indexes: >=20 > "pk_scanned_port_info" PRIMARY KEY, btree (scan_id, host_ip, port_num, > plugin_id, severity, data) >=20 > =20 >=20 > =20 >=20 > On inserting record I am getting this error "index row size 2728 exceeds > btree maximum, 2713" >=20 > =20 >=20 > How to solve this problem? >=20 > =20 >=20 > =20 >=20 > =20 >=20 --=20 Martijn van Oosterhout http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them. --3uo+9/B/ebqu+fSQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFCntuUY5Twig3Ge+YRAlihAKChY17HSt7Xn1DyuHUp6aZ7981lZQCgqJCD Fal150UEC3YcZoUR8qMtqos= =u64w -----END PGP SIGNATURE----- --3uo+9/B/ebqu+fSQ--