timescale · billy-the-fish · May 10, 2024 · Nov 30, 2023 · Nov 30, 2023 · Dec 14, 2023
diff --git a/_partials/_cloud-connect.md b/_partials/_cloud-connect.md
@@ -2,28 +2,22 @@
 
 ### Check your service and connect to it
 
-To check a service associated with your account is running, then connect to it:
+To ensure a Timescale service is running correctly:
 
 1.  In the [Services section in Timescale Console][services-portal], check that your service is marked as `Running`.
 
-1.  In your development environment open [psql][install-psql] and connect to your service with the value of
-    `Service URL` in the config file you just saved.
+1. Use PopSQL or psql to connect to your service:
+    - [Setup PopSQL][popsql]: Follow the instructions to easily connect to your service in the UI.
+    - [psql][install-psql]: Connect to your service with the value of `Service URL` from the config file you 
+      just saved.
 
-    The command line looks like:
-    <CodeBlock canCopy={true} showLineNumbers={false} children={`
-    psql "postgres://tsdbadmin:<PASSWORD>@<HOST>:<PORT>/tsdb?sslmode=require"
-    `} />
+      <CodeBlock canCopy={true} showLineNumbers={false} children={`
+      psql "postgres://tsdbadmin:<PASSWORD>@<HOST>:<PORT>/tsdb?sslmode=require"
+      `} />
 
-    You are connected to your service and are now able to issue commands. You see something like:
+    You are connected to your service and are now able to issue commands. 
 
-    <CodeBlock canCopy={false} showLineNumbers={true} children={`
-    psql (14.5, server 15.3 (Ubuntu 15.3-1.pgdg22.04+1))
-    SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, bits: 256, compression: off)
-    Type "help" for help.
-    tsdb=>
-    `} />
-
-1.  To create a PostgreSQL table, copy the following into the psql prompt and press Enter:
+1.  Create a PostgreSQL table, copy the following into [PopSQL][popsql] or psql, then run your query:
 
     ```sql
     CREATE TABLE stocks_real_time (
@@ -34,15 +28,9 @@ To check a service associated with your account is running, then connect to it:
     );
     ```
 
-1.  Check that the table exists in your service with the `\dt` command. In psql:
-
-    <CodeBlock canCopy={true} showLineNumbers={false} children={`
-    \\dt
-    `} />
-
-    You see the table listing in your service.
-
-1. To disconnect, type `exit`.
+1.  Check that the table exists.
+    - In PopSQL, you see the table in the UI. 
+    - In psql, run the `\dt` command, You see the table listing in your service. To disconnect, type `exit`.
 
 
 Quick recap, you find configuration information about your
@@ -54,4 +42,5 @@ config file.
 [tsc-portal]: https://console.cloud.timescale.com/
 [account-portal]: https://console.cloud.timescale.com/dashboard/account
 [services-portal]: https://console.cloud.timescale.com/dashboard/services
-[install-psql]: /use-timescale/:currentVersion:/integrations/query-admin/psql/
+[install-psql]: /use-timescale/:currentVersion:/integrations/query-admin/psql/
+[popsql]: /use-timescale/:currentVersion:/popsql/
diff --git a/_partials/_cloud-installation.md b/_partials/_cloud-installation.md
@@ -2,14 +2,16 @@
 
 ### Create a Timescale account
 
-If you have not already signed up for Timescale, join up now:
+To setup Timescale:
 
 1.  Sign up for a [30 day free trial][sign-up].
 
     You receive a confirmation email in your inbox.
 1.  In the confirmation email, click the link supplied and sign in to [Timescale Console][tsc-portal].
 
-    Answer the requirements questions, it helps us optimize for your use case. You can now create a Timescale service.
+    Answer the requirements questions, they help us optimize the Timescale service for your use case. You can now create a Timescale service.
+
+
 
 </Procedure>
 

diff --git a/_partials/_cloud-integrations-exporter-region.md b/_partials/_cloud-integrations-exporter-region.md
@@ -1,4 +1,4 @@
 <Highlight type="important">
-Your exporter must be in the same AWS region as your database service. If you
-have databases in multiple regions, you can create multiple exporters.
+Your exporter must be in the same AWS region as the Timescale Service it is attached to. 
+If you have Timescale Services running in multiple regions, create an exporter for each region. 
 </Highlight>
