From: Richard Huxton <dev@archonet.com>
To: dpandey@secf.com
Cc: pgsql-general@postgresql.org, 'PostgreSQL' <pgsql-sql@postgresql.org>
Subject: Re: index row size 2728 exceeds btree maximum, 2713
Date: Thu, 02 Jun 2005 10:58:49 +0100
Message-ID: <429ED859.1070308@archonet.com> (raw)
In-Reply-To: <20050602071021.512DC5286E@svr1.postgresql.org>
References: <20050602071021.512DC5286E@svr1.postgresql.org>
Dinesh Pandey wrote:
> -----------+-----------------------+-----------
> 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"
Well - the error message is clear enough. The question is, what to do.
Without knowing what the table "means", it's difficult to say what the
primary-key should be, but it seems unlikely to include an
unlimited-length text-field called "data".
If the data itself doesn't offer any suitable candidate keys (as can
well be the case) then common practice is to generate a unique number
and use that as an ID - in PostgreSQL's case by use of the SERIAL
pseudo-type.
Does that help?
--
Richard Huxton
Archonet Ltd
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: dev@archonet.com, dpandey@secf.com
Subject: Re: index row size 2728 exceeds btree maximum, 2713
In-Reply-To: <429ED859.1070308@archonet.com>
* 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