Tom Lane wrote:
> Mark Kirkwood <markir@paradise.net.nz> 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 deduce how many work_mem allocations there
>> will be.
>
> The problem with this is that many of the cost models depend on
> work_mem, so you can't simply arbitrarily alter the setting
> after-the-fact. At least not if you don't want to kill performance.
>
Right - the intention would be to merely count the number of work_mem
allocations against some type of total, rather than modifying work_mem
itself.
Cheers
Mark
