From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_restore man page question |
Date: | 2016-03-07 17:33:17 |
Message-ID: | 56DDBB5D.7010604@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 03/07/2016 09:17 AM, Karsten Hilbert wrote:
> The man page of pg_restore says
>
> --disable-triggers
> This option is relevant only when performing a
> data-only restore. It instructs pg_restore to execute
> commands to temporarily disable triggers on the
> target tables while the data is reloaded. [...]
>
> This hint seems overly narrow: when doing a restore of schema
> PLUS data (IOW, not a schema-only restore) it should apply,
> too, shouldn't it ?
No because triggers are restored AFTER data. This explicitly applies to
data being restored to an existing schema that has triggers on the table
the data is being loaded into.
Sincerely,
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
From | Date | Subject | |
---|---|---|---|
Next Message | Geoff Winkless | 2016-03-07 17:35:04 | Re: index problems (again) |
Previous Message | Steven Xu | 2016-03-07 17:21:56 | Re: Custom column ordering |