From: | "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Trigger disable for table |
Date: | 2008-10-02 10:59:45 |
Message-ID: | 20081002105945.GF20230@a-kretschmer.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
am Thu, dem 02.10.2008, um 12:26:20 +0200 mailte Frank Durstewitz folgendes:
> My idea is to have it like
> ...
> IF NEW.published = TRUE THEN
> ALTER TABLE a DISABLE TRIGGER mytrigger USER;
> (do update here)
> ALTER TABLE a ENABLE TRIGGER mytrigger USER;
> ...
>
> Will a construct like this disable the trigger only inside the this
> function or is the trigger disabled outside (visiblility?) the function,
> too, which is unacceptable.
I think, you can do that, but an 'ALTER TABLE' produce a
AccessExclusiveLock on this table.
Andreas
--
Andreas Kretschmer
Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header)
GnuPG-ID: 0x3FFF606C, privat 0x7F4584DA http://wwwkeys.de.pgp.net
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2008-10-02 11:49:06 | Re: Transactions within a function body |
Previous Message | Terry Lee Tucker | 2008-10-02 10:52:07 | Re: Trigger disable for table |