]> git.ipfire.org Git - thirdparty/postgresql.git/commit
projects / thirdparty / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 113b0a2) | 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)
commit09c11134916c4fdae0bf557c02181e60e76b28ea
treed1875d100d2591763210664320c1a791ceabd249tree | snapshot
parent113b0a2dd79b369e3adc238896c0909935a5adb3commit | 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