Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role)

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Cc: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Daniel Farina" <daniel(at)heroku(dot)com>, "Magnus Hagander" <magnus(at)hagander(dot)net>, "Noah Misch" <noah(at)leadboat(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role)
Date: 2012-03-27 18:21:22
Message-ID: 201203272021.23540.andres@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tuesday, March 27, 2012 07:51:59 PM Kevin Grittner wrote:
> > 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.
Hm. I don't think that is an entirely valid argumentation. The same user could
have entirely different databases. They even could have distinct access
countrol via the clients ip.
I have seen the same cluster being used for prod/test instances at smaller
shops several times.

Whether thats a valid usecase I have no idea.

Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2012-03-27 18:47:06 Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
Previous Message Daniel Farina 2012-03-27 17:52:43 Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role)