Subject: Re: [PERFORM] Hints proposal
From: Jeff Davis <pgsql@j-davis.com>
To: Bucky Jordan <bjordan@lumeta.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>, josh@agliodbs.com,
	"Jim C. Nasby" <jim@nasby.net>, pgsql-hackers@postgresql.org
In-Reply-To: <78ED28FACE63744386D68D8A9D1CF5D4209CBD@MAIL.corp.lumeta.com>
References: <78ED28FACE63744386D68D8A9D1CF5D4209CBD@MAIL.corp.lumeta.com>
Content-Type: text/plain
Date: Fri, 13 Oct 2006 10:23:31 -0700
Message-Id: <1160760211.31966.231.camel@dogma.v10.wvs>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Fri, 2006-10-13 at 13:08 -0400, Bucky Jordan wrote:
> > It sounds horrible to me too, and I'm the one that thought of it (or
> at
> > least I'm the one that introduced it to this thread).
> > 
> > However, everything is relative. Since the other idea floating around
> is
> > to put the same hinting information into the client queries
> themselves,
> > regexes look great by comparison (in my opinion).
> 
> I was merely expressing the same opinion. But I'm not one of those

I didn't mean to imply otherwise.

> working on the planner, and all I can say to those of you who are is
> your efforts on good design are most appreciated, even if they do take
> longer than we users would like at times.
> 
> My only point was that they should *NOT* be put in queries themselves as
> this scatters the nightmare into user code as well. Of course, other
> more sane ideas are most welcome. I don't like screeching on blackboards
> either. (regular expressions, although very valuable at times, seem to
> have that effect quite often...)

Right. And I think the sane ideas are along the lines of estimate & cost
corrections (like Tom is saying).

Regards,
	Jeff Davis