[Bizgres-general] Statement Queuing take II - Resource Scheduling

[Josh Berkus]

Jim,

> I'm thinking that for the first pass maybe we should only look at
> whatever role you have active at the time. 

Yes.  By "lowest role in the tree" I meant "partents of the role currently 
active".  As in, do not try to do anything fancy with recursive analysis of 
the parent roles.

Hmm.  I can see some problems with that too.  How are parameters set for 
parent roles (like SEARCH_PATH) currently handled?

> Or, take the minimum of all 
> limits that apply to roles that are directly INHERITed by the current
> role, if SET ROLE hasn't been used.

No.  Too complicated, for no real benefit.

> Right - The SET ROLE is a bit alarming, as it means users can 'switch
> off' their resource limits in some cases. 

I see this as a feature and not a flaw.  Think of the smart DBA who wants to 
deliberately run some queries as "joe user" and others as "report writer".  
He can SET ROLE, run some queries, SET ROLE again, and run the others.

It does mean that you have to be careful what roles your users belong to, but 
when is that not the case?

-- 
Josh Berkus
PostgreSQL @ Sun
San Francisco