Merge branch 'latest' into 3292-docs-rfc-update-docs-to-remove-centos-have-correct-versions-of-postgres-support-and-align-supported-platforms

atovpeko · web-flow · commit 0993b304023d · 2025-09-02T12:03:59.000+03:00
diff --git a/_partials/_livesync-terminal.md b/_partials/_livesync-terminal.md
@@ -178,9 +178,9 @@ instance to a $SERVICE_LONG:
    As you run $LIVESYNC continuously, best practice is to run it as a Docker daemon.
 
    ```shell
-   docker run -d --rm --name livesync timescale/live-sync:v0.1.22 run \
+   docker run -d --rm --name livesync timescale/live-sync:v0.1.25 run \
       --publication <publication_name> --subscription <subscription_name> \
-      --source $SOURCE --target $TARGET
+      --source $SOURCE --target $TARGET --table-map <table_map_as_json>
    ```
 
    `--publication`: The name of the publication as you created in the previous step. To use multiple publication repeat the `--publication` flag.
@@ -191,6 +191,19 @@ instance to a $SERVICE_LONG:
 
    `--target`: The connection string to the target $SERVICE_LONG.
 
+   `--table-map`: (Optional) A JSON string that maps source tables to target tables. If not provided, the source and target table names are assumed to be the same.
+   For example, to map the source table `metrics` to the target table `metrics_data`:
+
+   ```
+   --table-map '{"source": {"schema": "public", "table": "metrics"}, "target": {"schema": "public", "table": "metrics_data"}}'
+   ```
+   To map only the schema, use:
+
+   ```
+   --table-map '{"source": {"schema": "public"}, "target": {"schema": "analytics"}}'
+   ```
+   This flag can be repeated for multiple table mappings.
+
 1. **Capture Logs**
 
    Once $LIVESYNC is running as a docker daemon, you can also capture the logs:
@@ -315,7 +328,7 @@ EOF
    Use the `--drop` flag to remove the replication slots created by $LIVESYNC on the source database.
 
    ```shell
-   docker run -it --rm --name livesync timescale/live-sync:v0.1.22 run \
+   docker run -it --rm --name livesync timescale/live-sync:v0.1.25 run \
       --publication <publication_name> --subscription <subscription_name> \
       --source $SOURCE --target $TARGET \
       --drop
diff --git a/_partials/_toolkit-install-update-debian-base.md b/_partials/_toolkit-install-update-debian-base.md
@@ -0,0 +1,78 @@
+## Prerequisites
+
+To follow this procedure:
+
+- [Install $TIMESCALE_DB][debian-install].
+- Add the $TIMESCALE_DB repository and the GPG key.
+
+## Install $TOOLKIT_LONG
+
+These instructions use the `apt` package manager.
+
+<Procedure>
+
+1.  Update your local repository list:
+
+    ```bash
+    sudo apt update
+    ```
+
+1.  Install TimescaleDB Toolkit:
+
+    ```bash
+    sudo apt install timescaledb-toolkit-postgresql-17
+    ```
+
+1.  [Connect to the database][connect] where you want to use $TOOLKIT_SHORT.
+1.  Create the $TOOLKIT_SHORT extension in the database:
+
+    ```sql
+    CREATE EXTENSION timescaledb_toolkit;
+    ```
+
+</Procedure>
+
+## Update $TOOLKIT_LONG
+
+Update $TOOLKIT_SHORT by installing the latest version and running `ALTER EXTENSION`.
+
+<Procedure>
+
+1.  Update your local repository list:
+
+    ```bash
+    apt update
+    ```
+
+1. Install the latest version of $TOOLKIT_LONG:
+
+    ```bash
+    apt install timescaledb-toolkit-postgresql-17
+    ```
+
+1.  [Connect to the database][connect] where you want to use the new version of $TOOLKIT_SHORT.
+1.  Update the $TOOLKIT_SHORT extension in the database:
+
+    ```sql
+    ALTER EXTENSION timescaledb_toolkit UPDATE;
+    ```
+
+    <Highlight type="note">
+
+    For some $TOOLKIT_SHORT versions, you might need to disconnect and reconnect active
+    sessions.
+
+    </Highlight>
+
+</Procedure>
+
+[brew-install]: https://brew.sh
+[cloud]: /use-timescale/:currentVersion:/services/
+[debian-install]: /self-hosted/:currentVersion:/install/installation-linux/
+[docker-install]: /self-hosted/:currentVersion:/install/installation-docker/
+[mst]: /mst/:currentVersion:/
+[red-hat-install]: /self-hosted/:currentVersion:/install/installation-linux/
+[toolkit-gh-docs]: https://github.com/timescale/timescaledb-toolkit#-installing-from-source
+[connect]: /integrations/:currentVersion:/find-connection-details/
+[update-docker]: /self-hosted/:currentVersion:/upgrades/upgrade-docker/
+[macos-install]: /self-hosted/:currentVersion:/install/installation-macos/
diff --git a/_partials/_toolkit-install-update-redhat-base.md b/_partials/_toolkit-install-update-redhat-base.md
@@ -0,0 +1,86 @@
+
+## Prerequisites
+
+To follow this procedure:
+
+- [Install $TIMESCALE_DB][red-hat-install].
+- Create a $TIMESCALE_DB repository in your `yum` `repo.d` directory.
+
+## Install $TOOLKIT_LONG
+
+These instructions use the `yum` package manager.
+
+<Procedure>
+
+1.  Set up the repository:
+
+    ```bash
+    curl -s https://packagecloud.io/install/repositories/timescale/timescaledb/script.deb.sh | sudo bash
+    ```
+
+1.  Update your local repository list:
+
+    ```bash
+    yum update
+    ```
+
+1.  Install $TOOLKIT_LONG:
+
+    ```bash
+    yum install timescaledb-toolkit-postgresql-17
+    ```
+
+1.  [Connect to the database][connect] where you want to use $TOOLKIT_SHORT.
+1.  Create the $TOOLKIT_SHORT extension in the database:
+
+    ```sql
+    CREATE EXTENSION timescaledb_toolkit;
+    ```
+
+</Procedure>
+
+## Update $TOOLKIT_LONG
+
+Update $TOOLKIT_SHORT by installing the latest version and running `ALTER EXTENSION`.
+
+<Procedure>
+
+1.  Update your local repository list:
+
+    ```bash
+    yum update
+    ```
+
+1.  Install the latest version of $TOOLKIT_LONG:
+
+    ```bash
+    yum install timescaledb-toolkit-postgresql-17
+    ```
+
+1.  [Connect to the database][connect] where you want to use the new version of $TOOLKIT_SHORT.
+1.  Update the $TOOLKIT_SHORT extension in the database:
+
+    ```sql
+    ALTER EXTENSION timescaledb_toolkit UPDATE;
+    ```
+
+    <Highlight type="note">
+
+    For some $TOOLKIT_SHORT versions, you might need to disconnect and reconnect active
+    sessions.
+
+    </Highlight>
+
+</Procedure>
+
+
+[brew-install]: https://brew.sh
+[cloud]: /use-timescale/:currentVersion:/services/
+[debian-install]: /self-hosted/:currentVersion:/install/installation-linux/
+[docker-install]: /self-hosted/:currentVersion:/install/installation-docker/
+[mst]: /mst/:currentVersion:/
+[red-hat-install]: /self-hosted/:currentVersion:/install/installation-linux/
+[toolkit-gh-docs]: https://github.com/timescale/timescaledb-toolkit#-installing-from-source
+[connect]: /integrations/:currentVersion:/find-connection-details/
+[update-docker]: /self-hosted/:currentVersion:/upgrades/upgrade-docker/
+[macos-install]: /self-hosted/:currentVersion:/install/installation-macos/
diff --git a/about/changelog.md b/about/changelog.md
@@ -9,18 +9,54 @@ products: [cloud]
 
 All the latest features and updates to $CLOUD_LONG.
 
-## Cross-region backups, PostgreSQL options, and onboarding
+## 🚁 Enhancements to the Postgres source connector
+<Label type="date">August 28, 2025</Label>
+
+- **Easy table selection**: You can now sync the complete source schema in one go. Select multiple tables from the 
+   drop-down menu and start the connector.
+
+- **Sync metadata**: Connectors now display the following detailed metadata:
+    - `Initial data copy`: The number of rows copied at any given point in time.
+    - `Change data capture`: The replication lag represented in time and data size.
+- **Improved UX design**: In-progress syncs with separate sections showing the tables and metadata for 
+   `initial data copy` and `change data capture`, plus a dedicated tab where you can add more tables to the connector.
+
+   ![Connectors UX](https://assets.timescale.com/docs/images/tiger-cloud-console/connectors-new-ui.png )
+
+## 🦋 Developer role GA and hypertable transformation in Console
+<Label type="date">August 21, 2025</Label>
+
+### Developer role (GA)
+
+The [Developer role in Tiger Cloud](https://docs.tigerdata.com/use-timescale/latest/security/members/) is now 
+generally available. It’s a project‑scoped permission set that lets technical users build and 
+operate services, create or modify resources, run queries, and use observability—without admin or billing access. 
+This enforces least‑privilege by default, reducing risk and audit noise, while keeping governance with Admins/Owners and 
+billing with Finance. This means faster delivery (fewer access escalations), protected sensitive settings, 
+and clear boundaries, so the right users can ship changes safely, while compliance and cost control remain intact.
+
+### Transform a table to a hypertable from the Explorer
+
+In Console, you can now easily create hypertables from your regular Postgres tables directly from the Explorer. 
+Clicking on any Postgres table shows an option to open up the hypertable action. Follow the simple steps to set up your 
+partition key and transform the table to a hypertable.
+
+![Transform a table to a hypertable](https://assets.timescale.com/docs/images/table_to_hypertable_1.png)
+
+![Transform a table to a hypertable](https://assets.timescale.com/docs/images/table_to_hypertable_2.png)
+
+## Cross-region backups, Postgres options, and onboarding
 <Label type="date">August 14, 2025</Label>
 
 ### Cross-region backups
 
 You can now store backups in a different region than your service, which improves resilience and helps meet enterprise compliance requirements. Cross‑region backups are available on our Enterprise plan for free at launch; usage‑based billing may be introduced later. For full details, please [see the docs](https://docs.tigerdata.com/use-timescale/latest/backup-restore/#enable-cross-region-backup).
 
-### Standard PostgreSQL instructions for onboarding
+### Standard Postgres instructions for onboarding
 We have added basic instructions for INSERT, UPDATE, DELETE commands to the Tiger Cloud console.  It's now shown as an option in the Import Data page.
 
-### PostgreSQL-only service type
-In Tiger Cloud, you now have an option to choose PostgreSQL-only in the service creation flow. Just click on "Looking for PostgreSQL" on the Service Type screen.
+### Postgres-only service type
+In Tiger Cloud, you now have an option to choose Postgres-only in the service creation flow. Just click `Looking for plan PostgreSQL?` on the `Service Type` screen.
 
 ## Viewer role GA, EXPLAIN plans, and chunk index sizes in Explorer
 <Label type="date">July 31, 2025</Label>
diff --git a/api/hypertable/split_chunk.md b/api/hypertable/split_chunk.md
@@ -11,22 +11,31 @@ products: [cloud, mst, self_hosted]
 
 # split_chunk() <Tag type="community">Community</Tag>
 
-Split a large chunk at a specific point in time.
+Split a large chunk at a specific point in time. If you do not specify the timestamp to split at, `chunk` 
+is split equally. 
 
 ## Samples
 
-Split a chunk at a specific time:
+* Split a chunk at a specific time:
 
-```sql
-CALL split_chunk('chunk_1', split_at => '2025-03-01 00:00');
-```
+    ```sql
+    CALL split_chunk('chunk_1', split_at => '2025-03-01 00:00');
+    ```
 
+* Split a chunk in two:
+
+  For example, If the chunk duration is, 24 hours, the following command splits `chunk_1` into 
+  two chunks of 12 hours each.
+    ```sql
+    CALL split_chunk('chunk_1');
+    ```
+  
 ## Required arguments
 
-|Name|Type| Description                      |
-|---|---|----------------------------------|
-| `chunk` | REGCLASS | Name of the chunk to split.      |
-| `split_at` | `TIMESTAMPTZ`| Timestamp to split the chunk at. |
+|Name|Type| Required | Description                      |
+|---|---|---|----------------------------------|
+| `chunk` | REGCLASS | ✔ | Name of the chunk to split.      |
+| `split_at` | `TIMESTAMPTZ`| ✖ |Timestamp to split the chunk at. |
 
 
 ## Returns
diff --git a/getting-started/services.md b/getting-started/services.md
@@ -35,6 +35,8 @@ Now that you have an active $ACCOUNT_LONG, you create and manage your $SERVICE_S
 
    ![Create a $SERVICE_LONG](https://assets.timescale.com/docs/images/tiger-cloud-console/create-tiger-cloud-service.png)
 
+   To create a plain $PG $SERVICE_SHORT, without any additional capabilities, click `Looking for plan PostgreSQL?` in the top right.
+   
 1. Follow the next steps in `Create a service` to configure the region, compute size, environment, availability, connectivity, and $SERVICE_SHORT name. Then click `Create service`.
 
    Your $SERVICE_SHORT is constructed and ready to use in a few seconds. 
diff --git a/lambda/redirects.js b/lambda/redirects.js
@@ -849,6 +849,10 @@ module.exports = [
     from: "/latest/getting-started/setup",
     to: "https://docs.tigerdata.com/self-hosted/latest/install/"
   },
+  {
+    from: "/latest/using-timescaledb/backup",
+    to: "https://docs.tigerdata.com/self-hosted/latest/backup-and-restore/"
+  },
   {
     from: "/v0.9/faq",
     to: "https://docs.tigerdata.com/about/latest/"
@@ -885,6 +889,10 @@ module.exports = [
     from: "/latest/api#add_dimension",
     to: "https://docs.tigerdata.com/api/latest/hypertable/add_dimension/"
   },
+  {
+    from: "/latest/api#backup",
+    to: "https://docs.tigerdata.com/self-hosted/latest/backup-and-restore/"
+  },
   {
     from: "/timescaledb/latest/tutorials/grafana/grafana-variables/",
     to: "https://docs.tigerdata.com/integrations/latest/grafana/"
diff --git a/mst/installation-mst.md b/mst/installation-mst.md
@@ -108,6 +108,20 @@ Description | Enables scalable inserts and complex queries for time-series data
 defaultdb=>
 ```
 
+## Install and update TimescaleDB Toolkit
+
+Run this command on each database you want to use the $TOOLKIT_SHORT with:
+
+```sql
+CREATE EXTENSION timescaledb_toolkit;
+```
+
+Update an installed version of the $TOOLKIT_SHORT using this command:
+
+```sql
+ALTER EXTENSION timescaledb_toolkit UPDATE;
+```
+
 ## Where to next
 
 Now that you have your first service up and running, you can check out the
diff --git a/self-hosted/tooling/install-toolkit.md b/self-hosted/tooling/install-toolkit.md
diff --git a/tutorials/blockchain-query/blockchain-compress.md b/tutorials/blockchain-query/blockchain-compress.md
diff --git a/use-timescale/configuration/customize-configuration.md b/use-timescale/configuration/customize-configuration.md
