Tom Lane wrote:
Mark Kirkwood <[EMAIL PROTECTED]> writes:
Right - in principle it is not that difficult to add (once I have the
machinery for the cost limiter going properly that is). I thinking we
could either:
1. Add hooks to count work_mem allocations where they happen, or
2. Scan the pla
Mark Kirkwood <[EMAIL PROTECTED]> writes:
> Right - in principle it is not that difficult to add (once I have the
> machinery for the cost limiter going properly that is). I thinking we
> could either:
> 1. Add hooks to count work_mem allocations where they happen, or
> 2. Scan the plan tree and
Jim C. Nasby wrote:
Something that would be extremely useful to add to the first pass of
this would be to have a work_mem limiter. This would allow users to set
work_mem much more aggressively without worrying about pushing the
machine to swapping. That capability alone would make this valuable t
Something that would be extremely useful to add to the first pass of
this would be to have a work_mem limiter. This would allow users to set
work_mem much more aggressively without worrying about pushing the
machine to swapping. That capability alone would make this valuable to a
very large number
A while ago in connection with the 8.2 planning [1] there was some
discussion of resource management and statement queuing [2].
I am currently looking at implementing a resource management/queuing
module for Greenplum - initially targeting Bizgres, but I'm thinking it
could be beneficial for non-
