On Fri, Oct 7, 2016 at 5:09 PM, Tom Lane 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 CO
I've been looking into the misbehavior complained of here:
https://www.postgresql.org/message-id/CADbMkNPT-Jz5PRSQ4RbUASYAjocV_KHUWapR%2Bg8fNvhUAyRpxA%40mail.gmail.com
I originally thought this was pg_dump's fault, but I now think it's not,
or at least that changing the backend's behavior would be
