Re: rename constraint behavior for duplicate names?

Allan Wang <allanvv@gmail.com> writes:
> Alright, I see why the checks are still needed. The unique index should
> be on relname, conname right? Also looking into DROP CONSTRAINT's code,
> it gives a notice about "multiple constraint names dropped" when
> RemoveRelConstraints(rel, conname) returns > 1. This check isn't needed
> anymore right? Also RemoveRelConstraints can be simplified to assume
> only one row will need removing, and be turned into a void function?

Not unless you want to break the "quiet" option for ATExecDropConstraint.
        regards, tom lane