From: Basil Bourque <basil.bourque@gmail.com>
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: PostgreSQL 12 Press Release - First Draft
In-Reply-To: <7640cf7b-f26a-70ca-bf7b-ef71ddd866bc@postgresql.org>
Date: Wed, 21 Aug 2019 15:37:25 -0700
Cc: PostgreSQL Advocacy <pgsql-advocacy@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CCDB2760-2E0B-4DDC-8F8B-BE726CFAC16D@gmail.com>
References: <c56eeb88-4a8c-2c6c-b5f1-9d46872c247c@postgresql.org>
 <b410b1c8555292daaef9feac7d1ce20d@xs4all.nl>
 <7640cf7b-f26a-70ca-bf7b-ef71ddd866bc@postgresql.org>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Precedence: bulk

=E2=80=94=E2=80=94=E2=80=94

=E2=80=9COSCon=E2=80=9D should be =E2=80=9COSCON=E2=80=9D, all =
uppercase.

Source: https://conferences.oreilly.com/oscon/oscon-or

=E2=80=94=E2=80=94=E2=80=94

I would make two sentences of this:

>PostgreSQL 12 also improves the performance of
adding data to partitioned tables with "INSERT" and "COPY", and a new =
partition
can now be attached to a table without blocking queries.

=E2=80=A6to this:

>PostgreSQL 12 also improves the performance of
adding data to partitioned tables with "INSERT" and =E2=80=9CCOPY=E2=80=9D=
. And a new partition
can now be attached to a table without blocking queries.

=E2=80=94=E2=80=94=E2=80=94

Shorten:

>PostgreSQL 12 introduces the ability to run queries over JSON documents =
using
JSON path expressions defined in the SQL/JSON standard. Additionally, =
certain
JSON path expressions can utilize the existing indexing mechanisms for =
documents
stored in the JSONB format to efficiently retrieve data.

=E2=80=A6to this:

>PostgreSQL 12 introduces the ability to run queries over JSON documents =
using=20
JSON path expressions defined in the SQL/JSON standard. Such queries may =
utilize=20
the existing indexing mechanisms for documents stored in the JSONB =
format to=20
efficiently retrieve data.

=E2=80=94=E2=80=94=E2=80=94

I would mention the SQL standard here (SQL:2003 as I recall). And drop =
the words =E2=80=9Calso=E2=80=9D and =E2=80=9Conly". So this:

>PostgreSQL 12 also introduces generated columns, which is a type of =
column that
can be computed its value from other columns in the same table. =
Currently,
PostgreSQL only supports "stored generated columns," where the computed =
value is
stored on the disk.

=E2=80=A6becomes:

>PostgreSQL 12 introduces "generated columns=E2=80=9D. Defined in the =
SQL standard, this type of column computes its value from the values of =
other columns in the same table. Currently,
PostgreSQL supports "stored generated columns," where the computed value =
is
stored on the disk.

=E2=80=94=E2=80=94=E2=80=94

Your document looks good to me as-is. My only addition would be =
something about Just-In-Time (JIT) compiling and use of LLVM because:

 (a) JIT & LLVM are high-tech items that may catch the attention of =
some. So, good PR.
 (b) The feature provide significant improvements in performance to =
some.

Something like (caveat, I am not an expert here):

>Through the use of LLVM compiler technology, PostgreSQL 12 now enables =
by default the Just-In-Time (JIT) compiling of generated code. =
Longer-running CPU-intensive queries can see significant performance =
improvements.=20


=E2=80=94Basil Bourque