Bug 128

Change the EXCEPTION in alterTableConfigureTrigger() and
alterTableDropTrigger() into a NOTICE if the underlying table
has been dropped.

src/backend/slony1_funcs.sql

@@ -3919,7 +3919,8 @@ begin
 				and PGXC.relname = T.tab_idxname
 				for update;
 	if not found then
-		raise exception 'Slony-I: alterTableDropTriggers(): Table with id % not found', p_tab_id;
+		raise notice 'Slony-I: alterTableDropTriggers(): Table with id % not found', p_tab_id;
+		return 0;
 	end if;
 	v_tab_fqname = v_tab_row.tab_fqname;
 
@@ -3985,7 +3986,8 @@ begin
 				and PGXC.relname = T.tab_idxname
 				for update;
 	if not found then
-		raise exception 'Slony-I: alterTableConfigureTriggers(): Table with id % not found', p_tab_id;
+		raise notice 'Slony-I: alterTableConfigureTriggers(): Table with id % not found', p_tab_id;
+		return 0;
 	end if;
 	v_tab_fqname = v_tab_row.tab_fqname;
 
@@ -5797,4 +5799,4 @@ comment on function @NAMESPACE@.reshapeSubscription(int4,int4,int4) is
 'Run on a receiver/subscriber node when the provider for that
 subscription is being changed.  Slonik will invoke this method
 before the SUBSCRIBE_SET event propogates to the receiver
-so listen paths can be updated.';
+so listen paths can be updated.';