| From: | moj(at)dshare(dot)de |
|---|---|
| To: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Missing parallel_workers setting in the chapter for parallel query |
| Date: | 2016-11-02 10:13:22 |
| Message-ID: | 20161102101322.15993.47292@wrigleys.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/static/parallel-query.html
Description:
Hi,
maybe i overlooked something, but i have hard time to unterstand, why
max_parallel_workers_per_gather was not fully utilised in some cases.
After reading the source code, I realized that there is a setting at table
level:
parallel_workers
(https://www.postgresql.org/docs/9.6/static/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS)
I think it would help, if this setting is mentioned in the chapter for
parallel query
(https://www.postgresql.org/docs/9.6/static/parallel-query.html)
Perhaps this page would be a good place:
https://www.postgresql.org/docs/9.6/static/when-can-parallel-query-be-used.html
Regards,
Marc-Olaf
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sallyx | 2016-11-04 18:58:41 | SET AUTOCOMMIT TO OFF is no longer supported |
| Previous Message | Michael Paquier | 2016-11-02 01:13:08 | Re: Missing tablespace_option | effective_io_concurrency |