aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/commit_ts.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-05-07 13:16:50 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-05-07 13:16:50 -0400
commit691d99de386aa1f5a858e04634dbaaba48488ef8 (patch)
tree2c738c6ec6750fc92482e25fcf87d840861f7c74 /src/backend/access/transam/commit_ts.c
parent7dc1d359699345a2b2af6af6d21bd6f7bd6cfb27 (diff)
downloadpostgresql-691d99de386aa1f5a858e04634dbaaba48488ef8.tar.gz
postgresql-691d99de386aa1f5a858e04634dbaaba48488ef8.zip
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.
Diffstat (limited to 'src/backend/access/transam/commit_ts.c')
0 files changed, 0 insertions, 0 deletions