To: Csaba Nagy <nagy@ecircle-ag.com>
cc: postgres hackers <pgsql-hackers@postgresql.org>,
	"Jim C. Nasby" <jim@nasby.net>,
	postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: [HACKERS] Hints proposal 
In-reply-to: <1160670865.28751.58.camel@coppola.muc.ecircle.de> 
References: <20061012151439.GT28647@nasby.net>
 <10866.1160667752@sss.pgh.pa.us>
	<1160670865.28751.58.camel@coppola.muc.ecircle.de>
Comments: In-reply-to Csaba Nagy <nagy@ecircle-ag.com>
	message dated "Thu, 12 Oct 2006 18:34:25 +0200"
Date: Thu, 12 Oct 2006 13:18:17 -0400
Message-ID: <13954.1160673497@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Csaba Nagy <nagy@ecircle-ag.com> writes:
> Until that point is achieved, the above proposal is one of the simplest
> to understand for the tweaking DBA, and the fastest to deploy when faced
> with catastrophic plans. And I would guess it is one of the simplest to
> be implemented and probably not very high maintenance either, although
> this is just a guess.

That guess is wrong ... but more to the point, if you think that "simple
and easy to implement" should be the overriding concern for designing a
new feature, see mysql.  They've used that design approach for years and
look what a mess they've got.  This project has traditionally done
things differently and I feel no need to change that mindset now.

			regards, tom lane