github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-22 22:56:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

standby clone: minimize requirement to check upstream data directory location

Browse Source 
repmgr has always insisted on determining the upstream's data directory
location, which requires superuser permissions (or from PostgreSQL 10,
membership of the default role "pg_read_all_settings").

Knowledge of the data directory location was required to implement rsync
cloning (now deprecated), but with pg_basebackup the minimum permission
requirement is now only a normal user with access to the repmgr metadata
and a user with replication permissions. The ability to determine the
data directory location is only required if the user specifies the
--copy-external-config-files option, which needs to be able to determine
the data directory to work out which configuration files are located
outside it.

This patch makes it possible to clone a standby with minimum
permissions, with appropriate checks for available permissions if
--copy-external-config-files is provided.

Implements part of GitHub #536 and addresses issue raised in #586.
This commit is contained in:
Ian Barwick
2019-10-23 10:46:16 +09:00
parent d7fd55be99
commit be494f0d5f
4 changed files with 89 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
HISTORY
View File

@@ -2,6 +2,8 @@
repmgr: don't query upstream's data directory (Ian)
repmgr: rename --recovery-conf-only to --replication-conf-only (Ian)
repmgr: ensure postgresql.auto.conf is created with corretc permissions (Ian)
repmgr: minimize requirement to check upstream data directory location
during "standby clone" (Ian)
5.0 2019-10-15
general: add PostgreSQL 12 support (Ian)