From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: system administration functions with hardcoded superuser checks |
Date: | 2012-12-18 17:29:01 |
Message-ID: | CA+U5nMKf5yEWCPBdEiGx=Q1zoNmHZdix-yse6cLnVbia_EwPZQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 18 December 2012 17:09, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> There are some system administration functions that have hardcoded
> superuser checks, specifically:
>
> pg_reload_conf
> pg_rotate_logfile
> pg_read_file
> pg_read_file_all
> pg_read_binary_file
> pg_read_binary_file_all
> pg_stat_file
> pg_ls_dir
>
> Some of these are useful in monitoring or maintenance tools, and the
> hardcoded superuser checks require that these tools run with maximum
> privileges. Couldn't we just install these functions without default
> privileges and allow users to grant privileges as necessary?
+1
But I would include recovery functions also.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Groshev Andrey | 2012-12-18 17:34:53 | Re: [GENERAL] trouble with pg_upgrade 9.0 -> 9.1 |
Previous Message | Peter Eisentraut | 2012-12-18 17:09:10 | system administration functions with hardcoded superuser checks |