AmodKakade12

thanks for reply. I dont have any logical replication setup. I could work around the problem by starting the database in single user mode and then drop the database postgres@***~]$...

Hi, @DimCitus @JelteF @mtuncer Appreciate help from the experts on this limitation. Reopening for further discussion! Regards Amod

Hi, @DimCitus @JelteF @mtuncer Hi Further update. I have found only following workaround to solve this 1. Stop the systemd daemon for pg_auto_failover service on all replica & primary 2....

Thanks for reply. I feel the PGAF healthcheck user keeps connected to the database which causes above issue. I can see following messages appearing on the DB log Is there...

Further I have used following commands to create the monitor and database Monitor yum -y install pg_auto_failover_17 pg_autoctl create monitor --pgctl /usr/pgsql-17/bin/pg_ctl --pgdata --hostname --ssl-self-signed --ssl-mode require --pgport --auth scram-sha-256...

> Does inserting data (and committing) work against a table that you create in the database before? > > I had similar behaviours when communication between the worker nodes was...

@dimitri Appreciate if users of this great tool can provide their experience on this. This looks like a limitation to the software and requires outage to fix. It would be...