Re: Re: [BUGS] BUG #3965: UNIQUE constraint fails on long column values

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Phil Frost <phil(at)macprofessionals(dot)com>, PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Re: [BUGS] BUG #3965: UNIQUE constraint fails on long column values
Date: 2008-03-05 18:36:26
Message-ID: 200803051836.m25IaQl06279@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-docs

Gurjeet Singh wrote:
> On Wed, Mar 5, 2008 at 10:39 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> > Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bill Moran 2008-03-05 18:58:25 Re: BUG #4012: bug in pg_query
Previous Message Renato Gravino Neto 2008-03-05 18:31:52 BUG #4012: bug in pg_query

Browse pgsql-docs by date

  From Date Subject
Next Message Joshua D. Drake 2008-03-05 18:53:07 Re: FAQ on Embedding Postgres
Previous Message Joshua D. Drake 2008-03-05 18:30:43 Re: FAQ on Embedding Postgres