> so, we are gonna have an AI built into the database now too? my
> experience to date is that each scenario is different for what can be done
> to fix something ... as my last problem shows. I could remove the index,
> since it isn't used anywhere else that I'm aware of, or, as philip pointed
> out, I could change my query ...
>
> now, this 'PERFORMANCE_TIPS', would it have to be smart enough to think
> about Philips solution, or only Tom's? How is such a knowledge base
> maintained? Who is turned off of PgSQL when they enable that, and it
> doesn't help their performance even though they follow the
> recommendations?
Well, I think it would be helpful to catch the most obvious things
people forget, but if no one thinks its a good idea, I will yank it.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
