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

[Mark Kirkwood]

Simon Riggs wrote:
> On Mon, 2006-06-12 at 14:59 +1200, Mark Kirkwood wrote:
>   
>> 6/ Is the decision to make the resource locks distinct from the standard 
>> locks a good one? For instance it may make the deadlock detection code 
>> more complex, and it probably requires an additional LOCKTABLE hash. On 
>> the other had it could well increase robustness by not touching the lock 
>> code.
>>     
>
> If you want to re-write the deadlock detector...
>
>   
(Chuckles) - yep, a little scary.
>> 7/ Catalog changes and additions need to be thought about (e.g. for just 
>> simultaneous statement limits, we could add an element to the ROLE 
>> catalog, but it may be better to create a new ROLE_RESOURCES catalog). 
>> Ideas?
>>     
>
> An array of resource constraints on each role, so only one new
> attribute.
>   
Ah - yes, that's probably the most "Postgresqlian" way to do it!