| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Daniel Farina <daniel(at)heroku(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role) |
| Date: | 2012-03-27 09:04:30 |
| Message-ID: | 20120327090430.GD29452@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 26, 2012 at 07:53:25PM -0400, Robert Haas wrote:
> I think the more important question is a policy question: do we want
> it to work like this? It seems like a policy question that ought to
> be left to the DBA, but we have no policy management framework for
> DBAs to configure what they do or do not wish to allow. Still, if
> we've decided it's OK to allow cancelling, I don't see any real reason
> why this should be treated differently.
The DBA can customize policy by revoking public execute permissions on
pg_catalog.pg_terminate_backend and interposing a security definer function
implementing his checks. For the population who will want something different
here, that's adequate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2012-03-27 09:25:27 | Improvement of log messages in pg_basebackup |
| Previous Message | Dimitri Fontaine | 2012-03-27 08:27:41 | Re: Command Triggers patch v18 |