From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Statement Queuing |
Date: | 2006-07-20 04:49:36 |
Message-ID: | 44BF0B60.904@paradise.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Mark Kirkwood <markir(at)paradise(dot)net(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2006-07-20 05:18:39 | Re: [PATCHES] 8.2 features? |
Previous Message | Tom Lane | 2006-07-20 04:36:54 | Re: [PATCHES] 8.2 features? |