This is an automated email from the ASF dual-hosted git repository.

yuxiqian pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink-cdc.git


The following commit(s) were added to refs/heads/master by this push:
     new cd8b8a98e [docs][connect/postgres] Improve Incremental Snapshot 
Reading formatting and references (#4472)
cd8b8a98e is described below

commit cd8b8a98ed1e2d6edf7fe8861f5c87a47013bee3
Author: nhuantho <[email protected]>
AuthorDate: Tue Jul 14 09:33:15 2026 +0700

    [docs][connect/postgres] Improve Incremental Snapshot Reading formatting 
and references (#4472)
---
 docs/content.zh/docs/connectors/flink-sources/postgres-cdc.md | 8 ++++----
 docs/content/docs/connectors/flink-sources/postgres-cdc.md    | 8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/content.zh/docs/connectors/flink-sources/postgres-cdc.md 
b/docs/content.zh/docs/connectors/flink-sources/postgres-cdc.md
index 24c6e67cd..8ef10d97a 100644
--- a/docs/content.zh/docs/connectors/flink-sources/postgres-cdc.md
+++ b/docs/content.zh/docs/connectors/flink-sources/postgres-cdc.md
@@ -219,10 +219,10 @@ Connector Options
           <td>Boolean</td>
           <td>Incremental snapshot is a new mechanism to read snapshot of a 
table. Compared to the old snapshot mechanism,
               the incremental snapshot has many advantages, including:
-                (1) source can be parallel during snapshot reading,
-                (2) source can perform checkpoints in the chunk granularity 
during snapshot reading,
-                (3) source doesn't need to acquire global read lock (FLUSH 
TABLES WITH READ LOCK) before snapshot reading.
-              Please see <a href="#incremental-snapshot-reading ">Incremental 
Snapshot Reading</a>section for more detailed information.
+                <br/>(1) source can be parallel during snapshot reading,
+                <br/>(2) source can perform checkpoints in the chunk 
granularity during snapshot reading,
+                <br/>(3) source doesn't need to acquire global read lock 
(FLUSH TABLES WITH READ LOCK) before snapshot reading.
+              <br/>Please see <a 
href="#incremental-snapshot-reading-experimental">Incremental Snapshot 
Reading</a> section for more detailed information.
           </td>
     </tr>
     <tr>
diff --git a/docs/content/docs/connectors/flink-sources/postgres-cdc.md 
b/docs/content/docs/connectors/flink-sources/postgres-cdc.md
index d3c999ce4..5615c6c6f 100644
--- a/docs/content/docs/connectors/flink-sources/postgres-cdc.md
+++ b/docs/content/docs/connectors/flink-sources/postgres-cdc.md
@@ -216,10 +216,10 @@ SELECT * FROM shipments;
           <td>Boolean</td>
           <td>Incremental snapshot is a new mechanism to read snapshot of a 
table. Compared to the old snapshot mechanism,
               the incremental snapshot has many advantages, including:
-                (1) source can be parallel during snapshot reading,
-                (2) source can perform checkpoints in the chunk granularity 
during snapshot reading,
-                (3) source doesn't need to acquire global read lock (FLUSH 
TABLES WITH READ LOCK) before snapshot reading.
-              Please see <a href="#incremental-snapshot-reading ">Incremental 
Snapshot Reading</a>section for more detailed information.
+                <br/>(1) source can be parallel during snapshot reading,
+                <br/>(2) source can perform checkpoints in the chunk 
granularity during snapshot reading,
+                <br/>(3) source doesn't need to acquire global read lock 
(FLUSH TABLES WITH READ LOCK) before snapshot reading.
+              <br/>Please see <a 
href="#incremental-snapshot-reading-experimental">Incremental Snapshot 
Reading</a> section for more detailed information.
           </td>
     </tr>
     <tr>

Reply via email to