This patch improves the "drop things" documentation by mentioning the easier to use slonik_drop_table script.
Mark
--- old-slony1-1.2.2/doc/adminguide/dropthings.sgml 2007-01-04 15:43:05.000000000 -0500 +++ new-slony1-1.2.2/doc/adminguide/dropthings.sgml 2007-01-04 15:43:05.000000000 -0500 @@ -82,9 +82,20 @@ </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 altperl ulities are installed, you can use the slonik_drop_table +helper script to drop a table from replication. Simply run slonik_drop_table +with no arguments to review the correct usage of the script. After dropping +the table, you should also remove it from slon_tools.conf +</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 +126,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>
_______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
