From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: disable triggers using psql |
Date: | 2011-02-16 16:30:34 |
Message-ID: | 20110216163033.GU96213@shinkuro.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Feb 16, 2011 at 10:08:53AM -0500, David Johnston wrote:
> I may be off-track here but triggers do not enforce referential integrity -
> constraints do. If you need to disable triggers you can do so via the ALTER
> TABLE command.
Unless something very big changed when I wasn't looking, the
constraints are actually implemented as triggers under the hood. But
you're right that it'd be cleaner to drop the constraints and re-add
them than to fool with system triggers.
> The reason I think pg_restore works for you is because when a table is built
> using pg_restore all the data is loaded into all tables BEFORE any
> constraints are created. I believe that if you did a data-only dump from
> pg_dump you would have the same integrity problems.
Yes.
A
--
Andrew Sullivan
ajs(at)crankycanuck(dot)ca
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2011-02-16 16:33:22 | Re: Raid Controller Write Cache setting for WAL and Data |
Previous Message | Piotr Gasidło | 2011-02-16 15:40:43 | Raid Controller Write Cache setting for WAL and Data |