-
Notifications
You must be signed in to change notification settings - Fork 477
Clarify sequence bumps perform replicated writes #22039
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify sequence bumps perform replicated writes #22039
Conversation
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Rafi Shamim ***@***.***> writes:
this lgtm!
sweet thanks!
it may be worth mentioning something about cached sequences too.
something to the effect of: [Cached sequences]
(#link-to-cached-sequence-docs) can reduce the frequency of these
writes, though gaps in sequence values may occur if cached values are
lost
(These will perform better than normal sequences, but not as good as
the ID generation functions)
updated to add your suggested language with the link to cached
sequences!
thanks for the review Rafi!
|
|
PS @rafiss after docs team review I am planning to backport this change to the docs for all supported versions v23.2 and later - please let me know if you disagree for any reason! i suspect it's still true on those older versions too, right? |
florence-crl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, with non-blocking nits.
|
thanks for the reviews! now backporting to docs for all supported versions before merging ... |
This was not stated explicitly enough in the `CREATE SEQUENCE` docs and led to performance issues for a customer who had migrated from PG with sequence usage. Fixes DOC-15768
46c0d0e to
2921032
Compare
This was not stated explicitly enough in the
CREATE SEQUENCEdocs and led to performance issues for a customer who had migrated from PG with sequence usage.Fixes DOC-15768