| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | mahatmafatal(at)gmail(dot)com |
| Subject: | Improvements regarding explanation of parallel execution and detailed node parameters |
| Date: | 2019-07-26 17:07:40 |
| Message-ID: | 156416086029.1184.8453492993456200338@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/11/using-explain.html
Description:
Proposals for improvement of EXCPLAIN docu
https://www.postgresql.org/docs/current/using-explain.html:
1. There is no mentioning of how parallel execution gets depicted in the
execution plan.
-- how to interpret the actual_time with loops of a parallel executed
node?
2. I am logging execution plans with the help of the awsome auto_explain
plugin in JSON, scrape it from the log and transfer it to ELK stack for
further analysis. Therefore it would be quite helpful to have a reference
documentation about each and every individual node-type (Seq Scan, Hash
Join, Gather, Sort, Aggregate and so on.). Which are their optional fields,
which are mandatory, and most important, what is their semantic?
Kind regards
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Liudmila Mantrova | 2019-07-26 18:08:47 | suspicious wording in pg_rewind docs |
| Previous Message | Alvaro Herrera | 2019-07-25 17:03:56 | Re: Wrong formatting of the word 'executed' |