From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Disable Triggers |
Date: | 2008-02-21 17:20:22 |
Message-ID: | 20080221172022.GC18657@crankycanuck.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Feb 21, 2008 at 11:44:25AM -0500, Terry Lee Tucker wrote:
> table where, when the given trigger does fire, it checks for an entry in the
> table at the top of the trigger and takes the appropiate action. The problem
> is that the solution for disabling all triggers is used in several utility
> programs and I'm trying to avoid changing a bunch of code.
> I appreciate your input.
Well, you could try rewriting the function to disable all but the Slony
trigger. But there's something else wrong here.
I seem to recall that we found some code path where reltriggers wasn't
checked properly anyway, so disabling triggers wouldn't work exactly as you
are doing it. This was part of the reason for the catalogue-breaking oid
fiddling Slony does on replicated tables, IIRC. So I'm not even sure your
current approach will work reliably as you think.
Probably the right answer, I'm afraid, is to change your trigger functions
to fire more selectively, then make the disable trigger function a no-op (so
you don't have to change all your other code right now).
A
From | Date | Subject | |
---|---|---|---|
Next Message | Julio Cesar Leiva | 2008-02-21 17:33:03 | Re: PostgreSQL 8.3.0 RPMs are available for download |
Previous Message | Tom Lane | 2008-02-21 17:19:53 | Re: No pgxs.mk with win32 binaries |