From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add primary key/unique constraint using prefix columns of an index |
Date: | 2012-05-22 17:36:20 |
Message-ID: | CA+U5nMJRKj0+yuvmSaqWt=hVMeH2=ZLs70dw2MfRQRQex5EK_Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 22 May 2012 18:24, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> Now that there are index only scans, there is a use case for having a
> composite index which has the primary key or a unique key as the
> prefix column(s) but with extra columns after that. Currently you
> would also need another index with exactly the primary/unique key,
> which seems like a waste of storage and maintenance.
>
> Should there be a way to declare a "unique" index with the unique
> property applying to a prefix of the indexed columns/expression? And
> having that, a way to turn that prefix into a primary key constraint?
>
> Of course this is easier said then done, but is there some reason for
> it not to be a to-do item?
+1
Very useful
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-05-22 17:41:00 | Re: Add primary key/unique constraint using prefix columns of an index |
Previous Message | Josh Berkus | 2012-05-22 17:35:04 | Re: Changing the concept of a DATABASE |