Re: Postgres 11 release notes

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>

To: Dilip Kumar <dilipbalaut@gmail.com>

Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2018-05-14T20:41:54Z

Lists: pgsql-hackers

On Mon, May 14, 2018 at 05:34:54PM +0530, Dilip Kumar wrote:
> 
> On Fri, May 11, 2018 at 8:38 PM, Bruce Momjian <bruce@momjian.us> wrote:
> 
>     I have committed the first draft of the Postgres 11 release notes.  I
>     will add more markup soon.  You can view the most current version here:
> 
>             http://momjian.us/pgsql_docs/release-11.html
> 
>     I expect a torrent of feedback.  ;-)
> 
>     On a personal note, I want to apologize for not adequately championing
>     two features that I think have strategic significance but didn't make it
>     into Postgres 11:  parallel FDW access and improved multi-variate
>     statistics.  I hope to do better job during Postgres 12.
>    
>     --
>       Bruce Momjian  <bruce@momjian.us>        http://momjian.us
>       EnterpriseDB                             http://enterprisedb.com
> 
>     + As you are, so once was I.  As I am, so you will be. +
>     +                      Ancient Roman grave inscription +
> 
> 
> 
> I think the below commit is missed in the release notes?
> 
> 5edc63bda68a77c4d38f0cbeae1c4271f9ef4100
> 
> Committer: Robert Haas <rhaas@postgresql.org>  2017-11-10 13:50:50
> 
>     Account for the effect of lossy pages when costing bitmap scans.
>     
>     Dilip Kumar, reviewed by Alexander Kumenkov, Amul Sul, and me.
>     Some final adjustments by me.
> 
> As part of this commit, we are also accounting for the lossy pages during
> bitmap costing.  This will consider
> the effect of work_mem while selecting the bitmap heap scan path.

Uh, that seems very exotic to mention, sorry.  Others have opinions?

I have updated the PG11 doc URL with all the changes so far.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

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