CVS User Account cvsuser
Tue Jul 11 07:34:02 PDT 2006
Log Message:
-----------
Cosmetic changes to comments and such

Modified Files:
--------------
    slony1-engine/src/backend:
        README.events (r1.6 -> r1.7)
        slony1_funcs.sql (r1.88 -> r1.89)

-------------- next part --------------
Index: README.events
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/src/backend/README.events,v
retrieving revision 1.6
retrieving revision 1.7
diff -Lsrc/backend/README.events -Lsrc/backend/README.events -u -w -r1.6 -r1.7
--- src/backend/README.events
+++ src/backend/README.events
@@ -1,3 +1,7 @@
+Event Documentation
+---------------------
+$Id$
+
 STORE_NODE
 	ev_data1		no_id
 	ev_data2		no_comment
Index: slony1_funcs.sql
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/src/backend/slony1_funcs.sql,v
retrieving revision 1.88
retrieving revision 1.89
diff -Lsrc/backend/slony1_funcs.sql -Lsrc/backend/slony1_funcs.sql -u -w -r1.88 -r1.89
--- src/backend/slony1_funcs.sql
+++ src/backend/slony1_funcs.sql
@@ -661,7 +661,8 @@
 -- ----------------------------------------------------------------------
 -- FUNCTION registerNodeConnection (nodeid)
 --
---	
+-- register a node connection for a slon so that only that slon services
+-- the node
 -- ----------------------------------------------------------------------
 create or replace function @NAMESPACE at .registerNodeConnection (int4)
 returns int4
@@ -1017,7 +1018,7 @@
 	if exists (select true from @NAMESPACE at .sl_subscribe
 			where sub_provider = p_no_id)
 	then
-		raise exception ''Slony-I: Node % is still configured as data provider'',
+		raise exception ''Slony-I: Node % is still configured as a data provider'',
 				p_no_id;
 	end if;
 
@@ -1125,7 +1126,7 @@
 
 	-- ----
 	-- All consistency checks first
-	-- Check that every system that has a path to the failed node
+	-- Check that every node that has a path to the failed node
 	-- also has a path to the backup node.
 	-- ----
 	for v_row in select P.pa_client
@@ -1149,7 +1150,7 @@
 	loop
 		-- ----
 		-- Check that the backup node is subscribed to all sets
-		-- that origin on the failed node
+		-- that originate on the failed node
 		-- ----
 		select into v_row2 sub_forward, sub_active
 				from @NAMESPACE at .sl_subscribe
@@ -5372,7 +5373,7 @@
 		perform "pg_catalog".setval(''@NAMESPACE at .sl_log_status'', 3);
 		perform @NAMESPACE at .registry_set_timestamp(
 				''logswitch.laststart'', now()::timestamp);
-		raise notice ''Logswitch to sl_log_2 initiated'';
+		raise notice ''Slony-I: Logswitch to sl_log_2 initiated'';
 		return 2;
 	end if;
 
@@ -5384,7 +5385,7 @@
 		perform "pg_catalog".setval(''@NAMESPACE at .sl_log_status'', 2);
 		perform @NAMESPACE at .registry_set_timestamp(
 				''logswitch.laststart'', now()::timestamp);
-		raise notice ''Logswitch to sl_log_1 initiated'';
+		raise notice ''Slony-I: Logswitch to sl_log_1 initiated'';
 		return 1;
 	end if;
 



More information about the Slony1-commit mailing list