Re: [HACKERS] Hints proposal

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org
Subject: Re: [HACKERS] Hints proposal
Date: 2006-10-13 16:36:04
Message-ID: 25352.1160757364@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

"Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> I completely agree that it's much better *in the long run* to improve
> the planner and the statistics system so that we don't need hints. But
> there's been no plan put forward for how to do that, which means we also
> have no idea when some of these problems will be resolved.

You keep arguing on the assumption that the planner is static and
there's no one working on it. That is false --- although this thread
is certainly wasting a lot of time that could have been used more
productively ;-).

I also dispute your assumption that hints of the style you propose
will be easier to implement or maintain than the sort of
statistical-assumption tweaking that's been counter-proposed. Just for
starters, how are you going to get those hints through the parser and
rewriter? That's going to take an entire boatload of very ugly code
that isn't needed at all in a saner design.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2006-10-13 16:36:29 Re: Additional stats for Relations
Previous Message Roman Neuhauser 2006-10-13 16:30:39 Re: more anti-postgresql FUD

Browse pgsql-performance by date

  From Date Subject
Next Message Jeff Davis 2006-10-13 16:45:54 Re: [PERFORM] Hints proposal
Previous Message Jim C. Nasby 2006-10-13 16:16:14 Re: [HACKERS] Hints proposal