Uh ... why not just drop the constraint, and re-add it later if you want it again?
My 0.02€ : maybe because you must keep track of the constraint details to do so, this it is significantly more error prone than disable / enable when the bookkeeping is done by the system and if everything is in a transaction... If the ENABLE is automatically done on the next COMMIT, that would be even better.
This seems like adding a lot of mechanism (and possible bugs) for a rather marginal use-case.
That is possible! -- Fabien. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
