Re: BUG #15587: Partitions with ALTER TABLE ADD CONSTRAINT

Jesper Pedersen <jesper.pedersen@redhat.com>

From: Jesper Pedersen <jesper.pedersen@redhat.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>, pgsql-bugs@lists.postgresql.org
Date: 2019-01-10T17:43:11Z
Lists: 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


Commits

  1. Fix creation of duplicate foreign keys on partitions