TimescaleDB (Destination)
Overview
The TimescaleDB destination lets you load data into a TimescaleDB instance. TimescaleDB is PostgreSQL-compatible, so this destination uses the same connection and loading behavior as our Postgres-compatible destinations.
Use this destination when you want to write records into tables in TimescaleDB (including hypertables, if you’ve configured them on the TimescaleDB side).
Setup
- Ensure your TimescaleDB instance is reachable from the network where the data plane runs.
- Create (or choose) a database and schema to load into.
- Create a database user with permissions to create and write to the target tables (or at minimum, permissions required by your chosen sync mode).
- If you require TLS, ensure your instance is configured accordingly and you have the required connection details.
Authentication
Authenticate using standard PostgreSQL credentials:
- Hostname
- Port
- Database
- Username
- Password
- (Optional) SSL/TLS settings, depending on your deployment
Configuration
Configure the destination with the following fields:
| Field | Type | Required | Description |
|---|---|---|---|
host | string | Yes | TimescaleDB host name or IP address. |
port | number | Yes | Database port (commonly 5432). |
database | string | Yes | Database name to connect to. |
schema | string | No | Target schema to write into. If omitted, the database default schema is used (commonly public). |
username | string | Yes | Database user. |
password | string | Yes | Database password for the user. |
ssl / tls | varies | No | SSL/TLS configuration, if required by your TimescaleDB deployment. |
Hashing and normalization
This destination does not currently expose field-level hashing configuration in the connector.
If you need to store hashed identifiers in TimescaleDB, hash values upstream before syncing.
Data contract
This destination writes records into TimescaleDB tables using PostgreSQL-compatible semantics.
- Column types are mapped using PostgreSQL-compatible type handling.
- Table and column naming follow PostgreSQL rules for identifiers.
- Primary keys and upsert behavior (if applicable) depend on your sync configuration and the presence of unique constraints on the target table.
Streams
TimescaleDB is a destination, so it does not expose source streams. Instead, it receives records from your Reverse ETL model and loads them into the configured target table(s).
Notes and limitations
- TimescaleDB is PostgreSQL-compatible; any TimescaleDB-specific features (like hypertables, compression policies, retention policies) must be configured in TimescaleDB. The connector loads data into the target tables you specify.
- Ensure the destination user has sufficient privileges for the operations your sync requires (creating tables, inserting, updating, etc.).