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 Server 2.5 Latast Postgres Connector

What is the connector configuration?

• DEBEZIUM_SINK_TYPE=rabbitmq
        - DEBEZIUM_SINK_RABBITMQ_CONNECTION_HOST=rabbitmq
        - DEBEZIUM_SINK_RABBITMQ_CONNECTION_USERNAME=guest
        - DEBEZIUM_SINK_RABBITMQ_CONNECTION_PASSWORD=guest
        - DEBEZIUM_SINK_RABBITMQ_CONNECTION_PORT=5672
        - DEBEZIUM_SINK_RABBITMQ_ACKTIMEOUT=30000
        - DEBEZIUM_SINK_RABBITMQ_EXCHANGE=poc-debezium-server-exchange
        - DEBEZIUM_SOURCE_CONNECTOR_CLASS=io.debezium.connector.postgresql.PostgresConnector
        - DEBEZIUM_SOURCE_OFFSET_STORAGE_FILE_FILENAME=data/offsets.dat
        - DEBEZIUM_SOURCE_OFFSET_FLUSH_INTERVAL_MS=0
        - DEBEZIUM_SOURCE_DATABASE_HOSTNAME=postgres
        - DEBEZIUM_SOURCE_DATABASE_PORT=5432
        - DEBEZIUM_SOURCE_DATABASE_USER=postgres
        - DEBEZIUM_SOURCE_DATABASE_PASSWORD=postgres
        - DEBEZIUM_SOURCE_DATABASE_DBNAME=poc_debezium_server_db
        - DEBEZIUM_SOURCE_SCHEMA_INCLUDE_LIST=dbo
        - DEBEZIUM_SOURCE_PLUGIN_NAME=pgoutput
        - DEBEZIUM_SOURCE_TOPIC_PREFIX=sample_prefix
        - DEBEZIUM_SOURCE_TABLE_INCLUDE_LIST=dbo.sample(.),dbo.test(.)
        - DEBEZIUM_SOURCE_TOMBSTONES_ON_DELETE=false
        - DEBEZIUM_SOURCE_REPLICA_IDENTITY_AUTOSET_VALUES=dbo.sample_table:FULL,dbo.test_table:DEFAULT
        - INITIAL_SYNC_OFFSET=latest

  What is the captured database version and mode of depoyment?

Postgres 16 latest

Docker deployment

What behaviour do you expect?

According to the docs, when REPLICA IDENTITY is equals to default the primary key fields should be sent in before event field in update and delete operations

What behaviour do you see?

Before field is always null when REPLICA IDENTITY is equals to default 

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

yes

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

No

How to reproduce the issue using our tutorial deployment?

Create a table with default REPLICA IDENTY and WAL equals to logical and observe the results