Skip to content

Commit 648a644

Browse files
authored
docs: example review comments (#959)
* docs: postgres example postgre example docs * Update postgres_source.md
1 parent 90e1d33 commit 648a644

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

docs/docs/examples/examples/postgres_source.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -53,9 +53,10 @@ This step adds source data from PostgreSQL table `source_products` to the flow a
5353

5454
![Add PostgreSQL Source](/img/examples/postgres_source/source.png)
5555

56-
- Incremental Sync: When new or updated rows are found, only those rows are run through the pipeline, so downstream indexes and search results reflect the latest data while unchanged rows are untouched.
57-
- `ordinal_column` is recommended for change detection so the pipeline processes what's changed.
58-
- `notification`: when present, enable change capture based on Postgres LISTEN/NOTIFY.
56+
CocoIndex incrementally sync data from Postgres. When new or updated rows are found, only those rows run through the pipeline, so downstream indexes and search results reflect the latest data while unchanged rows are untouched. The following two arguments (both are optional) make this more efficient:
57+
58+
- `notification` enables change capture based on Postgres LISTEN/NOTIFY. Each change triggers an incremental processing on the specific row immediately.
59+
- Regardless if `notification` is provided or not, CocoIndex still needs to scan the full table to detect changes in some scenarios (e.g. between two `update` invocation), and the `ordinal_column` provides a field that CocoIndex can use to quickly detect which row has changed without reading value columns.
5960

6061
Check [Postgres source](https://cocoindex.io/docs/ops/sources#postgres) for more details.
6162

0 commit comments

Comments
 (0)