mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Tom Lane 2001-11-18 21:14:20 +00:00
parent 17f0b55d15
commit b16f6c6b95
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/ref/truncate.sgml
View File

@ -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 Postgres documentation
--> -->
@ -84,7 +84,13 @@ TRUNCATE
<command>TRUNCATE</command> quickly removes all rows from a <command>TRUNCATE</command> quickly removes all rows from a
table. It has the same effect as an unqualified table. It has the same effect as an unqualified
<command>DELETE</command> but since it does not actually scan the <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> </para>
</refsect1> </refsect1>