| From: | Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15587: Partitions with ALTER TABLE ADD CONSTRAINT |
| Date: | 2019-01-10 17:43:11 |
| Message-ID: | 3e406e7f-b3df-7f9d-fcf3-1201f3c87903@redhat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2019-01-10 19:17:03 | Re: BUG #15577: Query returns different results when executed multiple times |
| Previous Message | Tom Lane | 2019-01-10 17:41:49 | Re: BUG #15587: Partitions with ALTER TABLE ADD CONSTRAINT |