From b16f6c6b95b083ef2001755e707ac2b38db2965a Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 18 Nov 2001 21:14:20 +0000
Subject: [PATCH] Point out that TRUNCATE can't be used inside a transaction
block.
---
doc/src/sgml/ref/truncate.sgml | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml
index 861c93b1161..6d413fd7adc 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.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>
--
GitLab