@adam : I switched to pgoutput plugin, problem still exists.
“sometable” has a primary key and a default replica set.
Let me know what additional information you need from us at this time.
2022-10-03 15:09:00 source > REPLICA IDENTITY for 'public.sometable' is 'DEFAULT'; UPDATE and DELETE events will contain previous values only for PK colum
ns
2022-10-03 15:09:00 source > Searching for WAL resume position
2022-10-03 15:09:00 source > First LSN 'LSN{17E/92DBD370}' received
2022-10-03 15:09:00 source > LSN after last stored change LSN 'LSN{17E/92DBE0D0}' received
2022-10-03 15:09:00 source > WAL resume position 'LSN{17E/92DBE0D0}' discovered
2022-10-03 15:09:00 source > Connection gracefully closed
2022-10-03 15:09:00 source > Connection gracefully closed
2022-10-03 15:09:00 source > Initializing PgOutput logical decoder publication
2022-10-03 15:09:00 source > Requested thread factory for connector PostgresConnector, id = journal_processor named = keep-alive
2022-10-03 15:09:00 source > Creating thread debezium-postgresconnector-journal_processor-keep-alive
2022-10-03 15:09:00 source > Processing messages
2022-10-03 15:09:00 source > Streaming requested from LSN LSN{17E/92DBDC70}, received LSN LSN{17E/92DBD370} identified as already processed
2022-10-03 15:09:00 source > Streaming requested from LSN LSN{17E/92DBDC70}, received LSN LSN{0/0} identified as already processed
2022-10-03 15:09:00 source > Streaming requested from LSN LSN{17E/92DBDC70}, received LSN LSN{17E/92DBD370} identified as already processed
2022-10-03 15:09:00 source > Streaming requested from LSN LSN{17E/92DBDC70}, received LSN LSN{17E/92DBDC70} identified as already processed```