[bitnami/postgresql-repmgr] Feature Request : Add dbname in primary_conninfo at postgres.auto.conf to support Failover Slot in Bitnami PostgreSQL cluster

[PrabhuRaja1010]

I would like to request an enhancement to the Bitnami PostgreSQL with Repmgr container to support specifying a database name (dbname) in primary_conninfo.

Problem Statement:

PostgreSQL 17 introduces failover slots to improve logical replication during primary failovers. However, primary_conninfo does not currently support dbname=, which makes it difficult to maintain logical replication with failover slots in a Bitnami PostgreSQL cluster.

Since Bitnami's PostgreSQL container manages replication configurations dynamically, it would be helpful if dbname could be added to primary_conninfo within postgresql.auto.conf.

Proposed Enhancement:
Modify the Bitnami PostgreSQL container logic to allow users to:

1. Set a database name in primary_conninfo via an environment variable (e.g., REPMGR_PRIMARY_DBNAME).
2. Ensure primary_conninfo updates dynamically to include dbname= when configured.

Benefits:
Enables failover slots for logical replication users.
Reduces manual intervention during primary failover.
Improves compatibility with Debezium and other logical replication tools.

Would it be possible to consider this enhancement for an upcoming release? I’d be happy to discuss the details or provide more use cases.

Thank you for your time and consideration!

[javsalgar]

Hi!

Thank you so much for the feature request! I believe it makes sense. I will forward it to the team, but as it is not a critical feature, we cannot guarantee an ETA. If you want to speed up the process, you can submit a PR updating the libpostgresql.sh or librepmgr.sh libraries and we will review it.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

[thamerlan]

Hello,

Could you please clarify the current status of this issue?

At the moment primary_conninfo generated by the container does not include the dbname parameter. Starting with PostgreSQL 17, the sync_replication_slots worker requires dbname to be present in primary_conninfo. Without it, the slot synchronization worker fails to start and logical replication slots are not synchronized to the standby.

As a result, the sync_replication_slots feature effectively cannot be used in this setup. This also means that failover-safe logical replication (for example, for CDC tools such as Debezium) does not work, because logical slots are not replicated to standby nodes.

Is there a plan to update the generated primary_conninfo to include dbname (for example dbname=postgres or dbname=repmgr)?

Without this change, it is currently not possible to use the new slot failover functionality provided by PostgreSQL 17+.

Thank you.