davidzollo opened a new issue, #11039: URL: https://github.com/apache/seatunnel/issues/11039
## Background `PostgreSQL-CDC` currently supports only a small set of startup behaviors in SeaTunnel. There is no dedicated startup mode for resuming from the already committed position of the replication slot. For long-running jobs and controlled restarts, starting from the slot's committed position is an important operational path. ## Proposed change Add a committed-offset startup mode to `PostgreSQL-CDC` that begins consumption from the slot's committed LSN position. ## Expected behavior - The connector starts directly from the committed replication-slot position. - Snapshot is skipped in this mode. - Preconditions and operational caveats are documented clearly. ## Acceptance criteria - `PostgreSQL-CDC` accepts a committed-offset startup mode. - The mode starts from the committed slot position and resumes predictably. - Validation errors are explicit when the slot state does not support this mode. - English and Chinese docs are updated. - Add a focused test or integration validation path. ## Out of scope - Snapshot-only startup mode. - New schema evolution policies. - New metadata fields. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
