diff --git a/docs/en_US/pgadmin3.hhc b/docs/en_US/pgadmin3.hhc
index 66ee856691..4200fcf709 100644
--- a/docs/en_US/pgadmin3.hhc
+++ b/docs/en_US/pgadmin3.hhc
@@ -5842,7 +5842,7 @@
 		</UL>
 	</UL>
 	<LI> <OBJECT type="text/sitemap">
-		<param name="Name" value="Slony-I HEAD_20051102 Documentation">
+		<param name="Name" value="Slony-I HEAD_20051208 Documentation">
 		<param name="Local" value="slony/index.html">
 		</OBJECT>
 	<UL>
@@ -5858,27 +5858,27 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="What Slony-I is">
-					<param name="Local" value="slony/slonyintro.html#id514281">
+					<param name="Local" value="slony/slonyintro.html#id486434">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Why yet another replication system?">
-					<param name="Local" value="slony/slonyintro.html#id459618">
+					<param name="Local" value="slony/slonyintro.html#id459615">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="What Slony-I is not">
-					<param name="Local" value="slony/slonyintro.html#id459639">
+					<param name="Local" value="slony/slonyintro.html#id459634">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Why doesn't Slony-I do automatic fail-over/promotion?">
-					<param name="Local" value="slony/slonyintro.html#id459737">
+					<param name="Local" value="slony/slonyintro.html#id459733">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Current Limitations">
-					<param name="Local" value="slony/slonyintro.html#id459823">
+					<param name="Local" value="slony/slonyintro.html#id459819">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Replication Models">
-					<param name="Local" value="slony/slonyintro.html#id459938">
+					<param name="Local" value="slony/slonyintro.html#id459934">
 					</OBJECT>
 			</UL>
 			<LI> <OBJECT type="text/sitemap">
@@ -5892,11 +5892,11 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Slony-I Software Dependancies">
-					<param name="Local" value="slony/requirements.html#id460225">
+					<param name="Local" value="slony/requirements.html#id460221">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Getting Slony-I Source">
-					<param name="Local" value="slony/requirements.html#id461008">
+					<param name="Local" value="slony/requirements.html#id486473">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Time Synchronization">
@@ -5904,7 +5904,7 @@
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Network Connectivity">
-					<param name="Local" value="slony/requirements.html#id503538">
+					<param name="Local" value="slony/requirements.html#id486679">
 					</OBJECT>
 			</UL>
 			<LI> <OBJECT type="text/sitemap">
@@ -5914,31 +5914,31 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Short Version">
-					<param name="Local" value="slony/installation.html#id503803">
+					<param name="Local" value="slony/installation.html#id486943">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Configuration">
-					<param name="Local" value="slony/installation.html#id503820">
+					<param name="Local" value="slony/installation.html#id486960">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Example">
-					<param name="Local" value="slony/installation.html#id503885">
+					<param name="Local" value="slony/installation.html#id487026">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Build">
-					<param name="Local" value="slony/installation.html#id503978">
+					<param name="Local" value="slony/installation.html#id487118">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Installing Slony-I">
-					<param name="Local" value="slony/installation.html#id504038">
+					<param name="Local" value="slony/installation.html#id487178">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Installing Slony-I from RPMs">
-					<param name="Local" value="slony/installation.html#id504085">
+					<param name="Local" value="slony/installation.html#id487226">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Installing the Slony-I service on Windows&quot;">
-					<param name="Local" value="slony/installation.html#id504164">
+					<param name="Local" value="slony/installation.html#id487324">
 					</OBJECT>
 			</UL>
 			<LI> <OBJECT type="text/sitemap">
@@ -5948,27 +5948,27 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Cluster">
-					<param name="Local" value="slony/concepts.html#id504363">
+					<param name="Local" value="slony/concepts.html#id514215">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Node">
-					<param name="Local" value="slony/concepts.html#id514321">
+					<param name="Local" value="slony/concepts.html#id514273">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Replication Set">
-					<param name="Local" value="slony/concepts.html#id514402">
+					<param name="Local" value="slony/concepts.html#id514356">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Origin, Providers and Subscribers">
-					<param name="Local" value="slony/concepts.html#id514432">
+					<param name="Local" value="slony/concepts.html#id514386">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slon Daemon">
-					<param name="Local" value="slony/concepts.html#id514498">
+					<param name="Local" value="slony/concepts.html#id514451">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik Configuration Processor">
-					<param name="Local" value="slony/concepts.html#id514562">
+					<param name="Local" value="slony/concepts.html#id514515">
 					</OBJECT>
 			</UL>
 			<LI> <OBJECT type="text/sitemap">
@@ -5982,7 +5982,7 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Primary Keys">
-					<param name="Local" value="slony/definingsets.html#id514692">
+					<param name="Local" value="slony/definingsets.html#id514645">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Grouping tables into sets">
@@ -5990,7 +5990,7 @@
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="The Pathology of Sequences">
-					<param name="Local" value="slony/definingsets.html#id514982">
+					<param name="Local" value="slony/definingsets.html#id514935">
 					</OBJECT>
 			</UL>
 		</UL>
@@ -6005,16 +6005,16 @@
 				</OBJECT>
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
-					<param name="Name" value="Creating the pgbenchuser">
-					<param name="Local" value="slony/slonyadmin.html#id515383">
+					<param name="Name" value="Creating the pgbench user">
+					<param name="Local" value="slony/slonyadmin.html#id515431">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Preparing the databases">
-					<param name="Local" value="slony/slonyadmin.html#id515394">
+					<param name="Local" value="slony/slonyadmin.html#id515448">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Configuring the Database for Replication.">
-					<param name="Local" value="slony/slonyadmin.html#id515514">
+					<param name="Local" value="slony/slonyadmin.html#id515566">
 					</OBJECT>
 			</UL>
 			<LI> <OBJECT type="text/sitemap">
@@ -6032,19 +6032,19 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="CONFIG notices">
-					<param name="Local" value="slony/monitoring.html#id516282">
+					<param name="Local" value="slony/monitoring.html#id459433">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="DEBUG Notices">
-					<param name="Local" value="slony/monitoring.html#id516307">
+					<param name="Local" value="slony/monitoring.html#id516589">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="How to read Slony-I logs">
-					<param name="Local" value="slony/monitoring.html#id516363">
+					<param name="Local" value="slony/monitoring.html#id516646">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Nagios Replication Checks">
-					<param name="Local" value="slony/monitoring.html#id516582">
+					<param name="Local" value="slony/monitoring.html#id516864">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="test_slony_state">
@@ -6058,19 +6058,19 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Watchdogs: Keeping Slons Running">
-					<param name="Local" value="slony/maintenance.html#id517055">
+					<param name="Local" value="slony/maintenance.html#id517337">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Parallel to Watchdog: generate_syncs.sh">
-					<param name="Local" value="slony/maintenance.html#id517083">
+					<param name="Local" value="slony/maintenance.html#id517365">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Replication Test Scripts">
-					<param name="Local" value="slony/maintenance.html#id517183">
+					<param name="Local" value="slony/maintenance.html#id517465">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Log Files">
-					<param name="Local" value="slony/maintenance.html#id517393">
+					<param name="Local" value="slony/maintenance.html#id517675">
 					</OBJECT>
 			</UL>
 			<LI> <OBJECT type="text/sitemap">
@@ -6084,23 +6084,23 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Foreword">
-					<param name="Local" value="slony/failover.html#id517604">
+					<param name="Local" value="slony/failover.html#id517886">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Controlled Switchover">
-					<param name="Local" value="slony/failover.html#id517663">
+					<param name="Local" value="slony/failover.html#id517944">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Failover">
-					<param name="Local" value="slony/failover.html#id517791">
+					<param name="Local" value="slony/failover.html#id518072">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Automating FAIL OVER">
-					<param name="Local" value="slony/failover.html#id517945">
+					<param name="Local" value="slony/failover.html#id518296">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
-					<param name="Name" value="After Failover, Reconfiguring node1">
-					<param name="Local" value="slony/failover.html#id518015">
+					<param name="Name" value="After Failover, Reconfiguring node 1">
+					<param name="Local" value="slony/failover.html#rebuildnode1">
 					</OBJECT>
 			</UL>
 			<LI> <OBJECT type="text/sitemap">
@@ -6110,11 +6110,11 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="How listening can break">
-					<param name="Local" value="slony/listenpaths.html#id518257">
+					<param name="Local" value="slony/listenpaths.html#id518627">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="How the listen configuration should look">
-					<param name="Local" value="slony/listenpaths.html#id518342">
+					<param name="Local" value="slony/listenpaths.html#id518712">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Automated Listen Path Generation">
@@ -6140,23 +6140,23 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Dropping A Whole Node">
-					<param name="Local" value="slony/dropthings.html#id519664">
+					<param name="Local" value="slony/dropthings.html#id520032">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Dropping An Entire Set">
-					<param name="Local" value="slony/dropthings.html#id519751">
+					<param name="Local" value="slony/dropthings.html#id520120">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Unsubscribing One Node From One Set">
-					<param name="Local" value="slony/dropthings.html#id519850">
+					<param name="Local" value="slony/dropthings.html#id520218">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Dropping A Table From A Set">
-					<param name="Local" value="slony/dropthings.html#id519925">
+					<param name="Local" value="slony/dropthings.html#id520293">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Dropping A Sequence From A Set">
-					<param name="Local" value="slony/dropthings.html#id520023">
+					<param name="Local" value="slony/dropthings.html#id520391">
 					</OBJECT>
 			</UL>
 			<LI> <OBJECT type="text/sitemap">
@@ -6166,7 +6166,7 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Usage Hints">
-					<param name="Local" value="slony/logshipping.html#id520669">
+					<param name="Local" value="slony/logshipping.html#id521037">
 					</OBJECT>
 			</UL>
 			<LI> <OBJECT type="text/sitemap">
@@ -6176,11 +6176,11 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Changes that you might not want to process using EXECUTE SCRIPT">
-					<param name="Local" value="slony/ddlchanges.html#id521215">
+					<param name="Local" value="slony/ddlchanges.html#id521583">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Testing DDL Changes">
-					<param name="Local" value="slony/ddlchanges.html#id521379">
+					<param name="Local" value="slony/ddlchanges.html#id521746">
 					</OBJECT>
 			</UL>
 			<LI> <OBJECT type="text/sitemap">
@@ -6202,99 +6202,99 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Node/Cluster Configuration - cluster.nodes">
-					<param name="Local" value="slony/altperl.html#id522344">
+					<param name="Local" value="slony/altperl.html#id522712">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Set configuration - cluster.set1, cluster.set2">
-					<param name="Local" value="slony/altperl.html#id522444">
+					<param name="Local" value="slony/altperl.html#id522846">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_build_env">
-					<param name="Local" value="slony/altperl.html#id522560">
+					<param name="Local" value="slony/altperl.html#id522962">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_create_set">
-					<param name="Local" value="slony/altperl.html#id522602">
+					<param name="Local" value="slony/altperl.html#id523005">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_drop_node">
-					<param name="Local" value="slony/altperl.html#id522627">
+					<param name="Local" value="slony/altperl.html#id523029">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_drop_set">
-					<param name="Local" value="slony/altperl.html#id522641">
+					<param name="Local" value="slony/altperl.html#id523044">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_execute_script">
-					<param name="Local" value="slony/altperl.html#id522660">
+					<param name="Local" value="slony/altperl.html#id523062">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_failover">
-					<param name="Local" value="slony/altperl.html#id522667">
+					<param name="Local" value="slony/altperl.html#id523070">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_init_cluster">
-					<param name="Local" value="slony/altperl.html#id522675">
+					<param name="Local" value="slony/altperl.html#id523078">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_merge_sets">
-					<param name="Local" value="slony/altperl.html#id522691">
+					<param name="Local" value="slony/altperl.html#id523094">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_move_set">
-					<param name="Local" value="slony/altperl.html#id522698">
+					<param name="Local" value="slony/altperl.html#id523101">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="replication_test">
-					<param name="Local" value="slony/altperl.html#id522706">
+					<param name="Local" value="slony/altperl.html#id523109">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_restart_node">
-					<param name="Local" value="slony/altperl.html#id522721">
+					<param name="Local" value="slony/altperl.html#id523123">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_restart_nodes">
-					<param name="Local" value="slony/altperl.html#id522730">
+					<param name="Local" value="slony/altperl.html#id523133">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slony_show_configuration">
-					<param name="Local" value="slony/altperl.html#id522738">
+					<param name="Local" value="slony/altperl.html#id523141">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slon_kill">
-					<param name="Local" value="slony/altperl.html#id522750">
+					<param name="Local" value="slony/altperl.html#id523153">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slon_start">
-					<param name="Local" value="slony/altperl.html#id522759">
+					<param name="Local" value="slony/altperl.html#id523162">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slon_watchdog">
-					<param name="Local" value="slony/altperl.html#id522768">
+					<param name="Local" value="slony/altperl.html#id523171">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slon_watchdog2">
-					<param name="Local" value="slony/altperl.html#id522781">
+					<param name="Local" value="slony/altperl.html#id523184">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_store_node">
-					<param name="Local" value="slony/altperl.html#id522801">
+					<param name="Local" value="slony/altperl.html#id523204">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_subscribe_set">
-					<param name="Local" value="slony/altperl.html#id522809">
+					<param name="Local" value="slony/altperl.html#id523212">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_uninstall_nodes">
-					<param name="Local" value="slony/altperl.html#id522817">
+					<param name="Local" value="slony/altperl.html#id523220">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_unsubscribe_set">
-					<param name="Local" value="slony/altperl.html#id522837">
+					<param name="Local" value="slony/altperl.html#id523240">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="slonik_update_nodes">
-					<param name="Local" value="slony/altperl.html#id522844">
+					<param name="Local" value="slony/altperl.html#id523247">
 					</OBJECT>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="regenerate-listens">
@@ -6309,6 +6309,10 @@
 				<param name="Name" value="Slony-I Best Practices">
 				<param name="Local" value="slony/bestpractices.html">
 				</OBJECT>
+			<LI> <OBJECT type="text/sitemap">
+				<param name="Name" value="Slony-I Test Bed Framework">
+				<param name="Local" value="slony/testbed.html">
+				</OBJECT>
 			<LI> <OBJECT type="text/sitemap">
 				<param name="Name" value="More Slony-I Help">
 				<param name="Local" value="slony/help.html">
@@ -6316,7 +6320,7 @@
 			<UL>
 				<LI> <OBJECT type="text/sitemap">
 					<param name="Name" value="Other Information Sources">
-					<param name="Local" value="slony/help.html#id524802">
+					<param name="Local" value="slony/help.html#id525518">
 					</OBJECT>
 			</UL>
 		</UL>
diff --git a/docs/en_US/pgadmin3.hhk b/docs/en_US/pgadmin3.hhk
index c4b2f259c3..d8b859e4e4 100644
--- a/docs/en_US/pgadmin3.hhk
+++ b/docs/en_US/pgadmin3.hhk
@@ -2008,20 +2008,10 @@
 		<param name="Name" value="date">
 		<param name="See Also" value="formatting">
 		</OBJECT>
-	<UL>
-		<LI> <OBJECT type="text/sitemap">
-			<param name="Name" value="output format">
-			</OBJECT>
-	</UL>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="time">
 		<param name="See Also" value="formatting">
 		</OBJECT>
-	<UL>
-		<LI> <OBJECT type="text/sitemap">
-			<param name="Name" value="output format">
-			</OBJECT>
-	</UL>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="time zone">
 		<param name="Name" value="Time Zones">
@@ -10110,226 +10100,226 @@
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="cluster">
 		<param name="Name" value="Cluster">
-		<param name="Local" value="slony/concepts.html#id504366">
+		<param name="Local" value="concepts.html#id514219">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="node">
 		<param name="Name" value="Node">
-		<param name="Local" value="slony/concepts.html#id514324">
+		<param name="Local" value="concepts.html#id514277">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="replication set">
 		<param name="Name" value="Replication Set">
-		<param name="Local" value="slony/concepts.html#id514406">
+		<param name="Local" value="concepts.html#id514360">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="origin node">
 		<param name="Name" value="Origin, Providers and Subscribers">
-		<param name="Local" value="slony/concepts.html#id514437">
+		<param name="Local" value="concepts.html#id514390">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="provider node">
 		<param name="Name" value="Origin, Providers and Subscribers">
-		<param name="Local" value="slony/concepts.html#id514443">
+		<param name="Local" value="concepts.html#id514396">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="subscriber node">
 		<param name="Name" value="Origin, Providers and Subscribers">
-		<param name="Local" value="slony/concepts.html#id514464">
+		<param name="Local" value="concepts.html#id514418">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="cluster">
 		<param name="Name" value="Defining Slony-I Clusters">
-		<param name="Local" value="slony/cluster.html#id514604">
+		<param name="Local" value="cluster.html#id514557">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="replicating a first database">
 		<param name="Name" value="Replicating Your First Database">
-		<param name="Local" value="slony/slonyadmin.html#id515129">
+		<param name="Local" value="slonyadmin.html#id515083">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="subscribing nodes">
 		<param name="Name" value="Subscribing Nodes">
-		<param name="Local" value="slony/subscribenodes.html#id516032">
+		<param name="Local" value="subscribenodes.html#id516178">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="Controlled switchover">
 		<param name="Name" value="Controlled Switchover">
-		<param name="Local" value="slony/failover.html#id517667">
+		<param name="Local" value="failover.html#id517948">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="failover upon system failure">
 		<param name="Name" value="Failover">
-		<param name="Local" value="slony/failover.html#id517795">
+		<param name="Local" value="failover.html#id518076">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="listen paths">
 		<param name="Name" value="Slony-I listen paths">
-		<param name="Local" value="slony/listenpaths.html#id518148">
+		<param name="Local" value="listenpaths.html#id518517">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="locking issues">
 		<param name="Name" value="Locking Issues">
-		<param name="Local" value="slony/locking.html#id519025">
+		<param name="Local" value="locking.html#id519395">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="log shipping">
 		<param name="Name" value="Log Shipping - Slony-I with Files">
-		<param name="Local" value="slony/logshipping.html#id520107">
+		<param name="Local" value="logshipping.html#id520475">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="DDL changes">
 		<param name="Name" value="Database Schema Changes (DDL)">
-		<param name="Local" value="slony/ddlchanges.html#id520882">
+		<param name="Local" value="ddlchanges.html#id521250">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="DDL changes">
 		<param name="Name" value="Database Schema Changes (DDL)">
-		<param name="Local" value="slony/ddlchanges.html#id520882">
+		<param name="Local" value="ddlchanges.html#id521250">
 		</OBJECT>
 	<UL>
 		<LI> <OBJECT type="text/sitemap">
 			<param name="Name" value="database schema changes">
 			<param name="Name" value="Database Schema Changes (DDL)">
-			<param name="Local" value="slony/ddlchanges.html#id520882">
+			<param name="Local" value="ddlchanges.html#id521250">
 			</OBJECT>
 	</UL>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="version upgrades for PostgreSQL using Slony-I">
 		<param name="Name" value="Using Slony-I for PostgreSQL Upgrades">
-		<param name="Local" value="slony/versionupgrade.html#id522925">
+		<param name="Local" value="versionupgrade.html#id523328">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="best practices for Slony-I usage">
 		<param name="Name" value="Slony-I Best Practices ">
-		<param name="Local" value="slony/bestpractices.html#id523350">
+		<param name="Local" value="bestpractices.html#id523753">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="Frequently Asked Questions about Slony-I">
 		<param name="Name" value="Slony-I FAQ">
-		<param name="Local" value="slony/faq.html#id524876">
+		<param name="Local" value="faq.html#id525592">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="slon">
 		<param name="Name" value="Core Slony-I Programs">
-		<param name="Local" value="slony/slon.html#id529758">
+		<param name="Local" value="slon.html#id530369">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="configuration">
 		<param name="Name" value="Run-time Configuration">
-		<param name="Local" value="slony/runtime-config.html#id530782">
+		<param name="Local" value="runtime-config.html#id531404">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="configuration">
 		<param name="Name" value="Run-time Configuration">
-		<param name="Local" value="slony/runtime-config.html#id530782">
+		<param name="Local" value="runtime-config.html#id531404">
 		</OBJECT>
 	<UL>
 		<LI> <OBJECT type="text/sitemap">
 			<param name="Name" value="of the slon daemon">
 			<param name="Name" value="Run-time Configuration">
-			<param name="Local" value="slony/runtime-config.html#id530782">
+			<param name="Local" value="runtime-config.html#id531404">
 			</OBJECT>
 	</UL>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="syslog configuration parameter">
 		<param name="Name" value="Logging">
-		<param name="Local" value="slony/runtime-config.html#id530901">
+		<param name="Local" value="runtime-config.html#id531522">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="syslog_facility configuration parameter">
 		<param name="Name" value="Logging">
-		<param name="Local" value="slony/runtime-config.html#id530937">
+		<param name="Local" value="runtime-config.html#id531558">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="syslog_ident configuration parameter">
 		<param name="Name" value="Logging">
-		<param name="Local" value="slony/runtime-config.html#id530975">
+		<param name="Local" value="runtime-config.html#id531596">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="log_level configuration parameter">
 		<param name="Name" value="Logging">
-		<param name="Local" value="slony/runtime-config.html#id531009">
+		<param name="Local" value="runtime-config.html#id531630">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="log_pid configuration parameter">
 		<param name="Name" value="Logging">
-		<param name="Local" value="slony/runtime-config.html#id531043">
+		<param name="Local" value="runtime-config.html#id531664">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="log_timestamp configuration parameter">
 		<param name="Name" value="Logging">
-		<param name="Local" value="slony/runtime-config.html#id531075">
+		<param name="Local" value="runtime-config.html#id531696">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="log_timestamp_format configuration parameter">
 		<param name="Name" value="Logging">
-		<param name="Local" value="slony/runtime-config.html#id531108">
+		<param name="Local" value="runtime-config.html#id531730">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="pid_file configuration parameter">
 		<param name="Name" value="Logging">
-		<param name="Local" value="slony/runtime-config.html#id531156">
+		<param name="Local" value="runtime-config.html#id531777">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="cluster_name configuration parameter">
 		<param name="Name" value="Connection settings">
-		<param name="Local" value="slony/slon-config-connection.html#id531199">
+		<param name="Local" value="slon-config-connection.html#id531821">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="conn_info configuration parameter">
 		<param name="Name" value="Connection settings">
-		<param name="Local" value="slony/slon-config-connection.html#id531239">
+		<param name="Local" value="slon-config-connection.html#id531861">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="sql_on_connection configuration parameter">
 		<param name="Name" value="Connection settings">
-		<param name="Local" value="slony/slon-config-connection.html#id531278">
+		<param name="Local" value="slon-config-connection.html#id531900">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="sync_interval configuration parameter">
 		<param name="Name" value="Event Tuning">
-		<param name="Local" value="slony/slon-config-interval.html#id531329">
+		<param name="Local" value="slon-config-interval.html#id531951">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="sync_interval_timeout configuration parameter">
 		<param name="Name" value="Event Tuning">
-		<param name="Local" value="slony/slon-config-interval.html#id531362">
+		<param name="Local" value="slon-config-interval.html#id531983">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="sync_group_maxsize configuration parameter">
 		<param name="Name" value="Event Tuning">
-		<param name="Local" value="slony/slon-config-interval.html#id531433">
+		<param name="Local" value="slon-config-interval.html#id532055">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="vac_frequency configuration parameter">
 		<param name="Name" value="Event Tuning">
-		<param name="Local" value="slony/slon-config-interval.html#id531502">
+		<param name="Local" value="slon-config-interval.html#id532125">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="desired_sync_time configuration parameter">
 		<param name="Name" value="Event Tuning">
-		<param name="Local" value="slony/slon-config-interval.html#id531543">
+		<param name="Local" value="slon-config-interval.html#id532165">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="quit_sync_provider configuration parameter">
 		<param name="Name" value="Event Tuning">
-		<param name="Local" value="slony/slon-config-interval.html#id531594">
+		<param name="Local" value="slon-config-interval.html#id532216">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="quit_sync_finalsync configuration parameter">
 		<param name="Name" value="Event Tuning">
-		<param name="Local" value="slony/slon-config-interval.html#id531644">
+		<param name="Local" value="slon-config-interval.html#id532266">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="lag_interval configuration parameter">
 		<param name="Name" value="Event Tuning">
-		<param name="Local" value="slony/slon-config-interval.html#id531695">
+		<param name="Local" value="slon-config-interval.html#id532317">
 		</OBJECT>
 	<LI> <OBJECT type="text/sitemap">
 		<param name="Name" value="slonik">
 		<param name="Name" value="Core Slony-I Programs">
-		<param name="Local" value="slony/slonik.html#id531761">
+		<param name="Local" value="slonik.html#id532383">
 		</OBJECT>
 </UL>
 </BODY></HTML>
diff --git a/docs/en_US/pgadmin3.hhp b/docs/en_US/pgadmin3.hhp
index 45932fec3b..51752bed52 100644
--- a/docs/en_US/pgadmin3.hhp
+++ b/docs/en_US/pgadmin3.hhp
@@ -720,6 +720,7 @@ slony/noslonik.html
 slony/altperl.html
 slony/versionupgrade.html
 slony/bestpractices.html
+slony/testbed.html
 slony/help.html
 slony/faq.html
 slony/commandreference.html
diff --git a/docs/en_US/slony/addthings.html b/docs/en_US/slony/addthings.html
index 49a095f0f7..592f4eade9 100644
--- a/docs/en_US/slony/addthings.html
+++ b/docs/en_US/slony/addthings.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="locking.html" title="10. Locking Issues">
 <link rel="next" href="dropthings.html" title="12. Dropping things from Slony-I Replication">
diff --git a/docs/en_US/slony/admconninfo.html b/docs/en_US/slony/admconninfo.html
index e40ea87242..aef9210e35 100644
--- a/docs/en_US/slony/admconninfo.html
+++ b/docs/en_US/slony/admconninfo.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="hdrcmds.html" title="Slonik Preamble Commands">
 <link rel="prev" href="clustername.html" title="CLUSTER NAME">
 <link rel="next" href="cmds.html" title="Configuration and Action commmands">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">NODE ival ADMIN CONNINFO = 'DSN';</code> [<em class="replaceable"><code> ival;</code></em>] [<em class="replaceable"><code> 'conninfo'</code></em>]</p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532480"></a><h2>Description</h2>
