Skip to content

update postgresql documentation with walminer recommendation #210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
heywalter merged 1 commit into from
Jan 22, 2026
Merged

update postgresql documentation with walminer recommendation #210

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/connectors/on-prem-databases/postgresql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,7 +148,7 @@ When using PostgreSQL as the target database or obtaining incremental data via t
:::

- [Decoderbufs](https://github.com/debezium/postgres-decoderbufs): Suitable for PostgreSQL 9.6 and above, uses Google Protocol Buffers to parse WAL logs but requires more complex configuration.
- [Walminer](https://gitee.com/movead/XLogMiner/tree/master/): Does not rely on logical replication, doesn't require setting `wal_level` to `logical`, or adjusting replication slot configuration, but requires superuser permissions.
- [Walminer](https://gitee.com/movead/XLogMiner/tree/master/): Does not rely on logical replication, doesn't require setting `wal_level` to `logical`, or adjusting replication slot configuration, but requires superuser permissions. In a **replication architecture**, we recommend using the **Walminer** plugin to read incremental changes to ensure data integrity during failover.

Next, we will demonstrate the installation process using **Wal2json** as an example.

Expand Down Expand Up @@ -491,4 +491,4 @@ When configuring data synchronization/conversion tasks, you can use PostgreSQL a

-- Delete the Slot node
select * from pg_drop_replication_slot('tapdata');
```
```
Loading