<listitem><para>DDL changes that rename a replicated table do not
inform &slony1; of the new table name. If you change then name of
a replicated table you must allow &slony1; to find the new table name
-by calling <xref linkend="function.updaterelname-p-only-on-node-integer-p-set-id-integer">
+by calling <xref linkend="function.updaterelname">
</para>
</listitem>
<listitem><para> <link linkend="startslon">start_slon.sh</link>,
written with a view to managing the &lslon; configuration via the
<link linkend="runtime-config"> slon runtime configuraiton
-</file>.</para></listitem>
+</link>.</para></listitem>
<listitem><para> <link linkend=
"launchclusters">launch_clusters.sh</link>, which can start up
<!ENTITY funsetaddsequence "<xref linkend= function.setaddsequence-p-seq-comment-integer-p-fqname-integer-p-seq-id-text-p-set-id-text>">
<!ENTITY funsetdropsequence "<xref linkend= function.setdropsequence-p-seq-id-integer>">
<!ENTITY funsetmovetable "<xref linkend= function.setmovetable-p-new-set-id-integer-p-tab-id-integer>">
-<!ENTITY funddlscript "<xref linkend=function.ddlscript-complete-p-only-on-node-integer-p-script-text-p-set-id-integer>">
+<!ENTITY funddlscript "<xref linkend=function.ddlscript-complete-p-nodes-text>">
<!ENTITY fundropnode "<xref linkend=function.dropnode-p-no-id-integer>">
<!ENTITY funenablenode "<xref linkend=function.enablenode-p-no-id-integer>">
<!ENTITY funfailednode "<xref linkend=function.failednode-p-backup-node-integer-p-failed-node-integer>">
<!ENTITY funmoveset "<xref linkend=function.moveset-p-new-origin-integer-p-set-id-integer>">
<!ENTITY funsetmovesequence "<xref linkend=function.setmovesequence-p-new-set-id-integer-p-seq-id-integer>">
<!ENTITY funstoretrigger "<xref linkend=function.storetrigger-integer-name>">
-<!ENTITY funsubscribeset "<xref linkend=function.subscribeset-p-omit-copy-integer-p-sub-forward-integer-p-sub-receiver-integer-p-sub-provider-boolean-p-sub-set-boolean>">
+<!ENTITY fsubscribeset "<xref linkend=function.subscribeset-p-omit-copy-integer-p-sub-forward-integer-p-sub-receiver-integer-p-sub-provider-boolean-p-sub-set-boolean>">
<!ENTITY fununinstallnode "<xref linkend=function.uninstallnode>">
<!ENTITY fununlockset "<xref linkend=function.unlockset-p-set-id-integer>">
-<!ENTITY fununsubscribeset "<xref linkend=function.unsubscribeset-p-sub-receiver-integer-p-sub-set-integer>">
+<!ENTITY fununsubscribeset "<xref linkend=function.unsubscribeset-p-sub-set-integer-p-sub-receiver-integer-p-force-boolean>">
<!ENTITY bestpracticelink "<link linkend=bestpractices>Best Practice</link>">
<!ENTITY rmissingoids "<link linkend=missingoids>error messages indicating missing OIDs</link>">
<!ENTITY slnode "<xref linkend=table.sl-node>">
p_sub_set::text, p_sub_receiver::text);
end;
$$ language plpgsql;
-comment on function @NAMESPACE@.unsubscribeSet (p_sub_set int4, p_sub_receiver int4,boolean) is
-'unsubscribeSet (sub_set, sub_receiver)
+comment on function @NAMESPACE@.unsubscribeSet (p_sub_set int4, p_sub_receiver int4,force boolean) is
+'unsubscribeSet (sub_set, sub_receiver,force)
Unsubscribe node sub_receiver from subscription set sub_set. This is
invoked on the receiver node. It verifies that this does not break