update postgresql documentation with walminer recommendation

Author: heywalter

docs/connectors/on-prem-databases/postgresql.md

@@ -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.
 
@@ -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');
-  ```
+  ```