From: | Durumdara <durumdara(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Restore - disable triggers - when they fired? |
Date: | 2018-03-20 14:56:51 |
Message-ID: | CAEcMXhnYkiVmcKBVzmrQTe-ukb7cxz=cK2nbnY26A=Ywn2p6ng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dear Adrian!
2018-03-20 15:47 GMT+01:00 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>:
>
>>
>> When it would be useful?
>>
>
> https://www.postgresql.org/docs/10/static/app-pgrestore.html
> "--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. Use this if you have
> referential integrity checks or other triggers on the tables that you do
> not want to invoke during data reload.
>
> Presently, the commands emitted for --disable-triggers must be done as
> superuser. So you should also specify a superuser name with -S or,
> preferably, run pg_restore as a PostgreSQL superuser.
>
>
>
>
>> Firstly I supposed that data copy somehow could start the triggers - but
>> how?
>>
>> Which triggers? Or how they fired with this order?
>>
>
I have read it, but I don't understand it.
Do you have a good example?
Thanks!
dd
From | Date | Subject | |
---|---|---|---|
Next Message | Stuart McGraw | 2018-03-20 15:23:18 | postgresql-10.3 on unbuntu-17.10 - how?? |
Previous Message | Adrian Klaver | 2018-03-20 14:47:59 | Re: Restore - disable triggers - when they fired? |