TCapture is compatible with Postgres 16 version

From: TCapture via PostgreSQL Announce <announce-noreply(at)postgresql(dot)org>
To: PostgreSQL Announce <pgsql-announce(at)lists(dot)postgresql(dot)org>
Subject: TCapture is compatible with Postgres 16 version
Date: 2024-11-03 19:44:41
Message-ID: 173066308171.704.10407572072323919663@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-announce

Replication? do it easily with TCapture
------------
**We are very glad to announce the compatibility with PostgreSQL 16 version.**

**TCapture** is a bidirectional multi master replication server based on a 'capture and apply' asynchronous replica engine

The actual **TCapture** engine is a Java application which runs as a separate program outside "PostgreSQL" , and which must be started explicitly.
When **TCapture** is running, it will scan the transaction log of all primary databases and pick up transactions which must be replicated.
Transactions which have been picked up are stored in the 'store database' , a "PostgreSQL" user database exclusively used by **TCapture**.
In the store database, transaction is 'copied' to all store databases which have a subscription for this transaction.
Transaction is then applied to the replicate databases

One of the attractions of **TCapture** is that it’s quite easy to set up and configure: starting from scratch, you can deploy a working replication system in less than 30 minutes.
The setup procedure is described in the **TCapture** Guide. As always with replication, make sure you have a clear idea of the replication logic you want to implement before you start.

KEY FEATURE:
------------

- Transactional. SQL are captured transactionally, can be coupled with surrounding business logic.
- Efficient. It capture transactions for replication from Write-Ahead Logs (WAL) instead of using triggers, eliminating overhead on master databases and significantly reduces latency
- Flexible. No limits on the number of producers or consumers, but complexity increases
- Reliable. Transactions are stored in "PostgreSQL" database – this adds the benefit of write ahead logging and crash recovery.
- Transparent. No impact on the applications already running on that database, since both engine and 'store database' can run separate from production databases.
- Easy to use. Simple to set up and configure, is an effective tool for data replication between different "PostgreSQL" versions
- Open Source. No licensing fees, but occasionally you'll have to get your hands dirty

Browse pgsql-announce by date

  From Date Subject
Next Message PoWA via PostgreSQL Announce 2024-11-05 15:29:28 powa-collector 1.3.0 is out!
Previous Message Datasentinel via PostgreSQL Announce 2024-11-03 19:44:09 Datasentinel Release 2024.10