From: Bruce Momjian <bruce@momjian.us>
Message-Id: <200803051836.m25IaQl06279@momjian.us>
Subject: Re: Re: [BUGS] BUG #3965: UNIQUE constraint fails on
	long column values
In-Reply-To: <65937bea0803051030q6b8800c0pb6db4e7cae0bb45e@mail.gmail.com>
To: Gurjeet Singh <singh.gurjeet@gmail.com>
Date: Wed, 5 Mar 2008 13:36:26 -0500 (EST)
CC: Tom Lane <tgl@sss.pgh.pa.us>, Phil Frost <phil@macprofessionals.com>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Gurjeet Singh wrote:
> On Wed, Mar 5, 2008 at 10:39 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> > Bruce Momjian <bruce@momjian.us> writes:
> > > Part of the problem is we don't know the length --- it is the compressed
> > > length that is limited, I think to 8k.
> >
> > That's a problem, and the length limit is different for different index
> > types.  So you're really not going to be able to say anything very
> > specific.  Another problem is where would you put the information?
> 
> 
> In 'CREATE INDEX'  docs...
> 
> http://www.postgresql.org/docs/8.3/interactive/sql-createindex.html
> 
> Along with the following statement:
> 
> method: The name of the index method to be used. Choices are btree, hash,
> gist, and gin. The default method is btree.

We are trying to figure out how to specify the index-type-specific length
limits, not the index types themselves.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +