Stephan Szabo <sszabo@megazone23.bigpanda.com> writes:
>> However, if we are going to put that kind of knowledge into pg_dump,
>> it would only be a small further step to have it dump these triggers
>> as ALTER TABLE ADD CONSTRAINT commands instead. Which would be a lot
>> better for forward compatibility than dumping the raw triggers.
> Wasn't there still some question about the fact that ATAC causes a
> check of the constraint which for large tables is not insignificant.
> I don't remember if there was any consensus on how to deal with that.
Hmm, good point. That's probably why we didn't go ahead and do it
already...
Maybe we should just put the lookup hack into the backend's CREATE
CONSTRAINT TRIGGER code and leave it at that.
regards, tom lane
