Re: profiling connection overhead

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: profiling connection overhead
Date: 2010-12-07 02:09:56
Message-ID: AANLkTik-uSgR9mfUbkiV6vNtUG4MsqTvVrf1EXDJNYCe@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 6, 2010 at 2:47 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> Please explain more precisely what is wrong with SET SESSION
>> AUTHORIZATION / SET ROLE.
>
> 1) Session GUCS do not change with a SET ROLE (this is a TODO I haven't
> had any time to work on)
>
> 2) Users can always issue their own SET ROLE and then "hack into" other
> users' data.

Makes sense. It would be nice to fix those issues, independent of
anything else.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-12-07 02:10:13 Re: We really ought to do something about O_DIRECT and data=journalled on ext4
Previous Message Robert Haas 2010-12-07 02:05:28 Re: We really ought to do something about O_DIRECT and data=journalled on ext4