Re: [PROPOSAL] Covering + unique indexes.

From: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PROPOSAL] Covering + unique indexes.
Date: 2015-09-15 10:45:43
Message-ID: 55F7F6D7.1060800@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

15.09.2015 12:11, Vik Fearing:
> On 09/15/2015 10:57 AM, David Rowley wrote:
>>> I agree, that form
>>>> CREATE UNIQUE INDEX i ON t (f1, f2, f3) INCLUDE (f4)
>>>> is clear. f4 will be used in row compare and actually planner will be able
>>>> to use it as unique index (f1, f2, f3) with additional f4 or as
>>>> as unique index (f1, f2, f3, f4), because uniqueness on (f1, f2, f3) gives
>>>> warranty of uniqueness on (f1, f2, f3, f4)
>>>>
>>>>
>> I'd vote for this too. However, INCLUDE does not seem to be a reserved word
>> at the moment.
> What about CREATE UNIQUE INDEX i ON t (f1, f2, f3) WITH (f4); ?

WITH seems ambiguity to me. It refers to CTE, so I expect to see after
that a kind of query expression. But maybe that's just matter of habit.

BTW, that's the first syntax change I'm working with.
Is there any convention in PostgreSQL about new keywords and so on?
Where can I find it?

--
Anastasia Lubennikova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2015-09-15 11:01:25 Re: [PROPOSAL] Covering + unique indexes.
Previous Message sri harsha 2015-09-15 10:41:37 Multiple Update queries