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?

PostgreSQL version 3.1

What is the connector configuration?

Is arbitrary but the most import setting were

plugin.name=pgoutput

slot.stream.params=proto_version=4;messages=true

What is the captured database version and mode of deployment?

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

Local setup, rancher with stackgres deployed version 16 PostgreSQL database.

Azure, azure flexible server PostgreSQL deployment.

What behavior do you expect?

On slot creation:

`CREATE_REPLICATION_SLOT "debezium" LOGICAL XXX/XXX ( "proto_version" "4", "messages" "true")`

What behavior do you see?

On slot creation:
`CREATE_REPLICATION_SLOT "debezium" LOGICAL XXX/XXX ( "proto_version" "1", "messages" "true")`

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

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

Yes, the source of this hardcoding is defined here.

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

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

<Your answer>

How to reproduce the issue using our tutorial deployment?

<Your answer>

Simply add connector configuration setting slot.stream.params=proto_version=4.

Feature request or enhancement

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

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

This could help to support heartbeats without using a heartbeat table on a read replica. The situation this would help to address is one where you wish to replicate from a read replica with many databases with varying degrees of activity on them. In order to help keep the slots in check (i.e. prevent growth) it would be convenient to execute:

SELECT pg_logical_emit_message(false, 'heartbeat', now()::varchar);

against a primary and have these messages propagate through to the slot.

Implementation ideas (optional)

A starting point could be to identify a PostgreSQL version using:

SELECT version();

Using this and postgresql documentation one could potentially introduce a switch case for postgres versions.