You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: product_docs/docs/pgd/5/sequences.mdx
+5-1Lines changed: 5 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,8 @@ There are various possible algorithms for global sequences:
52
52
SnowflakeId sequences generate values using an algorithm that doesn't require
53
53
inter-node communication at any point. It's faster and more robust and has the
54
54
useful property of recording the timestamp when the values were
55
-
created.
55
+
created. Snowflake sequences are generally the preferred sequence option if the
56
+
application can support it.
56
57
57
58
SnowflakeId sequences have the restriction that they work only for 64-bit BIGINT
58
59
datatypes and produce values up to 19 digits long. This might be too long for
@@ -229,6 +230,9 @@ support renaming `galloc` sequences or moving them to another namespace or
229
230
renaming the namespace that contains a `galloc` sequence. Be
230
231
mindful of this limitation while designing application schema.
231
232
233
+
Additionally, after restoring a node from a backup, all galloc sequences must manually have their maximum value set to the maximum value of the attached data column.
234
+
235
+
232
236
#### Converting a local sequence to a galloc sequence
233
237
234
238
Before transforming a local sequence to galloc, you need to take care of several
0 commit comments