pgsql: Docs: improve warnings about nextval() not producing gapless seq - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Docs: improve warnings about nextval() not producing gapless seq
Date
Msg-id E1az5qp-00060v-5J@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Docs: improve warnings about nextval() not producing gapless sequences.

In the documentation for nextval(), point out explicitly that INSERT ...
ON CONFLICT will call nextval() if needed for the insertion case, whether
or not it ends up following the ON CONFLICT path.  This seems to be a
matter of some confusion, cf bug #14126, so let's be clear about it.

Also mention the issue in the CREATE SEQUENCE reference page, since that
is another place where people might expect such things to be covered.

Minor wording improvements nearby, as well.

Back-patch to 9.5 where ON CONFLICT was introduced.

Branch
------
REL9_5_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/673bceaf3f24a7a3d3ed346d07cedc6524ad888d

Modified Files
--------------
doc/src/sgml/func.sgml                | 22 ++++++++++++++--------
doc/src/sgml/ref/create_sequence.sgml | 10 ++++++++++
2 files changed, 24 insertions(+), 8 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Docs: improve warnings about nextval() not producing gapless seq
Next
From: Tom Lane
Date:
Subject: pgsql: In new pg_dump TAP tests, remove trailing "$" from regexps using