Re: Statement Queuing - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Statement Queuing
Date
Msg-id 23042.1153366443@sss.pgh.pa.us
Whole thread Raw
In response to Re: Statement Queuing  (Mark Kirkwood <markir@paradise.net.nz>)
Responses Re: Statement Queuing  (Mark Kirkwood <markir@paradise.net.nz>)
List pgsql-hackers
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: Statement Queuing
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] 8.2 features?