Re: Simple join optimized badly?
| От | Jim C. Nasby |
|---|---|
| Тема | Re: Simple join optimized badly? |
| Дата | |
| Msg-id | 20061010140222.GA72517@nasby.net обсуждение исходный текст |
| Ответ на | Re: Simple join optimized badly? ("Joshua D. Drake") |
| Ответы |
Re: Simple join optimized badly?
("Joshua D. Drake")
|
| Список | 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 Mon, Oct 09, 2006 at 03:41:09PM -0700, Joshua D. Drake wrote: > > > > One of the big problems with doing set enable_...=off is that there's no > > way to embed that into something like a view, so you're almost forced > > into putting into the application code itself, which makes matters even > > worse. If you could hint this within a query (maybe even on a per-table > > level), you could at least encapsulate that into a view. > > You can easily pass multiple statements within a single exec() or push > it into an SPF. Unless I'm missing something, putting multiple statements in a single exec means you're messing with the application code. And you can't update a SRF (also means messing with the application code). Though, I suppose you could update a view that pulled from an SRF... -- Jim Nasby EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
В списке pgsql-performance по дате отправления: