From: | Christian Elmerot <ce(at)one(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Running query without trigger? |
Date: | 2016-07-09 09:18:52 |
Message-ID: | 4ad357c6-0558-a73c-6290-168ebcfbe6f3@one.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2016-07-09 08:20, hamann(dot)w(at)t-online(dot)de wrote:
> Hi,
>
> a table is associated with a trigger for normal use.
> An admin (someone with ALTER privilege) can disable tthe trigger, run some bulk update,
> and then re-enable it. This means, however, that normal user activity has to be locked out.
>
> There are two possible scenarios: the bulk update would not cause trigger activity at all,
> because of the values and columns involved.
> or - the bulk update is followed by another bulk transaction that is equivalent to trigger
> invocations per row.
> At least in the first case, running this particular query without triggering the trigger,
> but normal activity still going on, would be really great
> Is there a way to achieve this?
>
> Regards
> Wolfgang Hamann
Well for temporary disabling triggers the easiest is to run:
SET session_replication_role = replica;
UPDATE ...
SET session_replication_role = DEFAULT;
This only affects the current session i.e. you and not any other
sessions which is what you seemed to require. All this assuming you run
a supported version of postgres
Regards,
Christian Elmerot, Systems Engineer One.com
From | Date | Subject | |
---|---|---|---|
Next Message | arnaud gaboury | 2016-07-09 09:54:58 | Re: Broken after upgrade |
Previous Message | Berend Tober | 2016-07-09 07:57:37 | Re: Running query without trigger? |