| Type: | real |
| Défaut: | 1000 |
| Min: | 0 |
| Max: | 1.79769e+308 |
| Contexte: | user |
| Redémarrer: | false |
| Depuis: | 9.6 |
Configure le coût estimé par l'optimiseur pour le lancement de processus de travail parallèle. La valeur par défaut est 1000.
Sur 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?
Sur pgsql-hackers
- Parallell hashjoin sometimes ignores temp_tablespaces
- Re: pgstat_report_activity() and parallel CREATE INDEX (was: Parallel index creation & pg_stat_activity)
- Re: Consider Parallelism While Planning For REFRESH MATERIALIZED VIEW
- RE: Parallel INSERT (INTO ... SELECT ...)
- Re: enable_incremental_sort changes query behavior