From c5f83259bf34ea4ce0cf56eef499a4fd810743d8 Mon Sep 17 00:00:00 2001 From: loquacity Date: Tue, 15 Aug 2023 15:19:43 +1000 Subject: [PATCH] Add data tiering limitation for dimensions --- use-timescale/data-tiering/about-data-tiering.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/use-timescale/data-tiering/about-data-tiering.md b/use-timescale/data-tiering/about-data-tiering.md index a8545b17a4..a72223eac1 100644 --- a/use-timescale/data-tiering/about-data-tiering.md +++ b/use-timescale/data-tiering/about-data-tiering.md @@ -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].