Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: ERROR: index row size 2960 exceeds btree maximum


  • From: Hannu Krosing <hannu(at)skype(dot)net>
  • To: Rodrigo Sakai <rodrigo(dot)sakai(at)poli(dot)usp(dot)br>
  • Cc: pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: ERROR: index row size 2960 exceeds btree maximum
  • Date: Thu, 31 May 2007 10:52:29 +0300
  • Message-id: <1180597949.30194.2.camel@hannu-laptop> <text/plain>

Ühel kenal päeval, K, 2007-05-30 kell 21:41, kirjutas Rodrigo Sakai:
>   Hello,
> 
>  
> 
>   I’m developing an application that needs a different data type. So,
> I have implemented this new data type inside postgresql using C, as
> documentation shows to.
> 
>  
> 
>   Basically, the data type is a composition of two timestamps, like:
> (timestamp, timestamp) and it is called ‘period’. So, almost
> everything is fine. Data type is ok, operators are ok, but the index
> doesn’t work fine.

...

> Here is the error about last INSERT:
> 
> ERROR: index row size 2960 exceeds btree maximum, 2713
> 
> SQL state: 54000
> 
> Hint: Values larger than 1/3 of a buffer page cannot be indexed.


It seems that your C datatype is buggy, generating binary representation
of Period that is bigger than 2713 bytes.

-------------
Hannu





Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group