I'd speculate that what happened in this case is as follows: 1. Database was set up with some set of triggers
2. Replication was set up 3. Oops, the triggers disappeared on a subscriber. Gotta add it back... 4. Some revision to subscriptions caused an attempt to rewrite the triggers. Triggers then clash...
--- Begin Message ------------- Forwarded message ---------- From: praneet <[EMAIL PROTECTED]> Date: May 5, 2006 1:19 AM Subject: Problem in replicating the tables having triggers To: [EMAIL PROTECTED] Hi Chirtopher, Myself Praneet from Delhi,India working on database replication with slony on suse Linux based system. I'm facing a problem which is much more critical for me while I'm replicating data from one node to another node. There is a problem which I've encontered in slony logs, like this I've created a set and added a table having associated triggers into that set but slony is not able to replicate data of this table from one node to another ; In log this is like this displayed..... 2006-05-03 21:20:01 EDT DEBUG3 remoteWorkerThread_2: table "msw"."callingplans" does not require Slony-I serial key 2006-05-03 21:20:01 EDT ERROR remoteWorkerThread_2: "select "_mswcluster".setAddTable_int(1, 11, '"msw"."callingplans"', 'callingplans_pkey', 'callingplans table'); " PGRES_FATAL_ERROR ERROR: duplicate key violates unique constraint "pg_trigger_tgrelid_tgname_index" CONTEXT: SQL statement "update "pg_catalog".pg_trigger set tgrelid = $1 where tgrelid = $2 and not exists ( select true from "_mswcluster".sl_table TAB, "_mswcluster".sl_trigger TRIG where TAB.tab_reloid = tgrelid and TAB.tab_id = TRIG.trig_tabid and TRIG.trig_tgname = tgname )" PL/pgSQL function "altertableforreplication" line 76 at SQL statement SQL statement "SELECT "_mswcluster".alterTableForReplication( $1 )" PL/pgSQL function "setaddtable_int" line 80 at perform ...... this shows it is trying to enter some value into pg_catalog.pg_trigger table but it is vain. Could you please suggest for something in this direction. Your invaluable help is highly appreciated. Waiting for your kind reply. Thanks in anticipation. Praneet Sr. Software Engineer Induslogic Inc, Delhi -- http://www3.sympatico.ca/cbbrowne/linux.html Oddly enough, this is completely standard behaviour for shells. This is a roundabout way of saying `don't use combined chains of `&&'s and `||'s unless you think Gödel's theorem is for sissies'.
--- End Message ---
_______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
