[Bizgres-general] [ENG] Re: Statement Queuing take II - Resource Scheduling (Running with cost and cursors)

Mark Kirkwood mkirkwood at greenplum.com
Wed Aug 2 11:11:37 UTC 2006


Luke Lonergan wrote:
> Mark, 
>
>   
>> An update on progress again:
>>
>> The machinery to  track  limit types other than merely active 
>> count was running for the first time today, so cost and count 
>> limit types are both working! (and work_mem could be made to 
>> work if I spent time on figuring out how to count the 
>> possible allocations in a plan).
>>     
>
> This is a big deal if I read this correctly - can we assign statements
> to queues post-planning based on their cost?
>
>
>   


The other thing I forgot to mention is that the queues can have several 
(currently two) types of limits in effect, which should make 'em more 
flexible:

e.g. I can have 1 queue with max active count=10 *and* max cost=10000000

So I can cap active count and cost in the queue.

Currently the *and* is the only possible logic, but it will be pretty 
easy to add the ability to either specify *and* or *or* for the limits 
in a queue.

Cheers

Mark




More information about the Bizgres-general mailing list