| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org mailing list" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Write Performance |
| Date: | 2010-01-05 23:55:04 |
| Message-ID: | 26667536-DB10-46E2-A7AB-38304A2BF59B@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Lardinois | 2010-01-06 00:06:02 | XML Type validates against xml schema? |
| Previous Message | Greg Smith | 2010-01-05 23:54:47 | Re: pgbench out of memory error |