aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
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:17:02 -0400
commit673bceaf3f24a7a3d3ed346d07cedc6524ad888d (patch)
treec29edfda3b56e0db67dcdd35e295aa44f806dfc3 /src/backend/access/gist
parenta3c17b2af89cd46b47df3483bb693312d7521795 (diff)
downloadpostgresql-673bceaf3f24a7a3d3ed346d07cedc6524ad888d.tar.gz
postgresql-673bceaf3f24a7a3d3ed346d07cedc6524ad888d.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/gist')
0 files changed, 0 insertions, 0 deletions