PostgreSQL Point-in-Time Recovery with Strimzi Debezium CDC

[artempol-dev]

Environment:

• Strimzi version: 0.46.0-kafka-3.9.0-debezium-3.1.1.Final
• PostgreSQL version: 15
• Configuration: wal_level = logical, logical replication slots

When performing PostgreSQL PITR (Point-in-Time Recovery), all logical replication slots are automatically dropped during recovery, which breaks Debezium CDC synchronization.

So i see many problems

1. PITR creates a new timeline, invalidating all existing LSN positions
2. Replication slots are deleted during recovery
3. Debezium's stored offsets in Kafka Connect become invalid
4. LSN references point to non-existent WAL segments on the old timeline

So my questions:

1. Are there any Strimzi/Debezium best practices for PostgreSQL PITR scenarios?

2. Does Strimzi/Debezium have any built-in recovery mechanisms for timeline changes that don't require full re-snapshotting?

3. What's the recommended approach for recovery with Strimzi deployments?

So maybe you'll share your experience, I'll appreciate it