Re: Simple join optimized badly?
| От | Jim C. Nasby |
|---|---|
| Тема | Re: Simple join optimized badly? |
| Дата | |
| Msg-id | 20061010142101.GD72517@nasby.net обсуждение исходный текст |
| Ответ на | Re: Simple join optimized badly? (Tom Lane) |
| Ответы |
Re: Simple join optimized badly?
(Josh Berkus)
|
| Список | pgsql-performance |
Дерево обсуждения
Simple join optimized badly?
("Craig A. James",
)
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? ("Denis Lussier", )
Re: Simple join optimized badly? (Jim Nasby, )
Re: Simple join optimized badly? (Josh Berkus, )
Re: Simple join optimized badly? ("Craig A. James", )
Re: Simple join optimized badly? (Mark Kirkwood, )
Re: Simple join optimized badly? ("Craig A. James", )
Re: Simple join optimized badly? (Mark Kirkwood, )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? (Josh Berkus, )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? (Scott Marlowe, )
Re: Simple join optimized badly? (Bruce Momjian, )
Re: Simple join optimized badly? ("Craig A. James", )
Re: Simple join optimized badly? (Chris Browne, )
Re: Simple join optimized badly? (Chris Browne, )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? (Mark Kirkwood, )
Re: Simple join optimized badly? (Mark Kirkwood, )
Re: Simple join optimized badly? (Tobias Brox, )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? ("Joshua D. Drake", )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? ("Joshua D. Drake", )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? (Josh Berkus, )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? (Bruno Wolff III, )
Re: Simple join optimized badly? (Brian Herlihy, )
Re: Simple join optimized badly? ("Craig A. James", )
Re: Simple join optimized badly? ("Joshua D. Drake", )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? ("Steinar H. Gunderson", )
Re: Simple join optimized badly? ("Joshua D. Drake", )
Re: Simple join optimized badly? ("Joshua D. Drake", )
Re: Simple join optimized badly? (Brian Herlihy, )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? (Brian Herlihy, )
Re: Simple join optimized badly? ("Bucky Jordan", )
Re: Simple join optimized badly? (Heikki Linnakangas, )
Re: Simple join optimized badly? (Bruce Momjian, )
Collect stats during seqscan (was: Simple join optimized badly?) ("Jim C. Nasby", )
Re: Simple join optimized badly? (Mark Lewis, )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? ("Denis Lussier", )
Re: Simple join optimized badly? (Jim Nasby, )
Re: Simple join optimized badly? (Josh Berkus, )
Re: Simple join optimized badly? ("Craig A. James", )
Re: Simple join optimized badly? (Mark Kirkwood, )
Re: Simple join optimized badly? ("Craig A. James", )
Re: Simple join optimized badly? (Mark Kirkwood, )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? (Josh Berkus, )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? (Scott Marlowe, )
Re: Simple join optimized badly? (Bruce Momjian, )
Re: Simple join optimized badly? ("Craig A. James", )
Re: Simple join optimized badly? (Chris Browne, )
Re: Simple join optimized badly? (Chris Browne, )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? (Mark Kirkwood, )
Re: Simple join optimized badly? (Mark Kirkwood, )
Re: Simple join optimized badly? (Tobias Brox, )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? ("Joshua D. Drake", )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? ("Joshua D. Drake", )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? (Josh Berkus, )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? (Bruno Wolff III, )
Re: Simple join optimized badly? (Brian Herlihy, )
Re: Simple join optimized badly? ("Craig A. James", )
Re: Simple join optimized badly? ("Joshua D. Drake", )
Re: Simple join optimized badly? ("Jim C. Nasby", )
Re: Simple join optimized badly? ("Steinar H. Gunderson", )
Re: Simple join optimized badly? ("Joshua D. Drake", )
Re: Simple join optimized badly? ("Joshua D. Drake", )
Re: Simple join optimized badly? (Brian Herlihy, )
Re: Simple join optimized badly? (Tom Lane, )
Re: Simple join optimized badly? (Brian Herlihy, )
Re: Simple join optimized badly? ("Bucky Jordan", )
Re: Simple join optimized badly? (Heikki Linnakangas, )
Re: Simple join optimized badly? (Bruce Momjian, )
Collect stats during seqscan (was: Simple join optimized badly?) ("Jim C. Nasby", )
Re: Simple join optimized badly? (Mark Lewis, )
On Tue, Oct 10, 2006 at 10:14:48AM -0400, Tom Lane wrote: > "Jim C. Nasby" <> writes: > > I'd rather have the ugly solution sooner rather than the elegant one > > later (if ever). > > The trouble with that is that we couldn't ever get rid of it, and we'd > be stuck with backward-compatibility concerns with the first (over > simplified) design. It's important to get it right the first time, > at least for stuff that you know perfectly well is going to end up > embedded in application code. We've depricated things before, I'm sure we'll do it again. Yes, it's a pain, but it's better than not having anything release after release. And having a formal hint language would at least allow us to eventually clean up some of these oddball cases, like the OFFSET 0 hack. I'm also not convinced that even supplimental statistics will be enough to ensure the planner always does the right thing, so query-level hints may have to stay (though it'd be great if that wasn't the case). -- Jim Nasby EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
В списке pgsql-performance по дате отправления: