Horton

Re: Postgres 11 release notes

Magnus Hagander <magnus@hagander.net>

View thread View on postgr.es
From: Magnus Hagander <magnus@hagander.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Bruce Momjian <bruce@momjian.us>, Tatsuo Ishii <ishii@sraoss.co.jp>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-05-16T16:28:43Z
Lists: pgsql-hackers 
On Wed, May 16, 2018 at 6:24 PM, Alvaro Herrera <alvherre@2ndquadrant.com>
wrote:

> On 2018-May-16, Magnus Hagander wrote:
>
> > On Wed, May 16, 2018 at 4:08 PM, Alvaro Herrera <
> alvherre@2ndquadrant.com>
> > wrote:
>
> > > I'm not sure why we say "huge (large) pages".  The natural term for
> > > Windows is "large-pages",
> > > https://msdn.microsoft.com/en-us/library/windows/desktop/
> > > aa366720(v=vs.85).aspx
> > > so I think we should use that terminology.  Maybe something like
> > >
> > > Add support for <firstterm>large pages</firstterm> on Windows (Takayuki
> > > Tsunakawa, Thomas Munro)
> > > This is controlled by the <link>huge_pages</link> configuration
> parameter.
> >
> > I assume the point here is that we the term huge pages is what's used
> > in PostgreSQL. For example, they are still configured using the
> > huge_pages GUC.
>
> That's exactly what my proposed wording says :-)
>
>
Uh. Nevermind. Nothing to see here. For some reason I only saw the first
paragraph.


-- 
 Magnus Hagander
 Me: https://www.hagander.net/ <http://www.hagander.net/>
 Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

Commits

  1. doc: update PG 11 release notes

  2. Fix misspelled pg_trgm contrib name in PostgreSQL 11 release notes

  3. Doc: clarify release note text about v11's new window function features.

  4. Improve wording of release notes item

  5. Fix typos in release notes

  6. Doc: preliminary list of PG11 major features.

  7. Make numeric power() handle NaNs according to the modern POSIX spec.

  8. Various improvements of skipping index scan during vacuum technics

  9. Revert back-branch changes in power()'s behavior for NaN inputs.

  10. Avoid wrong results for power() with NaN input on more platforms.

  11. Avoid wrong results for power() with NaN input on some platforms.

  12. Skip full index scan during cleanup of B-tree indexes when possible

  13. Rewrite the code that applies scan/join targets to paths.

  14. Postpone generate_gather_paths for topmost scan/join rel.

  15. Add casts from jsonb

  16. Make plpgsql use its DTYPE_REC code paths for composite-type variables.

  17. Don't allow VACUUM VERBOSE ANALYZE VERBOSE.

  18. Pass InitPlan values to workers via Gather (Merge).

  19. Account for the effect of lossy pages when costing bitmap scans.

  20. Allow no-op GiST support functions to be omitted.

  21. Rearm statement_timeout after each executed query.

  22. Push limit through subqueries to underlying sort, where possible.