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 623B45286E; Thu, 2 Jun 2005 09:23:26 -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 81553-05; Thu, 2 Jun 2005 12:23:22 +0000 (GMT) Received: from secf.com (209-128-104-244.bayarea.net [209.128.104.244]) by svr1.postgresql.org (Postfix) with ESMTP id 17F4F52825; Thu, 2 Jun 2005 09:23:21 -0300 (ADT) Received: from dinesh by secf.com (MDaemon.PRO.v8.0.2.R) with ESMTP id md50001007291.msg; Thu, 02 Jun 2005 05:23:43 -0700 Reply-To: From: "Dinesh Pandey" To: "'Ramakrishnan Muralidharan'" , , "'PostgreSQL'" Subject: Re: [SQL] index row size 2728 exceeds btree maximum, 2713 Date: Thu, 2 Jun 2005 17:48:47 +0530 Organization: Second Foundation India P Ltd. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0079_01C5679B.563FA2D0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcVnQWMS5ZegD05mSvW9iHeSQj1olwAFBl9wZcJ2XzBlv12uwIZb344g In-reply-to: <02767D4600E59A4487233B23AEF5C5992A4090@blrmail1.aus.pervasive.com> X-Authenticated-Sender: dpandey@secf.com X-Spam-Processed: mail.secf.com, Thu, 02 Jun 2005 05:23:43 -0700 (not processed: message from valid local sender) X-MDRemoteIP: 220.227.32.11 X-Return-Path: dpandey@secf.com X-MDAV-Processed: mail.secf.com, Thu, 02 Jun 2005 05:23:43 -0700 Message-Id: <20050602122321.17F4F52825@svr1.postgresql.org> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.35 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, HTML_MESSAGE, MSGID_FROM_MTA_ID X-Spam-Level: * X-Archive-Number: 200506/83 X-Sequence-Number: 78791 This is a multi-part message in MIME format. ------=_NextPart_000_0079_01C5679B.563FA2D0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Yes I am storing some "error messages" in data column, and the PK columns are party of search criteria. Thanks Dinesh Pandey _____ From: Ramakrishnan Muralidharan [mailto:ramakrishnanm@pervasive-postgres.com] Sent: Thursday, June 02, 2005 4:44 PM To: dpandey@secf.com; pgsql-general@postgresql.org; PostgreSQL Subject: RE: [SQL] index row size 2728 exceeds btree maximum, 2713 Hi It is not advisable to add a variable length data field in the Index key, since it is very difficult predict the size of the field which may vary from record to record. are you included this field for Full text search on data field? Regards, R.Muralidharan -----Original Message----- From: pgsql-sql-owner@postgresql.org [mailto:pgsql-sql-owner@postgresql.org]On Behalf Of Dinesh Pandey Sent: Thursday, January 01, 2004 3:14 PM To: Ramakrishnan Muralidharan; pgsql-general@postgresql.org; 'PostgreSQL' Subject: Re: [SQL] index row size 2728 exceeds btree maximum, 2713 Hi, 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 handle that? Thanks Dinesh Pandey _____ From: Ramakrishnan Muralidharan [mailto:ramakrishnanm@pervasive-postgres.com] 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 Hi, The issue looks like your Index width exceeds the maximum width of the index key limit, Please review the keys used in the index. Regards, R.Muralidharan -----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 TABLE -----------+-----------------------+----------- Column | Type -----------+-----------------------+----------- scan_id | bigint host_ip | character varying(15) port_num | integer plugin_id | integer severity | character varying(50) data | text Indexes: "pk_scanned_port_info" PRIMARY KEY, btree (scan_id, host_ip, port_num, plugin_id, severity, data) On inserting record I am getting this error "index row size 2728 exceeds btree maximum, 2713" How to solve this problem? ------=_NextPart_000_0079_01C5679B.563FA2D0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Yes I am = storing some “error messages” in data column, and the PK columns are = party of search criteria.

 <= /o:p>

Thanks
Dinesh Pandey

From: = Ramakrishnan Muralidharan [mailto:ramakrishnanm@pervasive-postgres.com]
Sent: Thursday, June 02, = 2005 4:44 PM
To: dpandey@secf.com; pgsql-general@postgresql.org; PostgreSQL
Subject: RE: [SQL] index = row size 2728 exceeds btree maximum, 2713<= /p>

 

      =    Hi

 

      =        It is not advisable to add a variable length data field in the Index = key, since it is very difficult predict the size of the field which may vary from = record to record.  <= /p>

 

      =        are you included this field for Full text search on data = field?<= /p>

 

Regards,<= /p>

R.Muralidharan<= /p>

-----Original = Message-----
From: pgsql-sql-owner@postgresql.org [mailto:pgsql-sql-owner@postgresql.org]On Behalf Of Dinesh Pandey
Sent: Thursday, January = 01, 2004 3:14 PM
To: Ramakrishnan = Muralidharan; pgsql-general@postgresql.org; 'PostgreSQL'
Subject: Re: [SQL] index = row size 2728 exceeds btree maximum, 2713<= /p>

Hi,

 

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 handle = that?

 

=

Thanks
Dinesh Pandey

From: = Ramakrishnan Muralidharan [mailto:ramakrishnanm@pervasive-postgres.com]
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<= /p>

 

      =    Hi,

 

      =        The issue looks like your Index width exceeds the maximum width =  of the index key limit, Please review the keys used in the = index.<= /p>

 

Regards,<= /p>

R.Muralidharan<= /p>

 

     <= /p>

-----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<= /p>

TABLE =

-----------+-----------------------+-----------=

  Column    |         Type      

-----------+-----------------------+-----------=

 scan_id    | bigint           &= nbsp;   

 host_ip    | character = varying(15)

 port_num | integer           =    

 plugin_id  | integer              &= nbsp;

 severity   | character varying(50) =

 data       | = text     &n= bsp;           

Indexes:

    "pk_scanned_port_info" PRIMARY KEY, btree (scan_id, host_ip, port_num, plugin_id, severity, = data)

 

 =

On inserting record I am getting = this error “index row size 2728 exceeds btree maximum, = 2713”

 

=

How to solve this problem?

 

 

 

------=_NextPart_000_0079_01C5679B.563FA2D0--