On Tue, Jun 17, 2003 at 11:49:44AM -0700, Josh Berkus wrote:
I also need something like that for my replication stuff:
When data from another node comes it, it should be written
directly to the tables, without any (unwanted) triggers firering.
On the other hand, in "normal" mode, also some mi
Mallah,
> in past we tried creating a plpgsql function that takes relname and schema
> and try setting reltriggers=0 on disabling and = (select count(*) from
pg_trigger
> for that relname and schema) on enabling .
>
> we got stuck somewhere and abandoned it , do u think above approach
> would
> Mallah,
>
>> >> Is setting reltriggers=0 on pg_class an accepatble way of
>> >> disabling triggers on a table temporarily?
>>
>> Ok , but someone on list was scary few months back.
>
> I've done it many times without a problem. The trick is re-setting the triggers to
> the
> correct number wh
Mallah,
> >> Is setting reltriggers=0 on pg_class an accepatble way of
> >> disabling triggers on a table temporarily?
>
> Ok , but someone on list was scary few months back.
I've done it many times without a problem. The trick is re-setting the
triggers to the correct number when you're done
Mallah,
> Is setting reltriggers=0 on pg_class an accepatble way of
> disabling triggers on a table temporarily?
Yes. pg_dump does this.
> secondly is it worth having commands like
> alter trigger inactive;
> alter trigger active ;
> i feel such commands exists on Oracle.
No, since DROP TRI
> Mallah,
>
>> Is setting reltriggers=0 on pg_class an accepatble way of
>> disabling triggers on a table temporarily?
Ok , but someone on list was scary few months back.
>
> Yes. pg_dump does this.
>
>> secondly is it worth having commands like
>> alter trigger inactive;
>> alter trigger act
