Re: Fixing inheritance merge behavior in ALTER TABLE ADD CONSTRAINT

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Benedikt Grundmann <bgrundmann(at)janestreet(dot)com>
Subject: Re: Fixing inheritance merge behavior in ALTER TABLE ADD CONSTRAINT
Date: 2016-10-07 21:40:18
Message-ID: CADkLM=e5+EsQh3OB561hLcNdiRT7WxdFt-W7308tGjUzK0-sow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 7, 2016 at 5:09 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> What seems like a saner answer to me is to change the backend so that it
> will accept these ALTER commands in either order, with the same end state.
> The reason it throws an error now, IMO, is just so that blindly issuing
> the same ALTER ADD CONSTRAINT twice will fail. But we could deal with
> that by saying that it's okay as long as the initially-targeted constraint
> doesn't already have conislocal = true.
>

+1. Been bitten by this one myself.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-10-07 22:57:18 Re: [COMMITTERS] pgsql: Remove -Wl,-undefined,dynamic_lookup in macOS build.
Previous Message Heikki Linnakangas 2016-10-07 21:37:28 Re: Radix tree for character conversion