Skip to content

Commit

Permalink
The default sequence type is distributed
Browse files Browse the repository at this point in the history
In #eng-pgd-bdr-harp, Jakub Wartak noticed the discrepancy and Petr Jelinek confirmed that this is something to be adjusted in the docs.

For reference: https://edb.slack.com/archives/C01GJ1C1BNH/p1668093242529229
  • Loading branch information
tureba authored Nov 10, 2022
1 parent 61f7daa commit f47e5f2
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions product_docs/docs/pgd/4/bdr/sequences.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -63,15 +63,15 @@ determines the kind of sequence to create when the `CREATE SEQUENCE`
command is executed or when a `serial`, `bigserial`, or
`GENERATED BY DEFAULT AS IDENTITY` column is created. Valid settings are:

- `local` (the default), meaning that newly created
- `local`, meaning that newly created
sequences are the standard PostgreSQL (local) sequences.
- `galloc`, which always creates globally allocated range sequences.
- `snowflakeid`, which creates global sequences for BIGINT sequences that
consist of time, nodeid, and counter components. You can't use it with
INTEGER sequences (so you can use it for `bigserial` but not for `serial`).
- `timeshard`, which is the older version of SnowflakeId sequence and is provided for
backward compatibility only. The SnowflakeId is preferred.
- `distributed`, which is a special value that you can use only for
- `distributed` (the default), which is a special value that you can use only for
`bdr.default_sequence_kind`. It selects `snowflakeid` for `int8`
sequences (i.e., `bigserial`) and `galloc` sequence for `int4`
(i.e., `serial`) and `int2` sequences.
Expand Down

0 comments on commit f47e5f2

Please sign in to comment.