pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Martijn van Oosterhout <kleptog@svana.org>
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: [SQL] index row size 2728 exceeds btree maximum, 2713
Date: Thu, 2 Jun 2005 12:12:36 +0200
Message-ID: <20050602101236.GC16799@svana.org> (raw)
In-Reply-To: <20050602094845.E510852923@svr1.postgresql.org>
References: <02767D4600E59A4487233B23AEF5C5992A408F@blrmail1.aus.pervasive.com>
	<20050602094845.E510852923@svr1.postgresql.org>

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 handle
> 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] 
> 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?
> 
>  
> 
>  
> 
>  
> 

-- 
Martijn van Oosterhout   <kleptog@svana.org>   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.

view thread (18+ messages)  latest in thread

Message-ID: <20050602101236.GC16799@svana.org>
Permalink:  ../20050602101236.GC16799@svana.org/
Also on:    postgresql.org/message-id/20050602101236.GC16799@svana.org

 · 

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: kleptog@svana.org, dpandey@secf.com, ramakrishnanm@pervasive-postgres.com
  Subject: Re: [SQL] index row size 2728 exceeds btree maximum, 2713
  In-Reply-To: <20050602101236.GC16799@svana.org>

* 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