From ddd78136764133b72bfe9102e60bbd49fa22b414 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Tue, 15 Dec 2015 16:42:18 -0500 Subject: [PATCH] Update 9.5 release notes through today. Also do another round of copy-editing, and fix up remaining FIXME items. --- doc/src/sgml/release-9.5.sgml | 333 ++++++++++++++++++++++------------ 1 file changed, 214 insertions(+), 119 deletions(-) diff --git a/doc/src/sgml/release-9.5.sgml b/doc/src/sgml/release-9.5.sgml index 110ba40c4df..7690a90c509 100644 --- a/doc/src/sgml/release-9.5.sgml +++ b/doc/src/sgml/release-9.5.sgml @@ -6,8 +6,8 @@ Release Date - 2015-??-?? - Current as of 2015-11-07 + 2016-??-?? + Current as of 2015-12-15 @@ -23,7 +23,7 @@ - Allow INSERTS + Allow INSERTs that would generate constraint conflicts to be turned into UPDATEs or ignored @@ -31,7 +31,7 @@ - Add GROUP BY analysis functions GROUP BY analysis features GROUPING SETS, CUBE and ROLLUP @@ -181,9 +181,9 @@ 2015-05-08 [9a08841] Stephe..: Change default for include_realm to 1 --> - Change the default value of include_realm to 1, so that - by default the realm is not removed from a GSS + Change the default value of the GSSAPI include_realm parameter to 1, so + that by default the realm is not removed from a GSS or SSPI principal name (Stephen Frost) @@ -201,18 +201,26 @@ + - The configuration parameter checkpoint_segments has - been removed. Its place is taken by the new - setting . If you had previously - tuned checkpoint_segments, the following formula will - give you an approximately equivalent setting: + Replace configuration parameter checkpoint_segments + with + and (Heikki Linnakangas) + + + + If you previously adjusted checkpoint_segments, the + following formula will give you an approximately equivalent setting: max_wal_size = (3 * checkpoint_segments) * 16MB Note that the default setting for max_wal_size is much higher than the default checkpoint_segments used - to be, so setting this might no longer be necessary. + to be, so adjusting it might no longer be necessary. @@ -222,7 +230,7 @@ max_wal_size = (3 * checkpoint_segments) * 16MB 2015-07-28 [6087d95] Andres..: Remove ssl renegotiation support. --> - Disable server configuration + Decommission server configuration parameter ssl_renegotiation_limit, which was deprecated in earlier releases (Andres Freund) @@ -253,8 +261,21 @@ max_wal_size = (3 * checkpoint_segments) * 16MB 2015-03-06 [bb8582a] Peter ..: Remove rolcatupdate --> - Remove pg_authid's - rolcatupdate field, as it had no value (Adam Brightwell) + Remove the pg_authid + catalog's rolcatupdate field, as it had no usefulness + (Adam Brightwell) + + + + + + + The pg_stat_replication + system view's sent field is now NULL, not zero, when + it has no valid value (Magnus Hagander) @@ -264,9 +285,13 @@ max_wal_size = (3 * checkpoint_segments) * 16MB --> Allow json and jsonb array extraction operators to - accept negative subscripts, which count from the end of JSON arrays. + accept negative subscripts, which count from the end of JSON arrays + (Peter Geoghegan, Andrew Dunstan) + + + Previously, these operators returned NULL for negative - subscripts. (Peter Geoghegan, Andrew Dunstan) + subscripts. @@ -322,10 +347,10 @@ max_wal_size = (3 * checkpoint_segments) * 16MB - Previously, a common table expression was required to return a - large number of rows ordered by bounding-box distance, and the - result then had to be filtered further with a more accurate - non-bounding-box distance calculation. + Previously, to exploit such an index a subquery had to be used to + select a large number of rows ordered by bounding-box distance, and + the result then had to be filtered further with a more accurate + distance calculation. @@ -352,9 +377,11 @@ Add GUC and storage parameter to set the maximum size of GIN pending list. - Previously the list size was controlled - by . This can also be set as an index - storage parameter. + This value can also be set on a per-index basis as an index storage + parameter. Previously the pending-list size was controlled + by , which was awkward because + appropriate values for work_mem are often much too large + for this purpose. @@ -701,7 +728,6 @@ Add GUC and storage parameter to set the maximum size of GIN pending list. 2015-02-23 [88e9823] Heikki..: Replace checkpoint_segments with min_wal_size a.. 2015-03-15 [a0f5954] Andres..: Increase max_wal_size's default from 128MB to 1.. 2015-06-29 [d661532] Heikki..: Also trigger restartpoints based on max_wal_siz.. -FIXME: Add docs about restartpoint behaviour change --> Replace configuration parameter checkpoint_segments @@ -710,10 +736,14 @@ FIXME: Add docs about restartpoint behaviour change - This allows the allocation of a large number of WAL files - without keeping them if they are not needed. Thus the default - for has been increased - to 1GB. + This change allows the allocation of a large number of WAL + files without keeping them after they are no longer needed. + Therefore the default for max_wal_size has been set + to 1GB, much larger than the old default + for checkpoint_segments. + Also note that standby servers perform restartpoints to try to limit + their WAL space consumption to max_wal_size; previously + they did not pay any attention to checkpoint_segments. @@ -750,8 +780,9 @@ FIXME: Add docs about restartpoint behaviour change 2015-04-03 [a75fb9b] Alvaro..: Have autovacuum workers listen to SIGHUP, too --> - Allow running autovacuum workers - to respond to configuration parameter changes (Michael Paquier) + Allow autovacuum workers + to respond to configuration parameter changes during a run + (Michael Paquier) @@ -993,7 +1024,7 @@ FIXME: Add docs about restartpoint behaviour change --> Allow recovery.conf's primary_conninfo to + linkend="primary-conninfo">primary_conninfo setting to use connection URIs, e.g. postgres:// (Alexander Shulgin) @@ -1014,7 +1045,7 @@ FIXME: Add docs about restartpoint behaviour change 2015-05-08 [2c8f483] Andres..: Represent columns requiring insert and update p.. --> - Allow INSERTS + Allow INSERTs that would generate constraint conflicts to be turned into UPDATEs or ignored (Peter Geoghegan, Heikki Linnakangas, Andres Freund) @@ -1032,7 +1063,7 @@ FIXME: Add docs about restartpoint behaviour change 2015-05-16 [f3d3118] Andres..: Support GROUPING SETS, CUBE and ROLLUP. --> - Add GROUP BY analysis functions GROUP BY analysis features GROUPING SETS, CUBE and ROLLUP @@ -1205,8 +1236,9 @@ FIXME: Add docs about restartpoint behaviour change - This controls viewing and adding/modifying rows via new commands - CREATE/CREATE/ALTER/DROP POLICY and ALTER TABLE ... ENABLE/DISABLE @@ -1221,7 +1253,7 @@ FIXME: Add docs about restartpoint behaviour change Allow changing of the WAL logging status of a table after creation with ALTER TABLE .. SET LOGGED / + linkend="SQL-ALTERTABLE">ALTER TABLE ... SET LOGGED / UNLOGGED (Fabrízio de Royes Mello) @@ -1277,7 +1309,7 @@ FIXME: Add docs about restartpoint behaviour change 2015-06-21 [ad89a5d] Alvaro..: Add transforms to pg_get_object_address and fr.. --> - Allow comments on domain + Support comments on domain constraints (Álvaro Herrera) @@ -1297,14 +1329,14 @@ FIXME: Add docs about restartpoint behaviour change 2015-05-11 [fa26424] Stephe..: Allow LOCK TABLE .. ROW EXCLUSIVE MODE with IN.. --> - Allow LOCK TABLE .. ROW EXCLUSIVE + Allow LOCK TABLE ... ROW EXCLUSIVE MODE for those with INSERT privileges (Stephen Frost) - Previously this required UPDATE, DELETE, or - TRUNCATE privileges. + Previously this command required UPDATE, DELETE, + or TRUNCATE privileges. @@ -1336,10 +1368,10 @@ FIXME: Add docs about restartpoint behaviour change - This allows these database settings to be - changed more easily than modifying the pg_database - system table. + system catalog. @@ -1368,21 +1400,6 @@ FIXME: Add docs about restartpoint behaviour change - - Allow foreign tables to participate in inheritance (Shigeru Hanada, - Etsuro Fujita) - - - - This also allows foreign tables to mark check constraints as not - valid, and to set storage and OID characteristics. - - - - - @@ -1391,7 +1408,7 @@ FIXME: Add docs about restartpoint behaviour change - These constraints are assumed to be enforced on the remote server, + Such constraints are assumed to be enforced on the remote server, and are not enforced locally. However, they are assumed to hold for purposes of query optimization, such as constraint @@ -1401,6 +1418,23 @@ FIXME: Add docs about restartpoint behaviour change + + Allow foreign tables to participate in inheritance (Shigeru Hanada, + Etsuro Fujita) + + + + To let this work naturally, foreign tables are now allowed to have + check constraints marked as not valid, and to set storage + and OID characteristics, even though these operations are + effectively no-ops for a foreign table. + + + + + @@ -1422,12 +1456,18 @@ FIXME: Add docs about restartpoint behaviour change - Add a set-returning function pg_event_trigger_ddl_commands(), which returns DDL activity - associated with event triggers (Álvaro Herrera) + Whenever a ddl_command_end event trigger is installed, + capture details of DDL activity for it to inspect + (Álvaro Herrera) + + + + This information is available through a set-returning function pg_event_trigger_ddl_commands(), + or by inspection of C data structures if that function doesn't + provide enough detail. @@ -1488,7 +1528,7 @@ FIXME: Better description? --> Allow the xml data type - to accept empty or all-whitespace values (Peter Eisentraut) + to accept empty or all-whitespace content values (Peter Eisentraut) @@ -1510,17 +1550,19 @@ FIXME: Better description? - Tighten syntax of interval precision - specifications (Bruce Momjian) + Disallow non-SQL-standard syntax for interval with + both precision and field specifications (Bruce Momjian) - Only allow interval precision to be specified after the - INTERVAL keyword if no units are specified. + Per the standard, such type specifications should be written as, + for example, INTERVAL MINUTE TO SECOND(2). + PostgreSQL formerly allowed this to be written as + INTERVAL(2) MINUTE TO SECOND, but it must now be + written in the standard way. @@ -1545,8 +1587,8 @@ FIXME: Add more specifics? Add data types regrole and regnamespace - that simplify pretty-printing the OID of a role or - namespace (Kyotaro Horiguchi) + that simplify entering and pretty-printing the OID of a role + or namespace (Kyotaro Horiguchi) @@ -1563,7 +1605,7 @@ FIXME: Add more specifics? 2015-05-31 [37def42] Andrew..: Rename jsonb_replace to jsonb_set and allow it .. --> - Add JSONB functions jsonb functions jsonb_set() and jsonb_pretty() @@ -1576,12 +1618,7 @@ FIXME: Add more specifics? 2014-12-12 [7e354ab] Andrew..: Add several generator functions for jsonb that .. --> - Add several generator functions for jsonb that already - existed for json (Andrew Dunstan) - - - - These are jsonb generator functions to_jsonb(), jsonb_object(), @@ -1592,7 +1629,12 @@ FIXME: Add more specifics? jsonb_agg(), and jsonb_object_agg(). + linkend="functions-aggregate-table">jsonb_object_agg() + (Andrew Dunstan) + + + + Equivalent functions already existed for type json. @@ -1638,7 +1680,7 @@ FIXME: Add more specifics? linkend="functions-json-processing-table">json_strip_nulls() and jsonb_strip_nulls() - functions to remove json null values from documents + functions to remove JSON null values from documents (Andrew Dunstan) @@ -1694,7 +1736,7 @@ FIXME: Add more specifics? 2014-12-15 [4520ba6] Heikki..: Add point <-> polygon distance operator. --> - Add point-to-polygon distance operator (<->) (Alexander Korotkov) @@ -1705,7 +1747,7 @@ FIXME: Add more specifics? 2014-08-27 [8167a38] Jeff D..: Allow multibyte characters as escape in SIMILA.. --> - Allow multibyte characters as escape in SIMILAR TO and SUBSTRING (Jeff Davis) @@ -1804,8 +1846,8 @@ FIXME: Add more specifics? - Now, role membership is sufficient; previously only the same - role could perform these operations. + Previously, only the specific role owning the target session could + perform these operations; now membership in that role is sufficient. @@ -1951,7 +1993,7 @@ FIXME: Add more specifics? 2015-03-25 [a4847fc] Tom Lane: Add an ASSERT statement in plpgsql. --> - Add ASSERT + Add an ASSERT statement in PL/pgSQL (Pavel Stehule) @@ -2054,6 +2096,17 @@ FIXME: Add more specifics? + + In vacuumdb, do not + prompt for the same password repeatedly when multiple connections + are necessary (Haribabu Kommi, Michael Paquier) + + + + + @@ -2107,13 +2160,13 @@ FIXME: Add more specifics? 2014-07-10 [5b214c5] Fujii ..: Add new ECHO mode 'errors' that displays only .. --> - Add errors mode to psql's - ECHO variable to display only failed commands + Add an errors mode that displays only failed commands + to psql's ECHO variable (Pavel Stehule) - This can also be enabled with the psql + This behavior can also be selected with psql's @@ -2168,6 +2221,22 @@ FIXME: Add more specifics? + + psql now fails if the file specified by + an + + + Previously, it effectively ignored the switch in such cases. + + + + + @@ -2207,10 +2276,12 @@ FIXME: Add more specifics? - variables shows psql's special variables - and options shows command-line options. - \? commands is the default output. This help - information can also be output via --help=section. + \? variables shows psql's special + variables and \? options shows the command-line options. + \? commands shows the meta-commands, which is the + traditional output and remains the default. These help displays + can also be obtained with the command-line + option --help=section. @@ -2245,7 +2316,7 @@ FIXME: Add more specifics? Also prevent @@ -2254,8 +2325,8 @@ FIXME: Add more specifics? 2014-11-22 [eca2b9b] Andrew..: Rework echo_hidden for \sf and \ef from commit .. --> - Allow psql's \sf and \ef - to honor ECHO_HIDDEN (Andrew Dunstan) + Make psql's \sf and \ef + commands honor ECHO_HIDDEN (Andrew Dunstan) @@ -2310,10 +2381,26 @@ FIXME: Add more specifics? + + Support table sizes exceeding 8GB in tar archive format (Tom Lane) + + + + The POSIX standard for tar format does not allow elements of a tar + archive to exceed 8GB, but most modern implementations of tar + support an extension that does allow it. Use the extension format + when necessary, rather than failing. + + + + + - Always have pg_dump print server and + Make pg_dump always print the server and pg_dump versions (Jing Wang) @@ -2348,8 +2435,8 @@ FIXME: Add more specifics? 2014-08-25 [ebe30ad] Bruce ..: pg_ctl, pg_upgrade: allow multiple -o/-O opti.. --> - Allow multiple pg_ctl @@ -2368,6 +2455,23 @@ FIXME: Add more specifics? + + + + If the server's listen address is set to a wildcard value + (0.0.0.0 in IPv4 or :: in IPv6), connect via + the loopback address rather than trying to use the wildcard address + literally (Kondo Yuta) + + + + This fix primarily affects Windows, since on other platforms + pg_ctl will prefer to use a Unix-domain socket. + + + @@ -2398,8 +2502,9 @@ FIXME: Add more specifics? 2014-08-25 [ebe30ad] Bruce ..: pg_ctl, pg_upgrade: allow multiple -o/-O optio.. --> - Allow multiple pg_upgrade - @@ -2415,17 +2520,6 @@ FIXME: Add more specifics? - - Document the use of rsync for standby server - upgrades using pg_upgrade (Stephen Frost, - Bruce Momjian) - - - - - @@ -2480,7 +2574,7 @@ FIXME: Add more specifics? - This is controlled by new @@ -2497,11 +2591,12 @@ FIXME: Add more specifics? Allow pgbench's \set command to handle - multi-operator expressions (Robert Haas, Fabien Coelho) + arithmetic expressions containing more than one operator, and add + % (modulo) to the set of operators it supports + (Robert Haas, Fabien Coelho) @@ -2698,8 +2793,8 @@ FIXME: Improve description, link --> Allow higher-precision time stamp resolution on Windows 8 or Windows - Server 2012 and later Windows systems (Craig Ringer) + class="osname">Windows 8, Windows + Server 2012, and later Windows systems (Craig Ringer)