Fri Jan 5 11:11:44 PST 2007
- Previous message: [Slony1-commit] By cbbrowne: Describe use of "altperl" scripts to drop a table from
- Next message: [Slony1-commit] By devrim: Fix sgml error
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message: ----------- Describe use of "altperl" scripts to drop a table from replication in the section on "dropping things." Per Mark Stosberg. Tags: ---- REL_1_2_STABLE Modified Files: -------------- slony1-engine/doc/adminguide: adminscripts.sgml (r1.40.2.5 -> r1.40.2.6) dropthings.sgml (r1.16 -> r1.16.2.1) -------------- next part -------------- Index: adminscripts.sgml =================================================================== RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/adminscripts.sgml,v retrieving revision 1.40.2.5 retrieving revision 1.40.2.6 diff -Ldoc/adminguide/adminscripts.sgml -Ldoc/adminguide/adminscripts.sgml -u -w -r1.40.2.5 -r1.40.2.6 --- doc/adminguide/adminscripts.sgml +++ doc/adminguide/adminscripts.sgml @@ -165,7 +165,7 @@ &slony1; cluster.</para> </sect3> -<sect3><title>slonik_drop_table</title> +<sect3 id="slonik-drop-table"><title>slonik_drop_table</title> <para>Generates Slonik script to drop a table from replication. Requires, as input, the ID number of the table (available from table @@ -535,8 +535,6 @@ not correspond, of course, to any database you actually want to use...</para> -</sect3> - <sect3><title>Node-Specific Values</title> <para>For each node, there are also four environment variables; for node 1: </para> Index: dropthings.sgml =================================================================== RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/dropthings.sgml,v retrieving revision 1.16 retrieving revision 1.16.2.1 diff -Ldoc/adminguide/dropthings.sgml -Ldoc/adminguide/dropthings.sgml -u -w -r1.16 -r1.16.2.1 --- doc/adminguide/dropthings.sgml +++ doc/adminguide/dropthings.sgml @@ -82,9 +82,23 @@ </sect2> <sect2><title> Dropping A Table From Replication</title> - <indexterm><primary>dropping a table from replication</primary></indexterm> +<sect3><title> Using the altperl tools </title> + +<para> +If the <link linkend="altperl"> altperl </link> utilities are +installed, you can use the <link linkend="slonik-drop-table"> +slonik_drop_table </link> helper script to drop a table from +replication. Simply run <command>slonik_drop_table</command> with no +arguments to review the correct usage of the script. After dropping +the table, you should also remove it from +<filename>slon_tools.conf</filename>. +</para> + +</sect3> +<sect3><title> Using Direct slonik commands </title> + <para>In &slony1; 1.0.5 and above, there is a Slonik command <xref linkend="stmtsetdroptable"> that allows dropping a single table from replication without forcing the user to drop the entire replication @@ -115,6 +129,7 @@ three queries using <xref linkend="stmtddlscript"> could do that; see <xref linkend="ddlchanges"> for more details. Also possible would be to connect to each database and submit the queries by hand.</para> +</sect3> </sect2> <sect2><title>Dropping A Sequence From Replication</title>
- Previous message: [Slony1-commit] By cbbrowne: Describe use of "altperl" scripts to drop a table from
- Next message: [Slony1-commit] By devrim: Fix sgml error
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list