-
Notifications
You must be signed in to change notification settings - Fork 453
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
87 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
| Property | UUID generated with `uuid_v4()` | INT generated with `unique_rowid()` | Sequences | | ||
|--------------------------------|-----------------------------------------|----------------------------------------------|--------------------------------| | ||
| Size | 16 bytes | 8 bytes | 1 to 8 bytes | | ||
| Ordering properties | Unordered | Somewhat time-ordered | Highly time-ordered | | ||
| Value distribution | Uniformly distributed (128 bits) | Contains time and space (node ID) components | Dense, small values | | ||
| Performance cost at generation | Small, scalable | Small, scalable | Variable, can cause contention | | ||
| Locality | Maximally distributed, least contention | Somewhat local, may cause INSERT contention | Highly local, most INSERT contention | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
Sequential numbers can be generated in CockroachDB using the built-in | ||
function `unique_rowid()` or using [SQL sequences](create-sequence.html). | ||
|
||
{{site.data.alerts.callout_info}}Unless you need roughly-ordered | ||
numbers, we recommend to use `UUID` values instead. See the previous | ||
FAQ for details.{{site.data.alerts.end}} | ||
|
||
{{site.data.alerts.callout_info}}Sequences produce <emph>unique</emph> | ||
values, however not all values are guaranteed to be produced (e.g., | ||
when a transaction is canceled after it consumes a value) and the | ||
values may be slightly reordered (e.g., when a transaction that | ||
consumes a lower sequence number commits after a transaction that | ||
consumes a higher number).{{site.data.alerts.end}} | ||
|
||
{{site.data.alerts.callout_info}}For maximum performance, avoid using | ||
sequences or <code>unique_rowid()</code> to generate row IDs or | ||
indexed columns. This is because sequence values and values generated | ||
by <code>unique_rowid()</code> are logically close to each other and | ||
can cause contention on few data ranges during inserts. Instead, | ||
prefer <code>UUID</code> identifiers.{{site.data.alerts.end}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
We find that most use cases that appear to ask for a strong time-based | ||
write ordering can be solved with other, more distribution-friendly | ||
solutions instead. For example, CockroachDB's [time travel queries | ||
(`AS OF SYSTEM | ||
TIME`)](https://www.cockroachlabs.com/blog/time-travel-queries-select-witty_subtitle-the_future/) | ||
support the following: | ||
|
||
- Paginate through all the changes to a table or dataset. | ||
- Determine the order of changes to data over time. | ||
- Determine the state of data at some point in the past. | ||
- Determine the changes to data between two points of time. | ||
|
||
Should your application absolutely require it, it is still possible to | ||
create a strictly monotonic counter in CockroachDB that increases over | ||
time, as follows: | ||
|
||
- initially: `CREATE TABLE cnt(val INT PRIMARY KEY); INSERT INTO cnt(val) VALUES(1);` | ||
- in each transaction: `INSERT INTO cnt(val) SELECT max(val)+1 FROM cnt RETURNING val;` | ||
|
||
This will cause all your INSERT transactions to conflict with each | ||
other and effectively force the transactions to commit one at a time | ||
throughout the cluster, which in turn guarantees the values generated | ||
in this way are strictly increasing over time without gaps. The caveat | ||
is that performance is severely limited as a result. | ||
|
||
Please contact us and describe your situation if you find yourself | ||
interested in this problem. We would be glad to help you find | ||
alternative solutions and possibly extend CockroachDB to better match | ||
your needs. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters