From: Flávio Suguimoto <flavio.suguimoto@pragyatechnologies.com>
To: Richard Huxton <dev@archonet.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Problems with disabling triggers in Postgres 7.3.9
Date: Thu, 9 Mar 2006 11:25:28 -0300
Message-ID: <GFEGIFLJJCMGLBLAHILKIECHCGAA.flavio.suguimoto@pragyatechnologies.com> (raw)
In-Reply-To: <44103409.6030801@archonet.com>
Hi Richard,
I have that trigger running on AFTER INSERT of participation table. That
trigger inserts 3 new record for each line i inserted in participation.
I guess the problem is in these two statement:
EXECUTE ''update pg_class set reltriggers=0 where relname = '' ||
quote_literal(tablename);
EXECUTE ''update pg_class set reltriggers = count(*) from pg_trigger where
pg_class.oid=tgrelid and relname = '' || quote_literal(tablename);
These statement is a walk-around to disable and enable the trigger on a
table and i use this to avoid the trigger be called recursively.
My question is there is another to do this trigger avoiding need to
disable/enable the triggers? Or there is an way to solve this problem with
RelationBuildTriggers?
regards,
Flávio Suguimoto
-----Original Message-----
From: Richard Huxton [mailto:dev@archonet.com]
Sent: Thursday, March 09, 2006 10:56 AM
To: Flávio Suguimoto
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] Problems with disabling triggers in Postgres 7.3.9
Flávio Suguimoto wrote:
> Hi all,
>
> I have a problem in a trigger that disable all the triggers of a table.
This
> error occurs randomly and my guess is that occurs when i have a lot of
> concurrents inserts in the table participation.
>
> The error is : RelationBuildTriggers: 2 record(s) not found for rel
> participation
Well, at the very least you should get an exclusive write-lock on the
table "participation" before turning its triggers off.
However, I'm doubtful that you really want to do that in any case. Can I
ask what problem you are trying to solve?
Oh, and upgrade to 7.3.14 too - you're missing 5 sets of bug-fixes.
--
Richard Huxton
Archonet Ltd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: flavio.suguimoto@pragyatechnologies.com, dev@archonet.com
Subject: Re: Problems with disabling triggers in Postgres 7.3.9
In-Reply-To: <GFEGIFLJJCMGLBLAHILKIECHCGAA.flavio.suguimoto@pragyatechnologies.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox