Stephen Frost <sfr...@snowman.net> writes:
> ... Lastly, there is the question of pg_cancel_backend and
> pg_terminate_backend. My thinking on this is to create a new
> 'pg_signal_backend' which admins could grant access to and leave the
> existing functions alone (modulo the change for has_privs_of_role as
> discussed previously). We'd rename the current 'pg_signal_backend' to
> something else (maybe '_helper'); it's not exposed anywhere and
> therefore renaming it shouldn't cause any heartache.
That seems fairly ugly. Why would we need a new, duplicative function
here? (Apologies if the reasoning was spelled out upthread, I've not
been paying much attention.)
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
