Skip to content

Commit

Permalink
Add data tiering limitation for dimensions
Browse files Browse the repository at this point in the history
  • Loading branch information
Loquacity committed Aug 15, 2023
1 parent 03abc56 commit c5f8325
Showing 1 changed file with 7 additions and 3 deletions.
10 changes: 7 additions & 3 deletions use-timescale/data-tiering/about-data-tiering.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,11 +88,15 @@ For more about how data tiering works, see the
native data types, but not for non-native types, such as `JSON`, `JSONB`,
and `GIS`.

* **Latency.** S3 has higher access latency than EBS however, S3 has
comparatively greater throughput for large scans. This can affect the
execution time of queries in latency-sensitive environments, especially
* **Latency.** S3 has higher access latency than EBS however, S3 has
comparatively greater throughput for large scans. This can affect the
execution time of queries in latency-sensitive environments, especially
lighter queries.

* **Number of dimensions.** You cannot use data tiering on hypertables
partitioned on more than one dimension. Make sure your hypertables is
partitioned on time only, before you enable data tiering.

## Learn more

Learn [how data tiering works][how-to].
Expand Down

0 comments on commit c5f8325

Please sign in to comment.