Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitb16f6c6

Browse files
committed
Point out that TRUNCATE can't be used inside a transaction block.
1 parent17f0b55 commitb16f6c6

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

‎doc/src/sgml/ref/truncate.sgml

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.3 2001/09/03 12:57:50 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.4 2001/11/18 21:14:20 tgl Exp $
33
Postgres documentation
44
-->
55

@@ -84,7 +84,13 @@ TRUNCATE
8484
<command>TRUNCATE</command> quickly removes all rows from a
8585
table. It has the same effect as an unqualified
8686
<command>DELETE</command> but since it does not actually scan the
87-
table it is faster. This is most effective on large tables.
87+
table it is faster. This is most useful on large tables.
88+
</para>
89+
90+
<para>
91+
<command>TRUNCATE</command> cannot be executed inside a transaction
92+
block (<command>BEGIN</>/<command>COMMIT</> pair), because there is
93+
no way to roll it back.
8894
</para>
8995
</refsect1>
9096

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp