Re: ERROR: index row size 2960 exceeds btree maximum

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
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: 2007-05-31 12:45:25
Message-ID: 20070531124525.GA4724@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rodrigo Sakai wrote:

> 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.

Does type tinterval not suit you? It is not very well documented but it
should work, or at least serve as a basis for developing your own types.

--
Alvaro Herrera http://www.amazon.com/gp/registry/DXLWNGRJD34J
Essentially, you're proposing Kevlar shoes as a solution for the problem
that you want to walk around carrying a loaded gun aimed at your foot.
(Tom Lane)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2007-05-31 12:56:00 Command tags in create/drop scripts
Previous Message Zdenek Kotala 2007-05-31 10:31:44 Re: Backend crash during explain