-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
What Debezium connector do you use and what version?
Postgres connector and Debezium 2.x.x
What is the connector configuration?
snapshot.mode = initial_only, everything else is irrelevant.
What is the captured database version and mode of depoyment?
On premise Postgres server.
What behaviour do you expect?
When running the connector with the initial_only snapshot mode, the connector stops after the snapshot is performed. Since the snapshot is a simple SELECT query that doesn't require the WAL, we don't have to require a "logical" replication slot in this case.
What behaviour do you see?
Fails with
Postgres server wal_level property must be "logical" but is: ...
Do you see the same behaviour using the latest relesead Debezium version?
Yes.
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
I do but they wouldn't be required as I know where it fails and intend to supply a fix.
How to reproduce the issue using our tutorial deployment?
No need.
- is cloned by
-
DBZ-6271 MySQL connector doesn't need to query binlog when snapshotting only
- Closed
- links to
-
RHEA-2023:120698 Red Hat build of Debezium 2.3.4 release