SEZ9 commented on issue #12585: URL: https://github.com/apache/seatunnel/issues/12585#issuecomment-5944663906
Thanks for the detailed report and the before/after table. Checking `wal_status` (and `invalidation_reason` on PostgreSQL 17+) in `pg_replication_slots` before handing the slot to Debezium and failing fast with a dedicated error code sounds like the right approach. I'll take a look at #12587; please make sure the `invalidation_reason` lookup is guarded by server version so PostgreSQL 13-16 (where the column doesn't exist) still work. One question on the invalidated-slot case: should the connector always fail fast and require the user to drop/recreate the slot and re-snapshot, or is there an expected automatic recovery path? Either way, it would help to include the recommended operator action in the `POSTGRES-04` error message (e.g. drop the slot and restart without the savepoint) so users know what to do when they hit it. <!-- streview-comment:1460 --> -- 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]
