]> git.ipfire.org Git - thirdparty/postgresql.git/commit
projects / thirdparty / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: a00bd7a) | 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)
commitb0a7161c564089d4119bbcd5e874a1f4430de1bc
tree83d5837ed832639e20592fb885acf8a9ab7c1fd0tree | snapshot
parenta00bd7aa17f652d88c8c0fe52286ef93bb4ec3cccommit | 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