Capabilities expected to be part of PostgreSQL 9.6 will substantially improve the performance of queries that touch large volumes of data, such as reporting queries on databases used primarily for OLTP. I'll discuss those improvements with examples and benchmark results. In addition, I'll discuss the cases where the current implementation fails to speed things up as much as one might hope, either because the optimal plan is not generated or because the plan fails to run as fast in parallel as might be hoped, and explain how we might improve things in the future. Finally, I'll discuss the pluggable nature of the parallelism infrastructure and explain how, first, it can be used for purposes other than running queries, and, second, if part of it doesn't work well in a particular case, a replacement part can be substituted in for that particular purpose without much impact on the surrounding code.