Re: Postgres 11 release notes
Brad DeJong <bpd0018@gmail.com>
I suggest the following edits for the PostgreSQL beta 2 release announcement. I did not provide the edits as a patch because I can't find the source of /about/news/1867. - This release contains ... as well as bug fixes that were reported ... + This release contains ... as well as fixes for bugs that were reported ... - we do not advise for you to run + we do not advise you to run or + we do not advise running - CHANGES SINCE BETA 2 + CHANGES SINCE BETA 1 - There have been many bug fixes for PostgreSQL 11 reported during - the Beta 1 period and applied to the Beta 2 release. Several bug fixes - reported for version 10 or earlier that also affected version 11 are - included in the Beta 2 release. + Fixes for many of the bugs reported during the PostgreSQL 11 Beta 1 + period have been applied to the Beta 2 release. Fixes for several bugs + reported for version 10 or earlier that affected version 11 have also + been included in the Beta 2 release. or, if you prefer active voice + PostgreSQL 11 Beta 2 contains fixes for many of the bugs that were + reported during the Beta 1 period and for several bugs reported + for version 10 or earlier that affected version 11. - ... eliminating a needless additional partition constraint checks ... + ... eliminating needless additional partition constraint checks ... - including returning NULL if slot is not advanced + including returning NULL if the slot is not advanced - Fix returning accurate results with ... This phrasing makes it sound like you didn't want the accurate results so you fixed them. :) Not being familiar with the fix in question, I do not have a suggestion as to how it should be rephrased.
Commits
-
doc: update PG 11 release notes
- 6eb612fea9d0 12.0 cited
-
Fix misspelled pg_trgm contrib name in PostgreSQL 11 release notes
- 3abc5a67edfd 12.0 landed
-
Doc: clarify release note text about v11's new window function features.
- 510421c45fb4 11.0 landed
- 11a3aeeb5e17 12.0 landed
-
Improve wording of release notes item
- bee6a683a5c3 11.0 landed
-
Fix typos in release notes
- fb6accd27b99 11.0 landed
-
Doc: preliminary list of PG11 major features.
- 4aad161c9a6d 11.0 landed
-
Make numeric power() handle NaNs according to the modern POSIX spec.
- d1fc750b5199 11.0 landed
-
Various improvements of skipping index scan during vacuum technics
- 8e12f4a250d2 11.0 cited
-
Revert back-branch changes in power()'s behavior for NaN inputs.
- f74d83b3034f 10.4 cited
-
Avoid wrong results for power() with NaN input on more platforms.
- 6bdf1303b34b 11.0 cited
-
Avoid wrong results for power() with NaN input on some platforms.
- 61b200e2f582 11.0 cited
-
Skip full index scan during cleanup of B-tree indexes when possible
- 857f9c36cda5 11.0 cited
-
Rewrite the code that applies scan/join targets to paths.
- 11cf92f6e2e1 11.0 cited
-
Postpone generate_gather_paths for topmost scan/join rel.
- 3f90ec8597c3 11.0 cited
-
Add casts from jsonb
- c0cbe00fee6d 11.0 cited
-
Make plpgsql use its DTYPE_REC code paths for composite-type variables.
- 4b93f57999a2 11.0 cited
-
Don't allow VACUUM VERBOSE ANALYZE VERBOSE.
- 921059bd66c7 11.0 cited
-
Pass InitPlan values to workers via Gather (Merge).
- e89a71fb449a 11.0 cited
-
Account for the effect of lossy pages when costing bitmap scans.
- 5edc63bda68a 11.0 cited
-
Allow no-op GiST support functions to be omitted.
- d3a4f89d8a3e 11.0 cited
-
Rearm statement_timeout after each executed query.
- f8e5f156b30e 11.0 cited
-
Push limit through subqueries to underlying sort, where possible.
- 1f6d515a67ec 11.0 cited