Revise limitations - TRUNCATE triggers are available in newer versions

of Postgres, so TRUNCATE can be replicated.

diff --git a/doc/adminguide/limitations.sgml b/doc/adminguide/limitations.sgml
index a2da12f0a597c91b3b5769ed29658aaabebc6162..1b13c74984e83688b741cbe471403df2d8f44d6a 100644 (file)
--- a/doc/adminguide/limitations.sgml
+++ b/doc/adminguide/limitations.sgml
@@ -9,8 +9,6 @@
 <listitem><para>Changes to large objects (BLOBS)</para></listitem>
 <listitem><para>Changes made by DDL commands</para></listitem>
 <listitem><para>Changes to users and roles</para></listitem>
-<listitem><para>Changes made by the TRUNCATE command, 
-though this might change in a future version of &slony1;</para></listitem>
 </itemizedlist>
 </para>
 
@@ -26,10 +24,9 @@ have to construct an SQL DDL script and submit it, via <xref
 linkend="stmtddlscript">.
 
 <para>If you have these sorts of requirements, it may be worth
-exploring the use of &postgres; 8.X <acronym>PITR</acronym> (Point In
+exploring the use of &postgres; 8.0+ <acronym>PITR</acronym> (Point In
 Time Recovery), where <acronym>WAL</acronym> logs are replicated to
-remote 
-
+remote nodes.
 
 </sect1>