Re: PostgreSQL 12 Press Release - First Draft

=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