X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id B92B29DC84B
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Thu, 15 Dec 2005 23:07:23 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 46551-01
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Thu, 15 Dec 2005 23:07:28 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from moonunit2.moonview.localnet (wsip-68-15-5-150.sd.sd.cox.net
	[68.15.5.150]) by postgresql.org (Postfix) with ESMTP id 7325E9DC820
	for <pgsql-performance@postgresql.org>;
	Thu, 15 Dec 2005 23:07:21 -0400 (AST)
Received: from [192.168.0.3] (moonunit3.moonview.localnet [192.168.0.3])
	by moonunit2.moonview.localnet (8.13.1/8.13.1) with ESMTP id
	jBG37cCP025775
	for <pgsql-performance@postgresql.org>; Thu, 15 Dec 2005 19:07:38 -0800
Message-ID: <43A22EA3.50007@modgraph-usa.com>
Date: Thu, 15 Dec 2005 19:04:03 -0800
From: "Craig A. James" <cjames@modgraph-usa.com>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Re: Overriding the optimizer
References: <200512141603.52583.blargity@gmail.com>
	<7484.1134600423@sss.pgh.pa.us>
	<1134629567.14248.27.camel@firebolt>
	<200512150148.16125.blargity@gmail.com>
	<1134644526.14248.60.camel@firebolt>
	<43A1C40D.8040006@paradise.net.nz>
	<43A1F6DB.3080805@modgraph-usa.com>
	<18537.1134692629@sss.pgh.pa.us>
In-Reply-To: <18537.1134692629@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.032 required=5 tests=[AWL=0.032]
X-Spam-Score: 0.032
X-Spam-Level: 
X-Archive-Number: 200512/374
X-Sequence-Number: 16195

Tom Lane wrote:
> This discussion has been had before (many times) ... see the -hackers
> archives for detailed arguments.  The one that carries the most weight
> in my mind is that planner hints embedded in applications will not adapt
> to changing circumstances --- the plan that was best when you designed
> the code might not be best today.

Absolutely right.  But what am I supposed to do *today* if the planner makes a mistake?  Shut down my web site?

Ropes are useful, but you can hang yourself with them.  Knives are useful, but you can cut yourself with them.  Should we ban useful tools because they cause harm to the careless?

Craig