]> git.ipfire.org Git - thirdparty/postgresql.git/commit
projects / thirdparty / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 88482d7) | patch
Doc: improve documentation about nextval()/setval().
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 24 Nov 2021 18:37:12 +0000 (13:37 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 24 Nov 2021 18:37:12 +0000 (13:37 -0500)
commit6d1bdd5e0712c0c3460d68dc2175f842530b1f83
treeec65a45913267905bbf207b83109954d3fb3c5f7tree | snapshot
parent88482d75cce5f3527ebad1cf42ec59a355f4b033commit | diff
Doc: improve documentation about nextval()/setval().

Clarify that the results of nextval and setval are not guaranteed
persistent until the calling transaction commits.  Some people
seem to have drawn the opposite conclusion from the statement that
these functions are never rolled back, so re-word to avoid saying
it quite that way.

Discussion: https://postgr.es/m/CAKU4AWohO=NfM-4KiZWvdc+z3c1C9FrUBR6xnReFJ6sfy0i=Lw@mail.gmail.com
doc/src/sgml/func.sgml diff | blob | blame | history
Mirror of https://git.postgresql.org/git/postgresql.git