diff --git a/_partials/_cloud-intro.md b/_partials/_cloud-intro.md
@@ -1,9 +1,9 @@
-Timescale is a cloud based PostgreSQL platform for resource-intensive workloads. We help you you build faster, scale further, and stay under budget. Timescale offers the following PostgreSQL database optimisations:
+Timescale is a cloud-based PostgreSQL platform for resource-intensive workloads. We help you build faster, scale further, and stay under budget. Timescale offers the following PostgreSQL database optimizations:
 
 - [**Time-series data**](https://www.timescale.com/blog/what-is-a-time-series-database/#what-is-a-time-series-database): a
-  TimescaleDB instance optimized for your time-series and analytics workloads. Get automated dynamic data partitioning, hybrid row-columnar storage, advanced compression techniques, incremental up-to-date materializations, and specialized analysis functions as well as cloud-only features like transparent tiering to low-cost object storage.
+  TimescaleDB instance optimized for your time-series and analytics workloads. Get automated dynamic data partitioning, hybrid row-columnar storage, advanced compression techniques, incremental up-to-date materializations, and specialized analysis functions as well as cloud-only features like transparent tiering and low-cost object storage.
 
 - **All other workloads**: a [Dynamic PostgreSQL](https://www.timescale.com/dynamic-postgresql) instance where you select a compute range, only paying for the base and the amount of extra CPU as you scale.
 
 All databases are extended with lightning fast vector search, and include all the cloud tooling you'd expect for production use,
-with automatic backups, high availability, read replicas, data forking, connection pooling, usage-based storage and much more.
+with automatic backups, high availability, read replicas, data forking, connection pooling, usage-based storage, and much more.
diff --git a/_partials/_compression-intro.md b/_partials/_compression-intro.md
@@ -9,3 +9,20 @@ data. This means that instead of using lots of rows to store the data, it stores
 the same data in a single row. Because a single row takes up less disk space
 than many rows, it decreases the amount of disk space required, and can also
 speed up your queries.
+
+For example, if you had a table with data that looked a bit like this:
+
+|Timestamp|Device ID|Device Type|CPU|Disk IO|
+|-|-|-|-|
+|12:00:01|A|SSD|70.11|13.4|
+|12:00:01|B|HDD|69.70|20.5|
+|12:00:02|A|SSD|70.12|13.2|
+|12:00:02|B|HDD|69.69|23.4|
+|12:00:03|A|SSD|70.14|13.0|
+|12:00:03|B|HDD|69.70|25.2|
+
+You can convert this to a single row in array form, like this:
+
+|Timestamp|Device ID|Device Type|CPU|Disk IO|
+|-|-|-|-|-|
+|[12:00:01, 12:00:01, 12:00:02, 12:00:02, 12:00:03, 12:00:03]|[A, B, A, B, A, B]|[SSD, HDD, SSD, HDD, SSD, HDD]|[70.11, 69.70, 70.12, 69.69, 70.14, 69.70]|[13.4, 20.5, 13.2, 23.4, 13.0, 25.2]|
diff --git a/_partials/_migrate_dual_write_step1.md b/_partials/_migrate_dual_write_step1.md
@@ -9,4 +9,4 @@ ensure that enough disk is pre-provisioned on your Timescale instance.
 
 <OpenSupportRequest />
 
-[create-service]: /use-timescale/:currentVersion:/services/create-a-service/
+[create-service]: /getting-started/:currentVersion:/services/
diff --git a/_partials/_migrate_dual_write_step2.md b/_partials/_migrate_dual_write_step2.md
@@ -7,8 +7,20 @@ you must think about how to handle the failure to write to either the source or
 target database, and what mechanism you want to or can build to recover from
 such a failure.
 
+Should your time-series data have foreign-key references into a plain table,
+you must ensure that your application correctly maintains the foreign key
+relations. If the referenced column is a `*SERIAL` type, the same row inserted
+into the source and target _may not_ obtain the same autogenerated id. If this
+happens, the data backfilled from the source to the target is internally
+inconsistent. In the best case it causes a foreign key violation, in the worst
+case, the foreign key constraint is maintained, but the data references the
+wrong foreign key. To avoid these issues, best practice is to follow
+[live migration].
+
 You may also want to execute the same read queries on the source and target
 database to evaluate the correctness and performance of the results which the
 queries deliver. Bear in mind that the target database spends a certain amount
 of time without all data being present, so you should expect that the results
 are not the same for some period (potentially a number of days).
+
+[live migration]: /migrate/:currentVersion:/live-migration/
diff --git a/_partials/_migrate_live_migration_cleanup.md b/_partials/_migrate_live_migration_cleanup.md
@@ -6,9 +6,9 @@ docker run --rm -it --name live-migration-clean \
     -e PGCOPYDB_TARGET_PGURI=$TARGET \
     --pid=host \
     -v ~/live-migration:/opt/timescale/ts_cdc \
-    timescale/live-migration:v0.0.7 clean --prune
+    timescale/live-migration:v0.0.14 clean --prune
 ```
 
 The `--prune` flag is used to delete temporary files in the `~/live-migration` directory
 that were needed for the migration process. It's important to note that executing the
-`clean` command means you cannot resume the interrupted live migration.
+`clean` command means you cannot resume the interrupted live migration.
diff --git a/_partials/_migrate_live_migration_docker_subcommand.md b/_partials/_migrate_live_migration_docker_subcommand.md
@@ -6,7 +6,7 @@ docker run --rm -it --name live-migration \
     -e PGCOPYDB_TARGET_PGURI=$TARGET \
     --pid=host \
     -v ~/live-migration:/opt/timescale/ts_cdc \
-    timescale/live-migration:v0.0.7 --help
+    timescale/live-migration:v0.0.14 --help
 
 Live migration moves your PostgreSQL/TimescaleDB to Timescale Cloud with minimal downtime.
 
@@ -53,7 +53,18 @@ docker run --rm -it --name live-migration-snapshot \
     -e PGCOPYDB_TARGET_PGURI=$TARGET \
     --pid=host \
     -v ~/live-migration:/opt/timescale/ts_cdc \
-    timescale/live-migration:v0.0.7 snapshot
+    timescale/live-migration:v0.0.14 snapshot
+```
+
+In addition to creating a snapshot, this process also validates prerequisites on the source and target to ensure the database instances are ready for replication.
+
+For example, it checks if all tables on the source have either a PRIMARY KEY or REPLICA IDENTITY set. If not, it displays a warning message listing the tables without REPLICA IDENTITY and waits for user confirmation before proceeding with the snapshot creation.
+
+```sh
+2024-03-25T12:40:40.884 WARNING: The following tables in the Source DB have neither a primary key nor a REPLICA IDENTITY (FULL/INDEX)
+2024-03-25T12:40:40.884 WARNING: UPDATE and DELETE statements on these tables will not be replicated to the Target DB
+2024-03-25T12:40:40.884 WARNING:        - public.metrics
+Press 'c' and ENTER to continue
 ```
 
 ### 3.b Perform live-migration
@@ -67,12 +78,11 @@ docker run --rm -it --name live-migration-migrate \
     -e PGCOPYDB_TARGET_PGURI=$TARGET \
     --pid=host \
     -v ~/live-migration:/opt/timescale/ts_cdc \
-    timescale/live-migration:v0.0.7 migrate
+    timescale/live-migration:v0.0.14 migrate
 ```
 <Highlight type="note">
 If the migrate command stops for any reason during execution, you can resume
 the migration from where it left off by adding a `--resume` flag. This is only
 possible if the `snapshot` command is intact and if a volume mount, such
-as ~/live-migration, is utilized. Note that the `snapshot` command is required
-only if you want to resume live migration in event of a crash.
-</Highlight>
+as `~/live-migration`, is utilized.
+</Highlight>
diff --git a/_partials/_migrate_live_migration_step2.md b/_partials/_migrate_live_migration_step2.md
@@ -2,6 +2,14 @@ import SetupSourceTarget from "versionContent/_partials/_migrate_set_up_source_a
 
 <SetupSourceTarget />
 
+<Highlight type="important">
+Do not use a Timescale connection pooler connection for live migration. There
+are a number of issues which can arise when using a connection pooler, and no
+advantage. Very small instances may not have enough connections configured by
+default, in which case you should modify the value of `max_connections`, in
+your instance, as shown on [Configure database parameters](/use-timescale/:currentVersion/configuration/customize-configuration/#configure-database-parameters).
+</Highlight>
+
 It's important to ensure that the `old_snapshot_threshold` value is set to the
 default value of `-1` in your source database. This prevents PostgreSQL from
 treating the data in a snapshot as outdated. If this value is set other than

diff --git a/_partials/_migrate_pg_dump_do_not_recommend_for_large_migration.md b/_partials/_migrate_pg_dump_do_not_recommend_for_large_migration.md
@@ -2,12 +2,11 @@ import OpenSupportRequest from "versionContent/_partials/_migrate_open_support_r
 
 We do not recommend using this migration method to migrate more than
 100&nbsp;GB of data, primarily because of the amount of downtime that it
-implies for your application, instead use the [dual-write and backfill]
+implies for your application, instead use the [live migration]
 low-downtime migration solution. Should you nonetheless wish to migrate more
 than 400&nbsp;GB of data with this method, open a support request to ensure
 that enough disk is pre-provisioned on your Timescale instance.
 
 <OpenSupportRequest />
 
-[dual-write and backfill]: /migrate/:currentVersion:/dual-write-and-backfill
-
+[live migration]: /migrate/:currentVersion:/live-migration
diff --git a/_partials/_multi-node-deprecation.md b/_partials/_multi-node-deprecation.md
@@ -1,7 +1,9 @@
 <Highlight type="warning">
-Multi-node support has been deprecated with TimescaleDB 2.13. This is the last version that includes multi-node support and it supports multi-node installations with PostgreSQL versions 13, 14, and 15.
 
-Learn more about it [here][multi-node-deprecation].
+[Multi-node support is deprecated][multi-node-deprecation].
+
+TimescaleDB v2.13 is the last release that includes multi-node support for PostgreSQL 
+versions 13, 14, and 15.
 </Highlight>
 
 [multi-node-deprecation]: https://github.com/timescale/timescaledb/blob/main/docs/MultiNodeDeprecation.md
diff --git a/_troubleshooting/cloud-singledb.md b/_troubleshooting/cloud-singledb.md
@@ -1,5 +1,5 @@
 ---
-title: Cannot add column to a compressed hypertable
+title: Cannot create another database
 section: troubleshooting
 products: [cloud, mst, self_hosted]
 topics: [services]
@@ -26,7 +26,8 @@ tags: [services]
 * Copy this comment at the top of every troubleshooting page
 -->
 
-Each Timescale service can have a single database. The database must be
-named `tsdb`. If you try to create an additional database you receive this error.
+Each Timescale service hosts a single database named `tsdb`. You see this error when you try 
+to create an additional database in a service. If you need another database, 
+[create a new service][create-service].
 
-If you need another database, you need to create a new service.
+[create-service]: /getting-started/:currentVersion:/services/#create-a-timescale-service
diff --git a/_troubleshooting/compression-dml-tuple-limit.md b/_troubleshooting/compression-dml-tuple-limit.md
@@ -31,7 +31,7 @@ The limit can be increased or turned off (set to 0) like so:
 
 ```sql
 -- set limit to a milion tuples
-SET timescaledb.timescaledb.max_tuples_decompressed_per_dml_transaction TO 1000000;
+SET timescaledb.max_tuples_decompressed_per_dml_transaction TO 1000000;
 -- disable limit by setting to 0
-SET timescaledb.timescaledb.max_tuples_decompressed_per_dml_transaction TO 0;
+SET timescaledb.max_tuples_decompressed_per_dml_transaction TO 0;
 ```
diff --git a/about/release-notes/changes-in-timescaledb-2.md b/about/release-notes/changes-in-timescaledb-2.md
@@ -422,7 +422,7 @@ statistics related to all jobs.
 
 #### Removed
 
-*   [`timescaledb_information.continuous_aggregate_stats`](https://legacy-docs.timescale.com/v1.7/api#timescaledb_information-continuous_aggregate_stats): Removed in favor of the `job_stats` view mentioned above.
+*   `timescaledb_information.continuous_aggregate_stats`: Removed in favor of the `job_stats` view mentioned above.
 
 ### Updating existing continuous aggregates
 
@@ -465,9 +465,9 @@ policies are now available in the main jobs view.
 
 #### Removed
 
-*   [`add_drop_chunks_policy`](https://legacy-docs.timescale.com/v1.7/api#add_drop_chunks_policy): removed in favor of the
+*   `add_drop_chunks_policy`: removed in favor of the
 explicit functions above.
-*   [`timescaledb_information.drop_chunks_policies`](https://legacy-docs.timescale.com/v1.7/api#timescaledb_information-drop_chunks_policies):
+*   `timescaledb_information.drop_chunks_policies`:
  view has been removed in favor of the more general jobs view.
 
 ### Compression
@@ -487,11 +487,11 @@ compression policies are now available in the main jobs view.
 
 #### Removed
 
-*   [`add_compress_chunk_policy`](https://legacy-docs.timescale.com/v1.7/api#add_compress_chunks_policy): Removed in favor of the
+*   `add_compress_chunk_policy`: Removed in favor of the
 explicit functions above.
-*   [`timescaledb_information.compressed_hypertable_stats`](https://legacy-docs.timescale.com/v1.7/api#timescaledb_information-compressed_hypertable_stats):
+*   `timescaledb_information.compressed_hypertable_stats`:
 Removed in favor of the new `hypertable_compression_stats(hypertable)` function linked above
-*   [`timescaledb_information.compressed_chunk_stats`](https://legacy-docs.timescale.com/v1.7/api#timescaledb_information-compressed_chunk_stats):
+*   `timescaledb_information.compressed_chunk_stats`:
 Removed in favor of the new `chunk_compression_stats(hypertable)` function linked above.
 
 ## Managing policies and other jobs
@@ -517,10 +517,10 @@ features has been removed. All features are available either under the community
 open-source Apache-2 License. [This blog post](https://blog.timescale.com/blog/building-open-source-business-in-cloud-era-v2/)
 explains the changes. The following changes were made to license API:
 
-*   [`timescaledb_information.license`](https://legacy-docs.timescale.com/v1.7/api#timescaledb_information-license):  This view
+*   `timescaledb_information.license`:  This view
 has been removed, as it primarily provided information on the enterprise license key's expiration date, which is no
 longer applicable. The current license used by the extension can instead be viewed in the GUC below.
-*   `timescaledb.license`: This GUC value (which replaces the former [`timescaledb.license_key`](https://legacy-docs.timescale.com/v1.7/api#timescaledb_license-key) GUC)
+*   `timescaledb.license`: This GUC value (which replaces the former `timescaledb.license_key` GUC)
 can take the value `timescale` or `apache`. It can be set only at startup (in the postgresql.conf configuration file
 or on the server command line), and allows limiting access to certain features
 by license. For example, setting the

diff --git a/about/release-notes/index.md b/about/release-notes/index.md
@@ -74,10 +74,10 @@ New compression settings take effect on any new chunks that are compressed after
 Following the deprecation announcement for Multi-node in TimescaleDB 2.13,
 Multi-node is no longer supported starting with TimescaleDB 2.14.
 
-TimescaleDB 2.13 is the last version that includes multi-node support. Learn more about it [here](docs/MultiNodeDeprecation.md).
+TimescaleDB 2.13 is the last version that includes multi-node support. Learn more about it [here][multi-node-deprecation].
 
 If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB, read the
-[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).
+[migration documentation][multi-node-to-timescale-service].
 
 #### Deprecation notice: recompress_chunk procedure
 TimescaleDB 2.14 is the last version that will include the recompress_chunk procedure. Its
@@ -174,10 +174,10 @@ available opportunity.
 #### Deprecation notice: Multi-node support
 TimescaleDB 2.13 is the last version that will include multi-node support. Multi-node
 support in 2.13 is available for PostgreSQL 13, 14 and 15. Learn more about it
-[here](https://github.com/timescale/timescaledb/blob/main/docs/MultiNodeDeprecation.md).
+[here][multi-node-deprecation].
 
 If you want to migrate from multi-node TimescaleDB to single-node TimescaleDB read the
-[migration documentation](https://docs.timescale.com/migrate/latest/multi-node-to-timescale-service/).
+[migration documentation][multi-node-to-timescale-service].
 
 #### PostgreSQL 13 deprecation announcement
 We will continue supporting PostgreSQL 13 until April 2024. Sooner to that time, we will announce the specific version of TimescaleDB in which PostgreSQL 13 support will not be included going forward.
@@ -692,3 +692,5 @@ For release notes for older TimescaleDB versions, see the
 [pg-upgrade]: /self-hosted/:currentVersion:/upgrades/upgrade-pg/
 [migrate-caggs]: /use-timescale/:currentVersion:/continuous-aggregates/migrate/
 [join-caggs]: /use-timescale/:currentVersion:/continuous-aggregates/create-a-continuous-aggregate/#create-a-continuous-aggregate-with-a-join
+[multi-node-to-timescale-service]:/migrate/:currentVersion:/playbooks/multi-node-to-timescale-service/
+[multi-node-deprecation]: https://github.com/timescale/timescaledb/blob/main/docs/MultiNodeDeprecation.md