diff --git a/doc/src/sgml/release-12.sgml b/doc/src/sgml/release-12.sgml
index 38c45967fcf..0ef385958dd 100644
--- a/doc/src/sgml/release-12.sgml
+++ b/doc/src/sgml/release-12.sgml
@@ -6,7 +6,7 @@
Release date:
- 2019-??-??, CURRENT AS OF 2019-09-06
+ 2019-??-??, CURRENT AS OF 2019-09-21
@@ -136,8 +136,9 @@
- Client- and server-side encryption for authentication using
+ Encryption of TCP/IP connections when using
GSSAPI
+ authentication
@@ -261,8 +262,8 @@ Author: Peter Eisentraut
and the server will not start if that file exists. recovery.signal
and standby.signal files are now used to switch
- into non-primary mode. trigger_file has been
- renamed to . The
+ into non-primary mode. The trigger_file setting
+ has been renamed to . The
standby_mode setting has been removed.
@@ -502,31 +503,6 @@ Author: Peter Geoghegan
-
-
- Allow data type name to use
- non-C collations (Tom Lane, Daniel Vérité)
-
-
-
- Type name still uses the C collation by
- default, rather than defaulting to the database collation.
- Regular-expression operators on name columns will now
- use the C collation by default. If you want non-C
- behavior for locale-dependent regular expression patterns (such
- as \w), attach an
- explicit COLLATE clause.
-
-
-
-
-
@@ -591,6 +567,77 @@ Author: Peter Eisentraut
+
+
+ Mark table columns of type name as having
+ C collation by default (Tom Lane, Daniel Vérité)
+
+
+
+ The comparison operators for data type name can now use
+ any collation, rather than always using C collation.
+ To preserve the previous semantics of queries, columns of
+ type name are now explicitly marked as
+ having C collation. A side effect of this is that
+ regular-expression operators on name columns will now
+ use the C collation by default, not the database
+ collation, to determine the behavior of locale-dependent regular
+ expression patterns (such as \w). If you want
+ non-C behavior for a regular expression on a name
+ column, attach an explicit COLLATE clause. (For
+ user-defined name columns, another possibility is to
+ specify a different collation at table creation time; but that just
+ moves the non-backwards-compatibility to the comparison operators.)
+
+
+
+
+
+
+
+ Treat object-name columns in
+ the information_schema
+ views as being of type name not varchar
+ (Tom Lane)
+
+
+
+ Per the SQL standard, object-name columns in
+ the information_schema views are declared
+ as being of domain type sql_identifier.
+ In PostgreSQL, the underlying catalog
+ columns are really of type name. This change
+ makes sql_identifier be a domain
+ over name, rather than varchar as before.
+ This eliminates a semantic mismatch in comparison and sorting
+ behavior, which can greatly improve the performance of queries
+ on information_schema views that restrict
+ an object-name column. Note however that inequality restrictions,
+ for example
+
+SELECT ... FROM information_schema.tables WHERE table_name < 'foo';
+
+ will now use C-locale comparison semantics by
+ default, rather than the database's default collation as before.
+ Sorting on these columns will also follow C ordering
+ rules. The previous behavior (and inefficiency) can be enforced by
+ adding a COLLATE "default" clause.
+
+
+
+
+
@@ -1453,7 +1500,7 @@ Author: Magnus Hagander
- Global objects have a pg_stat_database.datid
value of zero.
@@ -1605,58 +1652,6 @@ Author: Michael Paquier
-
- <link linkend="information-schema">Information Schema</link>
-
-
-
-
-
-
-
- Allow more use of indexes for text comparisons with
- information_schema columns (Tom Lane)
-
-
-
-
-
-
-
- Use C collation for name-type columns in
- information_schema views and the system
- catalogs (Tom Lane)
-
-
-
- This will produce more consistent behavior in databases with
- different collations, but will also cause sorts on these columns
- to produce results in C ordering, rather
- than the database's default collation.
-
-
-
-
-
-
-
- Ensure that information_schema outputs honor
- the system-defined maximum identifier length (Tom Lane)
-
-
-
-
-
-
@@ -1672,18 +1667,22 @@ Author: Stephen Frost
Add GSSAPI
- client- and server-side encryption support (Robbie Harwood,
- Stephen Frost)
+ encryption support (Robbie Harwood, Stephen Frost)
- Add hostgssenc
+ This feature allows TCP/IP connections to be encrypted when using
+ GSSAPI authentication, without having to set up a separate
+ encryption facility such as SSL.
+ In support of this, add hostgssenc
and hostnogssenc record types in pg_hba.conf.
- Such entries would typically use the gss
- authentication method. This change also adds a libpq
- option, and a
- system view.
+ linkend="auth-pg-hba-conf">pg_hba.conf
+ for selecting connections that do or do not use GSSAPI encryption,
+ corresponding to the existing hostssl
+ and hostnossl record types.
+ There is also a new
+ libpq option, and a system
+ view.
@@ -2080,9 +2079,9 @@ Author: Tomas Vondra
-->
- Add a WHERE clause to COPY
- FROM to control which rows are accepted (Surafel
- Temesgen)
+ Add a WHERE clause
+ to COPY FROM to
+ control which rows are accepted (Surafel Temesgen)
@@ -2097,16 +2096,17 @@ Author: Thomas Munro
-->
- Allow enumerated values to be added in more transaction types
+ Allow enumerated values to be added more flexibly
(Andrew Dunstan, Tom Lane, Thomas Munro)
- Previously, ALTER
- TYPE ... ADD VALUE could only be called in
- a transaction that created the enumerated type. Now, the only
- restriction is that the new enumerated value cannot be referenced
- until the transaction commits.
+ Previously, ALTER TYPE
+ ... ADD VALUE could not be called in a transaction
+ block, unless it was part of the same transaction that created the
+ enumerated type. Now it can be called in a later transaction, so
+ long as the new enumerated value is not referenced until after it is
+ committed.
@@ -2123,7 +2123,9 @@ Author: Peter Eisentraut
The commands are COMMIT AND
- CHAIN and ROLLBACK AND CHAIN.
+ CHAIN
+ and ROLLBACK AND
+ CHAIN.
@@ -2144,8 +2146,8 @@ Author: Fujii Masao
These options are vacuum_truncate and
toast.vacuum_truncate. Use of these options
- reduces vacuum's locking requirements, but prevents returning disk
- space to the operating system.
+ reduces VACUUM's locking requirements, but
+ prevents returning disk space to the operating system.
@@ -2180,7 +2182,7 @@ Author: Michael Paquier
Add the ability to skip VACUUM and
ANALYZE operations on tables that cannot be
- immediately locked (Nathan Bossart)
+ locked immediately (Nathan Bossart)
@@ -2233,8 +2235,8 @@ Author: Tomas Vondra
- This output can also be obtained in auto-explain via .log_settings.
+ This output can also be obtained in
+ by setting auto_explain.log_settings.
@@ -2263,8 +2265,8 @@ Author: Peter Eisentraut
- This allows modifications of reloptions and
- autovacuum settings.
+ Modifications of catalogs' reloptions and
+ autovacuum settings are now supported.
@@ -2280,8 +2282,8 @@ Author: Peter Eisentraut
- Previously, only the first column name was used, resulting in
- ambiguity for multi-column foreign keys.
+ Previously, only the first column name was included in the constraint
+ name, resulting in ambiguity for multi-column foreign keys.
@@ -2340,7 +2342,7 @@ Author: Peter Eisentraut
Allow creation of collations that report
- string equality for strings that are not byte-wise equal (Peter
+ string equality for strings that are not bit-wise equal (Peter
Eisentraut)
@@ -2685,24 +2687,6 @@ Author: Michael Meskes
-
-
- Add DECLARE STATEMENT support to
- ECPG (Takeshi Ideriha, Hayato Kuroda)
-
-
-
- This allows statements to be associated with named connections,
- so future operations like cursors don't need to re-reference the
- connection name.
-
-
-
-
-
@@ -2810,7 +2794,7 @@ Author: Peter Eisentraut
Show the manual page URL in
psql's \help output
- (Peter Eisentraut)
+ for a SQL command (Peter Eisentraut)
@@ -2945,13 +2929,14 @@ Author: Heikki Linnakangas
-->
- Properly detach the server on pg_ctl
- start (Paul Guo)
+ Properly detach the new server process
+ during pg_ctl start
+ (Paul Guo)
- This prevents later shell activity from interfering with the
- postmaster.
+ This prevents the server from being shut down if the shell script
+ that invoked pg_ctl is interrupted later.
@@ -3394,7 +3379,7 @@ Author: Jeff Davis
While CHECK OPTIONs on
postgres_fdw tables are ignored (because
the reference is foreign), views on such tables are considered
- local, so this release enforces CHECK OPTIONs
+ local, so this change enforces CHECK OPTIONs
on them. Previously, only INSERTs and
UPDATEs with RETURNING
clauses that returned CHECK OPTION values