Re: giving a user permission to kill their processes only

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-general(at)postgresql(dot)org
Cc: George Nychis <gnychis(at)cmu(dot)edu>
Subject: Re: giving a user permission to kill their processes only
Date: 2007-03-06 04:26:13
Message-ID: 200703052326.13542.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wednesday 28 February 2007 15:19, George Nychis wrote:
> Hey all,
>
> So the pg_cancel_backend() function by default is only available to super
> users, so I decided to write a wrapper function around, use a SECURITY
> DEFINER, and GRANT my user privilege to use the wrapper.
>
> BEGIN;
> CREATE FUNCTION kill_process(integer) RETURNS boolean AS 'select
> pg_cancel_backend($1);' LANGUAGE SQL SECURITY DEFINER;
> REVOKE EXECUTE ON FUNCTION kill_process(integer) FROM PUBLIC;
> COMMIT;
> GRANT EXECUTE ON FUNCTION kill_process(integer) TO gnychis;
>
> The problem with this is I can now kill other users postgresql processes.
> I was wondering if anyone knows a way in which i can check that the
> postgres process being killed is running a query for that user? Therefore,
> they can't kill queries in postgres processes started by other users.
>

you could try to match CURRENT_USER with the information in pg_stat_activity,
but be aware there is a reason why this functionality was made for
superusers...
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Florian G. Pflug 2007-03-06 04:29:14 Re: Support for idempotent schema changes?
Previous Message Robert Treat 2007-03-06 04:11:51 Re: pg temp tables