]> git.ipfire.org Git - thirdparty/postgresql.git/commit
projects / thirdparty / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 892da52) | 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)
commit499552273d47645c759d58c5916b3bc8ecc7f13d
tree403375abf25e0e41900c7a81fbc02989137dcf6atree
parent892da5200aaf31f950021b4bf92916ad35113f2ecommit | 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