Re: Statement Queuing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Statement Queuing
Date: 2006-07-20 03:34:03
Message-ID: 23042.1153366443@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-07-20 03:58:07 Re: [PATCHES] 8.2 features?
Previous Message Mark Kirkwood 2006-07-20 03:14:28 Re: Statement Queuing