+<a name="id533132"></a><h2>Description</h2>
 <p>     Describes how the <span class="application">slonik</span> utility can
      reach a nodes database in the cluster from where it is run
      (likely the DBA's workstation). The conninfo string is the string
@@ -29,7 +29,7 @@ <h2>Synopsis</h2>
      function. The user used to connect must be the special
      replication superuser, as some of the actions performed later may
      include operations that are strictly reserved for database
-     superusers by PostgreSQL.
+     superusers by <span class="productname">PostgreSQL</span>.
     </p>
 <p>     The <span class="application">slonik</span> utility will not try to
      connect to a given database unless some subsequent command
@@ -64,7 +64,7 @@ <h3 class="title">Note</h3>
      PATH</span></a>, see <a href="plainpaths.html" title="9.  Slony-I Path Communications">Section 9, &#8220; <span class="productname">Slony-I</span> Path Communications&#8221;</a>.</p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532585"></a><h2>Example</h2>
+<a name="id533244"></a><h2>Example</h2>
 <pre class="programlisting">     NODE 1 ADMIN CONNINFO = 'dbname=testdb host=server1 user=slony';
     </pre>
 </div>
diff --git a/docs/en_US/slony/altperl.html b/docs/en_US/slony/altperl.html
index 9f7e193456..c4d97798b7 100644
--- a/docs/en_US/slony/altperl.html
+++ b/docs/en_US/slony/altperl.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="noslonik.html" title="17.  Not Using Slonik - Bare Metal Slony-I
 Functions ">
@@ -31,7 +31,7 @@
 <span class="emphasis"><em>before</em></span> submitting it to <a href="slonik.html" title="slonik"><span class="refentrytitle"><a name="app-slonik-title"></a><span class="application">slonik</span></span></a>.</p>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522344"></a>18.1. Node/Cluster Configuration - cluster.nodes</h3></div></div></div>
+<a name="id522712"></a>18.1. Node/Cluster Configuration - cluster.nodes</h3></div></div></div>
 <p>The UNIX environment variable <code class="envar">SLONYNODES</code> is used
 to determine what Perl configuration file will be used to control the
 shape of the nodes in a <span class="productname">Slony-I</span> cluster.</p>
@@ -41,6 +41,15 @@
 <li><p><code class="envar">$CLUSTER_NAME</code>=orglogs;	# What is the name of the replication cluster?</p></li>
 <li><p><code class="envar">$LOGDIR</code>='/opt/OXRS/log/LOGDBS';	# What is the base directory for logs?</p></li>
 <li><p><code class="envar">$APACHE_ROTATOR</code>="/opt/twcsds004/OXRS/apache/rotatelogs";  # If set, where to find Apache log rotator</p></li>
+<li><p><code class="envar">foldCase</code> # If set to 1, object names (including schema names) will be
+folded to lower case.  By default, your object names will be left
+alone.  Note that <span class="productname">PostgreSQL</span> itself folds object names to lower case;
+if you create a table via the command <code class="command"> CREATE TABLE
+SOME_THING (Id INTEGER, STudlYName text);</code>, the result will
+be that all of those components are forced to lower case, thus
+equivalent to <code class="command"> create table some_thing (id integer,
+studlyname text);</code>, and the name of table and, in this case,
+the fields will all, in fact, be lower case. </p></li>
 </ul></div>
 <p> You then define the set of nodes that are to be replicated
 using a set of calls to <code class="function">add_node()</code>.</p>
@@ -62,7 +71,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522444"></a>18.2. Set configuration - cluster.set1, cluster.set2</h3></div></div></div>
+<a name="id522846"></a>18.2. Set configuration - cluster.set1, cluster.set2</h3></div></div></div>
 <p>The UNIX environment variable <code class="envar">SLONYSET</code> is used to
 determine what Perl configuration file will be used to determine what
 objects will be contained in a particular replication set.</p>
@@ -106,7 +115,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522560"></a>18.3. slonik_build_env</h3></div></div></div>
+<a name="id522962"></a>18.3. slonik_build_env</h3></div></div></div>
 <p>Queries a database, generating output hopefully suitable for
 <code class="filename">slon_tools.conf</code> consisting of:</p>
 <div class="itemizedlist"><ul type="disc">
@@ -117,7 +126,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522602"></a>18.4. slonik_create_set</h3></div></div></div>
+<a name="id523005"></a>18.4. slonik_create_set</h3></div></div></div>
 <p>This requires <code class="envar">SLONYSET</code> to be set as well as
 <code class="envar">SLONYNODES</code>; it is used to generate the <code class="command">slonik</code> script to set up
 a replication set consisting of a set of tables and sequences that are
@@ -125,89 +134,89 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522627"></a>18.5. slonik_drop_node</h3></div></div></div>
+<a name="id523029"></a>18.5. slonik_drop_node</h3></div></div></div>
 <p>Generates Slonik script to drop a node from a <span class="productname">Slony-I</span> cluster.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522641"></a>18.6. slonik_drop_set</h3></div></div></div>
+<a name="id523044"></a>18.6. slonik_drop_set</h3></div></div></div>
 <p>Generates Slonik script to drop a replication set
 (<span class="emphasis"><em>e.g.</em></span> - set of tables and sequences) from a
 <span class="productname">Slony-I</span> cluster.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522660"></a>18.7. slonik_execute_script</h3></div></div></div>
+<a name="id523062"></a>18.7. slonik_execute_script</h3></div></div></div>
 <p>Generates Slonik script to push DDL changes to a replication set.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522667"></a>18.8. slonik_failover</h3></div></div></div>
+<a name="id523070"></a>18.8. slonik_failover</h3></div></div></div>
 <p>Generates Slonik script to request failover from a dead node to some new origin</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522675"></a>18.9. slonik_init_cluster</h3></div></div></div>
+<a name="id523078"></a>18.9. slonik_init_cluster</h3></div></div></div>
 <p>Generates Slonik script to initialize a whole <span class="productname">Slony-I</span> cluster,
 including setting up the nodes, communications paths, and the listener
 routing.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522691"></a>18.10. slonik_merge_sets</h3></div></div></div>
+<a name="id523094"></a>18.10. slonik_merge_sets</h3></div></div></div>
 <p>Generates Slonik script to merge two replication sets together.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522698"></a>18.11. slonik_move_set</h3></div></div></div>
+<a name="id523101"></a>18.11. slonik_move_set</h3></div></div></div>
 <p>Generates Slonik script to move the origin of a particular set to a different node.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522706"></a>18.12. replication_test</h3></div></div></div>
+<a name="id523109"></a>18.12. replication_test</h3></div></div></div>
 <p>Script to test whether <span class="productname">Slony-I</span> is successfully replicating
 data.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522721"></a>18.13. slonik_restart_node</h3></div></div></div>
+<a name="id523123"></a>18.13. slonik_restart_node</h3></div></div></div>
 <p>Generates Slonik script to request the restart of a node.  This was
 particularly useful pre-1.0.5 when nodes could get snarled up when
 slon daemons died.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522730"></a>18.14. slonik_restart_nodes</h3></div></div></div>
+<a name="id523133"></a>18.14. slonik_restart_nodes</h3></div></div></div>
 <p>Generates Slonik script to restart all nodes in the cluster.  Not
 particularly useful.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522738"></a>18.15. slony_show_configuration</h3></div></div></div>
+<a name="id523141"></a>18.15. slony_show_configuration</h3></div></div></div>
 <p>Displays an overview of how the environment (e.g. - <code class="envar">SLONYNODES</code>) is set
 to configure things.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522750"></a>18.16. slon_kill</h3></div></div></div>
+<a name="id523153"></a>18.16. slon_kill</h3></div></div></div>
 <p>Kills slony watchdog and all slon daemons for the specified set.  It
 only works if those processes are running on the local host, of
 course!</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522759"></a>18.17. slon_start</h3></div></div></div>
+<a name="id523162"></a>18.17. slon_start</h3></div></div></div>
 <p>This starts a slon daemon for the specified cluster and node, and uses
 slon_watchdog to keep it running.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522768"></a>18.18. slon_watchdog</h3></div></div></div>
+<a name="id523171"></a>18.18. slon_watchdog</h3></div></div></div>
 <p>Used by <code class="command">slon_start</code>.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522781"></a>18.19. slon_watchdog2</h3></div></div></div>
+<a name="id523184"></a>18.19. slon_watchdog2</h3></div></div></div>
 <p>This is a somewhat smarter watchdog; it monitors a particular
 <span class="productname">Slony-I</span> node, and restarts the slon process if it hasn't seen updates
 go in in 20 minutes or more.</p>
@@ -216,29 +225,29 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522801"></a>18.20. slonik_store_node</h3></div></div></div>
+<a name="id523204"></a>18.20. slonik_store_node</h3></div></div></div>
 <p>Adds a node to an existing cluster.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522809"></a>18.21. slonik_subscribe_set</h3></div></div></div>
+<a name="id523212"></a>18.21. slonik_subscribe_set</h3></div></div></div>
 <p>Generates Slonik script to subscribe a particular node to a particular replication set.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522817"></a>18.22. slonik_uninstall_nodes</h3></div></div></div>
+<a name="id523220"></a>18.22. slonik_uninstall_nodes</h3></div></div></div>
 <p>This goes through and drops the <span class="productname">Slony-I</span> schema from each node;
 use this if you want to destroy replication throughout a cluster.
 This is a <span class="emphasis"><em>VERY</em></span> unsafe script!</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522837"></a>18.23. slonik_unsubscribe_set</h3></div></div></div>
+<a name="id523240"></a>18.23. slonik_unsubscribe_set</h3></div></div></div>
 <p>Generates Slonik script to unsubscribe a node from a replication set.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id522844"></a>18.24. slonik_update_nodes</h3></div></div></div>
+<a name="id523247"></a>18.24. slonik_update_nodes</h3></div></div></div>
 <p>Generates Slonik script to tell all the nodes to update the
 <span class="productname">Slony-I</span> functions.  This will typically be needed when you upgrade
 from one version of <span class="productname">Slony-I</span> to another.</p>
diff --git a/docs/en_US/slony/bestpractices.html b/docs/en_US/slony/bestpractices.html
index d006cf8859..501e6d46d7 100644
--- a/docs/en_US/slony/bestpractices.html
+++ b/docs/en_US/slony/bestpractices.html
@@ -5,15 +5,15 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="versionupgrade.html" title="19. Using Slony-I for PostgreSQL Upgrades">
-<link rel="next" href="help.html" title="21. More Slony-I Help">
+<link rel="next" href="testbed.html" title="21.  Slony-I Test Bed Framework ">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="bestpractices"></a>20.  <span class="productname">Slony-I</span> &#8220;<span class="quote">Best Practices</span>&#8221; </h2></div></div></div>
-<a name="id523350"></a><p> It is common for managers to have a desire to operate systems
+<a name="id523753"></a><p> It is common for managers to have a desire to operate systems
 using some available, documented set of &#8220;<span class="quote">best practices.</span>&#8221;
 Documenting that sort of thing is essential to ISO 9000, ISO 9001, and
 other sorts of organizational certifications. </p>
diff --git a/docs/en_US/slony/cluster.html b/docs/en_US/slony/cluster.html
index c8bcf1694f..f22cb571e4 100644
--- a/docs/en_US/slony/cluster.html
+++ b/docs/en_US/slony/cluster.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyintro.html" title="Slony-I Introduction">
 <link rel="prev" href="concepts.html" title="5. Slony-I Concepts">
 <link rel="next" href="definingsets.html" title="7. Defining Slony-I Replication Sets">
@@ -13,7 +13,7 @@
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="cluster"></a>6. Defining <span class="productname">Slony-I</span> Clusters</h2></div></div></div>
-<a name="id514604"></a><p>A <span class="productname">Slony-I</span> cluster is the basic grouping of database instances
+<a name="id514557"></a><p>A <span class="productname">Slony-I</span> cluster is the basic grouping of database instances
 in which replication takes place.  It consists of a set of <span class="productname">PostgreSQL</span>
 database instances in which is defined a namespace specific to that
 cluster.</p>
diff --git a/docs/en_US/slony/clustername.html b/docs/en_US/slony/clustername.html
index 8c8411e901..0e38c0343e 100644
--- a/docs/en_US/slony/clustername.html
+++ b/docs/en_US/slony/clustername.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="hdrcmds.html" title="Slonik Preamble Commands">
 <link rel="prev" href="hdrcmds.html" title="Slonik Preamble Commands">
 <link rel="next" href="admconninfo.html" title="ADMIN CONNINFO">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">CLUSTER NAME = </code> [<em class="replaceable"><code> 'clustername';</code></em>]</p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532367"></a><h2>Description</h2>
+<a name="id533017"></a><h2>Description</h2>
 <p>     Must be the very first statement in every
      <span class="application">slonik</span> script. It defines the
      namespace in which all <span class="productname">Slony-I</span>
@@ -41,7 +41,7 @@ <h2>Synopsis</h2>
     </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532415"></a><h2>Example</h2>
+<a name="id533065"></a><h2>Example</h2>
 <pre class="programlisting">     CLUSTER NAME = 'testcluster';
     </pre>
 </div>
diff --git a/docs/en_US/slony/cmds.html b/docs/en_US/slony/cmds.html
index 03e6daa5b0..efac52eccf 100644
--- a/docs/en_US/slony/cmds.html
+++ b/docs/en_US/slony/cmds.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="commandreference.html" title="Part I. Core Slony-I Programs">
 <link rel="prev" href="admconninfo.html" title="ADMIN CONNINFO">
 <link rel="next" href="stmtecho.html" title="ECHO">
diff --git a/docs/en_US/slony/commandreference.html b/docs/en_US/slony/commandreference.html
index faea4772cd..4d34e9e873 100644
--- a/docs/en_US/slony/commandreference.html
+++ b/docs/en_US/slony/commandreference.html
@@ -5,8 +5,8 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
-<link rel="up" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
+<link rel="up" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="prev" href="faq.html" title="Slony-I FAQ">
 <link rel="next" href="slon.html" title="slon">
 </head>
@@ -32,7 +32,7 @@
 </dt>
 <dt><span class="article"><a href="slonikref.html">Slonik Command Summary</a></span></dt>
 <dd><dl>
-<dt><span class="sect1"><a href="slonikref.html#id531923">1. Introduction</a></span></dt>
+<dt><span class="sect1"><a href="slonikref.html#id532547">1. Introduction</a></span></dt>
 <dd><dl><dt><span class="sect2"><a href="slonikref.html#outline">1.1. General outline</a></span></dt></dl></dd>
 </dl></dd>
 <dt><span class="reference"><a href="metacmds.html">I. Slonik Meta Commands</a></span></dt>
diff --git a/docs/en_US/slony/concepts.html b/docs/en_US/slony/concepts.html
index dbf0ecc53f..dbeeb3ab39 100644
--- a/docs/en_US/slony/concepts.html
+++ b/docs/en_US/slony/concepts.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyintro.html" title="Slony-I Introduction">
 <link rel="prev" href="installation.html" title="4. Slony-I Installation">
 <link rel="next" href="cluster.html" title="6. Defining Slony-I Clusters">
@@ -35,8 +35,8 @@
 algorithms used in <span class="productname">Slony-I</span>.</p>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id504363"></a>5.1. Cluster</h3></div></div></div>
-<a name="id504366"></a><p>In <span class="productname">Slony-I</span> terms, a &#8220;<span class="quote">cluster</span>&#8221; is a named set of
+<a name="id514215"></a>5.1. Cluster</h3></div></div></div>
+<a name="id514219"></a><p>In <span class="productname">Slony-I</span> terms, a &#8220;<span class="quote">cluster</span>&#8221; is a named set of
 <span class="productname">PostgreSQL</span> database instances; replication takes place between those
 databases.</p>
 <p>The cluster name is specified in each and every Slonik script via the directive:</p>
@@ -47,8 +47,8 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id514321"></a>5.2. Node</h3></div></div></div>
-<a name="id514324"></a><p>A <span class="productname">Slony-I</span> Node is a named <span class="productname">PostgreSQL</span> database that will be
+<a name="id514273"></a>5.2. Node</h3></div></div></div>
+<a name="id514277"></a><p>A <span class="productname">Slony-I</span> Node is a named <span class="productname">PostgreSQL</span> database that will be
 participating in replication.</p>
 <p>It is defined, near the beginning of each Slonik script, using the directive:</p>
 <pre class="programlisting"> NODE 1 ADMIN CONNINFO = 'dbname=testdb host=server1 user=slony';</pre>
@@ -63,21 +63,21 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id514402"></a>5.3.  Replication Set</h3></div></div></div>
-<a name="id514406"></a><p>A replication set is defined as a set of tables and sequences
+<a name="id514356"></a>5.3.  Replication Set</h3></div></div></div>
+<a name="id514360"></a><p>A replication set is defined as a set of tables and sequences
 that are to be replicated between nodes in a <span class="productname">Slony-I</span> cluster.</p>
 <p>You may have several sets, and the &#8220;<span class="quote">flow</span>&#8221; of
 replication does not need to be identical between those sets.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id514432"></a>5.4.  Origin, Providers and Subscribers</h3></div></div></div>
-<a name="id514437"></a><a name="id514443"></a><p>Each replication set has some origin node, which is the
+<a name="id514386"></a>5.4.  Origin, Providers and Subscribers</h3></div></div></div>
+<a name="id514390"></a><a name="id514396"></a><p>Each replication set has some origin node, which is the
 <span class="emphasis"><em>only</em></span> place where user applications are permitted
 to modify data in the tables that are being replicated.  This might
 also be termed the &#8220;<span class="quote">master provider</span>&#8221;; it is the main
 place from which data is provided.</p>
-<a name="id514464"></a><p>Other nodes in the cluster subscribe to the replication set,
+<a name="id514418"></a><p>Other nodes in the cluster subscribe to the replication set,
 indicating that they want to receive the data.</p>
 <p>The origin node will never be considered a
 &#8220;<span class="quote">subscriber.</span>&#8221; (Ignoring the case where the cluster is
@@ -89,7 +89,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id514498"></a>5.5. slon Daemon</h3></div></div></div>
+<a name="id514451"></a>5.5. slon Daemon</h3></div></div></div>
 <p>For each node in the cluster, there will be a <a href="slon.html" title="slon"><span class="refentrytitle"><a name="app-slon-title"></a><span class="application">slon</span></span></a> process to manage replication activity for that node.</p>
 <p> <a href="slon.html" title="slon"><span class="refentrytitle"><a name="app-slon-title"></a><span class="application">slon</span></span></a> is a program implemented in C that
 processes replication events.  There are two main sorts of events:</p>
@@ -109,7 +109,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id514562"></a>5.6. slonik Configuration Processor</h3></div></div></div>
+<a name="id514515"></a>5.6. slonik Configuration Processor</h3></div></div></div>
 <p> The <a href="slonik.html" title="slonik"><span class="refentrytitle"><a name="app-slonik-title"></a><span class="application">slonik</span></span></a> command processor processes scripts
 in a &#8220;<span class="quote">little language</span>&#8221; that are used to submit events to
 update the configuration of a <span class="productname">Slony-I</span> cluster.  This includes such
diff --git a/docs/en_US/slony/ddlchanges.html b/docs/en_US/slony/ddlchanges.html
index 38ea4525a8..041ad445f6 100644
--- a/docs/en_US/slony/ddlchanges.html
+++ b/docs/en_US/slony/ddlchanges.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="logshipping.html" title="13. Log Shipping - Slony-I with Files">
 <link rel="next" href="usingslonik.html" title="15. Using Slonik">
@@ -13,7 +13,7 @@
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="ddlchanges"></a>14. Database Schema Changes (DDL)</h2></div></div></div>
-<a name="id520882"></a><p>When changes are made to the database schema,
+<a name="id521250"></a><p>When changes are made to the database schema,
 <span class="emphasis"><em>e.g.</em></span> - adding fields to a table, it is necessary
 for this to be handled rather carefully, otherwise different nodes may
 get rather deranged because they disagree on how particular tables are
@@ -100,7 +100,8 @@
 that fewer locks need to be taken in order for the DDL script to make
 it into place.</p>
 <p> If a particular DDL script only affects one table, it should be
-unnecessary to lock <span class="emphasis"><em>all</em></span> application tables.</p>
+unnecessary to lock <span class="emphasis"><em>all</em></span> application
+tables.</p>
 </li>
 <li><p> You may need to take a brief application outage in
 order to ensure that your applications are not demanding locks that
@@ -120,7 +121,7 @@
 here: <a href="http://www.varlena.com/varlena/GeneralBits/88.php" target="_top">Varlena General Bits</a></p>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id521215"></a>14.1.  Changes that you might <span class="emphasis"><em>not</em></span> want to
+<a name="id521583"></a>14.1.  Changes that you might <span class="emphasis"><em>not</em></span> want to
 process using <code class="command">EXECUTE SCRIPT</code></h3></div></div></div>
 <p> While it is <span class="emphasis"><em> vitally necessary </em></span> to use
 <code class="command">EXECUTE SCRIPT</code> to propagate DDL modifications to
@@ -182,7 +183,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id521379"></a>14.2.  Testing DDL Changes </h3></div></div></div>
+<a name="id521746"></a>14.2.  Testing DDL Changes </h3></div></div></div>
 <p> A method for testing DDL changes has been pointed out as a
 likely &#8220;<span class="quote">best practice.</span>&#8221;</p>
 <p> You <span class="emphasis"><em>need</em></span> to test DDL scripts in a
diff --git a/docs/en_US/slony/definingsets.html b/docs/en_US/slony/definingsets.html
index 7b2351aaaa..3ada5b6860 100644
--- a/docs/en_US/slony/definingsets.html
+++ b/docs/en_US/slony/definingsets.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyintro.html" title="Slony-I Introduction">
 <link rel="prev" href="cluster.html" title="6. Defining Slony-I Clusters">
 <link rel="next" href="slonyadmin.html" title=" Slony-I Administration ">
@@ -26,7 +26,7 @@
 </ul></div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id514692"></a>7.1. Primary Keys</h3></div></div></div>
+<a name="id514645"></a>7.1. Primary Keys</h3></div></div></div>
 <p><span class="productname">Slony-I</span> <span class="emphasis"><em>needs</em></span> to have a primary key or
 candidate thereof on each table that is replicated.  PK values are
 used as the primary identifier for each tuple that is modified in the
@@ -116,7 +116,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id514982"></a>7.3.  The Pathology of Sequences </h3></div></div></div>
+<a name="id514935"></a>7.3.  The Pathology of Sequences </h3></div></div></div>
 <p> Each time a SYNC is processed, values are recorded for
 <span class="emphasis"><em>all</em></span> of the sequences in the set.  If there are a
 lot of sequences, this can cause <a href="table.sl-seqlog.html">sl_seqlog</a> to
diff --git a/docs/en_US/slony/dropthings.html b/docs/en_US/slony/dropthings.html
index 535bd8e2cd..ae21f05807 100644
--- a/docs/en_US/slony/dropthings.html
+++ b/docs/en_US/slony/dropthings.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="addthings.html" title="11. Adding Things to Replication">
 <link rel="next" href="logshipping.html" title="13. Log Shipping - Slony-I with Files">
@@ -17,7 +17,7 @@
 things from <span class="productname">Slony-I</span> replication.</p>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id519664"></a>12.1. Dropping A Whole Node</h3></div></div></div>
+<a name="id520032"></a>12.1. Dropping A Whole Node</h3></div></div></div>
 <p>If you wish to drop an entire node from replication, the <a href="slonik.html" title="slonik"><span class="refentrytitle"><a name="app-slonik-title"></a><span class="application">slonik</span></span></a> command <a href="stmtdropnode.html" title="DROP NODE"><span class="refentrytitle">DROP NODE</span></a> should do the
 trick.</p>
 <p>This will lead to <span class="productname">Slony-I</span> dropping the triggers (generally that
@@ -37,7 +37,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id519751"></a>12.2. Dropping An Entire Set</h3></div></div></div>
+<a name="id520120"></a>12.2. Dropping An Entire Set</h3></div></div></div>
 <p>If you wish to stop replicating a particular replication set,
 the <a href="slonik.html" title="slonik"><span class="refentrytitle"><a name="app-slonik-title"></a><span class="application">slonik</span></span></a> command <a href="stmtdropset.html" title="DROP SET"><span class="refentrytitle">DROP SET</span></a> is
 what you need to use.</p>
@@ -55,7 +55,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id519850"></a>12.3. Unsubscribing One Node From One Set</h3></div></div></div>
+<a name="id520218"></a>12.3. Unsubscribing One Node From One Set</h3></div></div></div>
 <p>The <a href="stmtunsubscribeset.html" title="UNSUBSCRIBE SET"><span class="refentrytitle">UNSUBSCRIBE SET</span></a> operation is a little
 less invasive than either <a href="stmtdropset.html" title="DROP SET"><span class="refentrytitle">DROP SET</span></a> or <a href="stmtdropnode.html" title="DROP NODE"><span class="refentrytitle">DROP NODE</span></a>; it involves dropping <span class="productname">Slony-I</span> triggers and
 restoring &#8220;<span class="quote">native</span>&#8221; triggers on one node, for one
@@ -75,7 +75,7 @@ <h3 class="title">Warning</h3>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id519925"></a>12.4.  Dropping A Table From A Set</h3></div></div></div>
+<a name="id520293"></a>12.4.  Dropping A Table From A Set</h3></div></div></div>
 <p>In <span class="productname">Slony-I</span> 1.0.5 and above, there is a Slonik command <a href="stmtsetdroptable.html" title="SET DROP TABLE"><span class="refentrytitle">SET DROP TABLE</span></a> that allows dropping a single table from
 replication without forcing the user to drop the entire replication
 set.</p>
@@ -101,7 +101,7 @@ <h3 class="title">Warning</h3>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id520023"></a>12.5. Dropping A Sequence From A Set</h3></div></div></div>
+<a name="id520391"></a>12.5. Dropping A Sequence From A Set</h3></div></div></div>
 <p>Just as with <a href="stmtsetdroptable.html" title="SET DROP TABLE"><span class="refentrytitle">SET DROP TABLE</span></a>, version 1.0.5
 introduces the operation <a href="stmtsetdropsequence.html" title="SET DROP SEQUENCE"><span class="refentrytitle">SET DROP SEQUENCE</span></a>.</p>
 <p>If you are running an earlier version, here are instructions as
diff --git a/docs/en_US/slony/failover.html b/docs/en_US/slony/failover.html
index 553d2c2a1d..b318314548 100644
--- a/docs/en_US/slony/failover.html
+++ b/docs/en_US/slony/failover.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="reshape.html" title="6. Reshaping a Cluster">
 <link rel="next" href="listenpaths.html" title="8. Slony-I listen paths">
@@ -15,7 +15,7 @@
 <a name="failover"></a>7. Doing switchover and failover with <span class="productname">Slony-I</span></h2></div></div></div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id517604"></a>7.1. Foreword</h3></div></div></div>
+<a name="id517886"></a>7.1. Foreword</h3></div></div></div>
 <p><span class="productname">Slony-I</span> is an asynchronous replication system.  Because of
 that, it is almost certain that at the moment the current origin of a
 set fails, the final transactions committed at the origin will have
@@ -38,8 +38,8 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id517663"></a>7.2.  Controlled Switchover</h3></div></div></div>
-<a name="id517667"></a><p> We assume a current &#8220;<span class="quote">origin</span>&#8221; as node1 with one
+<a name="id517944"></a>7.2.  Controlled Switchover</h3></div></div></div>
+<a name="id517948"></a><p> We assume a current &#8220;<span class="quote">origin</span>&#8221; as node1 with one
 &#8220;<span class="quote">subscriber</span>&#8221; as node2 (<span class="emphasis"><em>e.g.</em></span> -
 slave).  A web application on a third server is accessing the database
 on node1.  Both databases are up and running and replication is more
@@ -89,8 +89,8 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id517791"></a>7.3.  Failover</h3></div></div></div>
-<a name="id517795"></a><p> If some more serious problem occurs on the
+<a name="id518072"></a>7.3.  Failover</h3></div></div></div>
+<a name="id518076"></a><p> If some more serious problem occurs on the
 &#8220;<span class="quote">origin</span>&#8221; server, it may be necessary to <a href="stmtfailover.html" title="FAILOVER"><span class="refentrytitle">FAILOVER</span></a> to a backup server.  This is a highly
 undesirable circumstance, as transactions &#8220;<span class="quote">committed</span>&#8221; on
 the origin, but not applied to the subscribers, will be lost.  You may
@@ -130,6 +130,12 @@
 <span class="application">pgpool</span>) to cause it to reconnect to
 node2.</p></li>
 <li>
+<p> Purge out the abandoned node </p>
+<p> You will find, after the failover, that there are still a full
+set of references to node 1 in <a href="table.sl-node.html">sl_node</a>, as well
+as in referring tables such as <a href="table.sl-confirm.html">sl_confirm</a>;
+since data in <a href="table.sl-log-1.html">sl_log_1</a> is still present,
+<span class="productname">Slony-I</span> cannot immediately purge out the node. </p>
 <p> After the failover is complete and node2 accepts
 write operations against the tables, remove all remnants of node1's
 configuration information with the <a href="stmtdropnode.html" title="DROP NODE"><span class="refentrytitle">DROP NODE</span></a>
@@ -137,12 +143,22 @@
 
 </p>
 <pre class="programlisting">drop node (id = 1, event node = 2);</pre>
+<p> Supposing the failure resulted from some catastrophic failure
+of the hardware supporting node 1, there might be no
+&#8220;<span class="quote">remains</span>&#8221; left to look at.  If the failure was not
+&#8220;<span class="quote">total</span>&#8221;, as might be the case if the node had to be
+abandoned due to a network communications failure, you will find that
+node 1 still &#8220;<span class="quote">imagines</span>&#8221; itself to be as it was before the
+failure.  See <a href="failover.html#rebuildnode1" title="7.5. After Failover, Reconfiguring
+node 1">Section 7.5, &#8220;After Failover, Reconfiguring
+node 1&#8221;</a> for more details on the
+implications.</p>
 </li>
 </ul></div>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id517945"></a>7.4.  Automating <code class="command"> FAIL OVER </code> </h3></div></div></div>
+<a name="id518296"></a>7.4.  Automating <code class="command"> FAIL OVER </code> </h3></div></div></div>
 <p> If you do choose to automate <code class="command">FAIL OVER </code>, it
 is important to do so <span class="emphasis"><em>carefully.</em></span> You need to have
 good assurance that the failed node is well and truly failed, and you
@@ -173,13 +189,24 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id518015"></a>7.5. After Failover, Reconfiguring node1</h3></div></div></div>
-<p> After the above failover, the data stored on node1 will rapidly
-become increasingly out of sync with the rest of the nodes, and must
-be treated as corrupt.  Therefore, the only way to get node1 back and
-transfer the origin role back to it is to rebuild it from scratch as a
-subscriber, let it catch up, and then follow the switchover
-procedure.</p>
+<a name="rebuildnode1"></a>7.5. After Failover, Reconfiguring
+node 1</h3></div></div></div>
+<p> What happens to the failed node will depend somewhat on the
+nature of the catastrophe that lead to needing to fail over to another
+node.  If the node had to be abandoned because of physical destruction
+of its disk storage, there will likely not be anything of interest
+left.  On the other hand, a node might be abandoned due to the failure
+of a network connection, in which case the former
+&#8220;<span class="quote">provider</span>&#8221; can appear be functioning perfectly well.
+Nonetheless, once communications are restored, the fact of the
+<code class="command">FAIL OVER</code> makes it mandatory that the failed node
+be abandoned. </p>
+<p> After the above failover, the data stored on node 1 will
+rapidly become increasingly out of sync with the rest of the nodes,
+and must be treated as corrupt.  Therefore, the only way to get node 1
+back and transfer the origin role back to it is to rebuild it from
+scratch as a subscriber, let it catch up, and then follow the
+switchover procedure.</p>
 <p> A good reason <span class="emphasis"><em>not</em></span> to do this automatically
 is the fact that important updates (from a
 <span class="emphasis"><em>business</em></span> perspective) may have been
@@ -210,8 +237,8 @@ <h3 class="title">Warning</h3>
 network monitoring tool.  You need to have clear methods of
 communicating to applications and users what database hosts are to be
 used.  If those methods are lacking, adding replication to the mix
-will worsen the potential for confusion, and failover will be the
-point at which there is the greatest potential for confusion. </p>
+will worsen the potential for confusion, and failover will be a point
+at which there is enormous potential for confusion. </p>
 </div>
 <p> If the database is very large, it may take many hours to
 recover node1 as a functioning <span class="productname">Slony-I</span> node; that is another reason
diff --git a/docs/en_US/slony/faq.html b/docs/en_US/slony/faq.html
index 28520b9139..c6d3ac75a5 100644
--- a/docs/en_US/slony/faq.html
+++ b/docs/en_US/slony/faq.html
@@ -5,9 +5,9 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
-<link rel="up" href="index.html" title="Slony-I HEAD_20051102 Documentation">
-<link rel="prev" href="help.html" title="21. More Slony-I Help">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
+<link rel="up" href="index.html" title="Slony-I HEAD_20051208 Documentation">
+<link rel="prev" href="help.html" title="22. More Slony-I Help">
 <link rel="next" href="commandreference.html" title="Part I. Core Slony-I Programs">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="article" lang="en" id="faq">
@@ -33,32 +33,31 @@
    This is the path to postgres.h. Please specify the includeserverdir with
    --with-pgincludeserverdir=&lt;dir&gt;</a>
 </dt>
-<dt>2. <a href="faq.html#id524958">I looked for the _clustername namespace, and
+<dt>2. <a href="faq.html#id525674">I looked for the _clustername namespace, and
 it wasn't there.</a>
 </dt>
 <dt>3. <a href="faq.html#threadsafety"> Some events are moving around, but no replication is
 taking place.</a>
 </dt>
-<dt>4. <a href="faq.html#id459377">I tried creating a CLUSTER NAME with a "-" in it.
+<dt>4. <a href="faq.html#id525902">I tried creating a CLUSTER NAME with a "-" in it.
 That didn't work.</a>
 </dt>
-<dt>5. <a href="faq.html#id459412">  does not restart after
+<dt>5. <a href="faq.html#id525937">  does not restart after
 crash</a>
 </dt>
-<dt>6. <a href="faq.html#id525456">ps finds passwords on command line</a>
+<dt>6. <a href="faq.html#id526087">ps finds passwords on command line</a>
 </dt>
-<dt>7. <a href="faq.html#id525482">Slonik fails - cannot load
-PostgreSQL library -
+<dt>7. <a href="faq.html#id526113">Slonik fails - cannot load PostgreSQL library -
 PGRES_FATAL_ERROR load '$libdir/xxid';</a>
 </dt>
-<dt>8. <a href="faq.html#id525668">Table indexes with FQ namespace names
+<dt>8. <a href="faq.html#id526299">Table indexes with FQ namespace names
 
 set add table (set id = 1, origin = 1, id = 27, 
                full qualified name = 'nspace.some_table', 
                key = 'key_on_whatever', 
                comment = 'Table some_table in namespace nspace with a candidate primary key');</a>
 </dt>
-<dt>9. <a href="faq.html#id525698"> I'm trying to get a slave subscribed, and get the
+<dt>9. <a href="faq.html#id526329"> I'm trying to get a slave subscribed, and get the
 following messages in the logs:
 
 DEBUG1 copy_set 1
@@ -66,25 +65,25 @@
 WARN	remoteWorkerThread_1: transactions earlier than XID 127314958 are still in progress
 WARN	remoteWorkerThread_1: data copy for set 1 failed - sleep 60 seconds</a>
 </dt>
-<dt>10. <a href="faq.html#id525832">ERROR: duplicate key violates unique constraint "sl_table-pkey"</a>
+<dt>10. <a href="faq.html#id526463">ERROR: duplicate key violates unique constraint "sl_table-pkey"</a>
 </dt>
-<dt>11. <a href="faq.html#id525872">I need to drop a table from a replication set</a>
+<dt>11. <a href="faq.html#id526503">I need to drop a table from a replication set</a>
 </dt>
-<dt>12. <a href="faq.html#id525976">I need to drop a sequence from a replication set</a>
+<dt>12. <a href="faq.html#id526607">I need to drop a sequence from a replication set</a>
 </dt>
-<dt>13. <a href="faq.html#id526092">Slony-I: cannot add table to currently subscribed set 1</a>
+<dt>13. <a href="faq.html#id526723">Slony-I: cannot add table to currently subscribed set 1</a>
 </dt>
 <dt>14. <a href="faq.html#pglistenerfull">Some nodes start consistently falling behind</a>
 </dt>
-<dt>15. <a href="faq.html#id526230">I started doing a backup using
+<dt>15. <a href="faq.html#id526861">I started doing a backup using
 pg_dump, and suddenly Slony
 stops</a>
 </dt>
-<dt>16. <a href="faq.html#id526424">The slon spent the weekend out of
+<dt>16. <a href="faq.html#id527055">The slon spent the weekend out of
 commission [for some reason], and it's taking a long time to get a
 sync through.</a>
 </dt>
-<dt>17. <a href="faq.html#id526533">I pointed a subscribing node to a different provider
+<dt>17. <a href="faq.html#id527164">I pointed a subscribing node to a different provider
 and it stopped replicating</a>
 </dt>
 <dt>18. <a href="faq.html#faq17">After dropping a node, 
@@ -92,23 +91,23 @@
 </dt>
 <dt>19. <a href="faq.html#dupkey">Replication Fails - Unique Constraint Violation</a>
 </dt>
-<dt>20. <a href="faq.html#id527210"> If you have a  script
+<dt>20. <a href="faq.html#id527787"> If you have a  script
 something like this, it will hang on you and never complete, because
 you can't have wait for event inside a
 try block. A try block is
 executed as one transaction, and the event that you are waiting for
 can never arrive inside the scope of the transaction.</a>
 </dt>
-<dt>21. <a href="faq.html#id527265"> Is the ordering of tables in a set significant?</a>
+<dt>21. <a href="faq.html#id527862"> Is the ordering of tables in a set significant?</a>
 </dt>
-<dt>22. <a href="faq.html#id527343"> What happens with rules and triggers on
+<dt>22. <a href="faq.html#id527940"> What happens with rules and triggers on
 Slony-I-replicated tables?</a>
 </dt>
-<dt>23. <a href="faq.html#id527541"> After notification of a subscription on
+<dt>23. <a href="faq.html#id528138"> After notification of a subscription on
 another node, replication falls over, starting
 with the following error message:</a>
 </dt>
-<dt>24. <a href="faq.html#id527638">I just used  to move the
+<dt>24. <a href="faq.html#id528236">I just used  to move the
 origin to a new node.  Unfortunately, some subscribers are still
 pointing to the former origin node, so I can't take it out of service
 for maintenance without stopping them from getting updates.  What do I
@@ -124,15 +123,15 @@
 following error message repeating in them (when I encountered it,
 there was a nice long SQL statement above each entry):</a>
 </dt>
-<dt>27. <a href="faq.html#id528004"> After notification of a subscription on
+<dt>27. <a href="faq.html#id528607"> After notification of a subscription on
 another node, replication falls over on one of
 the subscribers, with the following error message:</a>
 </dt>
-<dt>28. <a href="faq.html#id528134"> I can do a pg_dump
+<dt>28. <a href="faq.html#id528714"> I can do a pg_dump
 and load the data back in much faster than the SUBSCRIBE
 SET runs.  Why is that?  </a>
 </dt>
-<dt>29. <a href="faq.html#id528264"> I had a network glitch that led to my
+<dt>29. <a href="faq.html#id528838"> I had a network glitch that led to my
 using  to fail over to an alternate node.
 The failure wasn't a disk problem that would corrupt databases; why do
 I need to rebuild the failed node from scratch? </a>
@@ -149,10 +148,10 @@
 something we didn't foresee when completely uninstalling a slony
 replication cluster from the master and slave...</a>
 </dt>
-<dt>32. <a href="faq.html#id528531"> Node #1 was dropped via , and the  one of the
+<dt>32. <a href="faq.html#id529104"> Node #1 was dropped via , and the  one of the
 other nodes is repeatedly failing with the error message:</a>
 </dt>
-<dt>33. <a href="faq.html#id528677"> I am using  Frotznik Freenix
+<dt>33. <a href="faq.html#id529251"> I am using  Frotznik Freenix
 4.5, with its FFPM (Frotznik Freenix
 Package Manager) package management system.  It comes with
 FFPM packages for PostgreSQL 7.4.7, which are what
@@ -162,37 +161,37 @@
 <dt>34. <a href="faq.html#sequenceset"> Bug #1226  indicates an error condition that can come up if
 you have a replication set that consists solely of sequences. </a>
 </dt>
-<dt>35. <a href="faq.html#id529095"> I tried the following query which did not work:</a>
+<dt>35. <a href="faq.html#id529669"> I tried the following query which did not work:</a>
 </dt>
 <dt>36. <a href="faq.html#v72upgrade"> I have a PostgreSQL 7.2-based system that I
 really, really want to use Slony-I to help me
 upgrade it to 8.0.  What is involved in getting Slony-I to work for
 that?</a>
 </dt>
-<dt>37. <a href="faq.html#id529370"> I am finding some multibyte columns (Unicode, Big5)
+<dt>37. <a href="faq.html#id529982"> I am finding some multibyte columns (Unicode, Big5)
 are being truncated.  Why?  </a>
 </dt>
-<dt>38. <a href="faq.html#id529406"> I need to rename a column that is in the
+<dt>38. <a href="faq.html#id530017"> I need to rename a column that is in the
 primary key for one of my replicated tables.  That seems pretty
 dangerous, doesn't it?  I have to drop the table out of replication
 and recreate it, right?</a>
 </dt>
-<dt>39. <a href="faq.html#id529512"> Replication has fallen behind, and it appears that the
+<dt>39. <a href="faq.html#id530124"> Replication has fallen behind, and it appears that the
 queries to draw data from / are taking a long time to pull just a few
 SYNCs. </a>
 </dt>
-<dt>40. <a href="faq.html#id529573">The  processes servicing my
+<dt>40. <a href="faq.html#id530184">The  processes servicing my
 subscribers are growing to enormous size, challenging system resources
 both in terms of swap space as well as moving towards breaking past
 the 2GB maximum process size on my system. </a>
 </dt>
 </dl>
-<a name="id524876"></a><table border="0" summary="Q and A Set">
+<a name="id525592"></a><table border="0" summary="Q and A Set">
 <col align="left" width="1%">
 <tbody>
 <tr class="question">
 <td align="left" valign="top">
-<a name="missingheaders"></a><a name="id524893"></a><b>1.</b>
+<a name="missingheaders"></a><a name="id525609"></a><b>1.</b>
 </td>
 <td align="left" valign="top">
 <p> I tried building <span class="productname">Slony-I</span> 1.1 and got the following
@@ -216,7 +215,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id524958"></a><a name="id524959"></a><b>2.</b>
+<a name="id525674"></a><a name="id525675"></a><b>2.</b>
 </td>
 <td align="left" valign="top"><p>I looked for the <code class="envar">_clustername</code> namespace, and
 it wasn't there.</p></td>
@@ -234,7 +233,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="threadsafety"></a><a name="id525007"></a><b>3.</b>
+<a name="threadsafety"></a><a name="id525722"></a><b>3.</b>
 </td>
 <td align="left" valign="top">
 <p> Some events are moving around, but no replication is
@@ -297,7 +296,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id459377"></a><a name="id459378"></a><b>4.</b>
+<a name="id525902"></a><a name="id525904"></a><b>4.</b>
 </td>
 <td align="left" valign="top"><p>I tried creating a CLUSTER NAME with a "-" in it.
 That didn't work.</p></td>
@@ -315,16 +314,16 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id459412"></a><a name="id459413"></a><b>5.</b>
+<a name="id525937"></a><a name="id525938"></a><b>5.</b>
 </td>
 <td align="left" valign="top">
 <p> <a href="slon.html" title="slon"><span class="refentrytitle"><a name="app-slon-title"></a><span class="application">slon</span></span></a> does not restart after
 crash</p>
-<p> After an immediate stop of postgresql (simulation of system
-crash) in pg_catalog.pg_listener a tuple with
-relname='_${cluster_name}_Restart' exists. slon doesn't start because
-it thinks another process is serving the cluster on this node.  What
-can I do? The tuples can't be dropped from this relation.</p>
+<p> After an immediate stop of <span class="productname">PostgreSQL</span> (simulation of system
+crash) in <code class="envar">pg_catalog.pg_listener</code> a tuple with <code class="command">relname='_${cluster_name}_Restart'</code> exists. slon doesn't
+start because it thinks another process is serving the cluster on this
+node.  What can I do? The tuples can't be dropped from this
+relation.</p>
 <p> The logs claim that </p>
 <div class="blockquote"><blockquote class="blockquote"><p>Another slon daemon is
 serving this node already</p></blockquote></div>
@@ -334,14 +333,14 @@
 <td align="left" valign="top"><b></b></td>
 <td align="left" valign="top">
 <p> The problem is that the system table
-<code class="envar">pg_catalog.pg_listener</code>, used by
-<span class="productname">PostgreSQL</span> to manage event notifications,
-contains some entries that are pointing to backends that no longer
-exist.  The new <a href="slon.html" title="slon"><span class="refentrytitle"><a name="app-slon-title"></a><span class="application">slon</span></span></a> instance connects to the
-database, and is convinced, by the presence of these entries, that an
-old <span class="application">slon</span> is still servicing this <span class="productname">Slony-I</span>
-node.</p>
-<p> The &#8220;<span class="quote">trash</span>&#8221; in that table needs to be thrown away.</p>
+<code class="envar">pg_catalog.pg_listener</code>, used by <span class="productname">PostgreSQL</span> to manage
+event notifications, contains some entries that are pointing to
+backends that no longer exist.  The new <a href="slon.html" title="slon"><span class="refentrytitle"><a name="app-slon-title"></a><span class="application">slon</span></span></a> instance
+connects to the database, and is convinced, by the presence of these
+entries, that an old <span class="application">slon</span> is still
+servicing this <span class="productname">Slony-I</span> node.</p>
+<p> The &#8220;<span class="quote">trash</span>&#8221; in that table needs to be thrown
+away.</p>
 <p>It's handy to keep a slonik script similar to the following to
 run in such cases:
 
@@ -360,11 +359,16 @@
 so that you can restart the node.</p>
 <p>As of version 1.0.5, the startup process of slon looks for this
 condition, and automatically cleans it up.</p>
+<p> As of version 8.1 of <span class="productname">PostgreSQL</span>, the functions that manipulate
+<code class="envar">pg_listener</code> do not support this usage, so for <span class="productname">Slony-I</span>
+versions after 1.1.2 (<span class="emphasis"><em>e.g. - </em></span> 1.1.5), this
+&#8220;<span class="quote">interlock</span>&#8221; behaviour is handled via a new table, and the
+issue should be transparently &#8220;<span class="quote">gone.</span>&#8221; </p>
 </td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id525456"></a><a name="id525457"></a><b>6.</b>
+<a name="id526087"></a><a name="id526088"></a><b>6.</b>
 </td>
 <td align="left" valign="top">
 <p>ps finds passwords on command line</p>
@@ -379,11 +383,10 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id525482"></a><a name="id525483"></a><b>7.</b>
+<a name="id526113"></a><a name="id526114"></a><b>7.</b>
 </td>
 <td align="left" valign="top">
-<p>Slonik fails - cannot load
-<span class="productname">PostgreSQL</span> library -
+<p>Slonik fails - cannot load <span class="productname">PostgreSQL</span> library -
 <code class="command">PGRES_FATAL_ERROR load '$libdir/xxid';</code></p>
 <p> When I run the sample setup script I get an error message similar
 to:
@@ -424,7 +427,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id525668"></a><a name="id525669"></a><b>8.</b>
+<a name="id526299"></a><a name="id526300"></a><b>8.</b>
 </td>
 <td align="left" valign="top">
 <p>Table indexes with FQ namespace names
@@ -444,7 +447,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id525698"></a><a name="id525699"></a><b>9.</b>
+<a name="id526329"></a><a name="id526330"></a><b>9.</b>
 </td>
 <td align="left" valign="top">
 <p> I'm trying to get a slave subscribed, and get the
@@ -501,7 +504,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id525832"></a><a name="id525833"></a><b>10.</b>
+<a name="id526463"></a><a name="id526464"></a><b>10.</b>
 </td>
 <td align="left" valign="top">
 <p>ERROR: duplicate key violates unique constraint "sl_table-pkey"</p>
@@ -523,7 +526,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id525872"></a><a name="id525873"></a><b>11.</b>
+<a name="id526503"></a><a name="id526504"></a><b>11.</b>
 </td>
 <td align="left" valign="top"><p>I need to drop a table from a replication set</p></td>
 </tr>
@@ -568,7 +571,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id525976"></a><a name="id525977"></a><b>12.</b>
+<a name="id526607"></a><a name="id526608"></a><b>12.</b>
 </td>
 <td align="left" valign="top"><p>I need to drop a sequence from a replication set</p></td>
 </tr>
@@ -608,7 +611,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id526092"></a><a name="id526093"></a><b>13.</b>
+<a name="id526723"></a><a name="id526724"></a><b>13.</b>
 </td>
 <td align="left" valign="top">
 <p>Slony-I: cannot add table to currently subscribed set 1</p>
@@ -631,7 +634,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="pglistenerfull"></a><a name="id526126"></a><b>14.</b>
+<a name="pglistenerfull"></a><a name="id526757"></a><b>14.</b>
 </td>
 <td align="left" valign="top">
 <p>Some nodes start consistently falling behind</p>
@@ -669,7 +672,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id526230"></a><a name="id526231"></a><b>15.</b>
+<a name="id526861"></a><a name="id526862"></a><b>15.</b>
 </td>
 <td align="left" valign="top"><p>I started doing a backup using
 <span class="application">pg_dump</span>, and suddenly Slony
@@ -725,7 +728,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id526424"></a><a name="id526425"></a><b>16.</b>
+<a name="id527055"></a><a name="id527056"></a><b>16.</b>
 </td>
 <td align="left" valign="top"><p>The <span class="application">slon</span> spent the weekend out of
 commission [for some reason], and it's taking a long time to get a
@@ -753,7 +756,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id526533"></a><a name="id526534"></a><b>17.</b>
+<a name="id527164"></a><a name="id527165"></a><b>17.</b>
 </td>
 <td align="left" valign="top"><p>I pointed a subscribing node to a different provider
 and it stopped replicating</p></td>
@@ -821,7 +824,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="faq17"></a><a name="id526700"></a><b>18.</b>
+<a name="faq17"></a><a name="id527331"></a><b>18.</b>
 </td>
 <td align="left" valign="top"><p>After dropping a node, <a href="table.sl-log-1.html">sl_log_1</a>
 isn't getting purged out anymore.</p></td>
@@ -886,7 +889,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="dupkey"></a><a name="id526901"></a><b>19.</b>
+<a name="dupkey"></a><a name="id527532"></a><b>19.</b>
 </td>
 <td align="left" valign="top">
 <p>Replication Fails - Unique Constraint Violation</p>
@@ -967,7 +970,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id527210"></a><a name="id527212"></a><b>20.</b>
+<a name="id527787"></a><a name="id527788"></a><b>20.</b>
 </td>
 <td align="left" valign="top">
 <p> If you have a <a href="slonik.html" title="slonik"><span class="refentrytitle"><a name="app-slonik-title"></a><span class="application">slonik</span></span></a> script
@@ -1000,7 +1003,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id527265"></a><a name="id527266"></a><b>21.</b>
+<a name="id527862"></a><a name="id527863"></a><b>21.</b>
 </td>
 <td align="left" valign="top"><p> Is the ordering of tables in a set significant?</p></td>
 </tr>
@@ -1033,7 +1036,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id527343"></a><a name="id527344"></a><b>22.</b>
+<a name="id527940"></a><a name="id527941"></a><b>22.</b>
 </td>
 <td align="left" valign="top"><p> What happens with rules and triggers on
 <span class="productname">Slony-I</span>-replicated tables?</p></td>
@@ -1100,7 +1103,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id527541"></a><a name="id527542"></a><b>23.</b>
+<a name="id528138"></a><a name="id528139"></a><b>23.</b>
 </td>
 <td align="left" valign="top">
 <p> After notification of a subscription on
@@ -1149,7 +1152,7 @@
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id527638"></a><a name="id527640"></a><b>24.</b>
+<a name="id528236"></a><a name="id528237"></a><b>24.</b>
 </td>
 <td align="left" valign="top"><p>I just used <a href="stmtmoveset.html" title="MOVE SET"><span class="refentrytitle">MOVE SET</span></a> to move the
 origin to a new node.  Unfortunately, some subscribers are still
@@ -1174,7 +1177,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="longtxnsareevil"></a><a name="id527692"></a><b>25.</b>
+<a name="longtxnsareevil"></a><a name="id528289"></a><b>25.</b>
 </td>
 <td align="left" valign="top"><p> Replication has been slowing down, I'm seeing
 <code class="command"> FETCH 100 FROM LOG </code> queries running for a long
@@ -1203,11 +1206,10 @@ <h3 class="title">Warning</h3>
 <tr class="answer">
 <td align="left" valign="top"><b></b></td>
 <td align="left" valign="top"><p> You can monitor for this condition inside the database
-only if the <span class="productname"> PostgreSQL </span> <code class="filename">postgresql.conf </code> parameter
-<code class="envar">stats_command_string</code> is set to true.  If that is set,
-then you may submit the query <code class="command"> select * from pg_stat_activity
-where current_query like '%IDLE% in transaction'; </code> which
-will find relevant activity.</p></td>
+only if the <span class="productname">PostgreSQL</span> <code class="filename"> postgresql.conf </code>
+parameter <code class="envar">stats_command_string</code> is set to true.  If that
+is set, then you may submit the query <code class="command"> select * from
+pg_stat_activity where current_query like '%IDLE% in transaction';</code> which will find relevant activity.  </p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"><b></b></td>
@@ -1224,8 +1226,9 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"><b></b></td>
-<td align="left" valign="top"><p> There are plans for <span class="productname"> PostgreSQL</span> to have a timeout parameter, <code class="envar">open_idle_transaction_timeout </code>, which would cause old
-transactions to time out after some period of disuse.  Buggy
+<td align="left" valign="top"><p> There are plans for <span class="productname">PostgreSQL</span> to have a timeout
+parameter, <code class="envar"> open_idle_transaction_timeout </code>, which would
+cause old transactions to time out after some period of disuse.  Buggy
 connection pool logic is a common culprit for this sort of thing.
 There are plans for <span class="productname"> <a href="help.html#pgpool"> pgpool</a> </span> to provide a better alternative, eventually,
 where connections would be shared inside a connection pool implemented
@@ -1237,7 +1240,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="neededexecddl"></a><a name="id527892"></a><b>26.</b>
+<a name="neededexecddl"></a><a name="id528490"></a><b>26.</b>
 </td>
 <td align="left" valign="top">
 <p> Behaviour - all the subscriber nodes start to fall
@@ -1258,7 +1261,7 @@ <h3 class="title">Warning</h3>
 fix the entries in <a href="table.sl-log-1.html">sl_log_1</a> by hand.</p>
 <div class="itemizedlist"><ul type="disc">
 <li><p> You'll need to identify from either the slon logs, or
-the PostgreSQL database logs exactly which statement it is that is
+the <span class="productname">PostgreSQL</span> database logs exactly which statement it is that is
 causing the error.</p></li>
 <li>
 <p> You need to fix the Slony-defined triggers on the
@@ -1310,7 +1313,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id528004"></a><a name="id528005"></a><b>27.</b>
+<a name="id528607"></a><a name="id528609"></a><b>27.</b>
 </td>
 <td align="left" valign="top">
 <p> After notification of a subscription on
@@ -1355,7 +1358,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id528134"></a><a name="id528135"></a><b>28.</b>
+<a name="id528714"></a><a name="id528715"></a><b>28.</b>
 </td>
 <td align="left" valign="top"><p> I can do a <code class="command">pg_dump</code>
 and load the data back in much faster than the <code class="command">SUBSCRIBE
@@ -1364,21 +1367,18 @@ <h3 class="title">Warning</h3>
 <tr class="answer">
 <td align="left" valign="top"><b></b></td>
 <td align="left" valign="top">
-<p> <span class="productname">Slony-I</span> depends on there
-being an already existant index on the primary key, and leaves all
-indexes alone whilst using the <span class="productname">PostgreSQL</span>
-<code class="command">COPY</code> command to load the data.  Further hurting
-performane, the <code class="command">COPY SET</code> event starts by deleting
-the contents of tables, which potentially leaves a lot of dead tuples</p>
+<p> <span class="productname">Slony-I</span> depends on there being an already existant
+index on the primary key, and leaves all indexes alone whilst using
+the <span class="productname">PostgreSQL</span> <code class="command">COPY</code> command to load the data.
+Further hurting performane, the <code class="command">COPY SET</code> event
+starts by deleting the contents of tables, which potentially leaves a
+lot of dead tuples</p>
 <p> When you use <code class="command">pg_dump</code> to dump the contents of
 a database, and then load that, creation of indexes is deferred until
 the very end.  It is <span class="emphasis"><em>much</em></span> more efficient to
 create indexes against the entire table, at the end, than it is to
 build up the index incrementally as each row is added to the
 table.</p>
-<p> Unfortunately, dropping and recreating indexes &#8220;<span class="quote">on the
-fly,</span>&#8221; as it were, has proven thorny.  Doing it automatically
-hasn't been implemented.  </p>
 </td>
 </tr>
 <tr class="answer">
@@ -1391,16 +1391,15 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"><b></b></td>
-<td align="left" valign="top"><p> There is a TODO item for implementation in
-<span class="productname">PostgreSQL</span> that adds a new option,
-something like <code class="option">BULKLOAD</code>, which would defer revising
-indexes until the end, and regenerating indexes in bulk.  That will
-likely not be available until <span class="productname">PostgreSQL</span>
-8.1, but it should substantially improve performance once available.</p></td>
+<td align="left" valign="top"><p> <span class="productname">Slony-I</span> version 1.1.5 and later versions should handle
+this automatically; it &#8220;<span class="quote">thumps</span>&#8221; on the indexes in the
+<span class="productname">PostgreSQL</span> catalog to hide them, in much the same way triggers are
+hidden, and then &#8220;<span class="quote">fixes</span>&#8221; the index pointers and reindexes
+the table. </p></td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id528264"></a><a name="id528266"></a><b>29.</b>
+<a name="id528838"></a><a name="id528839"></a><b>29.</b>
 </td>
 <td align="left" valign="top"><p> I had a network &#8220;<span class="quote">glitch</span>&#8221; that led to my
 using <a href="stmtfailover.html" title="FAILOVER"><span class="refentrytitle">FAILOVER</span></a> to fail over to an alternate node.
@@ -1431,7 +1430,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="morethansuper"></a><a name="id528355"></a><b>30.</b>
+<a name="morethansuper"></a><a name="id528929"></a><b>30.</b>
 </td>
 <td align="left" valign="top">
 <p> I created a &#8220;<span class="quote">superuser</span>&#8221; account,
@@ -1470,7 +1469,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="missingoids"></a><a name="id528447"></a><b>31.</b>
+<a name="missingoids"></a><a name="id529021"></a><b>31.</b>
 </td>
 <td align="left" valign="top">
 <p> We got bitten by
@@ -1526,7 +1525,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id528531"></a><a name="id528532"></a><b>32.</b>
+<a name="id529104"></a><a name="id529105"></a><b>32.</b>
 </td>
 <td align="left" valign="top">
 <p> Node #1 was dropped via <a href="stmtdropnode.html" title="DROP NODE"><span class="refentrytitle">DROP NODE</span></a>, and the <a href="slon.html" title="slon"><span class="refentrytitle"><a name="app-slon-title"></a><span class="application">slon</span></span></a> one of the
