Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role) - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role)
Date
Msg-id 4F71B7EF020000250004670B@gw.wicourts.gov
Whole thread Raw
In response to Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role)  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> wrote:
> Daniel Farina <daniel@heroku.com> wrote:
>> Is there a hypothetical DBA that doesn't want a mere-mortal user
>> to be able to signal one of their own backends to do "cancel
>> query, rollback the transaction, then close the socket"?  If so,
>> why?
Setting aside possible bugs in the mechanism, I have trouble
imagining a use-case where it would be undesirable to allow this.
> Well, I guess if you have different people sharing the same
> user-ID, you probably wouldn't want that.
As Tom pointed out, if there's another person sharing the user ID
you're using, and you don't trust them, their ability to cancel your
session is likely way down the list of concerns you should have.
-Kevin


pgsql-hackers by date:

Previous
From: Daniel Farina
Date:
Subject: Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role)
Next
From: Daniel Farina
Date:
Subject: Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role)