Query Planning Gone Wrong
Formal Metadata
| Title | Query Planning Gone Wrong |
|
| Title of Series | |
| Number of Parts | 25 |
| Author | |
| Contributors | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Ottawa, Canada |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | An analysis of common query planner failure modes
The PostgreSQL query planner does an excellent job with most queries, but no query planner is perfect.
In this talk, I'll analyze some of the commonly-reported cases where it fails to produce an acceptable plan, based on posts to pgsql-performance and other cases I've encountered on the job. |
|
