>
> Technically you *can* disable triggers, including RI checks, but it's VERY
> unwise and almost completely defeats the purpose of having the checks. In
> most such situations you're much better off dropping the constraints then
> adding them again at the end of the load.
I know that the SQL server bulk loader defaults to not firing the
triggers and I was hoping there would be an option on the COPY command
to accomplish the same thing.
pg_dump has a --disable-triggers option too.
It seems to me that the COPY FROM should have an option that bypasses
the triggers as a convience.
Both the SQL server team and the postgres team have obviously
recognized that there will be situations where the DBA will want to
bulk load data without firing off a set of triggers for every insert.
It doesn't seem like an outrageous expectation that the COPY command
or something similar should have that option.
