summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2020-10-19 19:02:25 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2020-10-19 19:03:02 +0300
commitd348473b783c37a1937065812217eb269b8f2613 (patch)
treea1c832132c5bc9573d5f5c33b60d3858575c5498
parent609fe21c0dbd50cd5e3d13a73ea2f757fdfc75ff (diff)
Fix TRUNCATE doc: ALTER SEQUENCE RESTART is now transactional.
ALTER SEQUENCE RESTART was made transactional in commit 3d79013b97. Backpatch to v10, where that was introduced. Patch by Justin Pryzby, per Yaroslav Schekin's report. Discussion: https://www.postgresql.org/message-id/20201005191922.GE17626%40telsasoft.com
-rw-r--r--doc/src/sgml/ref/truncate.sgml3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml
index e9c8a03a638..f3ad9fc660c 100644
--- a/doc/src/sgml/ref/truncate.sgml
+++ b/doc/src/sgml/ref/truncate.sgml
@@ -157,8 +157,7 @@ TRUNCATE [ TABLE ] [ ONLY ] <replaceable class="PARAMETER">name</replaceable> [
When <literal>RESTART IDENTITY</> is specified, the implied
<command>ALTER SEQUENCE RESTART</> operations are also done
transactionally; that is, they will be rolled back if the surrounding
- transaction does not commit. This is unlike the normal behavior of
- <command>ALTER SEQUENCE RESTART</>. Be aware that if any additional
+ transaction does not commit. Be aware that if any additional
sequence operations are done on the restarted sequences before the
transaction rolls back, the effects of these operations on the sequences
will be rolled back, but not their effects on <function>currval()</>;