Skip to content

Update sequences.mdx #6151

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

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion product_docs/docs/pgd/5/sequences.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,8 @@ There are various possible algorithms for global sequences:
SnowflakeId sequences generate values using an algorithm that doesn't require
inter-node communication at any point. It's faster and more robust and has the
useful property of recording the timestamp when the values were
created.
created. Snowflake sequences are generally the preferred sequence option if the
application can support it.

SnowflakeId sequences have the restriction that they work only for 64-bit BIGINT
datatypes and produce values up to 19 digits long. This might be too long for
Expand Down Expand Up @@ -229,6 +230,10 @@ support renaming `galloc` sequences or moving them to another namespace or
renaming the namespace that contains a `galloc` sequence. Be
mindful of this limitation while designing application schema.

Additionally, after restoring a node from a backup, all galloc sequences must manually have
their next value set to the maximum value of the related column.
See ["Set a new start value for the sequence"](#2-set-a-new-start-value-for-the-sequence).

#### Converting a local sequence to a galloc sequence

Before transforming a local sequence to galloc, you need to take care of several
Expand Down
Loading