Обсуждение: Re: [SQL] index row size 2728 exceeds btree maximum, 2713
-----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, 2713TABLE
-----------+-----------------------+-----------
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?
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, 2713TABLE
-----------+-----------------------+-----------
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?
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.