Re: Request: set opclass for generated unique and primary key indexes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Request: set opclass for generated unique and primary key indexes
Date: 2006-02-22 15:27:57
Message-ID: 11917.1140622077@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> writes:
> There isn't possibility change opclass for generated UNIQUE indexes.

Why would you need it?

> USING INDEX [TABLESPACE ..] [OPCLASS ..]

This is unworkable --- consider a table with more than one unique
constraint and/or multiple-column constraints.

I seem to recall someone proposing extending the syntax of the UNIQUE
constraints themselves, but there really isn't enough use-case to
justify it AFAICS. Especially not when you can always use CREATE UNIQUE
INDEX.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregor Zeitlinger 2006-02-22 15:41:37 LIMIT and JOINS
Previous Message Pavel Stehule 2006-02-22 15:08:59 Request: set opclass for generated unique and primary key indexes