New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why repmgr role needs superuser privileges ? #74
Comments
It needs to read sensitive information from pg_settings which only a super user can. More precisely, these tuples need to be read: The information is needed for cloning, so it knows which files to rsync (if they happen to be outside pgdata). Regards, |
Thanks for following up. That triggers another question : why installing these functions by default if we do not use repmgrd ?Regards |
I don't understand your question. What specifically do you want repmgr to do for you? There are many tasks that repmgr does which require superuser privileges, although some could be circumvented. Regards, |
I wanted to know if with repmgr release 3 it was still necessary to give superuser privilege to repmgr user as for starter I ONLY want to use plain repmgr features (cloning and switchover) BUT NOT repmgrd features (failover and monitoring). And concerning my previous comment (default install of repmgr_funcs when you don't use repmgrd), I will open another issue.Anyway, best regards for your feedback. |
Well, as I said before, you need superuser privileges for cloning. Regards, |
But you wrote cloning in rsync context. But I will always use pg_basebackup not rsync. |
I did not say that. ;) I said that repmgr needs to run this query during the cloning process, which only a superuser can: WITH dd AS ( If the configuration files reside outside PGDATA (very common on Debian and Ubuntu systems), then they will need to be rsyncd separately, as pg_basebackup can't copy them. Regards, |
It is not a priority for us to make it possible to use repmgr without superuser privileges. If this is something that you particularly need, you will need to review and make the necessary changes to the source code (for example, if everything you need can always be copied with pg_basebackup, you don't need to run the above query). |
Fair enough. I understand your point but I'm always suspicious concerning granting superuser priv. |
Can you detail for which features postgresql role needs supeuuser privs ?
For security reasons i would like to constrain it to the minimum necessary.
Thanks in advance for any reply.
The text was updated successfully, but these errors were encountered: