Martín Marqués
Martín Marqués
As an example: ``` repmgr=# select * from repmgr.nodes ; node_id | upstream_node_id | active | node_name | type | location | priority | conninfo | repluser | slot_name |...
One option would be to grant usage on the schema and select over the tables to the pg_monitor role. Now if we consider that the conninfo shouldn't be visible we...
Closing as this has been solved already
@mcyprian do you still see this issue on 5.1? Anyway, the logs seem to indicate that the problem might be somewhere else: ``` [2019-11-30 09:35:49] [ERROR] connection to database failed...
There's no bug that relates to a memory leak in that version (we did find one many years ago which got fixed). Can you give us more details on how...
This is not a configuration we support, and with the current backup recovery implementation, it would be hard to make it available for other backup tools like pgbackrest.
Either way, let us know if you are looking to have pgbackrest for full recovery, or for cloning standby nodes (the latter is not possible using `repmgr standby clone` and...
Closing this as we haven't had a reply to Ian's message in over 9 months
FYI, this is related to a customer ticket RT75337
Did you check your postgres server logs around the time of the backup, particularly the error from running `pg_stop_backup()`?