From: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Disable Triggers |
Date: | 2008-02-21 16:26:33 |
Message-ID: | 9725AE48-6765-4B39-A4BB-849E7D3B6E49@themactionfaction.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Feb 21, 2008, at 10:20 AM, Terry Lee Tucker wrote:
> Greetings:
>
> We have been working diligently toward integrating Slony into our
> production
> databases. We've been having trouble with various tables, although
> being
> replicated perfectly in the initial replication stage, afterwards,
> getting
> out of sync.
>
> I have finally figured out what the problem is. We have a Perl
> process that
> continually updates certain columns across all databases. That Perl
> process
> calls a function we have written called disable_triggers which updates
> pg_class, setting reltriggers to 0 for the given table, and then
> later, after
> the work is complete, resetting reltriggers to the original value.
> Unfortunately, during this process, the Slony trigger is disabled
> as well
> which is causing our problem.
>
> My questions is this: how would I go about changing my function so
> that all
> the triggers EXCEPT the Slony trigger would be disabled? Any ideas?
>
> Version:
> PostgreSQL 7.4.19 on i686-redhat-linux-gnu, compiled by GCC gcc
> (GCC) 3.4.6
> 20060404 (Red Hat 3.4.6-9)
Couldn't your triggers check some flag to determine if they should
continue?
Cheers,
M
From | Date | Subject | |
---|---|---|---|
Next Message | hernan gonzalez | 2008-02-21 16:34:15 | text and bytea |
Previous Message | Terry Lee Tucker | 2008-02-21 15:26:05 | Disable Triggers |