From 5d3cbc45ee687acb034c3f38662cb0525723212d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B4natas=20Davi=20Paganini?= Date: Wed, 4 Sep 2024 07:16:06 -0300 Subject: [PATCH] Remove obsolete message (#3408) * Remove obsolete message * Add empty line to close the ul/li --------- Co-authored-by: Iain Cox --- .../user-defined-actions/example-tiered-storage.md | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/use-timescale/user-defined-actions/example-tiered-storage.md b/use-timescale/user-defined-actions/example-tiered-storage.md index 1b62c9ff53..95c71eb328 100644 --- a/use-timescale/user-defined-actions/example-tiered-storage.md +++ b/use-timescale/user-defined-actions/example-tiered-storage.md @@ -86,15 +86,7 @@ to move data to low-cost object storage backed by Amazon S3. ); ``` - -This procedure uses PostgreSQL's regular `ALTER TABLE ... SET TABLESPACE` syntax -to move chunks. You could also write the procedure using TimescaleDB's -[`move_chunk`](/api/latest/hypertable/move_chunk) function. The -`move_chunk` function reorders the data as part of the move, which makes -subsequent queries faster. It also requires lower lock levels, so the chunk -remains available for reads during the move. - - + [moving-data]: /use-timescale/:currentVersion:/user-defined-actions/example-tiered-storage/