Skip to content

Commit b4f9517

Browse files
robsoncoelhorobsoncoelho
authored
Merge branch 'latest' into 4369-docs-rfcmake-a-title-or-anchor-so-we-can-easily-link-to-the-partitioning-types-v1
2 parents ec9ad0d + 126da49 commit b4f9517

File tree

10 files changed

+296
-168
lines changed

10 files changed

+296
-168
lines changed

‎_partials/_livesync-terminal.md‎

Lines changed: 16 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -178,9 +178,9 @@ instance to a $SERVICE_LONG:
178178
As you run $LIVESYNC continuously, best practice is to run it as a Docker daemon.
179179

180180
```shell
181-
docker run -d --rm --name livesync timescale/live-sync:v0.1.22 run \
181+
docker run -d --rm --name livesync timescale/live-sync:v0.1.25 run \
182182
--publication <publication_name> --subscription <subscription_name> \
183-
--source $SOURCE --target $TARGET
183+
--source $SOURCE --target $TARGET --table-map <table_map_as_json>
184184
```
185185

186186
`--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:
191191

192192
`--target`: The connection string to the target $SERVICE_LONG.
193193

194+
`--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.
195+
For example, to map the source table `metrics` to the target table `metrics_data`:
196+
197+
```
198+
--table-map '{"source": {"schema": "public", "table": "metrics"}, "target": {"schema": "public", "table": "metrics_data"}}'
199+
```
200+
To map only the schema, use:
201+
202+
```
203+
--table-map '{"source": {"schema": "public"}, "target": {"schema": "analytics"}}'
204+
```
205+
This flag can be repeated for multiple table mappings.
206+
194207
1. **Capture Logs**
195208

196209
Once $LIVESYNC is running as a docker daemon, you can also capture the logs:
@@ -315,7 +328,7 @@ EOF
315328
Use the `--drop` flag to remove the replication slots created by $LIVESYNC on the source database.
316329

