\Tom Lane wrote: > Bruno Wolff III <[EMAIL PROTECTED]> writes: > > In the following paragraph there appear to be two typos. I think > > "optimizer make" should be "optimizer makes" and that "lose-source" > > should be "closed-source". > > > It is difficult to explain all the optimizer improvements that go into a release > > like this. They involve complex adjustments to the logic used to select indexes, > > join methods, and join order. They are difficult to explain, but the result is > > that the optimizer make quicker and better choices in how to execute queries, > > resulting in improved performance. The close relationship between our developers > > and users reporting problems allows us to make rapid and complex optimizer > > improvements that would be very difficult for lose-source companies to emulate. > > I'd suggest removing the paragraph entirely, on the grounds that it is > content-free fluff.
Hey, that's your content-free fluff. :-) You make major optimizer improvements in every release, but they are so complex it is impossible to explain them to people. This paragraph tries to address that. However, since you don't like it, I will remove it entirely. If you change your mind we can re-add it. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
