Yes, it isn't a name problem then. On our two slave nodes:

tmc=# select tgrelid, tgname,count(*) from pg_trigger group by 1,2  
having count(*) > 1;
tgrelid | tgname | count
---------+--------+-------
(0 rows)

So are you saying that EXECUTE SCRIPT would disable triggers even on  
tables in different schemas? In any case, assuming that your  
hypothesis is correct, how do we fix this now? (I'd like to be able  
to run execute script on my slony tables sometimes ; ) )

On Jun 29, 2006, at 4:48 PM, Christopher Browne wrote:

> Kick me if I'm wrong, but I don't think that's quite at the root of  
> the
> problem...
>
> The name of the trigger wasn't the whole problem; the unique index was
> on (reloid, trigger name).
>
> There shouldn't be any conflict if you have a trigger on a table that
> isn't participating in replication at all.

> I'll go out on a limb and suggest that something more complex  
> happened...
>
> At Time T1, I expect you added triggers to those tables on the  
> subscriber.
>
> At Time T2 > T1, you ran EXECUTE SCRIPT, which, after running the
> script, hid them.
>
> Someone noticed the triggers were gone.
>
> Time T3 > T2, triggers were added again.
>
> Subsequently, EXECUTE SCRIPT would lead to the breakage observed.




######################################################################
This e-mail is confidential and should not be redistributed or
forwarded by the recipient.  The information contained in this e-mail
message is intended only for the use of the individual or entity named
above.  If the reader of this message is not the intended recipient or
you have received this communication in error, please immediately
notify us by telephone.  Receipt by anyone other than the intended
recipient is not a waiver of any work-product or, if applicable,
attorney-client privilege.

This e-mail does not constitute an offering of any security.  Such an
offering may only be made by means of a private placement memorandum
or other disclosure document.  Nothing in this e-mail constitutes
investment advice.  Past performance is not indicative of future
results.  All e-mail to and from Millburn Ridgefield Corporation and
its affiliates is monitored, stored and made available to regulators
if requested.
######################################################################