317330
```shell
318-
docker run -it --rm --name livesync timescale/live-sync:v0.1.22 run \
331+
docker run -it --rm --name livesync timescale/live-sync:v0.1.25 run \
319332
--publication <publication_name> --subscription <subscription_name> \
320333
--source $SOURCE --target $TARGET \
321334
--drop

‎_partials/_toolkit-install-update-debian-base.md‎

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
## Prerequisites
2+
3+
To follow this procedure:
4+
5+
- [Install $TIMESCALE_DB][debian-install].
6+
- Add the $TIMESCALE_DB repository and the GPG key.
7+
8+
## Install $TOOLKIT_LONG
9+
10+
These instructions use the `apt` package manager.
11+
12+
<Procedure>
13+
14+
1. Update your local repository list:
15+
16+
```bash
17+
sudo apt update
18+
```
19+
20+
1. Install TimescaleDB Toolkit:
21+
22+
```bash
23+
sudo apt install timescaledb-toolkit-postgresql-17
24+
```
25+
26+
1. [Connect to the database][connect] where you want to use $TOOLKIT_SHORT.
27+
1. Create the $TOOLKIT_SHORT extension in the database:
28+
29+
```sql
30+
CREATE EXTENSION timescaledb_toolkit;
31+
```
32+
33+
</Procedure>
34+
35+
## Update $TOOLKIT_LONG
36+
37+
Update $TOOLKIT_SHORT by installing the latest version and running `ALTER EXTENSION`.
38+
39+
<Procedure>
40+
41+
1. Update your local repository list:
42+
43+
```bash
44+
apt update
45+
```
46+
47+
1. Install the latest version of $TOOLKIT_LONG:
48+
49+
```bash
50+
apt install timescaledb-toolkit-postgresql-17
51+
```
52+
53+
1. [Connect to the database][connect] where you want to use the new version of $TOOLKIT_SHORT.
54+
1. Update the $TOOLKIT_SHORT extension in the database:
55+
56+
```sql
57+
ALTER EXTENSION timescaledb_toolkit UPDATE;
58+
```
59+
60+
<Highlight type="note">
61+
62+
For some $TOOLKIT_SHORT versions, you might need to disconnect and reconnect active
63+
sessions.
64+
65+
</Highlight>
66+
67+
</Procedure>
68+
69+
[brew-install]: https://brew.sh
70+
[cloud]: /use-timescale/:currentVersion:/services/
71+
[debian-install]: /self-hosted/:currentVersion:/install/installation-linux/
72+
[docker-install]: /self-hosted/:currentVersion:/install/installation-docker/
73+
[mst]: /mst/:currentVersion:/
74+
[red-hat-install]: /self-hosted/:currentVersion:/install/installation-linux/
75+
[toolkit-gh-docs]: https://github.com/timescale/timescaledb-toolkit#-installing-from-source
76+
[connect]: /integrations/:currentVersion:/find-connection-details/
77+
[update-docker]: /self-hosted/:currentVersion:/upgrades/upgrade-docker/
78+
[macos-install]: /self-hosted/:currentVersion:/install/installation-macos/

‎_partials/_toolkit-install-update-redhat-base.md‎

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
2+
## Prerequisites
3+
4+
To follow this procedure:
5+
6+
- [Install $TIMESCALE_DB][red-hat-install].
7+
- Create a $TIMESCALE_DB repository in your `yum` `repo.d` directory.
8+
9+
## Install $TOOLKIT_LONG
10+
11+
These instructions use the `yum` package manager.
12+
13+
<Procedure>
14+
15+
1. Set up the repository:
16+
17+
```bash
18+
curl -s https://packagecloud.io/install/repositories/timescale/timescaledb/script.deb.sh | sudo bash
19+
```
20+
21+
1. Update your local repository list:
22+
23+
```bash
24+
yum update
25+
```
26+
27+
1. Install $TOOLKIT_LONG:
28+
29+
```bash
30+
yum install timescaledb-toolkit-postgresql-17
31+
```
32+
33+
1. [Connect to the database][connect] where you want to use $TOOLKIT_SHORT.
34+
1. Create the $TOOLKIT_SHORT extension in the database:
35+
36+
```sql
37+
CREATE EXTENSION timescaledb_toolkit;
38+
```
39+
40+
</Procedure>
41+
42+
## Update $TOOLKIT_LONG
43+
44+
Update $TOOLKIT_SHORT by installing the latest version and running `ALTER EXTENSION`.
45+
46+
<Procedure>
47+
48+
1. Update your local repository list:
49+
50+
```bash
51+
yum update
52+
```
53+
54+
1. Install the latest version of $TOOLKIT_LONG:
55+
56+
```bash
57+
yum install timescaledb-toolkit-postgresql-17
58+
```
59+
60+
1. [Connect to the database][connect] where you want to use the new version of $TOOLKIT_SHORT.
61+
1. Update the $TOOLKIT_SHORT extension in the database:
62+
63+
```sql
64+
ALTER EXTENSION timescaledb_toolkit UPDATE;
65+
```
66+
67+
<Highlight type="note">
68+
69+
For some $TOOLKIT_SHORT versions, you might need to disconnect and reconnect active
70+
sessions.
71+
72+
</Highlight>
73+
74+
</Procedure>
75+
76+
77+
[brew-install]: https://brew.sh
78+
[cloud]: /use-timescale/:currentVersion:/services/
79+
[debian-install]: /self-hosted/:currentVersion:/install/installation-linux/
80+
[docker-install]: /self-hosted/:currentVersion:/install/installation-docker/
81+
[mst]: /mst/:currentVersion:/
82+
[red-hat-install]: /self-hosted/:currentVersion:/install/installation-linux/
83+
[toolkit-gh-docs]: https://github.com/timescale/timescaledb-toolkit#-installing-from-source
84+
[connect]: /integrations/:currentVersion:/find-connection-details/
85+
[update-docker]: /self-hosted/:currentVersion:/upgrades/upgrade-docker/
86+
[macos-install]: /self-hosted/:currentVersion:/install/installation-macos/

‎about/changelog.md‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,20 @@ products: [cloud]
99

1010
All the latest features and updates to $CLOUD_LONG.
1111

12+
## 🚁 Enhancements to the Postgres source connector
13+
<Label type="date">August 28, 2025</Label>
14+
15+
- **Easy table selection**: You can now sync the complete source schema in one go. Select multiple tables from the
16+
drop-down menu and start the connector.
17+
18+
- **Sync metadata**: Connectors now display the following detailed metadata:
19+
- `Initial data copy`: The number of rows copied at any given point in time.
20+
- `Change data capture`: The replication lag represented in time and data size.
21+
- **Improved UX design**: In-progress syncs with separate sections showing the tables and metadata for
22+
`initial data copy` and `change data capture`, plus a dedicated tab where you can add more tables to the connector.
23+
24+
![Connectors UX](https://assets.timescale.com/docs/images/tiger-cloud-console/connectors-new-ui.png )
25+
1226
## 🦋 Developer role GA and hypertable transformation in Console
1327
<Label type="date">August 21, 2025</Label>
1428

‎api/hypertable/split_chunk.md‎

Lines changed: 18 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11,22 +11,31 @@ products: [cloud, mst, self_hosted]
1111

1212
# split_chunk() <Tag type="community">Community</Tag>
1313

14-
Split a large chunk at a specific point in time.
14+
Split a large chunk at a specific point in time. If you do not specify the timestamp to split at, `chunk`
15+
is split equally.
1516

1617
## Samples
1718

18-
Split a chunk at a specific time:
19+
* Split a chunk at a specific time:
1920

20-
```sql
21-
CALL split_chunk('chunk_1', split_at => '2025-03-01 00:00');
22-
```
21+
```sql
22+
CALL split_chunk('chunk_1', split_at => '2025-03-01 00:00');
23+
```
2324

25+
* Split a chunk in two:
26+
27+
For example, If the chunk duration is, 24 hours, the following command splits `chunk_1` into
28+
two chunks of 12 hours each.
29+
```sql
30+
CALL split_chunk('chunk_1');
31+
```
32+
2433
## Required arguments
2534

26-
|Name|Type| Description |
27-
|---|---|----------------------------------|
28-
| `chunk` | REGCLASS | Name of the chunk to split. |
29-
| `split_at` | `TIMESTAMPTZ`| Timestamp to split the chunk at. |
35+
|Name|Type| Required | Description |
36+
|---|---|---|----------------------------------|
37+
| `chunk` | REGCLASS | ✔ | Name of the chunk to split. |
38+
| `split_at` | `TIMESTAMPTZ`| ✖ |Timestamp to split the chunk at. |
3039

3140

3241
## Returns

‎lambda/redirects.js‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -849,6 +849,10 @@ module.exports = [
849849
from: "/latest/getting-started/setup",
850850
to: "https://docs.tigerdata.com/self-hosted/latest/install/"
851851
},
852+
{
853+
from: "/latest/using-timescaledb/backup",
854+
to: "https://docs.tigerdata.com/self-hosted/latest/backup-and-restore/"
855+
},
852856
{
853857
from: "/v0.9/faq",
854858
to: "https://docs.tigerdata.com/about/latest/"
@@ -885,6 +889,10 @@ module.exports = [
885889
from: "/latest/api#add_dimension",
886890
to: "https://docs.tigerdata.com/api/latest/hypertable/add_dimension/"
887891
},
892+
{
893+
from: "/latest/api#backup",
894+
to: "https://docs.tigerdata.com/self-hosted/latest/backup-and-restore/"
895+
},
888896
{
889897
from: "/timescaledb/latest/tutorials/grafana/grafana-variables/",
890898
to: "https://docs.tigerdata.com/integrations/latest/grafana/"

‎mst/installation-mst.md‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,20 @@ Description | Enables scalable inserts and complex queries for time-series data
108108
defaultdb=>
109109
```
110110
111+
## Install and update TimescaleDB Toolkit
112+
113+
Run this command on each database you want to use the $TOOLKIT_SHORT with:
114+
115+
```sql
116+
CREATE EXTENSION timescaledb_toolkit;
117+
```
118+
119+
Update an installed version of the $TOOLKIT_SHORT using this command:
120+
121+
```sql
122+
ALTER EXTENSION timescaledb_toolkit UPDATE;
123+
```
124+
111125
## Where to next
112126
113127
Now that you have your first service up and running, you can check out the

0 commit comments

Comments
 (0)