> > 1. Add the FK to the table BEFORE COPYing data
> > 2. Use the old update blah set reltriggers = 0 trick
> > 3. restore the data
> > 4. Undo step 2
>
> The problem with that is that I think the reltriggers=0 trick only works
> if you're superuser, I thought that's why the trigger disabling became
> optional. A set that affected only atac would probably be reasonable in
> the dump (and presumably easy to do). It'd also carry over to future
> cases where we separate some check constraints (for examples ones
> that refer directly or indirectly to the same table in a subselect).
Well yes, this would be a super-user only ability. Are you worried about
people restoring dumps as non-superuser?
Chris