All issues

Search results

repmgr node rejoin can fail if command is run for two instances at the same time

Status: Open.

#920 In EnterpriseDB/repmgr;

· mbanck-cd opened on Aug 17, 2026

DROP_REPLICATION_SLOT via replication protocol incorrectly expects PGRES_TUPLES_OK

Status: Open.

#919 In EnterpriseDB/repmgr;

· Morpheion opened on Aug 13, 2026

standby switchover: CHECKPOINT executed on NULL superuser connection when repmgr user has pg_checkpoint

Status: Open.

#918 In EnterpriseDB/repmgr;

· Morpheion opened on Aug 13, 2026

Conflict between homepage and release note for Postgresql 18

Status: Open.

#917 In EnterpriseDB/repmgr;

· Brian417-cup opened on Jul 10, 2026

PostgreSQL 19 support

Status: Open.

#916 In EnterpriseDB/repmgr;

· wolfgangwalther opened on Jun 13, 2026

Plain ping instead of setting a PG server to be a witness?

Status: Open.

#907 In EnterpriseDB/repmgr;

· rihadik opened on Feb 1, 2026

incompatibility with barman

Status: Open.

#904 In EnterpriseDB/repmgr;

· joerggrosse-kracht opened on Dec 7, 2025

PG17 Logical slot failover not working as repmgr not setting dbname in primary_conninfo

Status: Open.

#903 In EnterpriseDB/repmgr;

· sreddy123 opened on Oct 15, 2025

Add option to skip archive_command validation during standby clone

Status: Open.

#902 In EnterpriseDB/repmgr;

· acastro2 opened on Oct 14, 2025

pgSQL14.10+repmgr5.4.1 sets up a master-slave replication cluster, and the service runs normally and replicates normally. Executing systemctl start repmgrd failed

Status: Open.

#900 In EnterpriseDB/repmgr;

· LiBiao-java opened on Aug 15, 2025

Failed node never marked inactive in Repmgr schema

Status: Open.

#898 In EnterpriseDB/repmgr;

· Aldenar opened on Jul 15, 2025

Issue with Repmgr 5.3.3 in Debian 12

Status: Open.

#897 In EnterpriseDB/repmgr;

· AshishPandyaEcosmob opened on Jul 15, 2025