Do we really want to mention 8.3 in current versions of the docs?
Hi, do we really want to reference version 8.3 in current docs? https://www.postgresql.org/docs/current/row-estimation-examples.html -> "The outputs shown are taken from version 8.3" The examples seem to be more or less fine,. Regards Daniel
Tutorial make command comment
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/tutorial-sql-intro.html Description: It would be valuable for someone who only just clones the repo, to mention that before running make to get the tutorial build, ./configure must be run at the root of the repo for other Makefiles to be populated. Kind regards, Efren
random-page-cost
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/runtime-config-query.html Description: Two comments on random-page-cost parameter here https://www.postgresql.org/docs/current/runtime-config-query.html#GUC-RANDOM-PAGE-COST 1) Adding a paragraph reminding us what random-access really mean in postgres would be extremely valuable. I find the first paragraph from the index - only scan section perfect. "This means that in an ordinary index scan, each row retrieval requires fetching data from both the index and the heap. Furthermore, while the index entries that match a given indexable WHERE condition are usually close together in the index, the table rows they reference might be anywhere in the heap. The heap-access portion of an index scan thus involves a lot of random access into the heap, which can be slow, particularly on traditional rotating media. " 2) A question, based on the definition of what random-access mean in postgres (hits to the heap) does the random-page-cost affect index-only and covering index scans at all? (assume zero heap fetches from hints etc.)? if no can we also add a note there. thank you! Hussein
There is no command pg_ctl reload in Postgresql 13 clusters
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/config-setting.html Description: Could you provide additional information about pg_ctlcluster command? On postgrsql 13 clusters there is no pg_ctl reload. So we should not use `pg_ctl reload` instead eg `pg_ctlcluster 13 main reload` (after listing clusters with `pg_lsclusters`).
Re: There is no command pg_ctl reload in Postgresql 13 clusters
PG Doc comments form writes: > Could you provide additional information about pg_ctlcluster command? pg_ctlcluster is not part of the community Postgres code. It is (I believe) added by the Debian packagers, so you'd have to discuss the state of their documentation with them. regards, tom lane
