| Type: | real |
| Default: | 1000 |
| Min: | 0 |
| Max: | 1.79769e+308 |
| Context: | user |
| Restart: | false |
| Since: | 9.6 |
Sets the planner's estimate of the cost of launching parallel worker processes. The default is 1000.
On StackOverflow
- Missing max_parallel_degree configuration parameter in PostgreSql 9.6
- Nested Loop Left Join cost too much time?
- Postgresql - not using parallelism
- Large COUNT DISTINCT performs slowly in postgresql
- Why does "explain analyzing" this query fnish fast (showing a parallel plan), while running the actual query without "explain analyze" doesn't?
On pgsql-hackers
- Re: How to launch parallel aggregations ?
- Re: pgstat_report_activity() and parallel CREATE INDEX (was: Parallel index creation & pg_stat_activity)
- Re: enable_incremental_sort changes query behavior
- Re: Parallel INSERT (INTO ... SELECT ...)
- Re: Re: Parallel scan with SubTransGetTopmostTransaction assert coredump