pg_upgrade docs are confusing if PostgreSQL's versioning system/language isn't known to reader

2017-12-18 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/9.6/static/pgupgrade.html Description: If a reader who is unfamiliar with PostgreSQL's versioning (where 9.5 and 9.6 are considered major versions) reads the documentation, it is unclear if t

Re: Typo

2017-12-18 Thread Peter Eisentraut
On 12/12/17 11:26, Peter Eisentraut wrote: > On 12/12/17 07:02, b...@merela.org wrote: >> The following documentation comment has been logged on the website: >> >> Page: https://www.postgresql.org/docs/10/static/using-explain.html >> Description: >> >> "The costs of the loop node are then set on th

Change to docs reporting form

2017-12-18 Thread Stephen Frost
Greetings, In order to avoid having emails generated from the doc reporting form be considered as spam by lots of people because it's clearly forged email, we've changed the 'From' to be a 'noreply' address and set the 'Reply-To' to be the original sender and the mailing list. Hopefully this chan

testing again

2017-12-18 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/static/index.html Description: this is another test of the emergency doc reporting form

test comment, please ignore

2017-12-18 Thread noreply
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/static/intro-whatis.html Description: This is a test of the new sending form. Please ignore this report :) //Magnus