@@ -1588,7 +1587,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id528677"></a><a name="id528678"></a><b>33.</b>
+<a name="id529251"></a><a name="id529252"></a><b>33.</b>
 </td>
 <td align="left" valign="top"><p> I am using <span class="productname"> Frotznik Freenix
 4.5</span>, with its <span class="acronym">FFPM</span> (Frotznik Freenix
@@ -1656,7 +1655,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="sequenceset"></a><a name="id529028"></a><b>34.</b>
+<a name="sequenceset"></a><a name="id529601"></a><b>34.</b>
 </td>
 <td align="left" valign="top"><p> <a href="http://gborg.postgresql.org/project/slony1/bugs/bugupdate.php?1226" target="_top">Bug #1226 </a> indicates an error condition that can come up if
 you have a replication set that consists solely of sequences. </p></td>
@@ -1683,7 +1682,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id529095"></a><a name="id529096"></a><b>35.</b>
+<a name="id529669"></a><a name="id529670"></a><b>35.</b>
 </td>
 <td align="left" valign="top">
 <p> I tried the following query which did not work:</p>
@@ -1761,7 +1760,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="v72upgrade"></a><a name="id529231"></a><b>36.</b>
+<a name="v72upgrade"></a><a name="id529840"></a><b>36.</b>
 </td>
 <td align="left" valign="top"><p> I have a <span class="productname">PostgreSQL</span> 7.2-based system that I
 <span class="emphasis"><em>really, really</em></span> want to use <span class="productname">Slony-I</span> to help me
@@ -1793,7 +1792,7 @@ <h3 class="title">Warning</h3>
 <p> Of course, now that you have done all of the above, it's not compatible
 with standard Slony now. So you either need to implement 7.2 in a less
 hackish way, or you can also hack up slony to work without schemas on
-newer versions of PostgreSQL so they can talk to each other.</p>
+newer versions of <span class="productname">PostgreSQL</span> so they can talk to each other.</p>
 <p> Almost immediately after getting the DB upgraded from 7.2 to 7.4, we
 deinstalled the hacked up Slony (by hand for the most part), and started
 a migration from 7.4 to 7.4 on a different machine using the regular
@@ -1821,7 +1820,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id529370"></a><a name="id529371"></a><b>37.</b>
+<a name="id529982"></a><a name="id529983"></a><b>37.</b>
 </td>
 <td align="left" valign="top"><p> I am finding some multibyte columns (Unicode, Big5)
 are being truncated.  Why?  </p></td>
@@ -1838,7 +1837,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id529406"></a><a name="id529407"></a><b>38.</b>
+<a name="id530017"></a><a name="id530018"></a><b>38.</b>
 </td>
 <td align="left" valign="top"><p> I need to rename a column that is in the
 primary key for one of my replicated tables.  That seems pretty
@@ -1879,7 +1878,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id529512"></a><a name="id529513"></a><b>39.</b>
+<a name="id530124"></a><a name="id530125"></a><b>39.</b>
 </td>
 <td align="left" valign="top"><p> Replication has fallen behind, and it appears that the
 queries to draw data from <a href="table.sl-log-1.html">sl_log_1</a>/<a href="table.sl-log-2.html">sl_log_2</a> are taking a long time to pull just a few
@@ -1896,7 +1895,7 @@ <h3 class="title">Warning</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id529573"></a><a name="id529574"></a><b>40.</b>
+<a name="id530184"></a><a name="id530185"></a><b>40.</b>
 </td>
 <td align="left" valign="top">
 <p>The <a href="slon.html" title="slon"><span class="refentrytitle"><a name="app-slon-title"></a><span class="application">slon</span></span></a> processes servicing my
diff --git a/docs/en_US/slony/function.add-missing-table-field-text-text-text-text.html b/docs/en_US/slony/function.add-missing-table-field-text-text-text-text.html
index 29bb339c38..3a4da38627 100644
--- a/docs/en_US/slony/function.add-missing-table-field-text-text-text-text.html
+++ b/docs/en_US/slony/function.add-missing-table-field-text-text-text-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-trigger.html" title="1.16.          Table:
          
diff --git a/docs/en_US/slony/function.altertableforreplication-integer.html b/docs/en_US/slony/function.altertableforreplication-integer.html
index b3837ae25f..64f49fb7f9 100644
--- a/docs/en_US/slony/function.altertableforreplication-integer.html
+++ b/docs/en_US/slony/function.altertableforreplication-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.add-missing-table-field-text-text-text-text.html" title="1.17.        add_missing_table_field( text, text, text, text )
       ">
diff --git a/docs/en_US/slony/function.altertablerestore-integer.html b/docs/en_US/slony/function.altertablerestore-integer.html
index 1b4351cdd3..1acc946235 100644
--- a/docs/en_US/slony/function.altertablerestore-integer.html
+++ b/docs/en_US/slony/function.altertablerestore-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.altertableforreplication-integer.html" title="1.18.        altertableforreplication( integer )
       ">
diff --git a/docs/en_US/slony/function.cleanupevent.html b/docs/en_US/slony/function.cleanupevent.html
index 8403a5280d..5d77e6de53 100644
--- a/docs/en_US/slony/function.cleanupevent.html
+++ b/docs/en_US/slony/function.cleanupevent.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.altertablerestore-integer.html" title="1.19.        altertablerestore( integer )
       ">
diff --git a/docs/en_US/slony/function.cleanuplistener.html b/docs/en_US/slony/function.cleanuplistener.html
index fe36a5b40d..624ebd1deb 100644
--- a/docs/en_US/slony/function.cleanuplistener.html
+++ b/docs/en_US/slony/function.cleanuplistener.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.cleanupevent.html" title="1.20.        cleanupevent(  )
       ">
diff --git a/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text-text.html b/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text-text.html
index f6b5602a91..4ad31ffb33 100644
--- a/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text-text.html
+++ b/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.createevent-name-text-text-text-text-text-text-text-text.html" title="1.29.        createevent( name, text, text, text, text, text, text, text, text )
       ">
diff --git a/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text.html b/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text.html
index d48d341f3f..aed95d89c1 100644
--- a/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text.html
+++ b/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.createevent-name-text-text-text-text-text-text-text.html" title="1.28.        createevent( name, text, text, text, text, text, text, text )
       ">
diff --git a/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text.html b/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text.html
index 06fac9dcb7..038ad8bb80 100644
--- a/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text.html
+++ b/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.createevent-name-text-text-text-text-text-text.html" title="1.27.        createevent( name, text, text, text, text, text, text )
       ">
diff --git a/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text.html b/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text.html
index 5d255ddea1..20035e8967 100644
--- a/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text.html
+++ b/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.createevent-name-text-text-text-text-text.html" title="1.26.        createevent( name, text, text, text, text, text )
       ">
diff --git a/docs/en_US/slony/function.createevent-name-text-text-text-text-text.html b/docs/en_US/slony/function.createevent-name-text-text-text-text-text.html
index 0785fce1b5..c18f55b445 100644
--- a/docs/en_US/slony/function.createevent-name-text-text-text-text-text.html
+++ b/docs/en_US/slony/function.createevent-name-text-text-text-text-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.createevent-name-text-text-text-text.html" title="1.25.        createevent( name, text, text, text, text )
       ">
diff --git a/docs/en_US/slony/function.createevent-name-text-text-text-text.html b/docs/en_US/slony/function.createevent-name-text-text-text-text.html
index 2e3262ca9c..57b866eb94 100644
--- a/docs/en_US/slony/function.createevent-name-text-text-text-text.html
+++ b/docs/en_US/slony/function.createevent-name-text-text-text-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.createevent-name-text-text-text.html" title="1.24.        createevent( name, text, text, text )
       ">
diff --git a/docs/en_US/slony/function.createevent-name-text-text-text.html b/docs/en_US/slony/function.createevent-name-text-text-text.html
index ffd3ca2b3a..c08f3a3a8f 100644
--- a/docs/en_US/slony/function.createevent-name-text-text-text.html
+++ b/docs/en_US/slony/function.createevent-name-text-text-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.createevent-name-text-text.html" title="1.23.        createevent( name, text, text )
       ">
diff --git a/docs/en_US/slony/function.createevent-name-text-text.html b/docs/en_US/slony/function.createevent-name-text-text.html
index 7e7554aca3..37cbf629b8 100644
--- a/docs/en_US/slony/function.createevent-name-text-text.html
+++ b/docs/en_US/slony/function.createevent-name-text-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.createevent-name-text.html" title="1.22.        createevent( name, text )
       ">
diff --git a/docs/en_US/slony/function.createevent-name-text.html b/docs/en_US/slony/function.createevent-name-text.html
index 5a5eb61428..59429c48e2 100644
--- a/docs/en_US/slony/function.createevent-name-text.html
+++ b/docs/en_US/slony/function.createevent-name-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.cleanuplistener.html" title="1.21.        cleanuplistener(  )
       ">
diff --git a/docs/en_US/slony/function.ddlscript-int-integer-text-integer.html b/docs/en_US/slony/function.ddlscript-int-integer-text-integer.html
index 71e15e8713..6b39b174ba 100644
--- a/docs/en_US/slony/function.ddlscript-int-integer-text-integer.html
+++ b/docs/en_US/slony/function.ddlscript-int-integer-text-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.ddlscript-integer-text-integer.html" title="1.31.        ddlscript( integer, text, integer )
       ">
diff --git a/docs/en_US/slony/function.ddlscript-integer-text-integer.html b/docs/en_US/slony/function.ddlscript-integer-text-integer.html
index 698894144b..9cb5cfbeba 100644
--- a/docs/en_US/slony/function.ddlscript-integer-text-integer.html
+++ b/docs/en_US/slony/function.ddlscript-integer-text-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.createevent-name-text-text-text-text-text-text-text-text-text.html" title="1.30.        createevent( name, text, text, text, text, text, text, text, text, text )
       ">
diff --git a/docs/en_US/slony/function.denyaccess.html b/docs/en_US/slony/function.denyaccess.html
index 76135247b9..123b463516 100644
--- a/docs/en_US/slony/function.denyaccess.html
+++ b/docs/en_US/slony/function.denyaccess.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.ddlscript-int-integer-text-integer.html" title="1.32.        ddlscript_int( integer, text, integer )
       ">
diff --git a/docs/en_US/slony/function.determineattkindserial-text.html b/docs/en_US/slony/function.determineattkindserial-text.html
index 9ce354a992..a5691f8570 100644
--- a/docs/en_US/slony/function.determineattkindserial-text.html
+++ b/docs/en_US/slony/function.determineattkindserial-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.denyaccess.html" title="1.33.        denyaccess(  )
       ">
diff --git a/docs/en_US/slony/function.determineattkindunique-text-name.html b/docs/en_US/slony/function.determineattkindunique-text-name.html
index f1b10ee685..06c3f9f657 100644
--- a/docs/en_US/slony/function.determineattkindunique-text-name.html
+++ b/docs/en_US/slony/function.determineattkindunique-text-name.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.determineattkindserial-text.html" title="1.34.        determineattkindserial( text )
       ">
diff --git a/docs/en_US/slony/function.determineidxnameserial-text.html b/docs/en_US/slony/function.determineidxnameserial-text.html
index ef2e52d51f..b1d093e692 100644
--- a/docs/en_US/slony/function.determineidxnameserial-text.html
+++ b/docs/en_US/slony/function.determineidxnameserial-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.determineattkindunique-text-name.html" title="1.35.        determineattkindunique( text, name )
       ">
diff --git a/docs/en_US/slony/function.determineidxnameunique-text-name.html b/docs/en_US/slony/function.determineidxnameunique-text-name.html
index f10827dd61..07b5a623d7 100644
--- a/docs/en_US/slony/function.determineidxnameunique-text-name.html
+++ b/docs/en_US/slony/function.determineidxnameunique-text-name.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.determineidxnameserial-text.html" title="1.36.        determineidxnameserial( text )
       ">
diff --git a/docs/en_US/slony/function.disablenode-int-integer.html b/docs/en_US/slony/function.disablenode-int-integer.html
index f031b65f28..41008693b4 100644
--- a/docs/en_US/slony/function.disablenode-int-integer.html
+++ b/docs/en_US/slony/function.disablenode-int-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.disablenode-integer.html" title="1.38.        disablenode( integer )
       ">
diff --git a/docs/en_US/slony/function.disablenode-integer.html b/docs/en_US/slony/function.disablenode-integer.html
index 99d4a4df0b..61e5eab9b2 100644
--- a/docs/en_US/slony/function.disablenode-integer.html
+++ b/docs/en_US/slony/function.disablenode-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.determineidxnameunique-text-name.html" title="1.37.        determineidxnameunique( text, name )
       ">
diff --git a/docs/en_US/slony/function.droplisten-int-integer-integer-integer.html b/docs/en_US/slony/function.droplisten-int-integer-integer-integer.html
index 180624440a..23ed36435f 100644
--- a/docs/en_US/slony/function.droplisten-int-integer-integer-integer.html
+++ b/docs/en_US/slony/function.droplisten-int-integer-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.droplisten-integer-integer-integer.html" title="1.40.        droplisten( integer, integer, integer )
       ">
diff --git a/docs/en_US/slony/function.droplisten-integer-integer-integer.html b/docs/en_US/slony/function.droplisten-integer-integer-integer.html
index 61c102c34e..af1d8e7bbd 100644
--- a/docs/en_US/slony/function.droplisten-integer-integer-integer.html
+++ b/docs/en_US/slony/function.droplisten-integer-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.disablenode-int-integer.html" title="1.39.        disablenode_int( integer )
       ">
diff --git a/docs/en_US/slony/function.dropnode-int-integer.html b/docs/en_US/slony/function.dropnode-int-integer.html
index 13afd98d74..a56572cc37 100644
--- a/docs/en_US/slony/function.dropnode-int-integer.html
+++ b/docs/en_US/slony/function.dropnode-int-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.dropnode-integer.html" title="1.42.        dropnode( integer )
       ">
diff --git a/docs/en_US/slony/function.dropnode-integer.html b/docs/en_US/slony/function.dropnode-integer.html
index 9daeb907db..577579d27d 100644
--- a/docs/en_US/slony/function.dropnode-integer.html
+++ b/docs/en_US/slony/function.dropnode-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.droplisten-int-integer-integer-integer.html" title="1.41.        droplisten_int( integer, integer, integer )
       ">
diff --git a/docs/en_US/slony/function.droppath-int-integer-integer.html b/docs/en_US/slony/function.droppath-int-integer-integer.html
index 7f582cec40..b6e240eb7a 100644
--- a/docs/en_US/slony/function.droppath-int-integer-integer.html
+++ b/docs/en_US/slony/function.droppath-int-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.droppath-integer-integer.html" title="1.44.        droppath( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.droppath-integer-integer.html b/docs/en_US/slony/function.droppath-integer-integer.html
index 594bfd37a0..847c7d06b8 100644
--- a/docs/en_US/slony/function.droppath-integer-integer.html
+++ b/docs/en_US/slony/function.droppath-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.dropnode-int-integer.html" title="1.43.        dropnode_int( integer )
       ">
diff --git a/docs/en_US/slony/function.dropset-int-integer.html b/docs/en_US/slony/function.dropset-int-integer.html
index 90b6a17072..ebbe885f47 100644
--- a/docs/en_US/slony/function.dropset-int-integer.html
+++ b/docs/en_US/slony/function.dropset-int-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.dropset-integer.html" title="1.46.        dropset( integer )
       ">
diff --git a/docs/en_US/slony/function.dropset-integer.html b/docs/en_US/slony/function.dropset-integer.html
index f401268db1..a56e0687a6 100644
--- a/docs/en_US/slony/function.dropset-integer.html
+++ b/docs/en_US/slony/function.dropset-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.droppath-int-integer-integer.html" title="1.45.        droppath_int( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.droptrigger-int-integer-name.html b/docs/en_US/slony/function.droptrigger-int-integer-name.html
index 2b2943af9a..7b01a4b7e9 100644
--- a/docs/en_US/slony/function.droptrigger-int-integer-name.html
+++ b/docs/en_US/slony/function.droptrigger-int-integer-name.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.droptrigger-integer-name.html" title="1.48.        droptrigger( integer, name )
       ">
diff --git a/docs/en_US/slony/function.droptrigger-integer-name.html b/docs/en_US/slony/function.droptrigger-integer-name.html
index 45622cff65..f186de26b8 100644
--- a/docs/en_US/slony/function.droptrigger-integer-name.html
+++ b/docs/en_US/slony/function.droptrigger-integer-name.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.dropset-int-integer.html" title="1.47.        dropset_int( integer )
       ">
diff --git a/docs/en_US/slony/function.enablenode-int-integer.html b/docs/en_US/slony/function.enablenode-int-integer.html
index 87ec832acf..0d0bcccaa9 100644
--- a/docs/en_US/slony/function.enablenode-int-integer.html
+++ b/docs/en_US/slony/function.enablenode-int-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.enablenode-integer.html" title="1.50.        enablenode( integer )
       ">
diff --git a/docs/en_US/slony/function.enablenode-integer.html b/docs/en_US/slony/function.enablenode-integer.html
index efee9f7d35..9238d6c31f 100644
--- a/docs/en_US/slony/function.enablenode-integer.html
+++ b/docs/en_US/slony/function.enablenode-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.droptrigger-int-integer-name.html" title="1.49.        droptrigger_int( integer, name )
       ">
diff --git a/docs/en_US/slony/function.enablesubscription-int-integer-integer-integer.html b/docs/en_US/slony/function.enablesubscription-int-integer-integer-integer.html
index 2b84353ae2..ceb260845d 100644
--- a/docs/en_US/slony/function.enablesubscription-int-integer-integer-integer.html
+++ b/docs/en_US/slony/function.enablesubscription-int-integer-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.enablesubscription-integer-integer-integer.html" title="1.52.        enablesubscription( integer, integer, integer )
       ">
diff --git a/docs/en_US/slony/function.enablesubscription-integer-integer-integer.html b/docs/en_US/slony/function.enablesubscription-integer-integer-integer.html
index 7855caaea4..fc8d4df4b5 100644
--- a/docs/en_US/slony/function.enablesubscription-integer-integer-integer.html
+++ b/docs/en_US/slony/function.enablesubscription-integer-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.enablenode-int-integer.html" title="1.51.        enablenode_int( integer )
       ">
diff --git a/docs/en_US/slony/function.failednode-integer-integer.html b/docs/en_US/slony/function.failednode-integer-integer.html
index 27170a65ef..5a59426bc9 100644
--- a/docs/en_US/slony/function.failednode-integer-integer.html
+++ b/docs/en_US/slony/function.failednode-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.enablesubscription-int-integer-integer-integer.html" title="1.53.        enablesubscription_int( integer, integer, integer )
       ">
diff --git a/docs/en_US/slony/function.failednode2-integer-integer-integer-bigint-bigint.html b/docs/en_US/slony/function.failednode2-integer-integer-integer-bigint-bigint.html
index 347aaf333e..e2a85498c5 100644
--- a/docs/en_US/slony/function.failednode2-integer-integer-integer-bigint-bigint.html
+++ b/docs/en_US/slony/function.failednode2-integer-integer-integer-bigint-bigint.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.failednode-integer-integer.html" title="1.54.        failednode( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.failoverset-int-integer-integer-integer.html b/docs/en_US/slony/function.failoverset-int-integer-integer-integer.html
index a6b8753860..d056a9fb0b 100644
--- a/docs/en_US/slony/function.failoverset-int-integer-integer-integer.html
+++ b/docs/en_US/slony/function.failoverset-int-integer-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.failednode2-integer-integer-integer-bigint-bigint.html" title="1.55.        failednode2( integer, integer, integer, bigint, bigint )
       ">
diff --git a/docs/en_US/slony/function.forwardconfirm-integer-integer-bigint-timestamp-without-time-zone.html b/docs/en_US/slony/function.forwardconfirm-integer-integer-bigint-timestamp-without-time-zone.html
index 53d175e2e5..c82461c558 100644
--- a/docs/en_US/slony/function.forwardconfirm-integer-integer-bigint-timestamp-without-time-zone.html
+++ b/docs/en_US/slony/function.forwardconfirm-integer-integer-bigint-timestamp-without-time-zone.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.failoverset-int-integer-integer-integer.html" title="1.56.        failoverset_int( integer, integer, integer )
       ">
diff --git a/docs/en_US/slony/function.generate-sync-event-interval.html b/docs/en_US/slony/function.generate-sync-event-interval.html
index 1d2bfcb6c3..26c549bc35 100644
--- a/docs/en_US/slony/function.generate-sync-event-interval.html
+++ b/docs/en_US/slony/function.generate-sync-event-interval.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.forwardconfirm-integer-integer-bigint-timestamp-without-time-zone.html" title="1.57.        forwardconfirm( integer, integer, bigint, timestamp without time zone )
       ">
diff --git a/docs/en_US/slony/function.getlocalnodeid-name.html b/docs/en_US/slony/function.getlocalnodeid-name.html
index 4f40c479ed..26b717e316 100644
--- a/docs/en_US/slony/function.getlocalnodeid-name.html
+++ b/docs/en_US/slony/function.getlocalnodeid-name.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.generate-sync-event-interval.html" title="1.58.        generate_sync_event( interval )
       ">
diff --git a/docs/en_US/slony/function.getmoduleversion.html b/docs/en_US/slony/function.getmoduleversion.html
index 7c72fc2744..d578d15a5e 100644
--- a/docs/en_US/slony/function.getmoduleversion.html
+++ b/docs/en_US/slony/function.getmoduleversion.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.getlocalnodeid-name.html" title="1.59.        getlocalnodeid( name )
       ">
diff --git a/docs/en_US/slony/function.getsessionrole-name.html b/docs/en_US/slony/function.getsessionrole-name.html
index f6c0883ea2..8afdbf38c4 100644
--- a/docs/en_US/slony/function.getsessionrole-name.html
+++ b/docs/en_US/slony/function.getsessionrole-name.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.getmoduleversion.html" title="1.60.        getmoduleversion(  )
       ">
diff --git a/docs/en_US/slony/function.initializelocalnode-integer-text.html b/docs/en_US/slony/function.initializelocalnode-integer-text.html
index 2168e8b617..2e5b53f53b 100644
--- a/docs/en_US/slony/function.initializelocalnode-integer-text.html
+++ b/docs/en_US/slony/function.initializelocalnode-integer-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.getsessionrole-name.html" title="1.61.        getsessionrole( name )
       ">
diff --git a/docs/en_US/slony/function.lockedset.html b/docs/en_US/slony/function.lockedset.html
index ce5b94997e..d643a975e3 100644
--- a/docs/en_US/slony/function.lockedset.html
+++ b/docs/en_US/slony/function.lockedset.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.initializelocalnode-integer-text.html" title="1.62.        initializelocalnode( integer, text )
       ">
diff --git a/docs/en_US/slony/function.lockset-integer.html b/docs/en_US/slony/function.lockset-integer.html
index 460a8bdce2..ce81e1a75f 100644
--- a/docs/en_US/slony/function.lockset-integer.html
+++ b/docs/en_US/slony/function.lockset-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.lockedset.html" title="1.63.        lockedset(  )
       ">
diff --git a/docs/en_US/slony/function.logtrigger.html b/docs/en_US/slony/function.logtrigger.html
index b01a876dc3..bcfaad2a66 100644
--- a/docs/en_US/slony/function.logtrigger.html
+++ b/docs/en_US/slony/function.logtrigger.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.lockset-integer.html" title="1.64.        lockset( integer )
       ">
diff --git a/docs/en_US/slony/function.mergeset-int-integer-integer.html b/docs/en_US/slony/function.mergeset-int-integer-integer.html
index 07dc9a212e..70eec68e82 100644
--- a/docs/en_US/slony/function.mergeset-int-integer-integer.html
+++ b/docs/en_US/slony/function.mergeset-int-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.mergeset-integer-integer.html" title="1.66.        mergeset( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.mergeset-integer-integer.html b/docs/en_US/slony/function.mergeset-integer-integer.html
index eb5b4f4663..f1294c3968 100644
--- a/docs/en_US/slony/function.mergeset-integer-integer.html
+++ b/docs/en_US/slony/function.mergeset-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.logtrigger.html" title="1.65.        logtrigger(  )
       ">
diff --git a/docs/en_US/slony/function.moveset-int-integer-integer-integer.html b/docs/en_US/slony/function.moveset-int-integer-integer-integer.html
index a608148563..e9f6229169 100644
--- a/docs/en_US/slony/function.moveset-int-integer-integer-integer.html
+++ b/docs/en_US/slony/function.moveset-int-integer-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.moveset-integer-integer.html" title="1.68.        moveset( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.moveset-integer-integer.html b/docs/en_US/slony/function.moveset-integer-integer.html
index b1c903bd9f..7f25fbb6c6 100644
--- a/docs/en_US/slony/function.moveset-integer-integer.html
+++ b/docs/en_US/slony/function.moveset-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.mergeset-int-integer-integer.html" title="1.67.        mergeset_int( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.rebuildlistenentries.html b/docs/en_US/slony/function.rebuildlistenentries.html
index f31bb1163f..db0bcd891e 100644
--- a/docs/en_US/slony/function.rebuildlistenentries.html
+++ b/docs/en_US/slony/function.rebuildlistenentries.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.moveset-int-integer-integer-integer.html" title="1.69.        moveset_int( integer, integer, integer )
       ">
diff --git a/docs/en_US/slony/function.rebuildlistenentriesone-integer-integer.html b/docs/en_US/slony/function.rebuildlistenentriesone-integer-integer.html
index 6d27df032c..b6a72058a3 100644
--- a/docs/en_US/slony/function.rebuildlistenentriesone-integer-integer.html
+++ b/docs/en_US/slony/function.rebuildlistenentriesone-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.rebuildlistenentries.html" title="1.70.        rebuildlistenentries(  )
       ">
diff --git a/docs/en_US/slony/function.sequencelastvalue-text.html b/docs/en_US/slony/function.sequencelastvalue-text.html
index c091c3a70c..0afc16ede0 100644
--- a/docs/en_US/slony/function.sequencelastvalue-text.html
+++ b/docs/en_US/slony/function.sequencelastvalue-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.rebuildlistenentriesone-integer-integer.html" title="1.71.        rebuildlistenentriesone( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.sequencesetvalue-integer-integer-bigint-bigint.html b/docs/en_US/slony/function.sequencesetvalue-integer-integer-bigint-bigint.html
index 97fb9234af..26ee1aec47 100644
--- a/docs/en_US/slony/function.sequencesetvalue-integer-integer-bigint-bigint.html
+++ b/docs/en_US/slony/function.sequencesetvalue-integer-integer-bigint-bigint.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.sequencelastvalue-text.html" title="1.72.        sequencelastvalue( text )
       ">
diff --git a/docs/en_US/slony/function.setaddsequence-int-integer-integer-text-text.html b/docs/en_US/slony/function.setaddsequence-int-integer-integer-text-text.html
index 87ae4da737..35caa1a1ff 100644
--- a/docs/en_US/slony/function.setaddsequence-int-integer-integer-text-text.html
+++ b/docs/en_US/slony/function.setaddsequence-int-integer-integer-text-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setaddsequence-integer-integer-text-text.html" title="1.74.        setaddsequence( integer, integer, text, text )
       ">
diff --git a/docs/en_US/slony/function.setaddsequence-integer-integer-text-text.html b/docs/en_US/slony/function.setaddsequence-integer-integer-text-text.html
index 7f054dc174..579ad1bfd8 100644
--- a/docs/en_US/slony/function.setaddsequence-integer-integer-text-text.html
+++ b/docs/en_US/slony/function.setaddsequence-integer-integer-text-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.sequencesetvalue-integer-integer-bigint-bigint.html" title="1.73.        sequencesetvalue( integer, integer, bigint, bigint )
       ">
diff --git a/docs/en_US/slony/function.setaddtable-int-integer-integer-text-name-text.html b/docs/en_US/slony/function.setaddtable-int-integer-integer-text-name-text.html
index c6baa5a183..4f966b5bce 100644
--- a/docs/en_US/slony/function.setaddtable-int-integer-integer-text-name-text.html
+++ b/docs/en_US/slony/function.setaddtable-int-integer-integer-text-name-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setaddtable-integer-integer-text-name-text.html" title="1.76.        setaddtable( integer, integer, text, name, text )
       ">
diff --git a/docs/en_US/slony/function.setaddtable-integer-integer-text-name-text.html b/docs/en_US/slony/function.setaddtable-integer-integer-text-name-text.html
index 539db8f547..4955821d93 100644
--- a/docs/en_US/slony/function.setaddtable-integer-integer-text-name-text.html
+++ b/docs/en_US/slony/function.setaddtable-integer-integer-text-name-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setaddsequence-int-integer-integer-text-text.html" title="1.75.        setaddsequence_int( integer, integer, text, text )
       ">
diff --git a/docs/en_US/slony/function.setdropsequence-int-integer.html b/docs/en_US/slony/function.setdropsequence-int-integer.html
index 720406ed9e..4a7b6f3abf 100644
--- a/docs/en_US/slony/function.setdropsequence-int-integer.html
+++ b/docs/en_US/slony/function.setdropsequence-int-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setdropsequence-integer.html" title="1.78.        setdropsequence( integer )
       ">
diff --git a/docs/en_US/slony/function.setdropsequence-integer.html b/docs/en_US/slony/function.setdropsequence-integer.html
index 127f37d693..a00157250a 100644
--- a/docs/en_US/slony/function.setdropsequence-integer.html
+++ b/docs/en_US/slony/function.setdropsequence-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setaddtable-int-integer-integer-text-name-text.html" title="1.77.        setaddtable_int( integer, integer, text, name, text )
       ">
diff --git a/docs/en_US/slony/function.setdroptable-int-integer.html b/docs/en_US/slony/function.setdroptable-int-integer.html
index fbb0d501d6..64741bc95d 100644
--- a/docs/en_US/slony/function.setdroptable-int-integer.html
+++ b/docs/en_US/slony/function.setdroptable-int-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setdroptable-integer.html" title="1.80.        setdroptable( integer )
       ">
diff --git a/docs/en_US/slony/function.setdroptable-integer.html b/docs/en_US/slony/function.setdroptable-integer.html
index 27d2ee1d1f..fa1d024c50 100644
--- a/docs/en_US/slony/function.setdroptable-integer.html
+++ b/docs/en_US/slony/function.setdroptable-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setdropsequence-int-integer.html" title="1.79.        setdropsequence_int( integer )
       ">
diff --git a/docs/en_US/slony/function.setmovesequence-int-integer-integer.html b/docs/en_US/slony/function.setmovesequence-int-integer-integer.html
index 2fc83ae9f2..d20def6868 100644
--- a/docs/en_US/slony/function.setmovesequence-int-integer-integer.html
+++ b/docs/en_US/slony/function.setmovesequence-int-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setmovesequence-integer-integer.html" title="1.82.        setmovesequence( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.setmovesequence-integer-integer.html b/docs/en_US/slony/function.setmovesequence-integer-integer.html
index 79cbb878a2..68f0bb9243 100644
--- a/docs/en_US/slony/function.setmovesequence-integer-integer.html
+++ b/docs/en_US/slony/function.setmovesequence-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setdroptable-int-integer.html" title="1.81.        setdroptable_int( integer )
       ">
diff --git a/docs/en_US/slony/function.setmovetable-int-integer-integer.html b/docs/en_US/slony/function.setmovetable-int-integer-integer.html
index 6b6b2ae9fe..9da874672f 100644
--- a/docs/en_US/slony/function.setmovetable-int-integer-integer.html
+++ b/docs/en_US/slony/function.setmovetable-int-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setmovetable-integer-integer.html" title="1.84.        setmovetable( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.setmovetable-integer-integer.html b/docs/en_US/slony/function.setmovetable-integer-integer.html
index 95d0fe1a5c..ae0171c13c 100644
--- a/docs/en_US/slony/function.setmovetable-integer-integer.html
+++ b/docs/en_US/slony/function.setmovetable-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setmovesequence-int-integer-integer.html" title="1.83.        setmovesequence_int( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.setsessionrole-name-text.html b/docs/en_US/slony/function.setsessionrole-name-text.html
index 1a8e9f6497..7b6e2566bd 100644
--- a/docs/en_US/slony/function.setsessionrole-name-text.html
+++ b/docs/en_US/slony/function.setsessionrole-name-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setmovetable-int-integer-integer.html" title="1.85.        setmovetable_int( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.slon-quote-brute-text.html b/docs/en_US/slony/function.slon-quote-brute-text.html
index 8694e6417d..61d940b3bb 100644
--- a/docs/en_US/slony/function.slon-quote-brute-text.html
+++ b/docs/en_US/slony/function.slon-quote-brute-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.setsessionrole-name-text.html" title="1.86.        setsessionrole( name, text )
       ">
diff --git a/docs/en_US/slony/function.slon-quote-input-text.html b/docs/en_US/slony/function.slon-quote-input-text.html
index aceb968933..f3bfa8630b 100644
--- a/docs/en_US/slony/function.slon-quote-input-text.html
+++ b/docs/en_US/slony/function.slon-quote-input-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.slon-quote-brute-text.html" title="1.87.        slon_quote_brute( text )
       ">
diff --git a/docs/en_US/slony/function.slonyversion.html b/docs/en_US/slony/function.slonyversion.html
index 295867ac32..4efdff4455 100644
--- a/docs/en_US/slony/function.slonyversion.html
+++ b/docs/en_US/slony/function.slonyversion.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.slon-quote-input-text.html" title="1.88.        slon_quote_input( text )
       ">
diff --git a/docs/en_US/slony/function.slonyversionmajor.html b/docs/en_US/slony/function.slonyversionmajor.html
index 7e4bc37e64..d03b70663c 100644
--- a/docs/en_US/slony/function.slonyversionmajor.html
+++ b/docs/en_US/slony/function.slonyversionmajor.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.slonyversion.html" title="1.89.        slonyversion(  )
       ">
diff --git a/docs/en_US/slony/function.slonyversionminor.html b/docs/en_US/slony/function.slonyversionminor.html
index 4192fb8ef9..1266bc8934 100644
--- a/docs/en_US/slony/function.slonyversionminor.html
+++ b/docs/en_US/slony/function.slonyversionminor.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.slonyversionmajor.html" title="1.90.        slonyversionmajor(  )
       ">
diff --git a/docs/en_US/slony/function.slonyversionpatchlevel.html b/docs/en_US/slony/function.slonyversionpatchlevel.html
index 5653fdd010..3cdfd014c4 100644
--- a/docs/en_US/slony/function.slonyversionpatchlevel.html
+++ b/docs/en_US/slony/function.slonyversionpatchlevel.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.slonyversionminor.html" title="1.91.        slonyversionminor(  )
       ">
diff --git a/docs/en_US/slony/function.storelisten-int-integer-integer-integer.html b/docs/en_US/slony/function.storelisten-int-integer-integer-integer.html
index c9861afb31..5b89fa9863 100644
--- a/docs/en_US/slony/function.storelisten-int-integer-integer-integer.html
+++ b/docs/en_US/slony/function.storelisten-int-integer-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.storelisten-integer-integer-integer.html" title="1.93.        storelisten( integer, integer, integer )
       ">
diff --git a/docs/en_US/slony/function.storelisten-integer-integer-integer.html b/docs/en_US/slony/function.storelisten-integer-integer-integer.html
index f37bd688eb..4b4743a700 100644
--- a/docs/en_US/slony/function.storelisten-integer-integer-integer.html
+++ b/docs/en_US/slony/function.storelisten-integer-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.slonyversionpatchlevel.html" title="1.92.        slonyversionpatchlevel(  )
       ">
diff --git a/docs/en_US/slony/function.storenode-int-integer-text-boolean.html b/docs/en_US/slony/function.storenode-int-integer-text-boolean.html
index ca4f6d5e72..746a617e15 100644
--- a/docs/en_US/slony/function.storenode-int-integer-text-boolean.html
+++ b/docs/en_US/slony/function.storenode-int-integer-text-boolean.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.storenode-integer-text-boolean.html" title="1.95.        storenode( integer, text, boolean )
       ">
diff --git a/docs/en_US/slony/function.storenode-integer-text-boolean.html b/docs/en_US/slony/function.storenode-integer-text-boolean.html
index 772f91a339..7c4ccba1b7 100644
--- a/docs/en_US/slony/function.storenode-integer-text-boolean.html
+++ b/docs/en_US/slony/function.storenode-integer-text-boolean.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.storelisten-int-integer-integer-integer.html" title="1.94.        storelisten_int( integer, integer, integer )
       ">
diff --git a/docs/en_US/slony/function.storepath-int-integer-integer-text-integer.html b/docs/en_US/slony/function.storepath-int-integer-integer-text-integer.html
index bbb8f6ccd1..4db6c08735 100644
--- a/docs/en_US/slony/function.storepath-int-integer-integer-text-integer.html
+++ b/docs/en_US/slony/function.storepath-int-integer-integer-text-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.storepath-integer-integer-text-integer.html" title="1.97.        storepath( integer, integer, text, integer )
       ">
diff --git a/docs/en_US/slony/function.storepath-integer-integer-text-integer.html b/docs/en_US/slony/function.storepath-integer-integer-text-integer.html
index 1330a9b77c..6080401312 100644
--- a/docs/en_US/slony/function.storepath-integer-integer-text-integer.html
+++ b/docs/en_US/slony/function.storepath-integer-integer-text-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.storenode-int-integer-text-boolean.html" title="1.96.        storenode_int( integer, text, boolean )
       ">
diff --git a/docs/en_US/slony/function.storeset-int-integer-integer-text.html b/docs/en_US/slony/function.storeset-int-integer-integer-text.html
index 3131eb3cb1..2b1b612316 100644
--- a/docs/en_US/slony/function.storeset-int-integer-integer-text.html
+++ b/docs/en_US/slony/function.storeset-int-integer-integer-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.storeset-integer-text.html" title="1.99.        storeset( integer, text )
       ">
diff --git a/docs/en_US/slony/function.storeset-integer-text.html b/docs/en_US/slony/function.storeset-integer-text.html
index 4a0d462e47..0bcc6abb01 100644
--- a/docs/en_US/slony/function.storeset-integer-text.html
+++ b/docs/en_US/slony/function.storeset-integer-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.storepath-int-integer-integer-text-integer.html" title="1.98.        storepath_int( integer, integer, text, integer )
       ">
diff --git a/docs/en_US/slony/function.storetrigger-int-integer-name.html b/docs/en_US/slony/function.storetrigger-int-integer-name.html
index 1b8233a2fa..fa593cae54 100644
--- a/docs/en_US/slony/function.storetrigger-int-integer-name.html
+++ b/docs/en_US/slony/function.storetrigger-int-integer-name.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.storetrigger-integer-name.html" title="1.101.        storetrigger( integer, name )
       ">
diff --git a/docs/en_US/slony/function.storetrigger-integer-name.html b/docs/en_US/slony/function.storetrigger-integer-name.html
index ac1c35b38f..003ef9b2d1 100644
--- a/docs/en_US/slony/function.storetrigger-integer-name.html
+++ b/docs/en_US/slony/function.storetrigger-integer-name.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.storeset-int-integer-integer-text.html" title="1.100.        storeset_int( integer, integer, text )
       ">
diff --git a/docs/en_US/slony/function.subscribeset-int-integer-integer-integer-boolean.html b/docs/en_US/slony/function.subscribeset-int-integer-integer-integer-boolean.html
index e9b08b043b..ce0a703d9d 100644
--- a/docs/en_US/slony/function.subscribeset-int-integer-integer-integer-boolean.html
+++ b/docs/en_US/slony/function.subscribeset-int-integer-integer-integer-boolean.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.subscribeset-integer-integer-integer-boolean.html" title="1.103.        subscribeset( integer, integer, integer, boolean )
       ">
diff --git a/docs/en_US/slony/function.subscribeset-integer-integer-integer-boolean.html b/docs/en_US/slony/function.subscribeset-integer-integer-integer-boolean.html
index 237c5168dc..e09b55bc1c 100644
--- a/docs/en_US/slony/function.subscribeset-integer-integer-integer-boolean.html
+++ b/docs/en_US/slony/function.subscribeset-integer-integer-integer-boolean.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.storetrigger-int-integer-name.html" title="1.102.        storetrigger_int( integer, name )
       ">
diff --git a/docs/en_US/slony/function.tableaddkey-text.html b/docs/en_US/slony/function.tableaddkey-text.html
index f111bcc1c5..da7ac1b5f5 100644
--- a/docs/en_US/slony/function.tableaddkey-text.html
+++ b/docs/en_US/slony/function.tableaddkey-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.subscribeset-int-integer-integer-integer-boolean.html" title="1.104.        subscribeset_int( integer, integer, integer, boolean )
       ">
diff --git a/docs/en_US/slony/function.tabledropkey-integer.html b/docs/en_US/slony/function.tabledropkey-integer.html
index ec9b551c00..f7e2e0a914 100644
--- a/docs/en_US/slony/function.tabledropkey-integer.html
+++ b/docs/en_US/slony/function.tabledropkey-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.tableaddkey-text.html" title="1.105.        tableaddkey( text )
       ">
diff --git a/docs/en_US/slony/function.tablehasserialkey-text.html b/docs/en_US/slony/function.tablehasserialkey-text.html
index c0de29c212..50157b1557 100644
--- a/docs/en_US/slony/function.tablehasserialkey-text.html
+++ b/docs/en_US/slony/function.tablehasserialkey-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.tabledropkey-integer.html" title="1.106.        tabledropkey( integer )
       ">
diff --git a/docs/en_US/slony/function.terminatenodeconnections-name.html b/docs/en_US/slony/function.terminatenodeconnections-name.html
index b7ea9a1dec..427706e7a8 100644
--- a/docs/en_US/slony/function.terminatenodeconnections-name.html
+++ b/docs/en_US/slony/function.terminatenodeconnections-name.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.tablehasserialkey-text.html" title="1.107.        tablehasserialkey( text )
       ">
diff --git a/docs/en_US/slony/function.uninstallnode.html b/docs/en_US/slony/function.uninstallnode.html
index 4936719f00..16df4466fa 100644
--- a/docs/en_US/slony/function.uninstallnode.html
+++ b/docs/en_US/slony/function.uninstallnode.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.terminatenodeconnections-name.html" title="1.108.        terminatenodeconnections( name )
       ">
diff --git a/docs/en_US/slony/function.unlockset-integer.html b/docs/en_US/slony/function.unlockset-integer.html
index a63b93de92..a8469fa6f7 100644
--- a/docs/en_US/slony/function.unlockset-integer.html
+++ b/docs/en_US/slony/function.unlockset-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.uninstallnode.html" title="1.109.        uninstallnode(  )
       ">
diff --git a/docs/en_US/slony/function.unsubscribeset-int-integer-integer.html b/docs/en_US/slony/function.unsubscribeset-int-integer-integer.html
index 0315172d38..7096d3edbb 100644
--- a/docs/en_US/slony/function.unsubscribeset-int-integer-integer.html
+++ b/docs/en_US/slony/function.unsubscribeset-int-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.unsubscribeset-integer-integer.html" title="1.111.        unsubscribeset( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.unsubscribeset-integer-integer.html b/docs/en_US/slony/function.unsubscribeset-integer-integer.html
index c921d1d599..cb9e97a403 100644
--- a/docs/en_US/slony/function.unsubscribeset-integer-integer.html
+++ b/docs/en_US/slony/function.unsubscribeset-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.unlockset-integer.html" title="1.110.        unlockset( integer )
       ">
diff --git a/docs/en_US/slony/function.updaterelname-integer-integer.html b/docs/en_US/slony/function.updaterelname-integer-integer.html
index c048e6b91a..abd229a9cf 100644
--- a/docs/en_US/slony/function.updaterelname-integer-integer.html
+++ b/docs/en_US/slony/function.updaterelname-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.unsubscribeset-int-integer-integer.html" title="1.112.        unsubscribeset_int( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.updatereloid-integer-integer.html b/docs/en_US/slony/function.updatereloid-integer-integer.html
index 9377a2b74a..d6a414882f 100644
--- a/docs/en_US/slony/function.updatereloid-integer-integer.html
+++ b/docs/en_US/slony/function.updatereloid-integer-integer.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.updaterelname-integer-integer.html" title="1.113.        updaterelname( integer, integer )
       ">
diff --git a/docs/en_US/slony/function.upgradeschema-text.html b/docs/en_US/slony/function.upgradeschema-text.html
index 58de12f465..961b001a4a 100644
--- a/docs/en_US/slony/function.upgradeschema-text.html
+++ b/docs/en_US/slony/function.upgradeschema-text.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="function.updatereloid-integer-integer.html" title="1.114.        updatereloid( integer, integer )
       ">
diff --git a/docs/en_US/slony/hdrcmds.html b/docs/en_US/slony/hdrcmds.html
index 47e7d7dfa8..ee69e6dd2a 100644
--- a/docs/en_US/slony/hdrcmds.html
+++ b/docs/en_US/slony/hdrcmds.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="commandreference.html" title="Part I. Core Slony-I Programs">
 <link rel="prev" href="stmtdefine.html" title="DEFINE">
 <link rel="next" href="clustername.html" title="CLUSTER NAME">
@@ -16,7 +16,7 @@
 <a name="hdrcmds"></a>Slonik Preamble Commands</h1></div></div>
 <hr>
 </div>
-<div class="partintro" lang="en" id="id532305">
+<div class="partintro" lang="en" id="id532953">
 <div></div>
 <p>    The following commands must appear as a &#8220;<span class="quote">preamble</span>&#8221; at
     the beginning of each <span class="application">slonik</span> command
diff --git a/docs/en_US/slony/help.html b/docs/en_US/slony/help.html
index 8a6fe9107b..b1748ad2c7 100644
--- a/docs/en_US/slony/help.html
+++ b/docs/en_US/slony/help.html
@@ -1,18 +1,18 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>21. More Slony-I Help</title>
+<title>22. More Slony-I Help</title>
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
-<link rel="prev" href="bestpractices.html" title="20.  Slony-I &#8220;Best Practices&#8221; ">
+<link rel="prev" href="testbed.html" title="21.  Slony-I Test Bed Framework ">
 <link rel="next" href="faq.html" title="Slony-I FAQ">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="help"></a>21. More <span class="productname">Slony-I</span> Help</h2></div></div></div>
+<a name="help"></a>22. More <span class="productname">Slony-I</span> Help</h2></div></div></div>
 <p>If you are having problems with <span class="productname">Slony-I</span>, you have several
 options for help:
 
@@ -52,7 +52,7 @@
 </ul></div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id524802"></a>21.1.  Other Information Sources</h3></div></div></div>
+<a name="id525518"></a>22.1.  Other Information Sources</h3></div></div></div>
 <div class="itemizedlist"><ul type="disc">
 <li><p> <a href="http://comstar.dotgeek.org/postgres/slony-config/" target="_top">slony-config</a> - A Perl tool for configuring Slony nodes using
 config files in an XML-based format that the tool transforms into a
diff --git a/docs/en_US/slony/index.html b/docs/en_US/slony/index.html
index 94e5426173..9da011ba52 100644
--- a/docs/en_US/slony/index.html
+++ b/docs/en_US/slony/index.html
@@ -1,18 +1,18 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Slony-I HEAD_20051102 Documentation</title>
+<title>Slony-I HEAD_20051208 Documentation</title>
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="next" href="slonyintro.html" title="Slony-I Introduction">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en" id="slony">
 <div class="titlepage">
 <div>
 <div><h1 class="title">
-<a name="slony"></a><span class="productname">Slony-I<br></span> HEAD_20051102 Documentation</h1></div>
+<a name="slony"></a><span class="productname">Slony-I<br></span> HEAD_20051208 Documentation</h1></div>
 <div><h3 class="corpauthor">The PostgreSQL Global Development Group</h3></div>
 <div><div class="author"><h3 class="author">
 <span class="firstname">Christopher</span> <span class="surname">Browne</span>
@@ -29,87 +29,88 @@
 <dd><dl>
 <dt><span class="sect1"><a href="slonyintro.html#introduction">1. Introduction to <span class="productname">Slony-I</span></a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="slonyintro.html#id514281">1.1. What <span class="productname">Slony-I</span> is</a></span></dt>
-<dt><span class="sect2"><a href="slonyintro.html#id459618">1.2. Why yet another replication system?</a></span></dt>
-<dt><span class="sect2"><a href="slonyintro.html#id459639">1.3.  What <span class="productname">Slony-I</span> is not</a></span></dt>
-<dt><span class="sect2"><a href="slonyintro.html#id459737">1.4.  Why doesn't <span class="productname">Slony-I</span> do automatic fail-over/promotion?</a></span></dt>
-<dt><span class="sect2"><a href="slonyintro.html#id459823">1.5.  Current Limitations</a></span></dt>
-<dt><span class="sect2"><a href="slonyintro.html#id459938">1.6. Replication Models</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id486434">1.1. What <span class="productname">Slony-I</span> is</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id459615">1.2. Why yet another replication system?</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id459634">1.3.  What <span class="productname">Slony-I</span> is not</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id459733">1.4.  Why doesn't <span class="productname">Slony-I</span> do automatic fail-over/promotion?</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id459819">1.5.  Current Limitations</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id459934">1.6. Replication Models</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="slonylistenercosts.html">2.  <span class="productname">Slony-I</span> Communications
 Costs</a></span></dt>
 <dt><span class="sect1"><a href="requirements.html">3. System Requirements</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="requirements.html#id460225">3.1.  <span class="productname">Slony-I</span> Software Dependancies</a></span></dt>
-<dt><span class="sect2"><a href="requirements.html#id461008">3.2.  Getting <span class="productname">Slony-I</span> Source</a></span></dt>
+<dt><span class="sect2"><a href="requirements.html#id460221">3.1.  <span class="productname">Slony-I</span> Software Dependancies</a></span></dt>
+<dt><span class="sect2"><a href="requirements.html#id486473">3.2.  Getting <span class="productname">Slony-I</span> Source</a></span></dt>
 <dt><span class="sect2"><a href="requirements.html#times">3.3.  Time Synchronization</a></span></dt>
-<dt><span class="sect2"><a href="requirements.html#id503538">3.4.  Network Connectivity</a></span></dt>
+<dt><span class="sect2"><a href="requirements.html#id486679">3.4.  Network Connectivity</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="installation.html">4. <span class="productname">Slony-I</span> Installation</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="installation.html#id503803">4.1. Short Version</a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id503820">4.2. Configuration</a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id503885">4.3. Example</a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id503978">4.4. Build</a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id504038">4.5.  Installing <span class="productname">Slony-I</span></a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id504085">4.6.  Installing <span class="productname">Slony-I</span> from RPMs</a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id504164">4.7.  Installing the <span class="productname">Slony-I</span> service on <span class="trademark">Windows</span>&#8482;</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id486943">4.1. Short Version</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id486960">4.2. Configuration</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id487026">4.3. Example</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id487118">4.4. Build</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id487178">4.5.  Installing <span class="productname">Slony-I</span></a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id487226">4.6.  Installing <span class="productname">Slony-I</span> from RPMs</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id487324">4.7.  Installing the <span class="productname">Slony-I</span> service on <span class="trademark">Windows</span>&#8482;</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="concepts.html">5. <span class="productname">Slony-I</span> Concepts</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="concepts.html#id504363">5.1. Cluster</a></span></dt>
-<dt><span class="sect2"><a href="concepts.html#id514321">5.2. Node</a></span></dt>
-<dt><span class="sect2"><a href="concepts.html#id514402">5.3.  Replication Set</a></span></dt>
-<dt><span class="sect2"><a href="concepts.html#id514432">5.4.  Origin, Providers and Subscribers</a></span></dt>
-<dt><span class="sect2"><a href="concepts.html#id514498">5.5. slon Daemon</a></span></dt>
-<dt><span class="sect2"><a href="concepts.html#id514562">5.6. slonik Configuration Processor</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514215">5.1. Cluster</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514273">5.2. Node</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514356">5.3.  Replication Set</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514386">5.4.  Origin, Providers and Subscribers</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514451">5.5. slon Daemon</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514515">5.6. slonik Configuration Processor</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="cluster.html">6. Defining <span class="productname">Slony-I</span> Clusters</a></span></dt>
 <dt><span class="sect1"><a href="definingsets.html">7. Defining <span class="productname">Slony-I</span> Replication Sets</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="definingsets.html#id514692">7.1. Primary Keys</a></span></dt>
+<dt><span class="sect2"><a href="definingsets.html#id514645">7.1. Primary Keys</a></span></dt>
 <dt><span class="sect2"><a href="definingsets.html#definesets">7.2. Grouping tables into sets</a></span></dt>
-<dt><span class="sect2"><a href="definingsets.html#id514982">7.3.  The Pathology of Sequences </a></span></dt>
+<dt><span class="sect2"><a href="definingsets.html#id514935">7.3.  The Pathology of Sequences </a></span></dt>
 </dl></dd>
 </dl></dd>
 <dt><span class="article"><a href="slonyadmin.html"> Slony-I Administration </a></span></dt>
 <dd><dl>
 <dt><span class="sect1"><a href="slonyadmin.html#firstdb">1. Replicating Your First Database</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="slonyadmin.html#id515383">1.1. Creating the pgbenchuser</a></span></dt>
-<dt><span class="sect2"><a href="slonyadmin.html#id515394">1.2. Preparing the databases</a></span></dt>
-<dt><span class="sect2"><a href="slonyadmin.html#id515514">1.3. Configuring the Database for Replication.</a></span></dt>
+<dt><span class="sect2"><a href="slonyadmin.html#id515431">1.1. Creating the <span class="application">pgbench</span> user</a></span></dt>
+<dt><span class="sect2"><a href="slonyadmin.html#id515448">1.2. Preparing the databases</a></span></dt>
+<dt><span class="sect2"><a href="slonyadmin.html#id515566">1.3. Configuring the Database for Replication.</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="slonstart.html">2. Slon daemons</a></span></dt>
 <dt><span class="sect1"><a href="subscribenodes.html">3. Subscribing Nodes</a></span></dt>
 <dt><span class="sect1"><a href="monitoring.html">4. Monitoring</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="monitoring.html#id516282">4.1. CONFIG notices</a></span></dt>
-<dt><span class="sect2"><a href="monitoring.html#id516307">4.2. DEBUG Notices</a></span></dt>
-<dt><span class="sect2"><a href="monitoring.html#id516363">4.3.  How to read <span class="productname">Slony-I</span> logs </a></span></dt>
-<dt><span class="sect2"><a href="monitoring.html#id516582">4.4.  Nagios Replication Checks </a></span></dt>
+<dt><span class="sect2"><a href="monitoring.html#id459433">4.1. CONFIG notices</a></span></dt>
+<dt><span class="sect2"><a href="monitoring.html#id516589">4.2. DEBUG Notices</a></span></dt>
+<dt><span class="sect2"><a href="monitoring.html#id516646">4.3.  How to read <span class="productname">Slony-I</span> logs </a></span></dt>
+<dt><span class="sect2"><a href="monitoring.html#id516864">4.4.  Nagios Replication Checks </a></span></dt>
 <dt><span class="sect2"><a href="monitoring.html#testslonystate">4.5.  test_slony_state</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="maintenance.html">5. <span class="productname">Slony-I</span> Maintenance</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="maintenance.html#id517055">5.1.  Watchdogs: Keeping Slons Running</a></span></dt>
-<dt><span class="sect2"><a href="maintenance.html#id517083">5.2. Parallel to Watchdog: generate_syncs.sh</a></span></dt>
-<dt><span class="sect2"><a href="maintenance.html#id517183">5.3. Replication Test Scripts </a></span></dt>
-<dt><span class="sect2"><a href="maintenance.html#id517393">5.4.  Log Files</a></span></dt>
+<dt><span class="sect2"><a href="maintenance.html#id517337">5.1.  Watchdogs: Keeping Slons Running</a></span></dt>
+<dt><span class="sect2"><a href="maintenance.html#id517365">5.2. Parallel to Watchdog: generate_syncs.sh</a></span></dt>
+<dt><span class="sect2"><a href="maintenance.html#id517465">5.3. Replication Test Scripts </a></span></dt>
+<dt><span class="sect2"><a href="maintenance.html#id517675">5.4.  Log Files</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="reshape.html">6. Reshaping a Cluster</a></span></dt>
 <dt><span class="sect1"><a href="failover.html">7. Doing switchover and failover with <span class="productname">Slony-I</span></a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="failover.html#id517604">7.1. Foreword</a></span></dt>
-<dt><span class="sect2"><a href="failover.html#id517663">7.2.  Controlled Switchover</a></span></dt>
-<dt><span class="sect2"><a href="failover.html#id517791">7.3.  Failover</a></span></dt>
-<dt><span class="sect2"><a href="failover.html#id517945">7.4.  Automating <code class="command"> FAIL OVER </code> </a></span></dt>
-<dt><span class="sect2"><a href="failover.html#id518015">7.5. After Failover, Reconfiguring node1</a></span></dt>
+<dt><span class="sect2"><a href="failover.html#id517886">7.1. Foreword</a></span></dt>
+<dt><span class="sect2"><a href="failover.html#id517944">7.2.  Controlled Switchover</a></span></dt>
+<dt><span class="sect2"><a href="failover.html#id518072">7.3.  Failover</a></span></dt>
+<dt><span class="sect2"><a href="failover.html#id518296">7.4.  Automating <code class="command"> FAIL OVER </code> </a></span></dt>
+<dt><span class="sect2"><a href="failover.html#rebuildnode1">7.5. After Failover, Reconfiguring
+node 1</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="listenpaths.html">8. <span class="productname">Slony-I</span> listen paths</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="listenpaths.html#id518257">8.1. How listening can break</a></span></dt>
-<dt><span class="sect2"><a href="listenpaths.html#id518342">8.2. How the listen configuration should look</a></span></dt>
+<dt><span class="sect2"><a href="listenpaths.html#id518627">8.1. How listening can break</a></span></dt>
+<dt><span class="sect2"><a href="listenpaths.html#id518712">8.2. How the listen configuration should look</a></span></dt>
 <dt><span class="sect2"><a href="listenpaths.html#autolisten">8.3. Automated Listen Path Generation</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="plainpaths.html">9.  <span class="productname">Slony-I</span> Path Communications</a></span></dt>
@@ -117,19 +118,19 @@
 <dt><span class="sect1"><a href="addthings.html">11. Adding Things to Replication</a></span></dt>
 <dt><span class="sect1"><a href="dropthings.html">12. Dropping things from <span class="productname">Slony-I</span> Replication</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="dropthings.html#id519664">12.1. Dropping A Whole Node</a></span></dt>
-<dt><span class="sect2"><a href="dropthings.html#id519751">12.2. Dropping An Entire Set</a></span></dt>
-<dt><span class="sect2"><a href="dropthings.html#id519850">12.3. Unsubscribing One Node From One Set</a></span></dt>
-<dt><span class="sect2"><a href="dropthings.html#id519925">12.4.  Dropping A Table From A Set</a></span></dt>
-<dt><span class="sect2"><a href="dropthings.html#id520023">12.5. Dropping A Sequence From A Set</a></span></dt>
+<dt><span class="sect2"><a href="dropthings.html#id520032">12.1. Dropping A Whole Node</a></span></dt>
+<dt><span class="sect2"><a href="dropthings.html#id520120">12.2. Dropping An Entire Set</a></span></dt>
+<dt><span class="sect2"><a href="dropthings.html#id520218">12.3. Unsubscribing One Node From One Set</a></span></dt>
+<dt><span class="sect2"><a href="dropthings.html#id520293">12.4.  Dropping A Table From A Set</a></span></dt>
+<dt><span class="sect2"><a href="dropthings.html#id520391">12.5. Dropping A Sequence From A Set</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="logshipping.html">13. Log Shipping - <span class="productname">Slony-I</span> with Files</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="logshipping.html#id520669">13.1.  Usage Hints </a></span></dt></dl></dd>
+<dd><dl><dt><span class="sect2"><a href="logshipping.html#id521037">13.1.  Usage Hints </a></span></dt></dl></dd>
 <dt><span class="sect1"><a href="ddlchanges.html">14. Database Schema Changes (DDL)</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="ddlchanges.html#id521215">14.1.  Changes that you might <span class="emphasis"><em>not</em></span> want to
+<dt><span class="sect2"><a href="ddlchanges.html#id521583">14.1.  Changes that you might <span class="emphasis"><em>not</em></span> want to
 process using <code class="command">EXECUTE SCRIPT</code></a></span></dt>
-<dt><span class="sect2"><a href="ddlchanges.html#id521379">14.2.  Testing DDL Changes </a></span></dt>
+<dt><span class="sect2"><a href="ddlchanges.html#id521746">14.2.  Testing DDL Changes </a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="usingslonik.html">15. Using Slonik</a></span></dt>
 <dt><span class="sect1"><a href="slonikshell.html">16.  Embedding Slonik in Shell Scripts </a></span></dt>
@@ -137,36 +138,37 @@
 Functions </a></span></dt>
 <dt><span class="sect1"><a href="altperl.html">18. <span class="productname">Slony-I</span> Administration Scripts</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="altperl.html#id522344">18.1. Node/Cluster Configuration - cluster.nodes</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522444">18.2. Set configuration - cluster.set1, cluster.set2</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522560">18.3. slonik_build_env</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522602">18.4. slonik_create_set</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522627">18.5. slonik_drop_node</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522641">18.6. slonik_drop_set</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522660">18.7. slonik_execute_script</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522667">18.8. slonik_failover</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522675">18.9. slonik_init_cluster</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522691">18.10. slonik_merge_sets</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522698">18.11. slonik_move_set</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522706">18.12. replication_test</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522721">18.13. slonik_restart_node</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522730">18.14. slonik_restart_nodes</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522738">18.15. slony_show_configuration</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522750">18.16. slon_kill</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522759">18.17. slon_start</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522768">18.18. slon_watchdog</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522781">18.19. slon_watchdog2</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522801">18.20. slonik_store_node</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522809">18.21. slonik_subscribe_set</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522817">18.22. slonik_uninstall_nodes</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522837">18.23. slonik_unsubscribe_set</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522844">18.24. slonik_update_nodes</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id522712">18.1. Node/Cluster Configuration - cluster.nodes</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id522846">18.2. Set configuration - cluster.set1, cluster.set2</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id522962">18.3. slonik_build_env</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523005">18.4. slonik_create_set</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523029">18.5. slonik_drop_node</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523044">18.6. slonik_drop_set</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523062">18.7. slonik_execute_script</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523070">18.8. slonik_failover</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523078">18.9. slonik_init_cluster</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523094">18.10. slonik_merge_sets</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523101">18.11. slonik_move_set</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523109">18.12. replication_test</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523123">18.13. slonik_restart_node</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523133">18.14. slonik_restart_nodes</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523141">18.15. slony_show_configuration</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523153">18.16. slon_kill</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523162">18.17. slon_start</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523171">18.18. slon_watchdog</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523184">18.19. slon_watchdog2</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523204">18.20. slonik_store_node</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523212">18.21. slonik_subscribe_set</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523220">18.22. slonik_uninstall_nodes</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523240">18.23. slonik_unsubscribe_set</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523247">18.24. slonik_update_nodes</a></span></dt>
 <dt><span class="sect2"><a href="altperl.html#regenlisten">18.25. regenerate-listens</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="versionupgrade.html">19. Using <span class="productname">Slony-I</span> for <span class="productname">PostgreSQL</span> Upgrades</a></span></dt>
 <dt><span class="sect1"><a href="bestpractices.html">20.  <span class="productname">Slony-I</span> &#8220;<span class="quote">Best Practices</span>&#8221; </a></span></dt>
-<dt><span class="sect1"><a href="help.html">21. More <span class="productname">Slony-I</span> Help</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="help.html#id524802">21.1.  Other Information Sources</a></span></dt></dl></dd>
+<dt><span class="sect1"><a href="testbed.html">21.  <span class="productname">Slony-I</span> Test Bed Framework </a></span></dt>
+<dt><span class="sect1"><a href="help.html">22. More <span class="productname">Slony-I</span> Help</a></span></dt>
+<dd><dl><dt><span class="sect2"><a href="help.html#id525518">22.1.  Other Information Sources</a></span></dt></dl></dd>
 </dl></dd>
 <dt><span class="article"><a href="faq.html">Slony-I FAQ</a></span></dt>
 <dt><span class="part"><a href="commandreference.html">I. Core <span class="productname">Slony-I</span> Programs</a></span></dt>
@@ -187,7 +189,7 @@
 </dt>
 <dt><span class="article"><a href="slonikref.html">Slonik Command Summary</a></span></dt>
 <dd><dl>
-<dt><span class="sect1"><a href="slonikref.html#id531923">1. Introduction</a></span></dt>
+<dt><span class="sect1"><a href="slonikref.html#id532547">1. Introduction</a></span></dt>
 <dd><dl><dt><span class="sect2"><a href="slonikref.html#outline">1.1. General outline</a></span></dt></dl></dd>
 </dl></dd>
 <dt><span class="reference"><a href="metacmds.html">I. Slonik Meta Commands</a></span></dt>
@@ -609,7 +611,7 @@
 </div>
 <div class="list-of-figures">
 <p><b>List of Figures</b></p>
-<dl><dt>1.1. <a href="view.sl-seqlastvalue.html#id538430">Definition of view sl_seqlastvalue</a>
+<dl><dt>1.1. <a href="view.sl-seqlastvalue.html#id539298">Definition of view sl_seqlastvalue</a>
 </dt></dl>
 </div>
 <div class="list-of-tables">
diff --git a/docs/en_US/slony/installation.html b/docs/en_US/slony/installation.html
index 9723a52201..30dd661cb9 100644
--- a/docs/en_US/slony/installation.html
+++ b/docs/en_US/slony/installation.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyintro.html" title="Slony-I Introduction">
 <link rel="prev" href="requirements.html" title="3. System Requirements">
 <link rel="next" href="concepts.html" title="5. Slony-I Concepts">
@@ -13,10 +13,10 @@
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="installation"></a>4. <span class="productname">Slony-I</span> Installation</h2></div></div></div>
-<p>Note for <span class="trademark">Windows</span>&#8482; users:
-Unless you are planning on hacking the <span class="productname">Slony-I</span> code, it is highly
-recommended that you download and install a prebuilt binary 
-distribution and jump straight to the configuration section below.</p>
+<p>Note for <span class="trademark">Windows</span>&#8482; users: Unless you are planning on hacking the
+<span class="productname">Slony-I</span> code, it is highly recommended that you download and install
+a prebuilt binary distribution and jump straight to the configuration
+section below.</p>
 <p>You should have obtained the <span class="productname">Slony-I</span> source from the previous
 step. Unpack it.</p>
 <pre class="screen">gunzip slony.tar.gz;
@@ -26,7 +26,7 @@
 the installation procedure.</p>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id503803"></a>4.1. Short Version</h3></div></div></div>
+<a name="id486943"></a>4.1. Short Version</h3></div></div></div>
 <pre class="screen">PGMAIN=/usr/local/pgsql746-freebsd-2005-04-01 \
 ./configure \
     --prefix=$PGMAIN \
@@ -42,7 +42,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id503820"></a>4.2. Configuration</h3></div></div></div>
+<a name="id486960"></a>4.2. Configuration</h3></div></div></div>
 <p>The first step of the installation procedure is to configure the
 source tree for your system.  This is done by running the
 <span class="application">configure</span> script.  In early versions,
@@ -58,7 +58,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id503885"></a>4.3. Example</h3></div></div></div>
+<a name="id487026"></a>4.3. Example</h3></div></div></div>
 <p> After determining that the <span class="productname">PostgreSQL</span> instance to be used is
 installed in
 <code class="filename">/opt/dbs/pgsql746-aix-2005-04-01</code>:</p>
@@ -86,7 +86,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id503978"></a>4.4. Build</h3></div></div></div>
+<a name="id487118"></a>4.4. Build</h3></div></div></div>
 <p>To start the build process, type
 
 </p>
@@ -105,11 +105,11 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id504038"></a>4.5.  Installing <span class="productname">Slony-I</span></h3></div></div></div>
+<a name="id487178"></a>4.5.  Installing <span class="productname">Slony-I</span></h3></div></div></div>
 <p> To install <span class="productname">Slony-I</span>, enter
 
 <code class="command">gmake install</code></p>
-<p>This will install files into postgresql install directory as
+<p>This will install files into the postgresql install directory as
 specified by the <code class="command">configure</code>
 <code class="option">--prefix</code> option used in the <span class="productname">PostgreSQL</span> installation.
 Make sure you have appropriate permissions to write into that area.
@@ -117,7 +117,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id504085"></a>4.6.  Installing <span class="productname">Slony-I</span> from RPMs</h3></div></div></div>
+<a name="id487226"></a>4.6.  Installing <span class="productname">Slony-I</span> from RPMs</h3></div></div></div>
 <p> Even though <span class="productname">Slony-I</span> can be compiled and run on most Linux 
 distributions, it is also possible to install <span class="productname">Slony-I</span> using binary 
 packages. Slony Global Development Team provides official RPMs and SRPMs 
@@ -126,8 +126,8 @@
 http://developer.PostgreSQL.org/~devrim/slony . Please read <code class="command"> 
 CURRENT_MAINTAINER</code> file for the details of the RPMs. 
 Please note that the RPMs will look for RPM installation of 
-PostgreSQL, so if you install PosgtgreSQL from source, you should 
-manually ignore the RPM dependencies related to PostgreSQL.</p>
+<span class="productname">PostgreSQL</span>, so if you install <span class="productname">PostgreSQL</span> from source, you should 
+manually ignore the RPM dependencies related to <span class="productname">PostgreSQL</span>.</p>
 <p>Installing <span class="productname">Slony-I</span> using these RPMs is as easy as 
 installing any RPM.</p>
 <pre class="screen">rpm -ivh postgresql-slony1-engine-....rpm</pre>
@@ -142,11 +142,11 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id504164"></a>4.7.  Installing the <span class="productname">Slony-I</span> service on <span class="trademark">Windows</span>&#8482;</h3></div></div></div>
-<p> On <span class="trademark">Windows</span>&#8482; systems instead of running one
-slon daemon per node, a single slon service is installed which can then be
-controlled through the <code class="command">Services</code> control panel applet, or
-from a command prompt using the <code class="command">net</code> command.</p>
+<a name="id487324"></a>4.7.  Installing the <span class="productname">Slony-I</span> service on <span class="trademark">Windows</span>&#8482;</h3></div></div></div>
+<p> On <span class="trademark">Windows</span>&#8482; systems, instead of running one slon daemon per
+node, a single slon service is installed which can then be controlled
+through the <code class="command">Services</code> control panel applet, or from
+a command prompt using the <code class="command">net</code> command.</p>
 <pre class="screen">C:\Program Files\PostgreSQL\8.0\bin&gt; slon -regservice my_slon
 Service registered.
 Before you can run Slony, you must also register an engine!
diff --git a/docs/en_US/slony/ix01.html b/docs/en_US/slony/ix01.html
index 9e9294984e..d9f9fb1530 100644
--- a/docs/en_US/slony/ix01.html
+++ b/docs/en_US/slony/ix01.html
@@ -5,14 +5,14 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
-<link rel="up" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
+<link rel="up" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="prev" href="function.upgradeschema-text.html" title="1.115.        upgradeschema( text )
       ">
 </head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="index" id="id547931">
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="index" id="id548644">
 <div class="titlepage"><div><div><h2 class="title">
-<a name="id547931"></a>Index</h2></div></div></div>
+<a name="id548644"></a>Index</h2></div></div></div>
 <div class="index">
 <div class="indexdiv">
 <h3>B</h3>
@@ -22,7 +22,7 @@ <h3>B</h3>
 <div class="indexdiv">
 <h3>C</h3>
 <dl>
-<dt>cluster, <a href="concepts.html#id504363">Cluster</a>, <a href="cluster.html">Defining Slony-I Clusters</a>
+<dt>cluster, <a href="concepts.html#id514215">Cluster</a>, <a href="cluster.html">Defining Slony-I Clusters</a>
 </dt>
 <dt>cluster_name configuration parameter, <a href="slon-config-connection.html">Connection settings</a>
 </dt>
@@ -31,7 +31,7 @@ <h3>C</h3>
 </dt></dl></dd>
 <dt>conn_info configuration parameter, <a href="slon-config-connection.html">Connection settings</a>
 </dt>
-<dt>Controlled switchover, <a href="failover.html#id517663"> Controlled Switchover</a>
+<dt>Controlled switchover, <a href="failover.html#id517944"> Controlled Switchover</a>
 </dt>
 </dl>
 </div>
@@ -48,7 +48,7 @@ <h3>D</h3>
 <div class="indexdiv">
 <h3>F</h3>
 <dl>
-<dt>failover upon system failure, <a href="failover.html#id517791"> Failover</a>
+<dt>failover upon system failure, <a href="failover.html#id518072"> Failover</a>
 </dt>
 <dt>Frequently Asked Questions about Slony-I, <a href="faq.html">Slony-I FAQ</a>
 </dt>
@@ -77,12 +77,12 @@ <h3>L</h3>
 </div>
 <div class="indexdiv">
 <h3>N</h3>
-<dl><dt>node, <a href="concepts.html#id514321">Node</a>
+<dl><dt>node, <a href="concepts.html#id514273">Node</a>
 </dt></dl>
 </div>
 <div class="indexdiv">
 <h3>O</h3>
-<dl><dt>origin node, <a href="concepts.html#id514432"> Origin, Providers and Subscribers</a>
+<dl><dt>origin node, <a href="concepts.html#id514386"> Origin, Providers and Subscribers</a>
 </dt></dl>
 </div>
 <div class="indexdiv">
@@ -90,7 +90,7 @@ <h3>P</h3>
 <dl>
 <dt>pid_file configuration parameter, <a href="runtime-config.html#slon-config-logging">Logging</a>
 </dt>
-<dt>provider node, <a href="concepts.html#id514432"> Origin, Providers and Subscribers</a>
+<dt>provider node, <a href="concepts.html#id514386"> Origin, Providers and Subscribers</a>
 </dt>
 </dl>
 </div>
@@ -108,7 +108,7 @@ <h3>R</h3>
 <dl>
 <dt>replicating a first database, <a href="slonyadmin.html#firstdb">Replicating Your First Database</a>
 </dt>
-<dt>replication set, <a href="concepts.html#id514402"> Replication Set</a>
+<dt>replication set, <a href="concepts.html#id514356"> Replication Set</a>
 </dt>
 </dl>
 </div>
@@ -121,7 +121,7 @@ <h3>S</h3>
 </dt>
 <dt>sql_on_connection configuration parameter, <a href="slon-config-connection.html">Connection settings</a>
 </dt>
-<dt>subscriber node, <a href="concepts.html#id514432"> Origin, Providers and Subscribers</a>
+<dt>subscriber node, <a href="concepts.html#id514386"> Origin, Providers and Subscribers</a>
 </dt>
 <dt>subscribing nodes, <a href="subscribenodes.html">Subscribing Nodes</a>
 </dt>
diff --git a/docs/en_US/slony/listenpaths.html b/docs/en_US/slony/listenpaths.html
index 4d47c6bc90..94987572a9 100644
--- a/docs/en_US/slony/listenpaths.html
+++ b/docs/en_US/slony/listenpaths.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="failover.html" title="7. Doing switchover and failover with Slony-I">
 <link rel="next" href="plainpaths.html" title="9.  Slony-I Path Communications">
@@ -13,7 +13,7 @@
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="listenpaths"></a>8. <span class="productname">Slony-I</span> listen paths</h2></div></div></div>
-<a name="id518148"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
+<a name="id518517"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
 <h3 class="title">Note</h3>
 <p> If you are running version
 <span class="productname">Slony-I</span> 1.1 or later it should be
@@ -40,7 +40,7 @@ <h3 class="title">Note</h3>
 locations.</p>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id518257"></a>8.1. How listening can break</h3></div></div></div>
+<a name="id518627"></a>8.1. How listening can break</h3></div></div></div>
 <p>On one occasion, I had a need to drop a subscriber node (#2) and
 recreate it.  That node was the data provider for another subscriber
 (#3) that was, in effect, a &#8220;<span class="quote">cascaded slave.</span>&#8221; Dropping
@@ -65,7 +65,7 @@ <h3 class="title">Note</h3>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id518342"></a>8.2. How the listen configuration should look</h3></div></div></div>
+<a name="id518712"></a>8.2. How the listen configuration should look</h3></div></div></div>
 <p>The simple cases tend to be simple to cope with.  We need to
 instead look at a more complex node configuration.</p>
 <p>Consider a set of nodes, 1 thru 6, where 1 is the origin, 
diff --git a/docs/en_US/slony/locking.html b/docs/en_US/slony/locking.html
index fd19cd4806..c759bf49db 100644
--- a/docs/en_US/slony/locking.html
+++ b/docs/en_US/slony/locking.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="plainpaths.html" title="9.  Slony-I Path Communications">
 <link rel="next" href="addthings.html" title="11. Adding Things to Replication">
@@ -13,7 +13,7 @@
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="locking"></a>10. Locking Issues</h2></div></div></div>
-<a name="id519025"></a><p> One of the usual merits the use, by <span class="productname">PostgreSQL</span>, of
+<a name="id519395"></a><p> One of the usual merits the use, by <span class="productname">PostgreSQL</span>, of
 Multi-Version Concurrency Control (<span class="acronym">MVCC</span>) is that
 this eliminates a whole host of reasons to need to lock database
 objects.  On some other database systems, you need to acquire a table
@@ -136,11 +136,10 @@
 <p>
 </p>
 </li>
-<li><p> The section on <a href="ddlchanges.html" title="14. Database Schema Changes (DDL)"> DDL
-Changes </a> suggests some additional techniques that may be
-useful, such as moving tables between replication sets in such a way
-that you minimize the set of tables that need to be
-locked. </p></li>
+<li><p> The section  <a href="ddlchanges.html" title="14. Database Schema Changes (DDL)">Section 14, &#8220;Database Schema Changes (DDL)&#8221;</a> suggests some additional
+techniques that may be useful, such as moving tables between
+replication sets in such a way that you minimize the set of tables
+that need to be locked. </p></li>
 </ul></div>
 <p> Regrettably, there is no perfect answer to this.  If it is
 <span class="emphasis"><em>necessary</em></span> to submit a <a href="stmtmoveset.html" title="MOVE SET"><span class="refentrytitle">MOVE SET</span></a> request, then it is presumably
diff --git a/docs/en_US/slony/logshipping.html b/docs/en_US/slony/logshipping.html
index 5540946dc0..459b1f2368 100644
--- a/docs/en_US/slony/logshipping.html
+++ b/docs/en_US/slony/logshipping.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="dropthings.html" title="12. Dropping things from Slony-I Replication">
 <link rel="next" href="ddlchanges.html" title="14. Database Schema Changes (DDL)">
@@ -13,7 +13,7 @@
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="logshipping"></a>13. Log Shipping - <span class="productname">Slony-I</span> with Files</h2></div></div></div>
-<a name="id520107"></a><p> One of the new features for 1.1 is the ability to serialize the
+<a name="id520475"></a><p> One of the new features for 1.1 is the ability to serialize the
 updates to go out into log files that can be kept in a spool
 directory.</p>
 <p> The spool files could then be transferred via whatever means
@@ -55,18 +55,18 @@
 </ul></div>
 <div class="qandaset">
 <dl>
-<dt>13.1. <a href="logshipping.html#id520226"> Where are the spool files for a
+<dt>13.1. <a href="logshipping.html#id520594"> Where are the spool files for a
 subscription set generated?</a>
 </dt>
-<dt>13.2. <a href="logshipping.html#id520258"> What takes place when a /  takes
+<dt>13.2. <a href="logshipping.html#id520626"> What takes place when a /  takes
 place?</a>
 </dt>
-<dt>13.3. <a href="logshipping.html#id520283"> What if we run out of spool
+<dt>13.3. <a href="logshipping.html#id520651"> What if we run out of spool
 space?  </a>
 </dt>
-<dt>13.4. <a href="logshipping.html#id520304"> How do we set up a subscription?  </a>
+<dt>13.4. <a href="logshipping.html#id520672"> How do we set up a subscription?  </a>
 </dt>
-<dt>13.5. <a href="logshipping.html#id520379"> What are the limitations of log
+<dt>13.5. <a href="logshipping.html#id520747"> What are the limitations of log
 shipping? </a>
 </dt>
 </dl>
@@ -75,7 +75,7 @@
 <tbody>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id520226"></a><a name="id520228"></a><b>13.1.</b>
+<a name="id520594"></a><a name="id520596"></a><b>13.1.</b>
 </td>
 <td align="left" valign="top"><p> Where are the &#8220;<span class="quote">spool files</span>&#8221; for a
 subscription set generated?</p></td>
@@ -94,7 +94,7 @@ <h3 class="title">Note</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id520258"></a><a name="id520260"></a><b>13.2.</b>
+<a name="id520626"></a><a name="id520628"></a><b>13.2.</b>
 </td>
 <td align="left" valign="top"><p> What takes place when a <a href="stmtfailover.html" title="FAILOVER"><span class="refentrytitle">FAILOVER</span></a>/ <a href="stmtmoveset.html" title="MOVE SET"><span class="refentrytitle">MOVE SET</span></a> takes
 place?</p></td>
@@ -106,7 +106,7 @@ <h3 class="title">Note</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id520283"></a><a name="id520284"></a><b>13.3.</b>
+<a name="id520651"></a><a name="id520652"></a><b>13.3.</b>
 </td>
 <td align="left" valign="top"><p> What if we run out of &#8220;<span class="quote">spool
 space</span>&#8221;?  </p></td>
@@ -119,7 +119,7 @@ <h3 class="title">Note</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id520304"></a><a name="id520306"></a><b>13.4.</b>
+<a name="id520672"></a><a name="id520674"></a><b>13.4.</b>
 </td>
 <td align="left" valign="top"><p> How do we set up a subscription?  </p></td>
 </tr>
@@ -140,7 +140,7 @@ <h3 class="title">Note</h3>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="id520379"></a><a name="id520380"></a><b>13.5.</b>
+<a name="id520747"></a><a name="id520748"></a><b>13.5.</b>
 </td>
 <td align="left" valign="top"><p> What are the limitations of log
 shipping? </p></td>
@@ -235,7 +235,7 @@ <h3 class="title">Note</h3>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id520669"></a>13.1.  Usage Hints </h3></div></div></div>
+<a name="id521037"></a>13.1.  Usage Hints </h3></div></div></div>
 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
 <h3 class="title">Note</h3>
 <p> Here are some more-or-less disorganized notes about how
diff --git a/docs/en_US/slony/maintenance.html b/docs/en_US/slony/maintenance.html
index 6424aeadd0..c677eb50a9 100644
--- a/docs/en_US/slony/maintenance.html
+++ b/docs/en_US/slony/maintenance.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="monitoring.html" title="4. Monitoring">
 <link rel="next" href="reshape.html" title="6. Reshaping a Cluster">
@@ -53,7 +53,7 @@
 </ul></div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id517055"></a>5.1.  Watchdogs: Keeping Slons Running</h3></div></div></div>
+<a name="id517337"></a>5.1.  Watchdogs: Keeping Slons Running</h3></div></div></div>
 <p>There are a couple of &#8220;<span class="quote">watchdog</span>&#8221; scripts available that
 monitor things, and restart the <span class="application">slon</span> processes should
 they happen to die for some reason, such as a network &#8220;<span class="quote">glitch</span>&#8221;
@@ -62,7 +62,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id517083"></a>5.2. Parallel to Watchdog: generate_syncs.sh</h3></div></div></div>
+<a name="id517365"></a>5.2. Parallel to Watchdog: generate_syncs.sh</h3></div></div></div>
 <p>A new script for <span class="productname">Slony-I</span> 1.1 is
 <span class="application">generate_syncs.sh</span>, which addresses the following kind of
 situation.</p>
@@ -87,7 +87,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id517183"></a>5.3. Replication Test Scripts </h3></div></div></div>
+<a name="id517465"></a>5.3. Replication Test Scripts </h3></div></div></div>
 <p> In the directory <code class="filename">tools</code> may be found four
 scripts that may be used to do monitoring of <span class="productname">Slony-I</span> instances:
 
@@ -145,7 +145,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id517393"></a>5.4.  Log Files</h3></div></div></div>
+<a name="id517675"></a>5.4.  Log Files</h3></div></div></div>
 <p><a href="slon.html" title="slon"><span class="refentrytitle"><a name="app-slon-title"></a><span class="application">slon</span></span></a> daemons generate some more-or-less verbose
 log files, depending on what debugging level is turned on.  You might
 assortedly wish to:
diff --git a/docs/en_US/slony/metacmds.html b/docs/en_US/slony/metacmds.html
index dbd9a4ee4a..c3d4adc2f2 100644
--- a/docs/en_US/slony/metacmds.html
+++ b/docs/en_US/slony/metacmds.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="commandreference.html" title="Part I. Core Slony-I Programs">
 <link rel="prev" href="slonikref.html" title="Slonik Command Summary">
 <link rel="next" href="stmtinclude.html" title="INCLUDE">
@@ -16,7 +16,7 @@
 <a name="metacmds"></a>Slonik Meta Commands</h1></div></div>
 <hr>
 </div>
-<div class="partintro" lang="en" id="id532112">
+<div class="partintro" lang="en" id="id532755">
 <div></div>
 <p>     The following commands may be used to somewhat abstract the
      definitions of components of Slonik scripts; <a href="stmtinclude.html" title="INCLUDE"><span class="refentrytitle">INCLUDE</span></a> grouping configuration into central files
diff --git a/docs/en_US/slony/monitoring.html b/docs/en_US/slony/monitoring.html
index e37cf6ec05..7caef65099 100644
--- a/docs/en_US/slony/monitoring.html
+++ b/docs/en_US/slony/monitoring.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="subscribenodes.html" title="3. Subscribing Nodes">
 <link rel="next" href="maintenance.html" title="5. Slony-I Maintenance">
@@ -17,7 +17,7 @@
 and explanations of what they mean.</p>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id516282"></a>4.1. CONFIG notices</h3></div></div></div>
+<a name="id459433"></a>4.1. CONFIG notices</h3></div></div></div>
 <p>These entries are pretty straightforward. They are informative
 messages about your configuration.</p>
 <p>Here are some typical entries that you will probably run into in
@@ -34,7 +34,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id516307"></a>4.2. DEBUG Notices</h3></div></div></div>
+<a name="id516589"></a>4.2. DEBUG Notices</h3></div></div></div>
 <p>Debug notices are always prefaced by the name of the thread that
 the notice originates from. You will see messages from the following
 threads:
@@ -63,7 +63,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id516363"></a>4.3.  How to read <span class="productname">Slony-I</span> logs </h3></div></div></div>
+<a name="id516646"></a>4.3.  How to read <span class="productname">Slony-I</span> logs </h3></div></div></div>
 <p> Note that as far as slon is concerned, there is no "master" or
 "slave."  They are just nodes. </p>
 <p>What you can expect, initially, is to see, on both nodes, some
@@ -136,7 +136,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id516582"></a>4.4.  Nagios Replication Checks </h3></div></div></div>
+<a name="id516864"></a>4.4.  Nagios Replication Checks </h3></div></div></div>
 <p> The script in the <code class="filename">tools</code> directory called
 <code class="command"> pgsql_replication_check.pl </code> represents about best
 answers yet arrived at in several attempts to build replication tests
diff --git a/docs/en_US/slony/noslonik.html b/docs/en_US/slony/noslonik.html
index 367c43d7e6..578c8803c7 100644
--- a/docs/en_US/slony/noslonik.html
+++ b/docs/en_US/slony/noslonik.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="slonikshell.html" title="16.  Embedding Slonik in Shell Scripts ">
 <link rel="next" href="altperl.html" title="18. Slony-I Administration Scripts">
diff --git a/docs/en_US/slony/plainpaths.html b/docs/en_US/slony/plainpaths.html
index 48f856ecb7..99e63cb423 100644
--- a/docs/en_US/slony/plainpaths.html
+++ b/docs/en_US/slony/plainpaths.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="listenpaths.html" title="8. Slony-I listen paths">
 <link rel="next" href="locking.html" title="10. Locking Issues">
diff --git a/docs/en_US/slony/requirements.html b/docs/en_US/slony/requirements.html
index 698513046e..97d6469301 100644
--- a/docs/en_US/slony/requirements.html
+++ b/docs/en_US/slony/requirements.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyintro.html" title="Slony-I Introduction">
 <link rel="prev" href="slonylistenercosts.html" title="2.  Slony-I Communications
 Costs">
@@ -21,12 +21,11 @@
 this release are FreeBSD-4X-i368, FreeBSD-5X-i386, FreeBSD-5X-alpha,
 OS-X-10.3, Linux-2.4X-i386 Linux-2.6X-i386 Linux-2.6X-amd64,
 <span class="trademark">Solaris</span>&#8482;-2.8-SPARC,
-<span class="trademark">Solaris</span>&#8482;-2.9-SPARC, AIX 5.1,
-OpenBSD-3.5-sparc64 and <span class="trademark">Windows</span>&#8482; 2000, XP and 
-2003 (32 bit).</p>
+<span class="trademark">Solaris</span>&#8482;-2.9-SPARC, AIX 5.1, OpenBSD-3.5-sparc64
+and <span class="trademark">Windows</span>&#8482; 2000, XP and 2003 (32 bit).</p>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id460225"></a>3.1.  <span class="productname">Slony-I</span> Software Dependancies</h3></div></div></div>
+<a name="id460221"></a>3.1.  <span class="productname">Slony-I</span> Software Dependancies</h3></div></div></div>
 <p> At present, <span class="productname">Slony-I</span> <span class="emphasis"><em>as well as <span class="productname">PostgreSQL</span></em></span>
 need to be able to be compiled from source at your site.</p>
 <p> In order to compile <span class="productname">Slony-I</span>, you need to have the following
@@ -72,10 +71,10 @@
 <li><p> This documentation is written in SGML using <a href="http://docbook.com/" target="_top"> DocBook </a>, and may be processed into
 numerous formats including HTML, RTF, and PDF using tools in the
 <a href="http://docbook.sourceforge.net/" target="_top"> DocBook Open Repository</a> along with <a href="http://openjade.sourceforge.net/" target="_top">OpenJade.</a> </p></li>
-<li><p> On <span class="trademark">Windows</span>&#8482; you will also need the
-same <a href="http://www.postgresql.org/docs/faqs.FAQ_MINGW.html" target="_top">MinGW/Msys 
-Toolset</a> used to build PostgreSQL 8.0 and above.
-In addition you will need to install <a href="http://sourceware.org/pthreads-win32/" target="_top">pthreads-win32 2.x</a>. </p></li>
+<li><p> On <span class="trademark">Windows</span>&#8482; you will also need the same <a href="http://www.postgresql.org/docs/faqs.FAQ_MINGW.html" target="_top">MinGW/Msys
+Toolset</a> used to build <span class="productname">PostgreSQL</span> 8.0 and above.  In addition
+you will need to install <a href="http://sourceware.org/pthreads-win32/" target="_top">pthreads-win32
+2.x</a>. </p></li>
 </ul></div>
 <p> </p>
 <p>Also check to make sure you have sufficient disk space.  You
@@ -93,7 +92,7 @@ <h3 class="title">Note</h3>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id461008"></a>3.2.  Getting <span class="productname">Slony-I</span> Source</h3></div></div></div>
+<a name="id486473"></a>3.2.  Getting <span class="productname">Slony-I</span> Source</h3></div></div></div>
 <p>You can get the <span class="productname">Slony-I</span> source from <a href="http://developer.postgresql.org/~wieck/slony1/download/" target="_top">http://developer.postgresql.org/~wieck/slony1/download/</a></p>
 </div>
 <div class="sect2" lang="en">
@@ -142,7 +141,7 @@ <h3 class="title">Note</h3>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id503538"></a>3.4.  Network Connectivity</h3></div></div></div>
+<a name="id486679"></a>3.4.  Network Connectivity</h3></div></div></div>
 <p>It is necessary that the hosts that are to replicate between one
 another have <span class="emphasis"><em>bidirectional</em></span> network communications
 between the <span class="productname">PostgreSQL</span> instances.  That is, if node B is replicating
diff --git a/docs/en_US/slony/reshape.html b/docs/en_US/slony/reshape.html
index 4aae36ca89..83683099c8 100644
--- a/docs/en_US/slony/reshape.html
+++ b/docs/en_US/slony/reshape.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="maintenance.html" title="5. Slony-I Maintenance">
 <link rel="next" href="failover.html" title="7. Doing switchover and failover with Slony-I">
@@ -31,12 +31,13 @@
 <li><p> If the directions of data flows have changed, it is
 doubtless appropriate to issue a set of <a href="stmtdroplisten.html" title="DROP LISTEN"><span class="refentrytitle">DROP LISTEN</span></a> operations to drop out obsolete paths
 between nodes and <a href="stmtstorelisten.html" title="STORE LISTEN"><span class="refentrytitle">STORE LISTEN</span></a> to add the new
-ones.  At present, this is not changed automatically; at some point,
-<a href="stmtmoveset.html" title="MOVE SET"><span class="refentrytitle">MOVE SET</span></a> and <a href="stmtsubscribeset.html" title="SUBSCRIBE SET"><span class="refentrytitle">SUBSCRIBE SET</span></a> might change the paths as a side-effect.
-See <a href="listenpaths.html" title="8. Slony-I listen paths">Section 8, &#8220;<span class="productname">Slony-I</span> listen paths&#8221;</a> for more information about this.  In
-version 1.1 and later, it is likely that the generation of <a href="table.sl-listen.html">sl_listen</a> entries will be entirely automated, where
-they will be regenerated when changes are made to <a href="table.sl-path.html">sl_path</a> or <a href="table.sl-path.html">sl_path</a>, thereby
-making it unnecessary to even think about <a href="stmtstorelisten.html" title="STORE LISTEN"><span class="refentrytitle">STORE LISTEN</span></a>.</p></li>
+ones.  Up until version 1.1, this was not changed automatically; as of
+1.1, <a href="stmtmoveset.html" title="MOVE SET"><span class="refentrytitle">MOVE SET</span></a> and <a href="stmtsubscribeset.html" title="SUBSCRIBE SET"><span class="refentrytitle">SUBSCRIBE SET</span></a> change the paths as a side-effect.  See
+<a href="listenpaths.html" title="8. Slony-I listen paths">Section 8, &#8220;<span class="productname">Slony-I</span> listen paths&#8221;</a> for more information about this.  In
+version 1.1 and later, generation of <a href="table.sl-listen.html">sl_listen</a>
+entries is entirely automated, so that they are regenerated when
+changes are made to <a href="table.sl-path.html">sl_path</a> or <a href="table.sl-path.html">sl_path</a>, thereby making it unnecessary to even think
+about <a href="stmtstorelisten.html" title="STORE LISTEN"><span class="refentrytitle">STORE LISTEN</span></a>.</p></li>
 </ul></div>
 <p> The <code class="filename">altperl</code> toolset includes a
 <span class="application">regenerate-listens</span> script that is up to
diff --git a/docs/en_US/slony/runtime-config.html b/docs/en_US/slony/runtime-config.html
index ce9f82e5d5..4c0f8881e9 100644
--- a/docs/en_US/slony/runtime-config.html
+++ b/docs/en_US/slony/runtime-config.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="commandreference.html" title="Part I. Core Slony-I Programs">
 <link rel="prev" href="slon.html" title="slon">
 <link rel="next" href="slon-config-connection.html" title="2. Connection settings">
@@ -24,7 +24,7 @@
 <dt><span class="sect1"><a href="slon-config-interval.html">3. Event Tuning</a></span></dt>
 </dl>
 </div>
-<a name="id530782"></a><p>    There are several configuration parameters that affect the
+<a name="id531404"></a><p>    There are several configuration parameters that affect the
     behavior of the replication system.  In this section, we describe
     how to set the <span class="application">slon</span> daemon's
     configuration parameters; the following subsections discuss each
diff --git a/docs/en_US/slony/schema.html b/docs/en_US/slony/schema.html
index 136383bd1a..6a6907d0ff 100644
--- a/docs/en_US/slony/schema.html
+++ b/docs/en_US/slony/schema.html
@@ -5,8 +5,8 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
-<link rel="up" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
+<link rel="up" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="prev" href="supportedplatforms.html" title="Slony-I Supported Platforms">
 <link rel="next" href="table.sl-confirm.html" title="1.2.          Table:
          
diff --git a/docs/en_US/slony/slon-config-connection.html b/docs/en_US/slony/slon-config-connection.html
index 2d344d34f6..f03865fd23 100644
--- a/docs/en_US/slony/slon-config-connection.html
+++ b/docs/en_US/slony/slon-config-connection.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="runtime-config.html" title="Run-time Configuration">
 <link rel="prev" href="runtime-config.html" title="Run-time Configuration">
 <link rel="next" href="slon-config-interval.html" title="3. Event Tuning">
diff --git a/docs/en_US/slony/slon-config-interval.html b/docs/en_US/slony/slon-config-interval.html
index bb95a07697..14a54add77 100644
--- a/docs/en_US/slony/slon-config-interval.html
+++ b/docs/en_US/slony/slon-config-interval.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="runtime-config.html" title="Run-time Configuration">
 <link rel="prev" href="slon-config-connection.html" title="2. Connection settings">
 <link rel="next" href="slonik.html" title="slonik">
diff --git a/docs/en_US/slony/slon.html b/docs/en_US/slony/slon.html
index ee3de30b51..d0b810b232 100644
--- a/docs/en_US/slony/slon.html
+++ b/docs/en_US/slony/slon.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="commandreference.html" title="Part I. Core Slony-I Programs">
 <link rel="prev" href="commandreference.html" title="Part I. Core Slony-I Programs">
 <link rel="next" href="runtime-config.html" title="Run-time Configuration">
@@ -17,12 +17,12 @@ <h2>Name</h2>
 <p><span class="application">slon</span> &#8212;    <span class="productname">Slony-I</span> daemon
   </p>
 </div>
-<a name="id529758"></a><div class="refsynopsisdiv">
+<a name="id530369"></a><div class="refsynopsisdiv">
 <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">slon</code> [<em class="replaceable"><code>option</code></em>...] [<em class="replaceable"><code>clustername</code></em>] [<em class="replaceable"><code>conninfo</code></em>]</p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id529811"></a><h2>Description</h2>
+<a name="id530422"></a><h2>Description</h2>
 <p>   <span class="application">slon</span> is the daemon application that
    &#8220;<span class="quote">runs</span>&#8221; <span class="productname">Slony-I</span> replication.  A
    <span class="application">slon</span> instance must be run for each node
@@ -32,7 +32,7 @@ <h2>Synopsis</h2>
 <div class="refsect1" lang="en">
 <a name="r1-app-slon-3"></a><h2>Options</h2>
 <div class="variablelist"><dl>
-<dt><span class="term"><code class="option">-d</code><em class="replaceable"><code>debuglevel</code></em></span></dt>
+<dt><span class="term"><code class="option">-d</code><em class="replaceable"><code> debuglevel</code></em></span></dt>
 <dd>
 <p>      The <code class="envar">log_level</code> specifies the level of verbosity
       that <span class="application">slon</span> should use when logging its
@@ -53,7 +53,7 @@ <h2>Synopsis</h2>
 <p>
      </p>
 </dd>
-<dt><span class="term"><code class="option">-s</code><em class="replaceable"><code>SYNC check interval</code></em></span></dt>
+<dt><span class="term"><code class="option">-s</code><em class="replaceable"><code> SYNC check interval</code></em></span></dt>
 <dd>
 <p>      The <code class="envar">sync_interval</code>, measured in milliseconds,
       indicates how often <span class="application">slon</span> should check
@@ -75,7 +75,7 @@ <h2>Synopsis</h2>
       be much less the <code class="envar">sync_interval_timeout</code> value.
      </p>
 </dd>
-<dt><span class="term"><code class="option">-t</code><em class="replaceable"><code>SYNC
+<dt><span class="term"><code class="option">-t</code><em class="replaceable"><code> SYNC
     interval timeout</code></em></span></dt>
 <dd>
 <p>      At the end of each <code class="envar">sync_interval_timeout</code> timeout
@@ -94,7 +94,7 @@ <h2>Synopsis</h2>
       events are of not terribly much value.
      </p>
 </dd>
-<dt><span class="term"><code class="option">-g</code><em class="replaceable"><code>group size</code></em></span></dt>
+<dt><span class="term"><code class="option">-g</code><em class="replaceable"><code> group size</code></em></span></dt>
 <dd>
 <p>      This controls the maximum <code class="command">SYNC</code> group size,
       <code class="envar">sync_group_maxsize</code>; defaults to 6.  Thus, if a
@@ -154,7 +154,7 @@ <h2>Synopsis</h2>
       hopefully making operator assistance unnecessary.
      </p>
 </dd>
-<dt><span class="term"><code class="option">-o</code><em class="replaceable"><code>desired sync time</code></em></span></dt>
+<dt><span class="term"><code class="option">-o</code><em class="replaceable"><code> desired sync time</code></em></span></dt>
 <dd>
 <p> A &#8220;<span class="quote">maximum</span>&#8221; time planned for grouped <code class="command">SYNC</code>s.</p>
 <p> If replication is running behind, slon will gradually
@@ -183,7 +183,7 @@ <h2>Synopsis</h2>
       start with one sync at a time, if need be, so that if it is at
       all possible for replication to progress, it will.</p>
 </dd>
-<dt><span class="term"><code class="option">-c</code><em class="replaceable"><code>cleanup cycles</code></em></span></dt>
+<dt><span class="term"><code class="option">-c</code><em class="replaceable"><code> cleanup cycles</code></em></span></dt>
 <dd>
 <p>      The value <code class="envar">vac_frequency</code> indicates how often to
       <code class="command">VACUUM</code> in cleanup cycles.
@@ -207,7 +207,7 @@ <h2>Synopsis</h2>
      statistics in <code class="envar">pg_statistics</code>.
      </p>
 </dd>
-<dt><span class="term"><code class="option">-p</code><em class="replaceable"><code>PID filename</code></em></span></dt>
+<dt><span class="term"><code class="option">-p</code><em class="replaceable"><code> PID filename</code></em></span></dt>
 <dd>
 <p>      <code class="envar">pid_file</code> contains the filename in which the PID
       (process ID) of the <span class="application">slon</span> is stored.
@@ -217,11 +217,11 @@ <h2>Synopsis</h2>
       host.
      </p>
 </dd>
-<dt><span class="term"><code class="option">-f</code><em class="replaceable"><code>config file</code></em></span></dt>
+<dt><span class="term"><code class="option">-f</code><em class="replaceable"><code> config file</code></em></span></dt>
 <dd>
 <p>      File from which to read <span class="application">slon</span> configuration.
      </p>
-<p> This configuration is discussed further in <a href="runtime-config.html" title="Run-time Configuration">Run-time Configuration</a>.  If there are to be a complex set of
+<p> This configuration is  discussed  further  in <a href="runtime-config.html">Slon  Run-time Configuration</a>. If there are to be a complex set of
      configuration parameters, or if there are parameters you do not
      wish to be visible in the process environment variables (such as
      passwords), it may be convenient to draw many or all parameters
@@ -231,10 +231,10 @@ <h2>Synopsis</h2>
      other than the connection info.  Alternatively, you might create
      a configuration file for each node.</p>
 </dd>
-<dt><span class="term"><code class="option">-a</code><em class="replaceable"><code>archive directory</code></em></span></dt>
+<dt><span class="term"><code class="option">-a</code><em class="replaceable"><code> archive directory</code></em></span></dt>
 <dd><p>      <code class="envar">archive_dir</code> indicates a directory in which to
       place a sequence of <code class="command">SYNC</code> archive files for
-      use in <a href="logshipping.html" title="13. Log Shipping - Slony-I with Files"> log shipping</a> mode.
+      use in <a href="logshipping.html" title="13. Log Shipping - Slony-I with Files">log shipping</a> mode.
      </p></dd>
 <dt><span class="term"><code class="option">-q</code><em class="replaceable"><code> quit based on SYNC provider </code></em></span></dt>
 <dd>
@@ -263,9 +263,11 @@ <h2>Synopsis</h2>
 </dl></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id530760"></a><h2>Exit Status</h2>
+<a name="id531373"></a><h2>Exit Status</h2>
 <p>   <span class="application">slon</span> returns 0 to the shell if it
-   finished normally.  It returns -1 if it encounters any fatal error.
+   finished normally.  It returns via <code class="function">exit(-1)</code>
+   (which will likely provide a return value of either 127 or 255,
+   depending on your system) if it encounters any fatal error.
   </p>
 </div>
 </div></body>
diff --git a/docs/en_US/slony/slonik.html b/docs/en_US/slony/slonik.html
index 9daa3db6cf..b853d552f9 100644
--- a/docs/en_US/slony/slonik.html
+++ b/docs/en_US/slony/slonik.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="commandreference.html" title="Part I. Core Slony-I Programs">
 <link rel="prev" href="slon-config-interval.html" title="3. Event Tuning">
 <link rel="next" href="slonikref.html" title="Slonik Command Summary">
@@ -17,19 +17,19 @@ <h2>Name</h2>
 <p><span class="application">slonik</span> &#8212;       <span class="productname">Slony-I</span> command processor
     </p>
 </div>
-<a name="id531761"></a><div class="refsynopsisdiv">
+<a name="id532383"></a><div class="refsynopsisdiv">
 <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">slonik</code> [<em class="replaceable"><code>filename</code></em>]</p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id531791"></a><h2>Description</h2>
+<a name="id532414"></a><h2>Description</h2>
 <p>     <span class="application">slonik</span> is the command processor
      application that is used to set up and modify configurations of
      <span class="productname">Slony-I</span> replication clusters.
     </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id531813"></a><h2>Outline</h2>
+<a name="id532435"></a><h2>Outline</h2>
 <p>The <span class="application">slonik</span> command line utility is
   supposed to be used embedded into shell scripts; it reads commands
   from files or stdin.</p>
@@ -56,10 +56,11 @@ <h2>Synopsis</h2>
   <span class="emphasis"><em>generated</em></span> by scripts, such as Bash or Perl, and
   these sorts of scripting languages already have perfectly good ways
   of managing variables, doing iteration, and such.</p>
-<p>See also <a href="slonikref.html" title="Slonik Command Summary">Slonik Command Summary</a>. </p>
+<p>See also <a href="slonikref.html"> Slonik Command Language
+  reference </a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id531901"></a><h2>Exit Status</h2>
+<a name="id532525"></a><h2>Exit Status</h2>
 <p>   <span class="application">slonik</span> returns 0 to the shell if it
    finished normally.  Scripts may specify return codes.   
   </p>
diff --git a/docs/en_US/slony/slonikref.html b/docs/en_US/slony/slonikref.html
index 204f2518e8..f7c64c8dc5 100644
--- a/docs/en_US/slony/slonikref.html
+++ b/docs/en_US/slony/slonikref.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="commandreference.html" title="Part I. Core Slony-I Programs">
 <link rel="prev" href="slonik.html" title="slonik">
 <link rel="next" href="metacmds.html" title="Slonik Meta Commands">
@@ -19,13 +19,13 @@
 <div class="toc">
 <p><b>Table of Contents</b></p>
 <dl>
-<dt><span class="sect1"><a href="slonikref.html#id531923">1. Introduction</a></span></dt>
+<dt><span class="sect1"><a href="slonikref.html#id532547">1. Introduction</a></span></dt>
 <dd><dl><dt><span class="sect2"><a href="slonikref.html#outline">1.1. General outline</a></span></dt></dl></dd>
 </dl>
 </div>
 <div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id531923"></a>1. Introduction</h2></div></div></div>
+<a name="id532547"></a>1. Introduction</h2></div></div></div>
 <p>     <span class="application">Slonik</span> is a command line utility designed
      specifically to setup and modify configurations of the
      <span class="productname">Slony-I</span> replication system.
@@ -63,7 +63,7 @@
     </p>
 <div class="sect3" lang="en">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id532033"></a>1.1.1. Commands</h4></div></div></div>
+<a name="id532657"></a>1.1.1. Commands</h4></div></div></div>
 <p>      The slonik command language is format free. Commands begin with
       keywords and are terminated with a semicolon. Most commands have
       a list of parameters, some of which have default values and are
@@ -86,13 +86,13 @@
 </div>
 <div class="sect3" lang="en">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id532062"></a>1.1.2. Comments</h4></div></div></div>
+<a name="id532705"></a>1.1.2. Comments</h4></div></div></div>
 <p>      Comments begin at a hash sign (#) and extend to the end of the line.
      </p>
 </div>
 <div class="sect3" lang="en">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id532070"></a>1.1.3. Command groups</h4></div></div></div>
+<a name="id532713"></a>1.1.3. Command groups</h4></div></div></div>
 <p>      Commands can be combined into groups of commands with optional
       <code class="command">on error</code> and <code class="command">on success</code> conditionals.
       The syntax for this is:
diff --git a/docs/en_US/slony/slonikshell.html b/docs/en_US/slony/slonikshell.html
index 7fcead933f..5bb23160d1 100644
--- a/docs/en_US/slony/slonikshell.html
+++ b/docs/en_US/slony/slonikshell.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="usingslonik.html" title="15. Using Slonik">
 <link rel="next" href="noslonik.html" title="17.  Not Using Slonik - Bare Metal Slony-I
diff --git a/docs/en_US/slony/slonstart.html b/docs/en_US/slony/slonstart.html
index 8b5ce495a0..ce9413d53d 100644
--- a/docs/en_US/slony/slonstart.html
+++ b/docs/en_US/slony/slonstart.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="next" href="subscribenodes.html" title="3. Subscribing Nodes">
@@ -17,15 +17,15 @@
 <span class="application">slon</span> daemons.</p>
 <p>You need to run one <a href="slon.html" title="slon"><span class="refentrytitle"><a name="app-slon-title"></a><span class="application">slon</span></span></a> instance for each node
 in a <span class="productname">Slony-I</span> cluster, whether you consider that node a
-&#8220;<span class="quote">master</span>&#8221; or a &#8220;<span class="quote">slave</span>&#8221;. On Windows when 
+&#8220;<span class="quote">master</span>&#8221; or a &#8220;<span class="quote">slave</span>&#8221;. On <span class="trademark">Windows</span>&#8482; when
 running as a service things are slightly different. One slon service
 is installed, and a seperate configuration file registered for each
-node to be serviced by that machine. The main service then manages 
-the individual slons itself. Since a <code class="command">MOVE
-SET</code> or <code class="command">FAILOVER</code> can switch the roles of
-nodes, slon needs to be able to function for both providers and
-subscribers.  It is not essential that these daemons run on any
-particular host, but there are some principles worth considering:
+node to be serviced by that machine. The main service then manages the
+individual slons itself. Since a <code class="command">MOVE SET</code> or
+<code class="command">FAILOVER</code> can switch the roles of nodes, slon needs
+to be able to function for both providers and subscribers.  It is not
+essential that these daemons run on any particular host, but there are
+some principles worth considering:
 
 </p>
 <div class="itemizedlist"><ul type="disc">
diff --git a/docs/en_US/slony/slonyadmin.html b/docs/en_US/slony/slonyadmin.html
index 68fac07814..45c0fbe1e9 100644
--- a/docs/en_US/slony/slonyadmin.html
+++ b/docs/en_US/slony/slonyadmin.html
@@ -5,8 +5,8 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
-<link rel="up" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
+<link rel="up" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="prev" href="definingsets.html" title="7. Defining Slony-I Replication Sets">
 <link rel="next" href="slonstart.html" title="2. Slon daemons">
 </head>
@@ -27,40 +27,41 @@
 <dl>
 <dt><span class="sect1"><a href="slonyadmin.html#firstdb">1. Replicating Your First Database</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="slonyadmin.html#id515383">1.1. Creating the pgbenchuser</a></span></dt>
-<dt><span class="sect2"><a href="slonyadmin.html#id515394">1.2. Preparing the databases</a></span></dt>
-<dt><span class="sect2"><a href="slonyadmin.html#id515514">1.3. Configuring the Database for Replication.</a></span></dt>
+<dt><span class="sect2"><a href="slonyadmin.html#id515431">1.1. Creating the <span class="application">pgbench</span> user</a></span></dt>
+<dt><span class="sect2"><a href="slonyadmin.html#id515448">1.2. Preparing the databases</a></span></dt>
+<dt><span class="sect2"><a href="slonyadmin.html#id515566">1.3. Configuring the Database for Replication.</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="slonstart.html">2. Slon daemons</a></span></dt>
 <dt><span class="sect1"><a href="subscribenodes.html">3. Subscribing Nodes</a></span></dt>
 <dt><span class="sect1"><a href="monitoring.html">4. Monitoring</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="monitoring.html#id516282">4.1. CONFIG notices</a></span></dt>
-<dt><span class="sect2"><a href="monitoring.html#id516307">4.2. DEBUG Notices</a></span></dt>
-<dt><span class="sect2"><a href="monitoring.html#id516363">4.3.  How to read <span class="productname">Slony-I</span> logs </a></span></dt>
-<dt><span class="sect2"><a href="monitoring.html#id516582">4.4.  Nagios Replication Checks </a></span></dt>
+<dt><span class="sect2"><a href="monitoring.html#id459433">4.1. CONFIG notices</a></span></dt>
+<dt><span class="sect2"><a href="monitoring.html#id516589">4.2. DEBUG Notices</a></span></dt>
+<dt><span class="sect2"><a href="monitoring.html#id516646">4.3.  How to read <span class="productname">Slony-I</span> logs </a></span></dt>
+<dt><span class="sect2"><a href="monitoring.html#id516864">4.4.  Nagios Replication Checks </a></span></dt>
 <dt><span class="sect2"><a href="monitoring.html#testslonystate">4.5.  test_slony_state</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="maintenance.html">5. <span class="productname">Slony-I</span> Maintenance</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="maintenance.html#id517055">5.1.  Watchdogs: Keeping Slons Running</a></span></dt>
-<dt><span class="sect2"><a href="maintenance.html#id517083">5.2. Parallel to Watchdog: generate_syncs.sh</a></span></dt>
-<dt><span class="sect2"><a href="maintenance.html#id517183">5.3. Replication Test Scripts </a></span></dt>
-<dt><span class="sect2"><a href="maintenance.html#id517393">5.4.  Log Files</a></span></dt>
+<dt><span class="sect2"><a href="maintenance.html#id517337">5.1.  Watchdogs: Keeping Slons Running</a></span></dt>
+<dt><span class="sect2"><a href="maintenance.html#id517365">5.2. Parallel to Watchdog: generate_syncs.sh</a></span></dt>
+<dt><span class="sect2"><a href="maintenance.html#id517465">5.3. Replication Test Scripts </a></span></dt>
+<dt><span class="sect2"><a href="maintenance.html#id517675">5.4.  Log Files</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="reshape.html">6. Reshaping a Cluster</a></span></dt>
 <dt><span class="sect1"><a href="failover.html">7. Doing switchover and failover with <span class="productname">Slony-I</span></a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="failover.html#id517604">7.1. Foreword</a></span></dt>
-<dt><span class="sect2"><a href="failover.html#id517663">7.2.  Controlled Switchover</a></span></dt>
-<dt><span class="sect2"><a href="failover.html#id517791">7.3.  Failover</a></span></dt>
-<dt><span class="sect2"><a href="failover.html#id517945">7.4.  Automating <code class="command"> FAIL OVER </code> </a></span></dt>
-<dt><span class="sect2"><a href="failover.html#id518015">7.5. After Failover, Reconfiguring node1</a></span></dt>
+<dt><span class="sect2"><a href="failover.html#id517886">7.1. Foreword</a></span></dt>
+<dt><span class="sect2"><a href="failover.html#id517944">7.2.  Controlled Switchover</a></span></dt>
+<dt><span class="sect2"><a href="failover.html#id518072">7.3.  Failover</a></span></dt>
+<dt><span class="sect2"><a href="failover.html#id518296">7.4.  Automating <code class="command"> FAIL OVER </code> </a></span></dt>
+<dt><span class="sect2"><a href="failover.html#rebuildnode1">7.5. After Failover, Reconfiguring
+node 1</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="listenpaths.html">8. <span class="productname">Slony-I</span> listen paths</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="listenpaths.html#id518257">8.1. How listening can break</a></span></dt>
-<dt><span class="sect2"><a href="listenpaths.html#id518342">8.2. How the listen configuration should look</a></span></dt>
+<dt><span class="sect2"><a href="listenpaths.html#id518627">8.1. How listening can break</a></span></dt>
+<dt><span class="sect2"><a href="listenpaths.html#id518712">8.2. How the listen configuration should look</a></span></dt>
 <dt><span class="sect2"><a href="listenpaths.html#autolisten">8.3. Automated Listen Path Generation</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="plainpaths.html">9.  <span class="productname">Slony-I</span> Path Communications</a></span></dt>
@@ -68,19 +69,19 @@
 <dt><span class="sect1"><a href="addthings.html">11. Adding Things to Replication</a></span></dt>
 <dt><span class="sect1"><a href="dropthings.html">12. Dropping things from <span class="productname">Slony-I</span> Replication</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="dropthings.html#id519664">12.1. Dropping A Whole Node</a></span></dt>
-<dt><span class="sect2"><a href="dropthings.html#id519751">12.2. Dropping An Entire Set</a></span></dt>
-<dt><span class="sect2"><a href="dropthings.html#id519850">12.3. Unsubscribing One Node From One Set</a></span></dt>
-<dt><span class="sect2"><a href="dropthings.html#id519925">12.4.  Dropping A Table From A Set</a></span></dt>
-<dt><span class="sect2"><a href="dropthings.html#id520023">12.5. Dropping A Sequence From A Set</a></span></dt>
+<dt><span class="sect2"><a href="dropthings.html#id520032">12.1. Dropping A Whole Node</a></span></dt>
+<dt><span class="sect2"><a href="dropthings.html#id520120">12.2. Dropping An Entire Set</a></span></dt>
+<dt><span class="sect2"><a href="dropthings.html#id520218">12.3. Unsubscribing One Node From One Set</a></span></dt>
+<dt><span class="sect2"><a href="dropthings.html#id520293">12.4.  Dropping A Table From A Set</a></span></dt>
+<dt><span class="sect2"><a href="dropthings.html#id520391">12.5. Dropping A Sequence From A Set</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="logshipping.html">13. Log Shipping - <span class="productname">Slony-I</span> with Files</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="logshipping.html#id520669">13.1.  Usage Hints </a></span></dt></dl></dd>
+<dd><dl><dt><span class="sect2"><a href="logshipping.html#id521037">13.1.  Usage Hints </a></span></dt></dl></dd>
 <dt><span class="sect1"><a href="ddlchanges.html">14. Database Schema Changes (DDL)</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="ddlchanges.html#id521215">14.1.  Changes that you might <span class="emphasis"><em>not</em></span> want to
+<dt><span class="sect2"><a href="ddlchanges.html#id521583">14.1.  Changes that you might <span class="emphasis"><em>not</em></span> want to
 process using <code class="command">EXECUTE SCRIPT</code></a></span></dt>
-<dt><span class="sect2"><a href="ddlchanges.html#id521379">14.2.  Testing DDL Changes </a></span></dt>
+<dt><span class="sect2"><a href="ddlchanges.html#id521746">14.2.  Testing DDL Changes </a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="usingslonik.html">15. Using Slonik</a></span></dt>
 <dt><span class="sect1"><a href="slonikshell.html">16.  Embedding Slonik in Shell Scripts </a></span></dt>
@@ -88,58 +89,62 @@
 Functions </a></span></dt>
 <dt><span class="sect1"><a href="altperl.html">18. <span class="productname">Slony-I</span> Administration Scripts</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="altperl.html#id522344">18.1. Node/Cluster Configuration - cluster.nodes</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522444">18.2. Set configuration - cluster.set1, cluster.set2</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522560">18.3. slonik_build_env</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522602">18.4. slonik_create_set</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522627">18.5. slonik_drop_node</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522641">18.6. slonik_drop_set</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522660">18.7. slonik_execute_script</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522667">18.8. slonik_failover</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522675">18.9. slonik_init_cluster</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522691">18.10. slonik_merge_sets</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522698">18.11. slonik_move_set</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522706">18.12. replication_test</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522721">18.13. slonik_restart_node</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522730">18.14. slonik_restart_nodes</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522738">18.15. slony_show_configuration</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522750">18.16. slon_kill</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522759">18.17. slon_start</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522768">18.18. slon_watchdog</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522781">18.19. slon_watchdog2</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522801">18.20. slonik_store_node</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522809">18.21. slonik_subscribe_set</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522817">18.22. slonik_uninstall_nodes</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522837">18.23. slonik_unsubscribe_set</a></span></dt>
-<dt><span class="sect2"><a href="altperl.html#id522844">18.24. slonik_update_nodes</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id522712">18.1. Node/Cluster Configuration - cluster.nodes</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id522846">18.2. Set configuration - cluster.set1, cluster.set2</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id522962">18.3. slonik_build_env</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523005">18.4. slonik_create_set</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523029">18.5. slonik_drop_node</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523044">18.6. slonik_drop_set</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523062">18.7. slonik_execute_script</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523070">18.8. slonik_failover</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523078">18.9. slonik_init_cluster</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523094">18.10. slonik_merge_sets</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523101">18.11. slonik_move_set</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523109">18.12. replication_test</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523123">18.13. slonik_restart_node</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523133">18.14. slonik_restart_nodes</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523141">18.15. slony_show_configuration</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523153">18.16. slon_kill</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523162">18.17. slon_start</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523171">18.18. slon_watchdog</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523184">18.19. slon_watchdog2</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523204">18.20. slonik_store_node</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523212">18.21. slonik_subscribe_set</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523220">18.22. slonik_uninstall_nodes</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523240">18.23. slonik_unsubscribe_set</a></span></dt>
+<dt><span class="sect2"><a href="altperl.html#id523247">18.24. slonik_update_nodes</a></span></dt>
 <dt><span class="sect2"><a href="altperl.html#regenlisten">18.25. regenerate-listens</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="versionupgrade.html">19. Using <span class="productname">Slony-I</span> for <span class="productname">PostgreSQL</span> Upgrades</a></span></dt>
 <dt><span class="sect1"><a href="bestpractices.html">20.  <span class="productname">Slony-I</span> &#8220;<span class="quote">Best Practices</span>&#8221; </a></span></dt>
-<dt><span class="sect1"><a href="help.html">21. More <span class="productname">Slony-I</span> Help</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="help.html#id524802">21.1.  Other Information Sources</a></span></dt></dl></dd>
+<dt><span class="sect1"><a href="testbed.html">21.  <span class="productname">Slony-I</span> Test Bed Framework </a></span></dt>
+<dt><span class="sect1"><a href="help.html">22. More <span class="productname">Slony-I</span> Help</a></span></dt>
+<dd><dl><dt><span class="sect2"><a href="help.html#id525518">22.1.  Other Information Sources</a></span></dt></dl></dd>
 </dl>
 </div>
 <div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="firstdb"></a>1. Replicating Your First Database</h2></div></div></div>
-<a name="id515129"></a><p>In this example, we will be replicating a brand new pgbench
-database.  The mechanics of replicating an existing database are
-covered here, however we recommend that you learn how <span class="productname">Slony-I</span>
-functions by using a fresh new non-production database.</p>
-<p> Note that <span class="application">pgbench</span> is a "benchmark"
-tool that is in the <span class="productname">PostgreSQL</span> set of <code class="filename">contrib</code>
-tools. If you build <span class="productname">PostgreSQL</span> from source, you can readily head
-to <code class="filename">contrib/pgbench</code> and do a <code class="command">make
-install</code> to build and install it; it is not always included in
-packaged binary <span class="productname">PostgreSQL</span> installations.</p>
+<a name="id515083"></a><p>In this example, we will be replicating a brand new
+<span class="application">pgbench</span> database.  The mechanics of
+replicating an existing database are covered here, however we
+recommend that you learn how <span class="productname">Slony-I</span> functions by using a fresh new
+non-production database.</p>
+<p> Note that <span class="application">pgbench</span> is a
+&#8220;<span class="quote">benchmark</span>&#8221; tool that is in the <span class="productname">PostgreSQL</span> set of
+<code class="filename">contrib</code> tools. If you build <span class="productname">PostgreSQL</span> from
+source, you can readily head to <code class="filename">contrib/pgbench</code>
+and do a <code class="command">make install</code> to build and install it; you
+may discover that included in packaged binary <span class="productname">PostgreSQL</span>
+installations.</p>
 <p>The <span class="productname">Slony-I</span> replication engine is trigger-based, allowing us to
 replicate databases (or portions thereof) running under the same
 postmaster.</p>
-<p>This example will show how to replicate the pgbench database
-running on localhost (master) to the pgbench slave database also
-running on localhost (slave).  We make a couple of assumptions about
-your <span class="productname">PostgreSQL</span> configuration:
+<p>This example will show how to replicate the
+<span class="application">pgbench</span> database running on localhost
+(master) to the <span class="application">pgbench</span> slave database also running on localhost
+(slave).  We make a couple of assumptions about your <span class="productname">PostgreSQL</span>
+configuration:
 
 </p>
 <div class="itemizedlist"><ul type="disc">
@@ -183,12 +188,12 @@ <h3 class="title">Warning</h3>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id515383"></a>1.1. Creating the pgbenchuser</h3></div></div></div>
+<a name="id515431"></a>1.1. Creating the <span class="application">pgbench</span> user</h3></div></div></div>
 <p><code class="command">createuser -A -D $PGBENCHUSER</code></p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id515394"></a>1.2. Preparing the databases</h3></div></div></div>
+<a name="id515448"></a>1.2. Preparing the databases</h3></div></div></div>
 <pre class="programlisting">createdb -O $PGBENCHUSER -h $MASTERHOST $MASTERDBNAME
 createdb -O $PGBENCHUSER -h $SLAVEHOST $SLAVEDBNAME
 pgbench -i -s 1 -U $PGBENCHUSER -h $MASTERHOST $MASTERDBNAME</pre>
@@ -222,13 +227,13 @@ <h3 class="title">Warning</h3>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id515514"></a>1.3. Configuring the Database for Replication.</h3></div></div></div>
+<a name="id515566"></a>1.3. Configuring the Database for Replication.</h3></div></div></div>
 <p>Creating the configuration tables, stored procedures, triggers
 and configuration is all done through the <a href="slonik.html" title="slonik"><span class="refentrytitle"><a name="app-slonik-title"></a><span class="application">slonik</span></span></a>
 tool. It is a specialized scripting aid that mostly calls stored
 procedures in the master/slave (node) databases.  The script to create
 the initial configuration for the simple master-slave setup of our
-pgbench database looks like this:
+<span class="application">pgbench</span> database looks like this:
 
 </p>
 <pre class="programlisting">#!/bin/sh
@@ -308,9 +313,9 @@ <h3 class="title">Warning</h3>
 other messages, we aren't replicating any data yet.  The notices you
 are seeing is the synchronization of cluster configurations between
 the 2 <a href="slon.html" title="slon"><span class="refentrytitle"><a name="app-slon-title"></a><span class="application">slon</span></span></a> processes.</p>
-<p>To start replicating the 4 pgbench tables (set 1) from the
-master (node id 1) the the slave (node id 2), execute the following
-script.
+<p>To start replicating the 4 <span class="application">pgbench</span>
+tables (set 1) from the master (node id 1) the the slave (node id 2),
+execute the following script.
 
 </p>
 <pre class="programlisting">#!/bin/sh
@@ -334,12 +339,13 @@ <h3 class="title">Warning</h3>
 	 # ----
 	 subscribe set ( id = 1, provider = 1, receiver = 2, forward = no);
 _EOF_</pre>
-<p>Any second now, the replication daemon on <code class="envar">$SLAVEHOST</code> will start
-to copy the current content of all 4 replicated tables.  While doing
-so, of course, the pgbench application will continue to modify the
-database.  When the copy process is finished, the replication daemon
-on <code class="envar">$SLAVEHOST</code> will start to catch up by applying the
-accumulated replication log.  It will do this in little steps, 10
+<p>Any second now, the replication daemon on
+<code class="envar">$SLAVEHOST</code> will start to copy the current content of
+all 4 replicated tables.  While doing so, of course, the
+<span class="application">pgbench</span> application will continue to modify
+the database.  When the copy process is finished, the replication
+daemon on <code class="envar">$SLAVEHOST</code> will start to catch up by applying
+the accumulated replication log.  It will do this in little steps, 10
 seconds worth of application work at a time.  Depending on the
 performance of the two systems involved, the sizing of the two
 databases, the actual transaction load and how well the two databases
diff --git a/docs/en_US/slony/slonyintro.html b/docs/en_US/slony/slonyintro.html
index f495fd55f7..e2956fb6b6 100644
--- a/docs/en_US/slony/slonyintro.html
+++ b/docs/en_US/slony/slonyintro.html
@@ -5,9 +5,9 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
-<link rel="up" href="index.html" title="Slony-I HEAD_20051102 Documentation">
-<link rel="prev" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
+<link rel="up" href="index.html" title="Slony-I HEAD_20051208 Documentation">
+<link rel="prev" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="next" href="slonylistenercosts.html" title="2.  Slony-I Communications
 Costs">
 </head>
@@ -22,47 +22,47 @@
 <dl>
 <dt><span class="sect1"><a href="slonyintro.html#introduction">1. Introduction to <span class="productname">Slony-I</span></a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="slonyintro.html#id514281">1.1. What <span class="productname">Slony-I</span> is</a></span></dt>
-<dt><span class="sect2"><a href="slonyintro.html#id459618">1.2. Why yet another replication system?</a></span></dt>
-<dt><span class="sect2"><a href="slonyintro.html#id459639">1.3.  What <span class="productname">Slony-I</span> is not</a></span></dt>
-<dt><span class="sect2"><a href="slonyintro.html#id459737">1.4.  Why doesn't <span class="productname">Slony-I</span> do automatic fail-over/promotion?</a></span></dt>
-<dt><span class="sect2"><a href="slonyintro.html#id459823">1.5.  Current Limitations</a></span></dt>
-<dt><span class="sect2"><a href="slonyintro.html#id459938">1.6. Replication Models</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id486434">1.1. What <span class="productname">Slony-I</span> is</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id459615">1.2. Why yet another replication system?</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id459634">1.3.  What <span class="productname">Slony-I</span> is not</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id459733">1.4.  Why doesn't <span class="productname">Slony-I</span> do automatic fail-over/promotion?</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id459819">1.5.  Current Limitations</a></span></dt>
+<dt><span class="sect2"><a href="slonyintro.html#id459934">1.6. Replication Models</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="slonylistenercosts.html">2.  <span class="productname">Slony-I</span> Communications
 Costs</a></span></dt>
 <dt><span class="sect1"><a href="requirements.html">3. System Requirements</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="requirements.html#id460225">3.1.  <span class="productname">Slony-I</span> Software Dependancies</a></span></dt>
-<dt><span class="sect2"><a href="requirements.html#id461008">3.2.  Getting <span class="productname">Slony-I</span> Source</a></span></dt>
+<dt><span class="sect2"><a href="requirements.html#id460221">3.1.  <span class="productname">Slony-I</span> Software Dependancies</a></span></dt>
+<dt><span class="sect2"><a href="requirements.html#id486473">3.2.  Getting <span class="productname">Slony-I</span> Source</a></span></dt>
 <dt><span class="sect2"><a href="requirements.html#times">3.3.  Time Synchronization</a></span></dt>
-<dt><span class="sect2"><a href="requirements.html#id503538">3.4.  Network Connectivity</a></span></dt>
+<dt><span class="sect2"><a href="requirements.html#id486679">3.4.  Network Connectivity</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="installation.html">4. <span class="productname">Slony-I</span> Installation</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="installation.html#id503803">4.1. Short Version</a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id503820">4.2. Configuration</a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id503885">4.3. Example</a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id503978">4.4. Build</a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id504038">4.5.  Installing <span class="productname">Slony-I</span></a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id504085">4.6.  Installing <span class="productname">Slony-I</span> from RPMs</a></span></dt>
-<dt><span class="sect2"><a href="installation.html#id504164">4.7.  Installing the <span class="productname">Slony-I</span> service on <span class="trademark">Windows</span>&#8482;</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id486943">4.1. Short Version</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id486960">4.2. Configuration</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id487026">4.3. Example</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id487118">4.4. Build</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id487178">4.5.  Installing <span class="productname">Slony-I</span></a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id487226">4.6.  Installing <span class="productname">Slony-I</span> from RPMs</a></span></dt>
+<dt><span class="sect2"><a href="installation.html#id487324">4.7.  Installing the <span class="productname">Slony-I</span> service on <span class="trademark">Windows</span>&#8482;</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="concepts.html">5. <span class="productname">Slony-I</span> Concepts</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="concepts.html#id504363">5.1. Cluster</a></span></dt>
-<dt><span class="sect2"><a href="concepts.html#id514321">5.2. Node</a></span></dt>
-<dt><span class="sect2"><a href="concepts.html#id514402">5.3.  Replication Set</a></span></dt>
-<dt><span class="sect2"><a href="concepts.html#id514432">5.4.  Origin, Providers and Subscribers</a></span></dt>
-<dt><span class="sect2"><a href="concepts.html#id514498">5.5. slon Daemon</a></span></dt>
-<dt><span class="sect2"><a href="concepts.html#id514562">5.6. slonik Configuration Processor</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514215">5.1. Cluster</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514273">5.2. Node</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514356">5.3.  Replication Set</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514386">5.4.  Origin, Providers and Subscribers</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514451">5.5. slon Daemon</a></span></dt>
+<dt><span class="sect2"><a href="concepts.html#id514515">5.6. slonik Configuration Processor</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="cluster.html">6. Defining <span class="productname">Slony-I</span> Clusters</a></span></dt>
 <dt><span class="sect1"><a href="definingsets.html">7. Defining <span class="productname">Slony-I</span> Replication Sets</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="definingsets.html#id514692">7.1. Primary Keys</a></span></dt>
+<dt><span class="sect2"><a href="definingsets.html#id514645">7.1. Primary Keys</a></span></dt>
 <dt><span class="sect2"><a href="definingsets.html#definesets">7.2. Grouping tables into sets</a></span></dt>
-<dt><span class="sect2"><a href="definingsets.html#id514982">7.3.  The Pathology of Sequences </a></span></dt>
+<dt><span class="sect2"><a href="definingsets.html#id514935">7.3.  The Pathology of Sequences </a></span></dt>
 </dl></dd>
 </dl>
 </div>
@@ -71,7 +71,7 @@
 <a name="introduction"></a>1. Introduction to <span class="productname">Slony-I</span></h2></div></div></div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id514281"></a>1.1. What <span class="productname">Slony-I</span> is</h3></div></div></div>
+<a name="id486434"></a>1.1. What <span class="productname">Slony-I</span> is</h3></div></div></div>
 <p><span class="productname">Slony-I</span> is a &#8220;<span class="quote">master to multiple slaves</span>&#8221;
 replication system supporting cascading and slave promotion.  The big
 picture for the development of <span class="productname">Slony-I</span> is as a master-slave system
@@ -127,7 +127,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id459618"></a>1.2. Why yet another replication system?</h3></div></div></div>
+<a name="id459615"></a>1.2. Why yet another replication system?</h3></div></div></div>
 <p><span class="productname">Slony-I</span> was born from an idea to create a replication system
 that was not tied to a specific version of <span class="productname">PostgreSQL</span>, which is
 allowed to be started and stopped on an existing database without the
@@ -135,7 +135,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id459639"></a>1.3.  What <span class="productname">Slony-I</span> is not</h3></div></div></div>
+<a name="id459634"></a>1.3.  What <span class="productname">Slony-I</span> is not</h3></div></div></div>
 <div class="itemizedlist"><ul type="disc">
 <li><p><span class="productname">Slony-I</span> is not a network management system.</p></li>
 <li>
@@ -163,7 +163,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id459737"></a>1.4.  Why doesn't <span class="productname">Slony-I</span> do automatic fail-over/promotion?</h3></div></div></div>
+<a name="id459733"></a>1.4.  Why doesn't <span class="productname">Slony-I</span> do automatic fail-over/promotion?</h3></div></div></div>
 <p>Determining whether a node has &#8220;<span class="quote">failed</span>&#8221; is properly
 the responsibility of network management software, not <span class="productname">Slony-I</span>.  The
 configuration, fail-over paths, and preferred policies will be
@@ -185,7 +185,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id459823"></a>1.5.  Current Limitations</h3></div></div></div>
+<a name="id459819"></a>1.5.  Current Limitations</h3></div></div></div>
 <p><span class="productname">Slony-I</span> does not automatically propagate schema changes, nor
 does it have any ability to replicate large objects.  There is a
 single common reason for these limitations, namely that <span class="productname">Slony-I</span>
@@ -216,7 +216,7 @@
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id459938"></a>1.6. Replication Models</h3></div></div></div>
+<a name="id459934"></a>1.6. Replication Models</h3></div></div></div>
 <p>There are a number of distinct models for database replication;
 it is impossible for one replication system to be all things to all
 people.</p>
diff --git a/docs/en_US/slony/slonylistenercosts.html b/docs/en_US/slony/slonylistenercosts.html
index 314b5c74ee..2dddb5d4e1 100644
--- a/docs/en_US/slony/slonylistenercosts.html
+++ b/docs/en_US/slony/slonylistenercosts.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyintro.html" title="Slony-I Introduction">
 <link rel="prev" href="slonyintro.html" title="Slony-I Introduction">
 <link rel="next" href="requirements.html" title="3. System Requirements">
diff --git a/docs/en_US/slony/stmtcreateset.html b/docs/en_US/slony/stmtcreateset.html
index 70b0c0fec1..a657d38d14 100644
--- a/docs/en_US/slony/stmtcreateset.html
+++ b/docs/en_US/slony/stmtcreateset.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmttableaddkey.html" title="TABLE ADD KEY">
 <link rel="next" href="stmtdropset.html" title="DROP SET">
@@ -22,7 +22,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">CREATE SET (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534124"></a><h2>Description</h2>
+<a name="id534821"></a><h2>Description</h2>
 <p>     In the <span class="productname">Slony-I</span> replication system,
      replicated tables are organized in sets. As a general rule of
      thumb, a set should contain all the tables of one application,
@@ -46,10 +46,10 @@ <h2>Synopsis</h2>
 <dt><span class="term"><code class="literal"> COMMENT = 'string' </code></span></dt>
 <dd><p> A descriptive text added to the set entry.</p></dd>
 </dl></div>
-<p> This uses <a href="function.storeset-integer-text.html">schemadocstoreset( integer, text )</a>. </p>
+<p> This uses <a href="function.storeset-integer-text.html">schemadocstoreset( integer, text )</a> . </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534226"></a><h2>Example</h2>
+<a name="id534923"></a><h2>Example</h2>
 <pre class="programlisting">     CREATE SET ( ID = 1, 
                ORIGIN = 1,
                COMMENT = 'Tables for ticketing system' );
diff --git a/docs/en_US/slony/stmtddlscript.html b/docs/en_US/slony/stmtddlscript.html
index 614bc79ab6..4783f70a29 100644
--- a/docs/en_US/slony/stmtddlscript.html
+++ b/docs/en_US/slony/stmtddlscript.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtfailover.html" title="FAILOVER">
 <link rel="next" href="stmtupdatefunctions.html" title="UPDATE FUNCTIONS">
@@ -21,18 +21,19 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">EXECUTE SCRIPT (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id536303"></a><h2>Description</h2>
+<a name="id537061"></a><h2>Description</h2>
 <p> Executes a script containing arbitrary SQL statements on
      all nodes that are subscribed to a set at a common controlled
      point within the replication transaction stream.</p>
 <p> The specified event origin must be the origin of the set.
-     The script file must not contain any <code class="command">START</code> or
-     <code class="command">COMMIT TRANSACTION</code> calls.  (This may change in
-     PostgreSQL 8.0 once nested transactions, aka savepoints, are
-     supported) In addition, non-deterministic DML statements (like
-     updating a field with <code class="function">CURRENT_TIMESTAMP</code>) must
-     be avoided, since the data changes done by the script are
-     explicitly not replicated. </p>
+    The script file must not contain any <code class="command">START</code> or
+    <code class="command">COMMIT TRANSACTION</code> calls.  (This changes
+    somewhat in <span class="productname">PostgreSQL</span> 8.0 once nested transactions, aka
+    savepoints, are supported) In addition, non-deterministic DML
+    statements (like updating a field with
+    <code class="function">CURRENT_TIMESTAMP</code>) must be avoided, since the
+    data changes done by the script are explicitly not
+    replicated. </p>
 <div class="variablelist"><dl>
 <dt><span class="term"><code class="literal"> SET ID = ival </code></span></dt>
 <dd><p> The unique numeric ID number of the set affected by the script</p></dd>
@@ -57,9 +58,8 @@ <h2>Synopsis</h2>
 	subscribed to the set.</p></dd>
 </dl></div>
 <p> See also the warnings in <a href="ddlchanges.html" title="14. Database Schema Changes (DDL)">Section 14, &#8220;Database Schema Changes (DDL)&#8221;</a>.</p>
-<p> Note that this is a <a href="locking.html" title="10. Locking Issues"> locking
-    operation, </a> which means that it can get stuck behind other
-    database activity.</p>
+<p> Note that this is a <a href="locking.html" title="10. Locking Issues"> locking </a> operation, which means that
+    it can get stuck behind other database activity.</p>
 <p> At the start of this event, all tables in the specified set
     are unlocked via the function
     <code class="function">alterTableRestore(tab_id)</code>.  After the SQL
@@ -72,10 +72,18 @@ <h2>Synopsis</h2>
 <p> If a table's columns are modified, it is very important
     that the triggers be regenerated, otherwise they may be
     inappropriate for the new form of the table schema.</p>
+<p> Note that if you need to make reference to the cluster
+    name, you can use the token <code class="command">@CLUSTERNAME@</code>; if
+    you need to make reference to the <span class="productname">Slony-I</span> namespace, you can use
+    the token <code class="command">@NAMESPACE@</code>; both will be expanded
+    into the appropriate replacement tokens. </p>
+<p> It generally seems a bad idea to use quotes in DDL scripts.
+    It appears preferable to handle that sort of thing &#8220;<span class="quote">out of
+    band.</span>&#8221; </p>
 <p> This uses <a href="function.ddlscript-integer-text-integer.html">schemadocddlscript( integer, text, integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id536490"></a><h2>Example</h2>
+<a name="id537289"></a><h2>Example</h2>
 <pre class="programlisting">EXECUTE SCRIPT (
    SET ID = 1,
    FILENAME = '/tmp/changes_2004-05-01.sql',
diff --git a/docs/en_US/slony/stmtdefine.html b/docs/en_US/slony/stmtdefine.html
index a8c82d0bf0..8127c5cfea 100644
--- a/docs/en_US/slony/stmtdefine.html
+++ b/docs/en_US/slony/stmtdefine.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="metacmds.html" title="Slonik Meta Commands">
 <link rel="prev" href="stmtinclude.html" title="INCLUDE">
 <link rel="next" href="hdrcmds.html" title="Slonik Preamble Commands">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">define </code> [<em class="replaceable"><code> name </code></em>] [<em class="replaceable"><code> value </code></em>]</p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532253"></a><h2>Description</h2>
+<a name="id532901"></a><h2>Description</h2>
 <p>      This defines a named symbol.  Symbol names must follow the
       slonik rules for constructing identifiers, by starting with a
       letter, followed by letters, numbers, and underscores.
@@ -35,7 +35,7 @@ <h2>Synopsis</h2>
     </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532276"></a><h2>Example</h2>
+<a name="id532924"></a><h2>Example</h2>
 <pre class="programlisting">define    cluster movies;
 define    sakai   1;
 define    chen    2;
diff --git a/docs/en_US/slony/stmtdroplisten.html b/docs/en_US/slony/stmtdroplisten.html
index 441b4ffd5b..39eb53ccd8 100644
--- a/docs/en_US/slony/stmtdroplisten.html
+++ b/docs/en_US/slony/stmtdroplisten.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtstorelisten.html" title="STORE LISTEN">
 <link rel="next" href="stmttableaddkey.html" title="TABLE ADD KEY">
@@ -23,7 +23,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">DROP LISTEN (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533853"></a><h2>Description</h2>
+<a name="id534545"></a><h2>Description</h2>
 <p> Remove a &#8220;<span class="quote">listen</span>&#8221; configuration entry. </p>
 <div class="variablelist"><dl>
 <dt><span class="term"><code class="literal"> ORIGIN  = ival </code></span></dt>
@@ -38,7 +38,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.droplisten-integer-integer-integer.html">schemadocdroplisten( integer, integer, integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533917"></a><h2>Example</h2>
+<a name="id534608"></a><h2>Example</h2>
 <pre class="programlisting">     DROP LISTEN ( ORIGIN = 1, RECEIVER = 2, PROVIDER = 3 );
     </pre>
 </div>
diff --git a/docs/en_US/slony/stmtdropnode.html b/docs/en_US/slony/stmtdropnode.html
index 28a932f921..3387f3be9b 100644
--- a/docs/en_US/slony/stmtdropnode.html
+++ b/docs/en_US/slony/stmtdropnode.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtstorenode.html" title="STORE NODE">
 <link rel="next" href="stmtuninstallnode.html" title="UNINSTALL NODE">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">DROP NODE (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533083"></a><h2>Description</h2>
+<a name="id533761"></a><h2>Description</h2>
 <p>     Drop a node. This command removes the specified node entirely
      from the replication systems configuration. If the replication
      daemon is still running on that node (and processing events), it
@@ -46,14 +46,13 @@ <h3 class="title">Warning</h3>
    (this is particularly common for Java application frameworks with
    connection pools), the connections may cache query plans that
    include the pre-<code class="command">DROP NODE</code> state of things, and
-   you will get <a href="faq.html#missingoids"> error messages indicating
-   missing OIDs</a>.</p>
+   you will get <a href="faq.html#missingoids">error messages indicating missing OIDs</a>.</p>
 <p>After dropping a node, you may also need to recycle
    connections in your application.</p>
 </div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533176"></a><h2>Example</h2>
+<a name="id533854"></a><h2>Example</h2>
 <pre class="programlisting">     DROP NODE ( ID = 2 );
     </pre>
 </div>
diff --git a/docs/en_US/slony/stmtdroppath.html b/docs/en_US/slony/stmtdroppath.html
index 3d67ed1ead..4874839920 100644
--- a/docs/en_US/slony/stmtdroppath.html
+++ b/docs/en_US/slony/stmtdroppath.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtstorepath.html" title="STORE
      PATH">
@@ -22,7 +22,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">DROP PATH (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533603"></a><h2>Description</h2>
+<a name="id534290"></a><h2>Description</h2>
 <p> 	Remove the connection information between &#8220;<span class="quote">server</span>&#8221; and
      &#8220;<span class="quote">client</span>&#8221;.</p>
 <div class="variablelist"><dl>
@@ -38,7 +38,7 @@ <h2>Synopsis</h2>
 </dl></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533662"></a><h2>Example</h2>
+<a name="id534349"></a><h2>Example</h2>
 <pre class="programlisting">  DROP PATH ( SERVER = 1, CLIENT = 2 );
     </pre>
 </div>
diff --git a/docs/en_US/slony/stmtdropset.html b/docs/en_US/slony/stmtdropset.html
index 6c5e416b95..996052b708 100644
--- a/docs/en_US/slony/stmtdropset.html
+++ b/docs/en_US/slony/stmtdropset.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtcreateset.html" title="CREATE SET">
 <link rel="next" href="stmtmergeset.html" title="MERGE
@@ -23,7 +23,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">DROP SET (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534269"></a><h2>Description</h2>
+<a name="id534968"></a><h2>Description</h2>
 <p>     Drop a set of tables from the <span class="productname">Slony-I</span>
      configuration. This automatically unsubscribes all nodes from the
      set and restores the original triggers and rules on all
@@ -38,7 +38,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.dropset-integer.html">schemadocdropset( integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534321"></a><h2>Example</h2>
+<a name="id535021"></a><h2>Example</h2>
 <pre class="programlisting">  DROP SET ( ID = 5, 
              ORIGIN = 2 );
     </pre>
diff --git a/docs/en_US/slony/stmtdroptrigger.html b/docs/en_US/slony/stmtdroptrigger.html
index a787f81105..5d102f0bd0 100644
--- a/docs/en_US/slony/stmtdroptrigger.html
+++ b/docs/en_US/slony/stmtdroptrigger.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtstoretrigger.html" title="STORE TRIGGER">
 <link rel="next" href="stmtsubscribeset.html" title="SUBSCRIBE SET">
@@ -22,7 +22,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">DROP TRIGGER (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535383"></a><h2>Description</h2>
+<a name="id536114"></a><h2>Description</h2>
 <p> Remove the special handling for the specified trigger.
 
      </p>
@@ -43,7 +43,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.droptrigger-integer-name.html">schemadocdroptrigger( integer, name )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535448"></a><h2>Example</h2>
+<a name="id536179"></a><h2>Example</h2>
 <pre class="programlisting">DROP TRIGGER (
     TABLE ID = 2,
     TRIGGER NAME = 'cache_invalidation'
diff --git a/docs/en_US/slony/stmtecho.html b/docs/en_US/slony/stmtecho.html
index d1e1943064..b96cb618b0 100644
--- a/docs/en_US/slony/stmtecho.html
+++ b/docs/en_US/slony/stmtecho.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="cmds.html" title="Configuration and Action commmands">
 <link rel="next" href="stmtexit.html" title="EXIT">
@@ -21,12 +21,12 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">echo </code> [<em class="replaceable"><code> 'string'</code></em>]</p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532639"></a><h2>Description</h2>
+<a name="id533301"></a><h2>Description</h2>
 <p>     Prints the string literal on standard output.
     </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532647"></a><h2>Example</h2>
+<a name="id533308"></a><h2>Example</h2>
 <pre class="programlisting">     ECHO 'Node 1 initialized successfully';
     </pre>
 </div>
diff --git a/docs/en_US/slony/stmtexit.html b/docs/en_US/slony/stmtexit.html
index 12143c5e10..c1f92d0fb3 100644
--- a/docs/en_US/slony/stmtexit.html
+++ b/docs/en_US/slony/stmtexit.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtecho.html" title="ECHO">
 <link rel="next" href="stmtinitcluster.html" title="INIT CLUSTER">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">exit</code> [<em class="replaceable"><code> [-]ival</code></em>]</p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532693"></a><h2>Description</h2>
+<a name="id533357"></a><h2>Description</h2>
 <p>     Terminates script execution immediately, rolling back every
      open transaction on all database connections. The
      <span class="application">slonik</span> utility
@@ -29,7 +29,7 @@ <h2>Synopsis</h2>
     </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532710"></a><h2>Example</h2>
+<a name="id533374"></a><h2>Example</h2>
 <pre class="programlisting">     EXIT 0;
     </pre>
 </div>
diff --git a/docs/en_US/slony/stmtfailover.html b/docs/en_US/slony/stmtfailover.html
index 3fa0270ec6..9d35a2e62b 100644
--- a/docs/en_US/slony/stmtfailover.html
+++ b/docs/en_US/slony/stmtfailover.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtmoveset.html" title="MOVE SET">
 <link rel="next" href="stmtddlscript.html" title="EXECUTE SCRIPT">
@@ -22,7 +22,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">FAILOVER (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id536170"></a><h2>Description</h2>
+<a name="id536926"></a><h2>Description</h2>
 <p>     The <code class="command">FAILOVER</code> command causes the backup node to take over all sets
      that currently originate on the failed
      node. <span class="application">slonik</span> will contact all other
@@ -57,7 +57,7 @@ <h3 class="title">Warning</h3>
 <p> This uses <a href="function.failednode-integer-integer.html">schemadocfailednode( integer, integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id536267"></a><h2>Example</h2>
+<a name="id537023"></a><h2>Example</h2>
 <pre class="programlisting">FAILOVER (
    ID = 1,
    BACKUP NODE = 2
diff --git a/docs/en_US/slony/stmtinclude.html b/docs/en_US/slony/stmtinclude.html
index 8b0d5729a0..c536712229 100644
--- a/docs/en_US/slony/stmtinclude.html
+++ b/docs/en_US/slony/stmtinclude.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="metacmds.html" title="Slonik Meta Commands">
 <link rel="prev" href="metacmds.html" title="Slonik Meta Commands">
 <link rel="next" href="stmtdefine.html" title="DEFINE">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">include </code> [<em class="replaceable"><code> &lt;pathname&gt;</code></em>]</p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532170"></a><h2>Description</h2>
+<a name="id532815"></a><h2>Description</h2>
 <p>      This draws the specified slonik script inline into the present
       script.  If the <code class="option">pathname</code> specifies a relative
       path, <a href="slonik.html" title="slonik"><span class="refentrytitle"><a name="app-slonik-title"></a><span class="application">slonik</span></span></a> will search relative to the
@@ -32,7 +32,7 @@ <h2>Synopsis</h2>
       an error.  </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532196"></a><h2>Example</h2>
+<a name="id532841"></a><h2>Example</h2>
 <pre class="programlisting">     include &lt;/tmp/preamble.slonik&gt;;
     </pre>
 </div>
diff --git a/docs/en_US/slony/stmtinitcluster.html b/docs/en_US/slony/stmtinitcluster.html
index c89ad0afd6..33f38a5e40 100644
--- a/docs/en_US/slony/stmtinitcluster.html
+++ b/docs/en_US/slony/stmtinitcluster.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtexit.html" title="EXIT">
 <link rel="next" href="stmtstorenode.html" title="STORE NODE">
@@ -21,12 +21,12 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">INIT CLUSTER</code> [ID = <em class="replaceable"><code>integer</code></em>] [COMMENT = <em class="replaceable"><code>'string'</code></em>]</p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532777"></a><h2>Description</h2>
-<p> Initialize the first node in a new
-    <span class="productname">Slony-I</span> replication cluster.  The
-    initialization process consists of creating the cluster namespace,
-    loading all the base tables, functions, procedures and
-    initializing the node, using <a href="function.initializelocalnode-integer-text.html">schemadocinitializelocalnode( integer, text )</a> and <a href="function.enablenode-integer.html">schemadocenablenode( integer )</a>.
+<a name="id533443"></a><h2>Description</h2>
+<p> Initialize the first node in a new <span class="productname">Slony-I</span> replication
+    cluster.  The initialization process consists of creating the
+    cluster namespace, loading all the base tables, functions,
+    procedures and initializing the node, using
+    <a href="function.initializelocalnode-integer-text.html">schemadocinitializelocalnode( integer, text )</a> and <a href="function.enablenode-integer.html">schemadocenablenode( integer )</a>.
      
      </p>
 <div class="variablelist"><dl>
@@ -35,7 +35,7 @@ <h2>Synopsis</h2>
 <dt><span class="term"><code class="literal">COMMENT = 'comment
       text'</code></span></dt>
 <dd><p> A descriptive text added
-      to the node entry in the table <a href="table.sl-node.html">sl_node</a>.
+      to the node entry in the table <a href="table.sl-node.html">sl_node</a>. 
       </p></dd>
 </dl></div>
 <p>
@@ -47,12 +47,12 @@ <h2>Synopsis</h2>
     <span class="application">slonik</span> utility), while on the system
     where the node database is running the shared objects of the
     <span class="productname">Slony-I</span> system must be installed in the
-    PostgreSQL library directory. Also the procedural language
+    <span class="productname">PostgreSQL</span> library directory. Also the procedural language
     PL/pgSQL is assumed to already be installed in the target
     database.</p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532874"></a><h2>Example</h2>
+<a name="id533546"></a><h2>Example</h2>
 <pre class="programlisting">INIT CLUSTER (
    ID = 1,
    COMMENT = 'Node 1'
diff --git a/docs/en_US/slony/stmtlockset.html b/docs/en_US/slony/stmtlockset.html
index 2df249672a..95c0797a38 100644
--- a/docs/en_US/slony/stmtlockset.html
+++ b/docs/en_US/slony/stmtlockset.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtunsubscribeset.html" title="UNSUBSCRIBE SET">
 <link rel="next" href="stmtunlockset.html" title="UNLOCK SET">
@@ -23,7 +23,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">LOCK SET (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535811"></a><h2>Description</h2>
+<a name="id536550"></a><h2>Description</h2>
 <p> Guards a replication set against client application updates
     in preparation for a <a href="stmtmoveset.html" title="MOVE SET"><span class="refentrytitle">MOVE SET</span></a> command.
     </p>
@@ -34,9 +34,16 @@ <h2>Synopsis</h2>
     transaction to finish. At the same time it cannot hold an open
     transaction to the same database itself since this would result in
     blocking itself forever.</p>
-<p> Note that this is a <a href="locking.html" title="10. Locking Issues"> locking
-    operation, </a> which means that it can get stuck behind other
-    database activity.
+<p> Note that this is a <a href="locking.html" title="10. Locking Issues"> locking </a> operation, which means that
+    it can get stuck behind other database activity.</p>
+<p> The operation waits for transaction IDs to advance in order
+    that data is not missed on the new origin.  Thus, if you have
+    long-running transactions running on the source node, this
+    operation will wait for those transactions to complete.
+    Unfortunately, if you have another database on the same postmaster
+    as the origin node, long running transactions on that database
+    will also be considered even though they are essentially
+    independent.
      
      </p>
 <div class="variablelist"><dl>
@@ -50,7 +57,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.lockset-integer.html">schemadoclockset( integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535886"></a><h2>Example</h2>
+<a name="id536635"></a><h2>Example</h2>
 <pre class="programlisting">LOCK SET (
    ID = 1,
    RECEIVER = 3
diff --git a/docs/en_US/slony/stmtmergeset.html b/docs/en_US/slony/stmtmergeset.html
index 00b316f21c..34ef7e3c57 100644
--- a/docs/en_US/slony/stmtmergeset.html
+++ b/docs/en_US/slony/stmtmergeset.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtdropset.html" title="DROP SET">
 <link rel="next" href="stmtsetaddtable.html" title="SET ADD TABLE">
@@ -23,7 +23,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">MERGE SET (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534363"></a><h2>Description</h2>
+<a name="id535064"></a><h2>Description</h2>
 <p> Merge a set of tables and sequences into another one. This
      function is a workaround for the problem that it is not possible
      to add tables/sequences to already-subscribed sets. One may create
@@ -44,7 +44,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.mergeset-integer-integer.html">schemadocmergeset( integer, integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534434"></a><h2>Example</h2>
+<a name="id535135"></a><h2>Example</h2>
 <pre class="programlisting">     MERGE SET ( ID = 2, 
      ADD ID = 9999,
      ORIGIN = 1 );
diff --git a/docs/en_US/slony/stmtmoveset.html b/docs/en_US/slony/stmtmoveset.html
index 7c9d5c9f52..00c3bcf37e 100644
--- a/docs/en_US/slony/stmtmoveset.html
+++ b/docs/en_US/slony/stmtmoveset.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtunlockset.html" title="UNLOCK SET">
 <link rel="next" href="stmtfailover.html" title="FAILOVER">
@@ -22,7 +22,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">MOVE SET (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id536015"></a><h2>Description</h2>
+<a name="id536769"></a><h2>Description</h2>
 <p> Changes the origin of a set from one node to another. The
     new origin must be a current subscriber of the set. The set must
     currently be locked on the old origin. </p>
@@ -42,9 +42,8 @@ <h2>Synopsis</h2>
      instead of <code class="command">FAILOVER</code>, if at all possible, as
      <code class="command">FAILOVER</code> winds up discarding the old origin
      node as being corrupted.</p>
-<p> Note that this is a <a href="locking.html" title="10. Locking Issues"> locking
-    operation, </a> which means that it can get stuck behind other
-    database activity.
+<p> Note that this is a <a href="locking.html" title="10. Locking Issues"> locking </a> operation, which means that
+    it can get stuck behind other database activity.
      
      </p>
 <div class="variablelist"><dl>
@@ -60,7 +59,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.moveset-integer-integer.html">schemadocmoveset( integer, integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id536133"></a><h2>Example</h2>
+<a name="id536887"></a><h2>Example</h2>
 <pre class="programlisting">MOVE SET (
    ID = 1,
    OLD ORIGIN = 1,
diff --git a/docs/en_US/slony/stmtrestartnode.html b/docs/en_US/slony/stmtrestartnode.html
index 163d6700f5..47ee248248 100644
--- a/docs/en_US/slony/stmtrestartnode.html
+++ b/docs/en_US/slony/stmtrestartnode.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtuninstallnode.html" title="UNINSTALL NODE">
 <link rel="next" href="stmtstorepath.html" title="STORE
@@ -22,7 +22,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">RESTART NODE (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533366"></a><h2>Description</h2>
+<a name="id534049"></a><h2>Description</h2>
 <p> Causes an eventually running replication daemon on the
     specified node to shutdown and restart itself.  Theoretically,
     this command should be obsolete. In practice, TCP timeouts can
@@ -39,7 +39,7 @@ <h2>Synopsis</h2>
     </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533394"></a><h2>Example</h2>
+<a name="id534076"></a><h2>Example</h2>
 <pre class="programlisting">  RESTART NODE ( ID = 2 );
     </pre>
 </div>
diff --git a/docs/en_US/slony/stmtsetaddsequence.html b/docs/en_US/slony/stmtsetaddsequence.html
index 2b497f7ff3..f29877a914 100644
--- a/docs/en_US/slony/stmtsetaddsequence.html
+++ b/docs/en_US/slony/stmtsetaddsequence.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtsetaddtable.html" title="SET ADD TABLE">
 <link rel="next" href="stmtsetdroptable.html" title="SET DROP TABLE">
@@ -23,7 +23,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">SET ADD SEQUENCE (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534677"></a><h2>Description</h2>
+<a name="id535388"></a><h2>Description</h2>
 <p>     Add an existing user sequence to a replication set. The set
      cannot currently be subscribed by any other node - that
      functionality is supported by the <a href="stmtmergeset.html" title="MERGE
@@ -63,7 +63,7 @@ <h3 class="title">Note</h3>
 <p> This uses <a href="function.setaddsequence-integer-integer-text-text.html">schemadocsetaddsequence( integer, integer, text, text )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534789"></a><h2>Example</h2>
+<a name="id535500"></a><h2>Example</h2>
 <pre class="programlisting">     SET ADD SEQUENCE (
      SET ID = 1,
      ORIGIN = 1,
diff --git a/docs/en_US/slony/stmtsetaddtable.html b/docs/en_US/slony/stmtsetaddtable.html
index 667097a354..97b565335f 100644
--- a/docs/en_US/slony/stmtsetaddtable.html
+++ b/docs/en_US/slony/stmtsetaddtable.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtmergeset.html" title="MERGE
      SET">
@@ -23,7 +23,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">SET ADD TABLE (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534476"></a><h2>Description</h2>
+<a name="id535180"></a><h2>Description</h2>
 <p> Add an existing user table to a replication set. The set
     cannot currently be subscribed by any other node - that
     functionality is supported by the <a href="stmtmergeset.html" title="MERGE
@@ -34,19 +34,24 @@ <h2>Synopsis</h2>
      </p>
 <div class="variablelist"><dl>
 <dt><span class="term"><code class="literal"> SET ID = ival </code></span></dt>
-<dd><p> ID of the set to which the table is to be added.  </p></dd>
+<dd><p> ID of the set to which the table is to be added. </p></dd>
 <dt><span class="term"><code class="literal"> ORIGIN = ival </code></span></dt>
 <dd><p> Origin node for the set.  A future version of <span class="application">slonik</span>
 	 might figure out this information by itself.</p></dd>
 <dt><span class="term"><code class="literal"> ID = ival </code></span></dt>
-<dd><p> Unique ID of the table. These ID's are not
+<dd>
+<p> Unique ID of the table. These ID's are not
 	 only used to uniquely identify the individual table within the
 	 replication system. The numeric value of this ID also
 	 determines the order in which the tables are locked in a <a href="stmtlockset.html" title="LOCK SET"><span class="refentrytitle">LOCK SET</span></a> command for example. So
 	 these numbers should represent any applicable table hierarchy
 	 to make sure the <span class="application">slonik</span> command
 	 scripts do not deadlock at any critical
-	 moment.</p></dd>
+	 moment.</p>
+<p> This ID must be unique across all sets; you cannot
+         have two tables in the same cluster with the same
+         ID. </p>
+</dd>
 <dt><span class="term"><code class="literal"> FULLY QUALIFIED NAME = 'string' </code></span></dt>
 <dd><p> The full table name as described in
 	 <a href="stmttableaddkey.html" title="TABLE ADD KEY"><span class="refentrytitle">TABLE ADD KEY</span></a>.</p></dd>
@@ -66,7 +71,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.setaddtable-integer-integer-text-name-text.html">schemadocsetaddtable( integer, integer, text, name, text )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534632"></a><h2>Example</h2>
+<a name="id535341"></a><h2>Example</h2>
 <pre class="programlisting">SET ADD TABLE (
     SET ID = 1,
     ORIGIN = 1,
diff --git a/docs/en_US/slony/stmtsetdropsequence.html b/docs/en_US/slony/stmtsetdropsequence.html
index c6bf81e505..9916c739f2 100644
--- a/docs/en_US/slony/stmtsetdropsequence.html
+++ b/docs/en_US/slony/stmtsetdropsequence.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtsetdroptable.html" title="SET DROP TABLE">
 <link rel="next" href="stmtsetmovetable.html" title="SET MOVE
@@ -24,7 +24,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">SET DROP SEQUENCE (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534942"></a><h2>Description</h2>
+<a name="id535658"></a><h2>Description</h2>
 <p>     Drops an existing user sequence from a replication set.
      </p>
 <div class="variablelist"><dl>
@@ -39,7 +39,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.setdropsequence-integer.html">schemadocsetdropsequence( integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534995"></a><h2>Example</h2>
+<a name="id535711"></a><h2>Example</h2>
 <pre class="programlisting">     SET DROP SEQUENCE (
      ORIGIN = 1,
      ID = 20,
diff --git a/docs/en_US/slony/stmtsetdroptable.html b/docs/en_US/slony/stmtsetdroptable.html
index db4a532734..c3bfb89660 100644
--- a/docs/en_US/slony/stmtsetdroptable.html
+++ b/docs/en_US/slony/stmtsetdroptable.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtsetaddsequence.html" title="SET ADD SEQUENCE">
 <link rel="next" href="stmtsetdropsequence.html" title="SET DROP SEQUENCE">
@@ -23,7 +23,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">SET DROP TABLE (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534834"></a><h2>Description</h2>
+<a name="id535547"></a><h2>Description</h2>
 <p>     Drop a table from a replication set.
     </p>
 <p>     Note that this action will <span class="emphasis"><em> not </em></span> drop a
@@ -42,7 +42,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.setdroptable-integer.html">schemadocsetdroptable( integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534900"></a><h2>Example</h2>
+<a name="id535613"></a><h2>Example</h2>
 <pre class="programlisting">     SET DROP TABLE (
      ORIGIN = 1,
      ID = 20
diff --git a/docs/en_US/slony/stmtsetmovesequence.html b/docs/en_US/slony/stmtsetmovesequence.html
index 69d152f517..2bacf6f454 100644
--- a/docs/en_US/slony/stmtsetmovesequence.html
+++ b/docs/en_US/slony/stmtsetmovesequence.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtsetmovetable.html" title="SET MOVE
      TABLE">
@@ -24,7 +24,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">SET MOVE SEQUENCE (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535154"></a><h2>Description</h2>
+<a name="id535882"></a><h2>Description</h2>
 <p>     Change the set a sequence belongs to. The current set and the new
      set must originate on the same node and subscribed by the same
      nodes.
@@ -56,7 +56,7 @@ <h3 class="title">Caution</h3>
 <p> This uses <a href="function.setmovesequence-integer-integer.html">schemadocsetmovesequence( integer, integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535234"></a><h2>Example</h2>
+<a name="id535961"></a><h2>Example</h2>
 <pre class="programlisting">SET MOVE SEQUENCE (
     ORIGIN = 1,
     ID = 20,
diff --git a/docs/en_US/slony/stmtsetmovetable.html b/docs/en_US/slony/stmtsetmovetable.html
index ca2d2db35c..682360a589 100644
--- a/docs/en_US/slony/stmtsetmovetable.html
+++ b/docs/en_US/slony/stmtsetmovetable.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtsetdropsequence.html" title="SET DROP SEQUENCE">
 <link rel="next" href="stmtsetmovesequence.html" title="SET MOVE SEQUENCE">
@@ -24,7 +24,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">SET MOVE TABLE (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535038"></a><h2>Description</h2>
+<a name="id535756"></a><h2>Description</h2>
 <p>     Change the set a table belongs to. The current set and the new
      set must origin on the same node and subscribed by the same
      nodes.  </p>
@@ -55,7 +55,7 @@ <h3 class="title">Caution</h3>
 <p> This uses <a href="function.setmovetable-integer-integer.html">schemadocsetmovetable( integer, integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535111"></a><h2>Example</h2>
+<a name="id535836"></a><h2>Example</h2>
 <pre class="programlisting">SET MOVE TABLE (
     ORIGIN = 1,
     ID = 20,
diff --git a/docs/en_US/slony/stmtstorelisten.html b/docs/en_US/slony/stmtstorelisten.html
index 9b21dae4a0..05921ceffe 100644
--- a/docs/en_US/slony/stmtstorelisten.html
+++ b/docs/en_US/slony/stmtstorelisten.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtdroppath.html" title="DROP PATH">
 <link rel="next" href="stmtdroplisten.html" title="DROP LISTEN">
@@ -22,7 +22,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">STORE LISTEN (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533705"></a><h2>Description</h2>
+<a name="id534394"></a><h2>Description</h2>
 <p> A &#8220;<span class="quote">listen</span>&#8221; entry causes a node (receiver) to query an
      event provider for events that originate from a specific node, as
      well as confirmations from every existing node. It requires a
@@ -54,7 +54,7 @@ <h2>Synopsis</h2>
 <p> For more details, see <a href="listenpaths.html" title="8. Slony-I listen paths">Section 8, &#8220;<span class="productname">Slony-I</span> listen paths&#8221;</a>.</p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533810"></a><h2>Example</h2>
+<a name="id534499"></a><h2>Example</h2>
 <pre class="programlisting">     STORE LISTEN ( ORIGIN = 1, RECEIVER = 2, PROVIDER = 3 );
     </pre>
 </div>
diff --git a/docs/en_US/slony/stmtstorenode.html b/docs/en_US/slony/stmtstorenode.html
index 38a6812215..9b812bceeb 100644
--- a/docs/en_US/slony/stmtstorenode.html
+++ b/docs/en_US/slony/stmtstorenode.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtinitcluster.html" title="INIT CLUSTER">
 <link rel="next" href="stmtdropnode.html" title="DROP NODE">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">STORE NODE (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id532936"></a><h2>Description</h2>
+<a name="id533611"></a><h2>Description</h2>
 <p> Initialize a new node and add it to the configuration of an
     existing cluster.</p>
 <p> The initialization process consists of creating the cluster
@@ -39,9 +39,10 @@ <h2>Synopsis</h2>
 <dd><p> A descriptive text added to the node entry in the table <a href="table.sl-node.html">sl_node</a></p></dd>
 <dt><span class="term"><code class="literal"> SPOOLNODE = boolean </code></span></dt>
 <dd><p>Specifies that the new node is a virtual spool
-	 node for file archiving of replication log. If true
-	 <span class="application">slonik</span> will not attempt to initialize a database
-	 with the replication schema.</p></dd>
+       node for file archiving of replication log.  If true,
+       <span class="application">slonik</span> will not attempt to
+       initialize a database with the replication
+       schema.</p></dd>
 <dt><span class="term"><code class="literal"> EVENT NODE = ival </code></span></dt>
 <dd><p> The ID of the node used to create the configuration
 	 event that tells all existing nodes about the new node. Default
@@ -52,7 +53,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.initializelocalnode-integer-text.html">schemadocinitializelocalnode( integer, text )</a> and <a href="function.enablenode-integer.html">schemadocenablenode( integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533041"></a><h2>Example</h2>
+<a name="id533716"></a><h2>Example</h2>
 <pre class="programlisting">     STORE NODE ( ID = 2, COMMENT = 'Node 2');
     </pre>
 </div>
diff --git a/docs/en_US/slony/stmtstorepath.html b/docs/en_US/slony/stmtstorepath.html
index 457fe19237..35bdfd3bef 100644
--- a/docs/en_US/slony/stmtstorepath.html
+++ b/docs/en_US/slony/stmtstorepath.html
@@ -6,7 +6,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtrestartnode.html" title="RESTART NODE">
 <link rel="next" href="stmtdroppath.html" title="DROP PATH">
@@ -22,7 +22,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">STORE PATH (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533435"></a><h2>Description</h2>
+<a name="id534120"></a><h2>Description</h2>
 <p> Configures how the replication daemon of one node connects
      to the database of another node. If the replication system is
      supposed to use a special backbone network segment, this is the
@@ -62,7 +62,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.storepath-integer-integer-text-integer.html">schemadocstorepath( integer, integer, text, integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533560"></a><h2>Example</h2>
+<a name="id534244"></a><h2>Example</h2>
 <pre class="programlisting">STORE PATH ( SERVER = 1, CLIENT = 2, 
              CONNINFO = 'dbname=testdb host=server1 user=slony'
            );
diff --git a/docs/en_US/slony/stmtstoretrigger.html b/docs/en_US/slony/stmtstoretrigger.html
index 8b250c6b43..724744b9f0 100644
--- a/docs/en_US/slony/stmtstoretrigger.html
+++ b/docs/en_US/slony/stmtstoretrigger.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtsetmovesequence.html" title="SET MOVE SEQUENCE">
 <link rel="next" href="stmtdroptrigger.html" title="DROP TRIGGER">
@@ -23,7 +23,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">STORE TRIGGER (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535277"></a><h2>Description</h2>
+<a name="id536007"></a><h2>Description</h2>
 <p> By default, all user defined triggers and constraints are
      disabled on all subscriber nodes while a table is replicated. This
      command can be used to explicitly exclude a trigger from being
@@ -46,7 +46,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.storetrigger-integer-name.html">schemadocstoretrigger( integer, name )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535345"></a><h2>Example</h2>
+<a name="id536075"></a><h2>Example</h2>
 <pre class="programlisting">STORE TRIGGER (
     TABLE ID = 2,
     TRIGGER NAME = 'cache_invalidation'
diff --git a/docs/en_US/slony/stmtsubscribeset.html b/docs/en_US/slony/stmtsubscribeset.html
index 2fc9aa1a37..9c473d378b 100644
--- a/docs/en_US/slony/stmtsubscribeset.html
+++ b/docs/en_US/slony/stmtsubscribeset.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtdroptrigger.html" title="DROP TRIGGER">
 <link rel="next" href="stmtunsubscribeset.html" title="UNSUBSCRIBE SET">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">SUBSCRIBE SET (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535491"></a><h2>Description</h2>
+<a name="id536225"></a><h2>Description</h2>
 <p> Causes a node (subscriber) to start replicating a set of
     tables either from the origin or from another provider node, which
     must itself already be be an active, forwarding subscriber.</p>
@@ -87,7 +87,7 @@ <h3 class="title">Note</h3>
 <p> This uses <a href="function.subscribeset-integer-integer-integer-boolean.html">schemadocsubscribeset( integer, integer, integer, boolean )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535659"></a><h2>Example</h2>
+<a name="id536393"></a><h2>Example</h2>
 <pre class="programlisting">SUBSCRIBE SET (
    ID = 1,
    PROVIDER = 1,
diff --git a/docs/en_US/slony/stmttableaddkey.html b/docs/en_US/slony/stmttableaddkey.html
index 22e9fdca36..3775258333 100644
--- a/docs/en_US/slony/stmttableaddkey.html
+++ b/docs/en_US/slony/stmttableaddkey.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtdroplisten.html" title="DROP LISTEN">
 <link rel="next" href="stmtcreateset.html" title="CREATE SET">
@@ -23,7 +23,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">TABLE ADD KEY (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533959"></a><h2>Description</h2>
+<a name="id534653"></a><h2>Description</h2>
 <p>     In the <span class="productname">Slony-I</span> replication system,
      every replicated table is required to have at least one
      <code class="command">UNIQUE</code> constraint whose columns are
@@ -58,7 +58,7 @@ <h3 class="title">Note</h3>
 <p> This uses <a href="function.tableaddkey-text.html">schemadoctableaddkey( text )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id534081"></a><h2>Example</h2>
+<a name="id534775"></a><h2>Example</h2>
 <pre class="programlisting">     TABLE ADD KEY ( NODE ID = 1, 
      FULLY QUALIFIED NAME = 'public.history' );
     </pre>
diff --git a/docs/en_US/slony/stmtuninstallnode.html b/docs/en_US/slony/stmtuninstallnode.html
index b4a157082f..b498006a01 100644
--- a/docs/en_US/slony/stmtuninstallnode.html
+++ b/docs/en_US/slony/stmtuninstallnode.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtdropnode.html" title="DROP NODE">
 <link rel="next" href="stmtrestartnode.html" title="RESTART NODE">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">UNINSTALL NODE (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533218"></a><h2>Description</h2>
+<a name="id533897"></a><h2>Description</h2>
 <p> Restores all tables to the unlocked state, with all
      original user triggers, constraints and rules, eventually added
      <span class="productname">Slony-I</span> specific serial key columns
@@ -47,14 +47,13 @@ <h3 class="title">Warning</h3>
    (this is particularly common for Java application frameworks with
    connection pools), the connections may cache query plans that
    include the pre-<code class="command">UNINSTALL NODE</code> state of things,
-   and you will get <a href="faq.html#missingoids"> error messages
-   indicating missing OIDs</a>.</p>
+   and you will get <a href="faq.html#missingoids">error messages indicating missing OIDs</a>.</p>
 <p>After dropping a node, you may also need to recycle
    connections in your application.</p>
 </div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id533325"></a><h2>Example</h2>
+<a name="id534005"></a><h2>Example</h2>
 <pre class="programlisting">  UNINSTALL NODE ( ID = 2 );
     </pre>
 </div>
diff --git a/docs/en_US/slony/stmtunlockset.html b/docs/en_US/slony/stmtunlockset.html
index e0c9950fe3..15264cba20 100644
--- a/docs/en_US/slony/stmtunlockset.html
+++ b/docs/en_US/slony/stmtunlockset.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtlockset.html" title="LOCK SET">
 <link rel="next" href="stmtmoveset.html" title="MOVE SET">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">UNLOCK SET (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535928"></a><h2>Description</h2>
+<a name="id536679"></a><h2>Description</h2>
 <p> 
      Unlocks a previously locked set.
      
@@ -37,7 +37,7 @@ <h2>Synopsis</h2>
 <p> This uses <a href="function.unlockset-integer.html">schemadocunlockset( integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535973"></a><h2>Example</h2>
+<a name="id536724"></a><h2>Example</h2>
 <pre class="programlisting">UNLOCK SET (
    ID = 1,
    RECEIVER = 3
diff --git a/docs/en_US/slony/stmtunsubscribeset.html b/docs/en_US/slony/stmtunsubscribeset.html
index 0208e37394..7ccd458cce 100644
--- a/docs/en_US/slony/stmtunsubscribeset.html
+++ b/docs/en_US/slony/stmtunsubscribeset.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtsubscribeset.html" title="SUBSCRIBE SET">
 <link rel="next" href="stmtlockset.html" title="LOCK SET">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">UNSUBSCRIBE SET (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535702"></a><h2>Description</h2>
+<a name="id536438"></a><h2>Description</h2>
 <p> Stops the subscriber from replicating the set. The tables
      are opened up for full access by the client application on the
      former subscriber. The tables are not truncated or otherwise
@@ -50,7 +50,7 @@ <h3 class="title">Warning</h3>
 <p> This uses <a href="function.unsubscribeset-integer-integer.html">schemadocunsubscribeset( integer, integer )</a>. </p>
 </div>
 <div class="refsect1" lang="en">
-<a name="id535763"></a><h2>Example</h2>
+<a name="id536499"></a><h2>Example</h2>
 <pre class="programlisting">UNSUBSCRIBE SET (
    ID = 1,
    RECEIVER = 3
diff --git a/docs/en_US/slony/stmtupdatefunctions.html b/docs/en_US/slony/stmtupdatefunctions.html
index 95fee1c177..daa81ee58e 100644
--- a/docs/en_US/slony/stmtupdatefunctions.html
+++ b/docs/en_US/slony/stmtupdatefunctions.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtddlscript.html" title="EXECUTE SCRIPT">
 <link rel="next" href="stmtwaitevent.html" title="WAIT FOR EVENT">
@@ -21,7 +21,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">UPDATE FUNCTIONS (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id536528"></a><h2>Description</h2>
+<a name="id537330"></a><h2>Description</h2>
 <p> Reloads stored functions for a node.</p>
 <p>Reloads all stored procedure and function definitions in the
     <span class="productname">Slony-I</span> schema for the specified node. This command is usually
@@ -33,7 +33,7 @@ <h2>Synopsis</h2>
 </dl></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id536565"></a><h2>Example</h2>
+<a name="id537368"></a><h2>Example</h2>
 <pre class="programlisting">UPDATE FUNCTIONS (
     ID = 3        # Update functions on node 3
 );
diff --git a/docs/en_US/slony/stmtwaitevent.html b/docs/en_US/slony/stmtwaitevent.html
index 8e46b6fbbd..bcf4bd901b 100644
--- a/docs/en_US/slony/stmtwaitevent.html
+++ b/docs/en_US/slony/stmtwaitevent.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="cmds.html" title="Configuration and Action commmands">
 <link rel="prev" href="stmtupdatefunctions.html" title="UPDATE FUNCTIONS">
 <link rel="next" href="supportedplatforms.html" title="Slony-I Supported Platforms">
@@ -22,7 +22,7 @@ <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">WAIT FOR EVENT (options);</code></p></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id536602"></a><h2>Description</h2>
+<a name="id537407"></a><h2>Description</h2>
 <p> Waits for event Confirmation.</p>
 <p> <span class="application">Slonik</span> remembers the last event
      generated on every node during script execution (events generated
@@ -53,7 +53,7 @@ <h2>Synopsis</h2>
 </dl></div>
 </div>
 <div class="refsect1" lang="en">
-<a name="id536735"></a><h2>Example</h2>
+<a name="id537540"></a><h2>Example</h2>
 <pre class="programlisting">WAIT FOR EVENT (
   ORIGIN = ALL,
   CONFIRMED = ALL,
diff --git a/docs/en_US/slony/subscribenodes.html b/docs/en_US/slony/subscribenodes.html
index a575b61abc..a95af6c9f1 100644
--- a/docs/en_US/slony/subscribenodes.html
+++ b/docs/en_US/slony/subscribenodes.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="slonstart.html" title="2. Slon daemons">
 <link rel="next" href="monitoring.html" title="4. Monitoring">
@@ -13,7 +13,7 @@
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="subscribenodes"></a>3. Subscribing Nodes</h2></div></div></div>
-<a name="id516032"></a><p>Before you subscribe a node to a set, be sure that you have
+<a name="id516178"></a><p>Before you subscribe a node to a set, be sure that you have
 <a href="slon.html" title="slon"><span class="refentrytitle"><a name="app-slon-title"></a><span class="application">slon</span></span></a> processes running for both the provider and the
 new subscribing node. If you don't have slons running, nothing will
 happen, and you'll beat your head against a wall trying to figure out
diff --git a/docs/en_US/slony/supportedplatforms.html b/docs/en_US/slony/supportedplatforms.html
index f03d4f36c0..7fda8e7556 100644
--- a/docs/en_US/slony/supportedplatforms.html
+++ b/docs/en_US/slony/supportedplatforms.html
@@ -5,8 +5,8 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
-<link rel="up" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
+<link rel="up" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="prev" href="stmtwaitevent.html" title="WAIT FOR EVENT">
 <link rel="next" href="schema.html" title="Chapter 1. Schema schemadoc">
 </head>
@@ -49,7 +49,8 @@
 <td>Intel - 32 bit</td>
 <td>Jun 22, 2005</td>
 <td>dvdm at truteq.co.za</td>
-<td>PostgreSQL Version: 7.4.6</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 7.4.6</td>
 </tr>
 <tr>
 <td>Red Hat Linux</td>
@@ -57,7 +58,8 @@
 <td>x86</td>
 <td>Jun 22, 2005</td>
 <td>dvdm at truteq.co.za</td>
-<td>PostgreSQL Version: 7.4.5</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 7.4.5</td>
 </tr>
 <tr>
 <td>Debian GNU/Linux</td>
@@ -65,7 +67,8 @@
 <td>x86</td>
 <td>Jun 22, 2005</td>
 <td>cbbrowne at ca.afilias.info</td>
-<td>PostgreSQL Version: 7.4.8</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 7.4.8</td>
 </tr>
 <tr>
 <td>Debian GNU/Linux</td>
@@ -73,7 +76,8 @@
 <td>x86</td>
 <td>Jun 22, 2005</td>
 <td>cbbrowne at ca.afilias.info</td>
-<td>PostgreSQL Version: 8.0.2</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 8.0.2</td>
 </tr>
 <tr>
 <td>Debian GNU/Linux</td>
@@ -81,7 +85,8 @@
 <td>x86</td>
 <td>Jun 22, 2005</td>
 <td>cbbrowne at ca.afilias.info</td>
-<td>PostgreSQL Version: 7.3.9</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 7.3.9</td>
 </tr>
 <tr>
 <td>AIX</td>
@@ -89,7 +94,8 @@
 <td>PPC</td>
 <td>Jun 22, 2005</td>
 <td>cbbrowne at ca.afilias.info</td>
-<td>PostgreSQL Version: 7.4.8</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 7.4.8</td>
 </tr>
 <tr>
 <td>SunOS (a.k.a. Solaris8)</td>
@@ -97,7 +103,8 @@
 <td>x86</td>
 <td>Jun 22, 2005</td>
 <td>cbbrowne at ca.afilias.info</td>
-<td>PostgreSQL Version: 7.4.8</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 7.4.8</td>
 </tr>
 <tr>
 <td>Red Hat Enterprise Linux Enterprise Server</td>
@@ -105,7 +112,8 @@
 <td>x86</td>
 <td>Jun 22, 2005</td>
 <td>devrim at gunduz.org</td>
-<td>PostgreSQL Version: 8.0.3 , docs fail to build, NAMELEN value must be increased from 44 to 100 to build the docs, or use community RPMs</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 8.0.3 , docs fail to build, NAMELEN value must be increased from 44 to 100 to build the docs, or use community RPMs</td>
 </tr>
 <tr>
 <td>Red Hat Enterprise Linux Enterprise Server</td>
@@ -113,7 +121,8 @@
 <td>x86</td>
 <td>Jun 22, 2005</td>
 <td>devrim at gunduz.org</td>
-<td>PostgreSQL Version: 8.0.3 , docs fail to build, NAMELEN value must be increased from 44 to 100 to build the docs, or use community RPMs</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 8.0.3 , docs fail to build, NAMELEN value must be increased from 44 to 100 to build the docs, or use community RPMs</td>
 </tr>
 <tr>
 <td>Fedora Core</td>
@@ -121,7 +130,8 @@
 <td>x86</td>
 <td>Jun 22, 2005</td>
 <td>devrim at gunduz.org</td>
-<td>PostgreSQL Version: 8.0.3 , docs fail to build, NAMELEN value must be increased from 44 to 100 to build the docs, or use community RPMs</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 8.0.3 , docs fail to build, NAMELEN value must be increased from 44 to 100 to build the docs, or use community RPMs</td>
 </tr>
 <tr>
 <td>Fedora Core</td>
@@ -129,7 +139,8 @@
 <td>x86</td>
 <td>Jun 22, 2005</td>
 <td>devrim at gunduz.org</td>
-<td>PostgreSQL Version: 8.0.3 , docs fail to build, NAMELEN value must be increased from 44 to 100 to build the docs, or use community RPMs</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 8.0.3 , docs fail to build, NAMELEN value must be increased from 44 to 100 to build the docs, or use community RPMs</td>
 </tr>
 <tr>
 <td>Red Hat Linux</td>
@@ -137,7 +148,8 @@
 <td>x86</td>
 <td>Jul 14, 2005</td>
 <td>devrim at gunduz.org</td>
-<td>PostgreSQL Version: 8.0.3 , docs fail to build, NAMELEN value must be increased from 44 to 100 to build the docs, or use community RPMs</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 8.0.3 , docs fail to build, NAMELEN value must be increased from 44 to 100 to build the docs, or use community RPMs</td>
 </tr>
 <tr>
 <td>FreeBSD</td>
@@ -145,7 +157,8 @@
 <td>AMD64</td>
 <td>Jul 01, 2005</td>
 <td>stefan at kaltenbrunner.cc </td>
-<td>PostgreSQL Version: 8.0.3</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 8.0.3</td>
 </tr>
 <tr>
 <td>OpenBSD</td>
@@ -153,7 +166,8 @@
 <td>Sparc64</td>
 <td>Jul 01, 2005</td>
 <td>stefan at kaltenbrunner.cc </td>
-<td>PostgreSQL Version: 8.0.3</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 8.0.3</td>
 </tr>
 <tr>
 <td>OpenBSD</td>
@@ -161,7 +175,8 @@
 <td>x86</td>
 <td>Jul 01, 2005</td>
 <td>stefan at kaltenbrunner.cc </td>
-<td>PostgreSQL Version: 8.0.3</td>
+<td>
+<span class="productname">PostgreSQL</span> Version: 8.0.3</td>
 </tr>
 </tbody>
 </table>
diff --git a/docs/en_US/slony/table.sl-confirm.html b/docs/en_US/slony/table.sl-confirm.html
index c8806899c5..fa294ffee7 100644
--- a/docs/en_US/slony/table.sl-confirm.html
+++ b/docs/en_US/slony/table.sl-confirm.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="next" href="table.sl-event.html" title="1.3.          Table:
diff --git a/docs/en_US/slony/table.sl-event.html b/docs/en_US/slony/table.sl-event.html
index 82d84a58c1..ae9643e113 100644
--- a/docs/en_US/slony/table.sl-event.html
+++ b/docs/en_US/slony/table.sl-event.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-confirm.html" title="1.2.          Table:
          
diff --git a/docs/en_US/slony/table.sl-listen.html b/docs/en_US/slony/table.sl-listen.html
index d2e03108ac..2dea38e1a1 100644
--- a/docs/en_US/slony/table.sl-listen.html
+++ b/docs/en_US/slony/table.sl-listen.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-event.html" title="1.3.          Table:
          
diff --git a/docs/en_US/slony/table.sl-log-1.html b/docs/en_US/slony/table.sl-log-1.html
index c86e26d4ee..f5d413dcdd 100644
--- a/docs/en_US/slony/table.sl-log-1.html
+++ b/docs/en_US/slony/table.sl-log-1.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-listen.html" title="1.4.          Table:
          
diff --git a/docs/en_US/slony/table.sl-log-2.html b/docs/en_US/slony/table.sl-log-2.html
index 7f74e7ccb6..cf77769b6d 100644
--- a/docs/en_US/slony/table.sl-log-2.html
+++ b/docs/en_US/slony/table.sl-log-2.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-log-1.html" title="1.5.          Table:
          
diff --git a/docs/en_US/slony/table.sl-node.html b/docs/en_US/slony/table.sl-node.html
index d312e5e382..32ddff232f 100644
--- a/docs/en_US/slony/table.sl-node.html
+++ b/docs/en_US/slony/table.sl-node.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-log-2.html" title="1.6.          Table:
          
diff --git a/docs/en_US/slony/table.sl-path.html b/docs/en_US/slony/table.sl-path.html
index 2c12c86dc6..3e851cebe4 100644
--- a/docs/en_US/slony/table.sl-path.html
+++ b/docs/en_US/slony/table.sl-path.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-node.html" title="1.7.          Table:
          
diff --git a/docs/en_US/slony/table.sl-seqlog.html b/docs/en_US/slony/table.sl-seqlog.html
index 8ef2ecc579..4b140cf620 100644
--- a/docs/en_US/slony/table.sl-seqlog.html
+++ b/docs/en_US/slony/table.sl-seqlog.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="view.sl-seqlastvalue.html" title="1.9.          View:
          
diff --git a/docs/en_US/slony/table.sl-sequence.html b/docs/en_US/slony/table.sl-sequence.html
index 2dd556699e..05d0189a15 100644
--- a/docs/en_US/slony/table.sl-sequence.html
+++ b/docs/en_US/slony/table.sl-sequence.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-seqlog.html" title="1.10.          Table:
          
diff --git a/docs/en_US/slony/table.sl-set.html b/docs/en_US/slony/table.sl-set.html
index cb165aa8a8..218a420c75 100644
--- a/docs/en_US/slony/table.sl-set.html
+++ b/docs/en_US/slony/table.sl-set.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-sequence.html" title="1.11.          Table:
          
diff --git a/docs/en_US/slony/table.sl-setsync.html b/docs/en_US/slony/table.sl-setsync.html
index 6e644ae859..bfac1ca622 100644
--- a/docs/en_US/slony/table.sl-setsync.html
+++ b/docs/en_US/slony/table.sl-setsync.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-set.html" title="1.12.          Table:
          
diff --git a/docs/en_US/slony/table.sl-subscribe.html b/docs/en_US/slony/table.sl-subscribe.html
index 42eb2c7842..d89519f78a 100644
--- a/docs/en_US/slony/table.sl-subscribe.html
+++ b/docs/en_US/slony/table.sl-subscribe.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-setsync.html" title="1.13.          Table:
          
diff --git a/docs/en_US/slony/table.sl-table.html b/docs/en_US/slony/table.sl-table.html
index f0633648dc..cdb76c7e51 100644
--- a/docs/en_US/slony/table.sl-table.html
+++ b/docs/en_US/slony/table.sl-table.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-subscribe.html" title="1.14.          Table:
          
diff --git a/docs/en_US/slony/table.sl-trigger.html b/docs/en_US/slony/table.sl-trigger.html
index 4034c25df4..9cf7297180 100644
--- a/docs/en_US/slony/table.sl-trigger.html
+++ b/docs/en_US/slony/table.sl-trigger.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-table.html" title="1.15.          Table:
          
diff --git a/docs/en_US/slony/testbed.html b/docs/en_US/slony/testbed.html
new file mode 100644
index 0000000000..fc5f2d3f55
--- /dev/null
+++ b/docs/en_US/slony/testbed.html
@@ -0,0 +1,82 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>21.  Slony-I Test Bed Framework </title>
+<link rel="stylesheet" href="stylesheet.css" type="text/css">
+<link rev="made" href="pgsql-docs@postgresql.org">
+<meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
+<link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
+<link rel="prev" href="bestpractices.html" title="20.  Slony-I &#8220;Best Practices&#8221; ">
+<link rel="next" href="help.html" title="22. More Slony-I Help">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="testbed"></a>21.  <span class="productname">Slony-I</span> Test Bed Framework </h2></div></div></div>
+<p> As of version 1.2, <span class="productname">Slony-I</span> has a common test bed framework
+intended to better support performing a comprehensive set of tests.
+The code lives in the source tree under the <code class="filename"> tests</code> directory.</p>
+<p>Here are some of the vital files...</p>
+<div class="itemizedlist"><ul type="disc"><li><p> <code class="filename">run_test.sh</code> </p></li></ul></div>
+<p> This is the central script for running tests.  Typical usage is
+thus:</p>
+<p> <code class="command"> ./run_test.sh </code></p>
+<pre class="screen">usage ./run_test.sh testname</pre>
+<p> You need to specify the subdirectory name of the test set to be
+run; each such set is stored in a subdirectory of
+<code class="filename">tests</code>.</p>
+<p> You may need to set one or more of the following environment
+variables to reflect your local configuration.  For instance, the
+writer runs his &#8220;<span class="quote">main</span>&#8221; test like the following:</p>
+<pre class="screen"> PGBINDIR=/opt/OXRS/dbs/pgsql8/bin PGPORT=5532 PGUSER=cbbrowne ./run_test.sh test1 </pre>
+<div class="glosslist"><dl>
+<dt> <code class="envar">PGBINDIR</code> </dt>
+<dd>
+<p> This determines where the test scripts look for
+<span class="productname">PostgreSQL</span> and <span class="productname">Slony-I</span> binaries.  The default is <code class="filename">/usr/local/pgsql/bin</code> </p>
+<p> There are also variables <code class="envar">PGBINDIR1</code> thru
+<code class="envar">PGBINDIR13</code> which allows you to specify a separate path
+for each database instance.  That will be particularly useful when
+testing interoperability of <span class="productname">Slony-I</span> across different versions of
+<span class="productname">PostgreSQL</span>. In order to create a database of each respective version,
+you need to point to an <span class="application">initdb</span> of the
+appropriate version.</p>
+</dd>
+<dt> <code class="envar">PGPORT</code> </dt>
+<dd>
+<p> This indicates what port the backend is on.  By
+default, 5432 is used. </p>
+<p> There are also variables <code class="envar">PORT1</code> thru
+<code class="envar">PORT13</code> which allows you to specify a separate port
+number for each database instance.  That will be particularly useful
+when testing interoperability of <span class="productname">Slony-I</span> across different versions of
+<span class="productname">PostgreSQL</span>. </p>
+</dd>
+<dt> <code class="envar">PGUSER</code> </dt>
+<dd>
+<p> By default, the user <code class="filename">postgres</code> is
+used; this is taken as the default user ID to use for all of the
+databases. </p>
+<p> There are also variables <code class="envar">USER1</code> thru
+<code class="envar">USER13</code> which allow specifying a separate user name for
+each database instance.</p>
+</dd>
+<dt> <code class="envar">HOST</code> </dt>
+<dd>
+<p> By default, <code class="filename">localhost</code> is used.</p>
+<p> There are also variables <code class="envar">HOST1</code> thru
+<code class="envar">HOST13</code> which allow specifying a separate host for
+each database instance.</p>
+</dd>
+<dt> <code class="envar">DB1</code> thru <code class="envar">DB13 </code> </dt>
+<dd>
+<p> By default, <code class="filename">slonyregress1</code> thru
+<code class="filename">slonyregress13</code> are used.</p>
+<p> You may override these from the environment. </p>
+</dd>
+<dt><code class="envar">ENCODING</code></dt>
+<dd><p> By default, <code class="filename">UNICODE</code> is used, so
+that tests can create UTF8 tables and test the multibyte capabilities.</p></dd>
+</dl></div>
+</div></body>
+</html>
diff --git a/docs/en_US/slony/usingslonik.html b/docs/en_US/slony/usingslonik.html
index a70d1c6ec5..1122deeeb9 100644
--- a/docs/en_US/slony/usingslonik.html
+++ b/docs/en_US/slony/usingslonik.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="ddlchanges.html" title="14. Database Schema Changes (DDL)">
 <link rel="next" href="slonikshell.html" title="16.  Embedding Slonik in Shell Scripts ">
diff --git a/docs/en_US/slony/versionupgrade.html b/docs/en_US/slony/versionupgrade.html
index 584de09710..bc48f30a3a 100644
--- a/docs/en_US/slony/versionupgrade.html
+++ b/docs/en_US/slony/versionupgrade.html
@@ -5,7 +5,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="slonyadmin.html" title=" Slony-I Administration ">
 <link rel="prev" href="altperl.html" title="18. Slony-I Administration Scripts">
 <link rel="next" href="bestpractices.html" title="20.  Slony-I &#8220;Best Practices&#8221; ">
@@ -13,7 +13,7 @@
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="versionupgrade"></a>19. Using <span class="productname">Slony-I</span> for <span class="productname">PostgreSQL</span> Upgrades</h2></div></div></div>
-<a name="id522925"></a><p> A number of people have found
+<a name="id523328"></a><p> A number of people have found
 <span class="productname">Slony-I</span> useful for helping perform upgrades
 between major <span class="productname">PostgreSQL</span> releases
 (<span class="emphasis"><em> e.g.</em></span> which mandates running
diff --git a/docs/en_US/slony/view.sl-seqlastvalue.html b/docs/en_US/slony/view.sl-seqlastvalue.html
index 81b88e9fc6..64dbcdfe7d 100644
--- a/docs/en_US/slony/view.sl-seqlastvalue.html
+++ b/docs/en_US/slony/view.sl-seqlastvalue.html
@@ -8,7 +8,7 @@
 <link rel="stylesheet" href="stylesheet.css" type="text/css">
 <link rev="made" href="pgsql-docs@postgresql.org">
 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
-<link rel="start" href="index.html" title="Slony-I HEAD_20051102 Documentation">
+<link rel="start" href="index.html" title="Slony-I HEAD_20051208 Documentation">
 <link rel="up" href="schema.html" title="Chapter 1. Schema schemadoc">
 <link rel="prev" href="table.sl-path.html" title="1.8.          Table:
          
@@ -93,7 +93,7 @@
 
         </p>
 <div class="figure">
-<a name="id538430"></a><p class="title"><b>Figure 1.1. Definition of view sl_seqlastvalue</b></p>
+<a name="id539298"></a><p class="title"><b>Figure 1.1. Definition of view sl_seqlastvalue</b></p>
 <pre class="programlisting">SELECT sq.seq_id
 , sq.seq_set
 , sq.seq_reloid