Point out that TRUNCATE can't be used inside a transaction block.

diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml
index 861c93b1161df108ef7d67398fa6d3564f5a7514..6d413fd7adc218624e77a0de6febf758c0fb1713 100644 (file)
--- a/doc/src/sgml/ref/truncate.sgml
+++ b/doc/src/sgml/ref/truncate.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.3 2001/09/03 12:57:50 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.4 2001/11/18 21:14:20 tgl Exp $
 Postgres documentation
 -->
 
@@ -84,7 +84,13 @@ TRUNCATE
    <command>TRUNCATE</command> quickly removes all rows from a
    table. It has the same effect as an unqualified
    <command>DELETE</command> but since it does not actually scan the
-   table it is faster. This is most effective on large tables.
+   table it is faster. This is most useful on large tables.
+  </para>
+
+  <para>
+   <command>TRUNCATE</command> cannot be executed inside a transaction
+   block (<command>BEGIN</>/<command>COMMIT</> pair), because there is
+   no way to roll it back.
   </para>
  </refsect1>