Skip to content

Commit

Permalink
Update tiered-data-replicas-forks.md (#2936)
Browse files Browse the repository at this point in the history
Remove unnecessary line break

Signed-off-by: Mike Freedman <[email protected]>
Co-authored-by: Iain Cox <[email protected]>
  • Loading branch information
mfreed and billy-the-fish authored Mar 9, 2024
1 parent ebc0c48 commit 611c258
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions use-timescale/data-tiering/tiered-data-replicas-forks.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,6 @@ tags: [storage, data management]

There is one more thing that makes Tiered Storage even more amazing: when you keep data in the low-cost object storage tier,
you pay for this data only once, regardless of whether you have a [high-availability replica][ha-replica]

or [read replicas][read-replica] running in your service. We call this the savings multiplication effect of Tiered Storage.

The same applies to [forks][operations-forking], which you can use, for example, for running tests or creating dev environments.
Expand Down Expand Up @@ -70,4 +69,4 @@ Once 14 days pass after soft deleting the data,that is the number of references

[ha-replica]: /use-timescale/:currentVersion:/ha-replicas/high-availability/
[read-replica]: /use-timescale/:currentVersion:/ha-replicas/read-scaling/#read-replicas
[operations-forking]: /use-timescale/:currentVersion:/services/service-management/#fork-a-service
[operations-forking]: /use-timescale/:currentVersion:/services/service-management/#fork-a-service

0 comments on commit 611c258

Please sign in to comment.