From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Docs: improve warnings about nextval() not producing gapless seq |
Date: | 2016-05-07 17:17:11 |
Message-ID: | E1az5qp-00060u-5G@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/691d99de386aa1f5a858e04634dbaaba48488ef8
Modified Files
--------------
doc/src/sgml/func.sgml | 22 ++++++++++++++--------
doc/src/sgml/ref/create_sequence.sgml | 10 ++++++++++
2 files changed, 24 insertions(+), 8 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-05-07 20:36:56 | pgsql: In new pg_dump TAP tests, remove trailing "$" from regexps using |
Previous Message | Peter Eisentraut | 2016-05-07 17:02:31 | Re: [COMMITTERS] pgsql: Add TAP tests for pg_dump |