Skip to content
You're viewing documentation for v2026.11.9-beta. It may be out of date.Go to latest
TimescaleDB Enterprise
Esc
↑↓navigate↵open⌘Jpreview
On this page

Configuration and diagnostics

LiveSync settings in TimescaleDB Enterprise, capacity of the server that runs it, credentials, and the SQL check for slot lag.

Available settings

You set a session in the create form (see Create a session) or with the HTTP API. An API client can supply its own subscription name, at most 53 characters.

After creation, Edit changes only the tables and the table options, and only for a publication that the console created. To change the source, the target, the publication or the subscription, create a new session.

Other LiveSync options are not configurable. The console overwrites changes to the service files on the servers at the next deploy.

Capacity

  • Each session is a separate service on the primary. Stop on one session does not stop the others.
  • Sessions share the CPU, memory, disk and network of the primary with its database. A large initial copy can slow the other sessions and the database.
  • The initial copy uses more replication slots and connections on the source than streaming does.
  • Add sessions one at a time. Watch the server load, the source WAL, the target write load and the lag.

The console installs LiveSync from its server packages. If the component is missing, load the matching file under Administration → Server packages, then try again.

Credentials and connections

  • The console encrypts external connection strings and masks passwords in its responses.
  • Authentication and network access must work from each PostgreSQL server of the service that runs LiveSync.
  • Enter the TLS options of your database in the connection string. A Tiger Cloud target always uses sslmode=verify-full.
  • The connection string field does not accept environment variables or secret references.
  • LiveSync sends no telemetry.

SQL diagnostics

For an external source, the session panel does not show the slot lag. Check it on the source. The slot name starts with live_sync_ (see Multiple sessions):

SELECT slot_name, active, wal_status,
       pg_size_pretty(
         pg_wal_lsn_diff(pg_current_wal_lsn(), confirmed_flush_lsn)
       ) AS unconfirmed_wal
FROM pg_replication_slots
WHERE slot_name LIKE 'live_sync_%';
  • Good: active is t, wal_status is reserved, and unconfirmed_wal goes down.
  • Bad: active is f, wal_status is lost, or unconfirmed_wal keeps going up.

Metrics and dashboards

TimescaleDB Enterprise has no LiveSync metrics, dashboard or alert. Use the session panel. Database and server metrics are in Monitoring and Alerts.