Re: BUG #15587: Partitions with ALTER TABLE ADD CONSTRAINT - Mailing list pgsql-bugs

From Jesper Pedersen
Subject Re: BUG #15587: Partitions with ALTER TABLE ADD CONSTRAINT
Date
Msg-id 3e406e7f-b3df-7f9d-fcf3-1201f3c87903@redhat.com
Whole thread Raw
In response to Re: BUG #15587: Partitions with ALTER TABLE ADD CONSTRAINT  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: BUG #15587: Partitions with ALTER TABLE ADD CONSTRAINT
List pgsql-bugs
Hi,

On 1/10/19 12:11 PM, Alvaro Herrera wrote:
> On 2019-Jan-10, PG Bug reporting form wrote:
>> Removing ONLY from the ALTER command makes the index correct.
> 
> I'm not clear what problem you're reporting.  If you use ONLY, then the
> command doesn't cascade to create the index on partitions, and the index
> is marked invalid.  If you add the constraint to each partition and
> ALTER INDEX ATTACH PARTITION, the index on t1 should become valid when
> every partition of the table has its index.
> 

However, when you use ADD CONSTRAINT FOREIGN KEY you can't use ONLY, so 
would it be a good idea to make ADD CONSTRAINT UNIQUE behave the same 
way, i.e. error out ?

Best regards,
  Jesper


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15587: Partitions with ALTER TABLE ADD CONSTRAINT
Next
From: Thomas Munro
Date:
Subject: Re: BUG #15577: Query returns different results when executedmultiple times