| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER SYSTEM vs symlink |
| Date: | 2015-11-02 21:08:13 |
| Message-ID: | CA+Tgmob7yEM8YxKJPq2=wbwkhxerV-HVWDU+SE69i=m1epaM8g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 2, 2015 at 3:41 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>> Two different methods of restricting ALTER SYSTEM have already been
>> discussed on this thread: one using file permissions, and the other
>> using ProcessUtility_hook. I personally think that's good enough.
>
> The issue which I have with these suggestions is that one requires users
> to install an as-yet-unwritten module and the other is to hack with
> permissions in the data directory. As we've all seen, people playing in
> $PGDATA is generally a bad idea.
Well, fair enough. I think somebody could write that module in about
an hour, though. All you have to do is latch onto ProcessUtility_hook
and throw an error if you've got yourself an AlterSystemStmt.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haribabu Kommi | 2015-11-02 21:10:12 | Re: BUG #13741: vacuumdb does not accept valid password |
| Previous Message | Tom Lane | 2015-11-02 21:07:18 | Re: Patch to install config/missing |