Re: Postgres 11 release notes - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Postgres 11 release notes
Date
Msg-id CAKFQuwbZ42Sf1a1ORYnrOF5j4t48jhBwVBO9q=8PXo5v8qzC_A@mail.gmail.com
Whole thread Raw
In response to Postgres 11 release notes  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Postgres 11 release notes
Re: Postgres 11 release notes
List pgsql-hackers
On Fri, May 11, 2018 at 8:08 AM, 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

​Some thoughts:​

​As a major ​item:
""""
JIT compilation of some SQL code, including support for fast evaluation of expressions
""""

leaves me wondering what the general benefit is to the user.  Also, spelling out "Just-In-Time (JIT)" here seems warranted.


"""
No longer retain WAL that spans two checkpoints (Simon Riggs)

The retention of WAL records for only one checkpoint is required.
"""

Maybe: "Servers now only ensure that a single checkpoint record is present in the locally retained WAL.  Previously it would ensure at least two checkpoints were available for recovery."


"""
Also, if any table mentioned in VACUUM uses a column list, then ANALYZE keyword must be supplied; previously ANALYZE was implied in such cases.
"""

Should that be mentioned in the compatibility notes?


"""
Add the ability to define PL/pgSQL record types as not null, constant, or with initial values (Tom Lane)
"""

Found the commit message for this one - should we back-patch a documentation change indicating that this doesn't work prior to v11?

David J.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: why partition pruning doesn't work?
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: Postgres 11 release notes