Greg Clough

Check in the `/var/log/repmgr/repmgr-*.log` file... as likely `repmgrd` is no longer monitoring. I have to restart all daemons after any switchover/failover. The message I get is: ``` [2018-06-28 16:25:04] [WARNING]...

Oh yes @rpjeff, I see we have the same problem. Possibly we have the same misconfiguration, or it's a problem with repmgr. As a workaround I just restart all `repmgrd`...

The team here are pretty responsive, so I suspect someone will investigate it soon. In the meantime, just ensure you restart repmgr daemon after every host swap, either switchover or...

Thanks @ibarwick , we appreciate your time on this. I must admit that I missed the section where repmgrd must be stopped before doing a switchover. https://repmgr.org/docs/4.0/repmgr-standby-switchover.html > **Execution** >...

Also consider what happens when you have several servers being backed up to the same barman server: ``` pg01 --+--> barman01 pg02 --+ ... + pg99 --+ ``` You can...

Similar to #90 , and likely the same cause being the `put_in_order()` function.

This was a change introduced in PostgreSQL v15, so not something we can actually fix. It was deliberately tightened to encourage people to *not* use the `public` schema. Ideally you...

@maglub or @otakup0pe , could someone review this for me? I'll probably remove v10 soon, as that's been desupported by PGDG.

v9.5 and v9.6 are not longer supported, and `log_replication_commands` is already included in later versions.

@MrMegaNova , the pipeline seems to be breaking on **debian12**. I think it's unrelated to this PR, so any idea why? ``` TASK [Gathering Facts] ********************************************************* fatal: [postgresql-13]: FAILED! =>...