Re: [PROPOSAL] Covering + unique indexes. - Mailing list pgsql-hackers

From Vik Fearing
Subject Re: [PROPOSAL] Covering + unique indexes.
Date
Msg-id 55F7E0AB.3020600@2ndquadrant.fr
Whole thread Raw
In response to Re: [PROPOSAL] Covering + unique indexes.  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: [PROPOSAL] Covering + unique indexes.  (Anastasia Lubennikova <a.lubennikova@postgrespro.ru>)
List pgsql-hackers
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); ?
-- 
Vik Fearing                                          +33 6 46 75 15 36
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support



pgsql-hackers by date:

Previous
From: Rui Hai Jiang
Date:
Subject: Could the configure script detect the endianness for a Power CPU with endianness mode change
Next
From: David Rowley
Date:
Subject: Re: [PROPOSAL] Covering + unique indexes.