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

["Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com>]

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.

Best regards,
-- 
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | indiatimes | yahoo }.com

EnterpriseDB      http://www.enterprisedb.com

17° 29' 34.37"N,  78° 30' 59.76"E - Hyderabad *
18° 32' 57.25"N,  73° 56' 25.42"E - Pune
37° 47' 19.72"N, 122° 24' 1.69" W - San Francisco

http://gurjeet.frihost.net

Mail sent from my BlackLaptop device