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
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
