Subject: Re: [PROPOSAL] Covering + unique indexes.
To: pgsql-hackers@postgresql.org
References: <55F2C1BC.3010109@postgrespro.ru>
 <55F2CCD0.7040608@postgrespro.ru> <55F6F7AD.4080307@BlueTreble.com>
 <55F70D0A.2030503@sigaev.ru>
 <CAEepm=2G4jdaoXHU0PJ7MqLms88==r44z9bvLpnzjyOTDzwAEw@mail.gmail.com>
 <55F73FDA.2030001@BlueTreble.com> <55F7B7C9.6090109@sigaev.ru>
 <CAKJS1f-3op5KuH5PZcz3Whf1HSdOv8Jp6mpUSBA0J_fk8cHNQA@mail.gmail.com>
 <55F7E0AB.3020600@2ndquadrant.fr>
From: Anastasia Lubennikova <a.lubennikova@postgrespro.ru>
Message-ID: <55F7F6D7.1060800@postgrespro.ru>
Date: Tue, 15 Sep 2015 13:45:43 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55F7E0AB.3020600@2ndquadrant.fr>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers