Merge branch 'latest' into add-rocky-linux

Author: billy-the-fish

_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

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

use-timescale/configuration/customize-configuration.md

@@ -42,14 +42,6 @@ To modify a configured value, hover over the value and click the revealed pencil
 icon. This reveals an editable field to apply your change. Clicking anywhere
 outside of that field saves the value to be applied.
 
-<Highlight type="note">
-
-The values for some of the parameters vary depending on your [pricing plan][plan-features]. 
-For example, the value for `max_connections` is 25 in the Performance plan, but
-ranges from 25 to 500 in higher compute plans.
-
-</Highlight>
-
 <img class="main-content__illustration"
 width={1375} height={944}
 src="https://assets.timescale.com/docs/images/tsc-settings-change.webp"