Clarify add-after-delete column limitation with tiered hypertable (#3432

) Clarify limitation that columns can now be deleted on tiered hypertables, but you cannot subsequently add a new column to a tiered hypertable with the same name as the now-deleted column. Signed-off-by: Mike Freedman <[email protected]> Co-authored-by: atovpeko <[email protected]>
timescale · Sep 13, 2024 · 0021748 · 0021748
1 parent c15a52e
commit 0021748
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/use-timescale/data-tiering/about-data-tiering.md b/use-timescale/data-tiering/about-data-tiering.md
@@ -62,8 +62,8 @@ storage, so your queries fetch the same data as before.
     with `NULL` defaults, adding indexes, changing or renaming the hypertable
     schema, and adding `CHECK` constraints. For `CHECK` constraints, only
     untiered data is verified.
-    Columns can be deleted. However, you cannot add a new column with the same
-    name to the hypertable after enabling tiering.
+    Columns can also be deleted, but you cannot subsequently add a new column
+    to a tiered hypertable with the same name as the now-deleted column.
 
     _Disallowed_ modifications include: adding a column with non-`NULL`
     defaults, renaming a column, changing the data type of a