Re: Fixing inheritance merge behavior in ALTER TABLE ADD CONSTRAINT

<div dir="ltr"><div class="gmail_extra"><br /><div class="gmail_quote">On Fri, Oct 7, 2016 at 5:09 PM, Tom Lane <span
dir="ltr"><<ahref="mailto:tgl@sss.pgh.pa.us" target="_blank">tgl@sss.pgh.pa.us</a>></span> wrote:<br
/><blockquoteclass="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="a3s
aXjCHm157a0fbef7ee164f" id=":3za">What seems like a saner answer to me is to change the backend so that it<br /> will
acceptthese ALTER commands in either order, with the same end state.<br /> The reason it throws an error now, IMO, is
justso that blindly issuing<br /> the same ALTER ADD CONSTRAINT twice will fail.  But we could deal with<br /> that by
sayingthat it's okay as long as the initially-targeted constraint<br /> doesn't already have conislocal =
true.</div></blockquote></div><br/><br /></div><div class="gmail_extra">+1. Been bitten by this one myself.</div><div
class="gmail_extra"><br/></div></div>