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?

Debezium PostgreSQL connector v3.3.1

What is the connector configuration?

{     "column.exclude.list": ***REDACTED***,     "connector.class":  "io.debezium.connector.postgresql.PostgresConnector",     "database.dbname": ***REDACTED***,     "database.hostname": "***REDACTED***,     "database.include.schema.changes": "true",     "database.password": ***REDACTED***,     "database.port": "5432",     "database.server.name": "pg",     "database.sslmode": "allow",     "database.user": ***REDACTED***,     "decimal.handling.mode": "string",     "errors.log.enable": "true",     "errors.log.include.messages": "true",     "field.name.adjustment.mode": "avro",     "heartbeat.action.query": "select pg_logical_emit_message(false, 'heartbeat', now()::varchar)",     "heartbeat.interval.ms": "60000",     "incremental.snapshot.chunk.size": "10000",     "incremental.snapshot.watermarking.strategy": "insert_delete",     "name": "debezium-postgres-agribusiness-das-v3",     "plugin.name": "pgoutput",     "poll.interval.ms": "1000",     "producer.override.buffer.memory": "134217728",     "publication.autocreate.mode": "all_tables",     "publication.name": "dbz_pub_das",     "read.only": "true",     "schema.exclude.list": "workflows,system_log,storage",     "schema.name.adjustment.mode": "avro",     "signal.enabled.channels": "source,kafka",     "signal.kafka.bootstrap.servers": "kafka-cluster-kafka-bootstrap:9092",     "signal.kafka.poll.timeout.ms": "5000",     "signal.kafka.topic": "signal_pg_agribusiness_das",     "slot.max.retries": "2000",     "slot.name": "dbz_das",     "slot.retry.delay.ms": "5000",     "snapshot.fetch.size": "30720",     "snapshot.isolation.mode": "read_uncommitted",     "snapshot.locking.mode": "none",     "snapshot.mode": "no_data",     "tasks.max": "1",     "tombstones.on.delete": "false",     "topic.prefix": "pg_agribusiness_das" }

What is the captured database version and mode of deployment?

(E.g. on-premises, with a specific cloud provider, etc.)

PostgreSQL 14.19 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-26), 64-bit

Hosted on AWS but as a regular EC2 instance with a self-managed PostgreSQL install

What behavior do you expect?

Being able to start an incremental snapshot by signaling the signal topic.

What behavior do you see?

Right after starting the incremental snapshot the connector acknowledges it and then throws a null pointer exception

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

(Ideally, also verify with latest Alpha/Beta/CR version)

Tested with version 3.3.1

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

(You might be asked later to provide DEBUG/TRACE level log)

2025-11-24 13:44:06 INFO [debezium-postgresconnector-pg_agribusiness_das-SignalProcessor] ExecuteSnapshot:64 - Requested 'INCREMENTAL' snapshot of data collections '[field_events.event_attribute]' with additional conditions '[]' and surrogate key 'PK of table will be used' 2025-11-24 13:44:06 INFO [debezium-postgresconnector-pg_agribusiness_das-SignalProcessor] AbstractIncrementalSnapshotChangeEventSource:306 - Incremental snapshot for table 'field_events.event_attribute' will end at position [REDACTED] 2025-11-24 13:44:07 INFO [qtp387827651-61] RestServer:57 - 10.152.149.254 - - [24/Nov/2025:13:44:07 +0000] "GET /health HTTP/1.1" 200 94 "" "kube-probe/1.33+" 2 2025-11-24 13:44:12 INFO [qtp387827651-61] RestServer:57 - 10.152.149.99 - - [24/Nov/2025:13:44:12 +0000] "GET /connectors HTTP/1.1" 200 68 "" "curl/8.11.1" 2 2025-11-24 13:44:13 INFO [qtp387827651-61] RestServer:57 - 10.152.149.254 - - [24/Nov/2025:13:44:13 +0000] "GET /health HTTP/1.1" 200 94 "" "kube-probe/1.33+" 2 2025-11-24 13:44:17 INFO [qtp387827651-61] RestServer:57 - 10.152.149.254 - - [24/Nov/2025:13:44:17 +0000] "GET /health HTTP/1.1" 200 94 "" "kube-probe/1.33+" 1 2025-11-24 13:44:19 ERROR [debezium-postgresconnector-pg_agribusiness_das-change-event-source-coordinator] ErrorHandler:52 - Producer failure java.lang.NullPointerException: Cannot invoke "java.lang.Long.compareTo(java.lang.Long)" because "eventTxId" is null at io.debezium.connector.postgresql.PostgresReadOnlyIncrementalSnapshotContext.isTransactionVisible(PostgresReadOnlyIncrementalSnapshotContext.java:106) ~[debezium-connector-postgres-3.3.1.Final.jar:3.3.1.Final] at io.debezium.connector.postgresql.PostgresReadOnlyIncrementalSnapshotChangeEventSource.readUntilNewTransactionChange(PostgresReadOnlyIncrementalSnapshotChangeEventSource.java:176) ~[debezium-connector-postgres-3.3.1.Final.jar:3.3.1.Final] at io.debezium.connector.postgresql.PostgresReadOnlyIncrementalSnapshotChangeEventSource.processHeartbeat(PostgresReadOnlyIncrementalSnapshotChangeEventSource.java:160) ~[debezium-connector-postgres-3.3.1.Final.jar:3.3.1.Final] at io.debezium.connector.postgresql.PostgresReadOnlyIncrementalSnapshotChangeEventSource.processHeartbeat(PostgresReadOnlyIncrementalSnapshotChangeEventSource.java:68) ~[debezium-connector-postgres-3.3.1.Final.jar:3.3.1.Final] at io.debezium.pipeline.EventDispatcher.dispatchHeartbeatEventAlsoToIncrementalSnapshot(EventDispatcher.java:463) ~[debezium-core-3.3.1.Final.jar:3.3.1.Final] at io.debezium.connector.postgresql.PostgresStreamingChangeEventSource.processMessages(PostgresStreamingChangeEventSource.java:263) ~[debezium-connector-postgres-3.3.1.Final.jar:3.3.1.Final] at io.debezium.connector.postgresql.PostgresStreamingChangeEventSource.execute(PostgresStreamingChangeEventSource.java:205) ~[debezium-connector-postgres-3.3.1.Final.jar:3.3.1.Final] at io.debezium.connector.postgresql.PostgresStreamingChangeEventSource.execute(PostgresStreamingChangeEventSource.java:50) ~[debezium-connector-postgres-3.3.1.Final.jar:3.3.1.Final] at io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:329) ~[debezium-core-3.3.1.Final.jar:3.3.1.Final] at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:207) ~[debezium-core-3.3.1.Final.jar:3.3.1.Final] at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:147) ~[debezium-core-3.3.1.Final.jar:3.3.1.Final] at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?] at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?] at java.base/java.lang.Thread.run(Thread.java:840) [?:?] 2025-11-24 13:44:19 INFO [debezium-postgresconnector-pg_agribusiness_das-change-event-source-coordinator] Threads:273 - Requested thread factory for component JdbcConnection, id = JdbcConnection named = jdbc-connection-close

How to reproduce the issue using our tutorial deployment?

<Your answer>

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>