goutamadwant opened a new pull request, #12359: URL: https://github.com/apache/seatunnel/pull/12359
### Purpose of this pull request Refs #11739. Deliver the PostgreSQL feasibility-audit slice requested before implementing bounded reads. - Add EN/ZH analysis of configuration, transaction boundaries, event/commit LSN ordering, idle progress, queue draining, checkpoint recovery and replication-slot lifecycle. - Identify integration requirements with #11556 and #11029, including OpenGauss isolation, without duplicating their implementation. - Define eight acceptance scenarios and extend existing option/LSN characterization tests. This does not enable bounded reads or close the umbrella issue. Transaction cutoff semantics and reliable idle completion require agreement before implementation. ### Does this PR introduce _any_ user-facing change? Developer documentation only. Production code, dependencies, options and defaults remain unchanged; PostgreSQL still supports only `stop.mode = never`. ### How was this patch tested? - Java 11 focused Maven verify: 13 tests passed. - Complete PostgreSQL connector unit suite: 29 tests passed. - Spotless, whitespace checks and independent correctness/security reviews passed. - An initial sandbox restriction blocked Mockito attachment; the same tests passed with attachment permitted. - No PostgreSQL/OpenGauss E2E completion or restart claim is made. These remain documented implementation gates. ### Check list * [ ] New Jar license notice: N/A; no dependency added. * [x] English and Chinese documentation updated. * [ ] `incompatible-changes.md`: N/A; no runtime compatibility change. * [ ] Connector integration updates: N/A; plugin mapping, distribution POM, CI labels and plugin config remain unchanged. E2E scenarios are specified for the future implementation. -- 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]
