On Jan 5, 2010, at 3:46 PM, Tim Uckun wrote:
pg_dump has a --disable-triggers option too.
[...]
It doesn't seem like an outrageous expectation that the COPY command or something similar should have that option.
Well, whether an expectation is "outrageous" or not is a matter of viewpoint. The principle is that pg_dump and COPY have fundamentally different use cases. pg_dump is intended to restore a backup of data that was already in the database, and presumably was already validated by the appropriate constraints and triggers. COPY is used to create new records in a database, from arbitrary data, which may not be valid based on the database's vision of data consistency.
-- -- Christophe Pettus xof@xxxxxxxxxxxx -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
