From d851f002a469b81996c65b2826f3f595c5bf60bd Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 6 Dec 2002 03:15:07 +0000
Subject: [PATCH] With a recent commit truncate is transaction safe in 7.4.

Rod Taylor
---
 doc/src/sgml/ref/truncate.sgml | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml
index 723079ab3bc..e8691bc4ea9 100644
--- 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.8 2002/05/18 15:44:47 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.9 2002/12/06 03:15:07 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -84,12 +84,6 @@ TRUNCATE TABLE
    <command>DELETE</command> but since it does not actually scan the
    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>
 
  <refsect1 id="R1-SQL-TRUNCATE-2">