Re: Mini improvement: statement_cost_limit

From: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: Hans-Jürgen Schönig <postgres(at)cybertec(dot)at>, "daveg" <daveg(at)sonic(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "PG Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Mini improvement: statement_cost_limit
Date: 2008-08-05 06:37:04
Message-ID: 4897F510.20702@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
> On Sun, 2008-08-03 at 22:09 +0200, Hans-Jürgen Schönig wrote:
>
>>> Another alternative would be to have a plugin that can examine the
>>> plan
>>> immediately after planner executes, so you can implement this
>>> yourself,
>>> plus some other possibilities.
>>>
>
>> this would be really fancy.
>> how could a plugin like that look like?
>
> Hmm...thinks: exactly like the existing planner_hook().
>
> So, rewrite this as a planner hook and submit as a contrib module.

Now that's a good idea!

I personally don't think this feature is a good idea, for all the
reasons others have mentioned, but as a pgfoundry project it can be
downloaded by those who want it, and perhaps prove its usefulness for
others as well.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-08-05 06:52:29 Re: Automatic Client Failover
Previous Message ITAGAKI Takahiro 2008-08-05 06:26:08 Re: NDirectFileRead and Write