Re: [HACKERS] pg_terminate_backend and pg_cancel_backend by not administrator user

2011-07-01 Thread Torello Querci
2011/6/2 Noah Misch : > On Wed, Jun 01, 2011 at 10:26:34PM -0400, Josh Kupershmidt wrote: >> On Wed, Jun 1, 2011 at 5:55 PM, Noah Misch wrote: >> > On Sun, May 29, 2011 at 10:56:02AM -0400, Josh Kupershmidt wrote: >> >> Looking around, I see there were real problems[1] with sending SIGTERM >> >> t

Re: [HACKERS] pg_terminate_backend and pg_cancel_backend by not administrator user

2011-06-01 Thread Josh Kupershmidt
On Wed, Jun 1, 2011 at 5:55 PM, Noah Misch wrote: > On Sun, May 29, 2011 at 10:56:02AM -0400, Josh Kupershmidt wrote: >> Looking around, I see there were real problems[1] with sending SIGTERM >> to individual backends back in 2005 or so, and pg_terminate_backend() >> was only deemed safe enough to

Re: [HACKERS] pg_terminate_backend and pg_cancel_backend by not administrator user

2011-05-29 Thread Josh Kupershmidt
On Sun, May 29, 2011 at 5:04 AM, Noah Misch wrote: > What risks arise from unconditionally allowing these calls for the same user's > backends?  `pg_cancel_backend' ought to be safe enough; the user always has > access to the standard cancellation protocol, making the SQL interface a mere > conven

Re: [HACKERS] pg_terminate_backend and pg_cancel_backend by not administrator user

2011-05-28 Thread Josh Kupershmidt
On Fri, Mar 11, 2011 at 8:54 AM, Bruce Momjian wrote: > I have added it to the next commit fest. Hi Torello, I have volunteered (more accurately, Greg Smith "volunteered" me :-) to be a reviewer for this patch. I know you're a bit new here, so I thought I'd outline where this patch stands and wh

Re: [HACKERS] pg_terminate_backend and pg_cancel_backend by not administrator user

2011-03-11 Thread Bruce Momjian
Kevin Grittner wrote: > Torello Querci wrote: > > > I attach a path for this > > It's too late in the release cycle to consider this for version 9.1. > Please add it to the open CommitFest for consideration for 9.2: > > https://commitfest.postgresql.org/action/commitfest_view/open I have ad

Re: [HACKERS] pg_terminate_backend and pg_cancel_backend by not administrator user

2011-02-27 Thread Josh Kupershmidt
On Mon, Feb 14, 2011 at 8:58 AM, Anssi Kääriäinen wrote: > On 02/14/2011 02:10 PM, Torello Querci wrote: >> >> I suppose that give the right to the owner db user to terminate or >> cancel other session connected to the database which it is owner is a >> good thing. >> I not see any security proble

Re: [HACKERS] pg_terminate_backend and pg_cancel_backend by not administrator user

2011-02-14 Thread Kevin Grittner
Torello Querci wrote: > I attach a path for this It's too late in the release cycle to consider this for version 9.1. Please add it to the open CommitFest for consideration for 9.2: https://commitfest.postgresql.org/action/commitfest_view/open -Kevin -- Sent via pgsql-hackers mailing lis

Re: [HACKERS] pg_terminate_backend and pg_cancel_backend by not administrator user

2011-02-14 Thread Anssi Kääriäinen
On 02/14/2011 02:10 PM, Torello Querci wrote: I suppose that give the right to the owner db user to terminate or cancel other session connected to the database which it is owner is a good thing. I not see any security problem because this user can cancel or terminate only the session related with

[HACKERS] pg_terminate_backend and pg_cancel_backend by not administrator user

2011-02-14 Thread Torello Querci
Hi, this is the first time that I post here, so if I wrong please don't kill me ... I see that pg_terminate_backend and pg_cancel_backend can be execute only by admin users. This approach seems to be too restrictive in a lots of real situation. In dept, I have a situation where it is created one