Skip to content

Commit 6cc1a3d

Browse files
matthew123987djw-m
authored andcommitted
Update sequences.mdx
1 parent ec12750 commit 6cc1a3d

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

product_docs/docs/pgd/5/sequences.mdx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,8 @@ There are various possible algorithms for global sequences:
5252
SnowflakeId sequences generate values using an algorithm that doesn't require
5353
inter-node communication at any point. It's faster and more robust and has the
5454
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.
5657

5758
SnowflakeId sequences have the restriction that they work only for 64-bit BIGINT
5859
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
229230
renaming the namespace that contains a `galloc` sequence. Be
230231
mindful of this limitation while designing application schema.
231232

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+
232236
#### Converting a local sequence to a galloc sequence
233237

234238
Before transforming a local sequence to galloc, you need to take care of several

0 commit comments

Comments
 (0)