In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

Postgres CDC connector v2.5.3

What is the connector configuration?

   "signal.data.collection":"public.debezium_signal",

   "connector.class":"io.debezium.connector.postgresql.PostgresConnector",

   "slot.name":"<SLOT>",

   "publication.name":"<PUBLICATION>",

   "producer.override.security.protocol":"SASL_SSL",

   "tombstones.on.delete":"false",

   "topic.prefix":"<TOPIC-PREFIX>",

   "decimal.handling.mode":"double",

   "value.converter":"io.confluent.connect.avro.AvroConverter",

   "key.converter":"io.confluent.connect.avro.AvroConverter",

   "database.dbname":"<DBNAME>",

   "database.user":"<USER>",

   "time.precision.mode":"adaptive_time_microseconds",

   "database.port":"5432",

   "plugin.name":"pgoutput",

   "key.converter.schemas.enable":"false",

   "value.converter.schema.registry.url":"<SCHEMA-REGISTRY-URL>",

   "database.hostname":"<DBHOST>",

   "database.password":"<DBPASSWORD>",

   "schema.name.adjustment.mode":"avro",

   "name":"<NAME>",

   "value.converter.schemas.enable":"false",

   "producer.override.sasl.jaas.config":"<PATH-TO-SECRET>",

   "producer.override.sasl.mechanism":"PLAIN",

   "table.include.list":"<TABLES>..,public.debezium_signal",

   "key.converter.schema.registry.url":"<SCHEMA-REGISTRY-URL>",

   "snapshot.mode":"never",

   "field.name.adjustment.mode":"avro",

   "incremental.snapshot.watermarking.strategy":"insert_delete",
   "notification.sink.topic.name":"<NOTIFICATION-TOPIC>"

What is the captured database version and mode of depoyment?

AWS Aurora RDS

What behaviour do you expect?

The connector should properly snapshot table B after completing the snapshot for table A

What behaviour do you see?

• The snapshot for table A completes successfully.

• Upon starting the snapshot for table B, activity briefly peaks on the correct topic, but then the connector starts snapshotting table A again

• The issue persists even after issuing a stop-snapshot command, indicating the connector might be leaving a process hanging that requires recreation to fix.

Do you see the same behaviour using the latest relesead Debezium version?

Haven't tried.

Do you have the connector logs, ideally from start till finish?

No.

How to reproduce the issue using our tutorial deployment?

Trigger and incremental snapshot for one big table, wait till it completes successfully, then trigger an incremental snapshot for another big table.

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>