[Website]: Clarify Incremental Sync support and `track_commit_timestamp` usage for PostgreSQL Connector

[kouloumos]

Type of issue

Inaccurate

What documentation page is affected

https://www.elastic.co/docs/reference/search-connectors/es-connectors-postgresql

What happened?

Description:
I am opening this issue to address confusing and potentially misleading wording in the PostgreSQL connector documentation regarding Incremental Sync support.

The Issue:
Based on the general connector feature matrix/documentation here, it appears that the PostgreSQL connector does not support incremental syncs.

However, the specific PostgreSQL Connector documentation includes the following note in the usage/configuration section:

"To fetch the last updated time in PostgreSQL, track_commit_timestamp must be set to on. Otherwise, all data will be indexed in every sync."

Why this is confusing:
The phrase "Otherwise, all data will be indexed in every sync" strongly implies the inverse: that if track_commit_timestamp is set to on, the connector will not index all data every time (i.e., it will perform an incremental sync).

If the connector indeed only supports full syncs regardless of this setting, this wording is misleading to users who are trying to configure efficient data ingestion.

Expected Behavior / Request:
Please update the documentation to clarify the behavior:

1. Explicitly state whether Incremental Sync is supported for PostgreSQL.
2. If it is not supported, please rephrase the track_commit_timestamp section to remove the implication that it enables incremental indexing.
3. Clarify what track_commit_timestamp achieves if it does not prevent full re-indexing

Additional info

No response