diff --git a/doc/src/sgml/release-16.sgml b/doc/src/sgml/release-16.sgml index a1d9a3344a9..b71e77fa533 100644 --- a/doc/src/sgml/release-16.sgml +++ b/doc/src/sgml/release-16.sgml @@ -49,13 +49,28 @@ -Remove symbolic links for the postmaster binary (Peter Eisentraut) +Change assignment rules for PL/pgSQL bound cursor variables (Tom Lane) + + + +Previously, the string value of such variables was set to match the variable name during cursor assignment; now it will be assigned during OPEN, and will not match the variable name. + + + + + + + +Disallow NULLS NOT DISTINCT indexes for primary keys (Daniel Gustafsson) @@ -92,28 +107,15 @@ Backend support for this authentication method was removed in PostgreSQL 9.1. -Change assignment rules for PL/pgSQL bound cursor variables (Tom Lane) - - - -Previously, the string value of such variables was set to match the variable name during cursor assignment; now it will be assigned during OPEN, and will not match the variable name. - - - - - - - -Disallow NULLS NOT DISTINCT indexes for primary keys (Daniel Gustafsson) +Rename server variable force_parallel_mode to debug_parallel_query (David Rowley) @@ -128,6 +130,21 @@ Remove the ability to create views manually with ON SELECT rules (Tom Lane) + + + + +Remove the server variable vacuum_defer_cleanup_age (Andres Freund) + + + +This has been unnecessary since hot_standby_feedback and replication slots were added. + + + -Rename server variable force_parallel_mode to debug_parallel_query (David Rowley) - - - - - - - -Remove the server variable vacuum_defer_cleanup_age (Andres Freund) - - - -This has been unnecessary since hot_standby_feedback and replication slots were added. +Remove symbolic links for the postmaster binary (Peter Eisentraut) @@ -968,62 +968,6 @@ Allow the SCRAM iteration count to be set with server variable scram_iterations - - - - -Add support for regular expression matching on database and role entries in pg_hba.conf (Bertrand Drouvot) - - - -Regular expression patterns are prefixed with a slash. Database and role names that begin with slashes need to be double-quoted if referenced in pg_hba.conf. - - - - - - - -Improve user-column handling of pg_ident.conf to match pg_hba.conf (Jelte Fennema) - - - -Specifically, add support for "all", role membership with "+", and regular expressions with a leading slash. Any user name that matches these patterns must be double-quoted. - - - - - - - -Allow include files in pg_hba.conf and pg_ident.conf (Julien Rouhaud) - - - -These are controlled by "include", "include_if_exists", and "include_dir". System views pg_hba_file_rules and pg_ident_file_mappings now display the file name. - - - - - - - -Add rule and map numbers to the system view pg_hba_file_rules (Julien Rouhaud) - - - + + + +Add support for regular expression matching on database and role entries in pg_hba.conf (Bertrand Drouvot) + + + +Regular expression patterns are prefixed with a slash. Database and role names that begin with slashes need to be double-quoted if referenced in pg_hba.conf. + + + + + + + +Improve user-column handling of pg_ident.conf to match pg_hba.conf (Jelte Fennema) + + + +Specifically, add support for "all", role membership with "+", and regular expressions with a leading slash. Any user name that matches these patterns must be double-quoted. + + + + + + + +Allow include files in pg_hba.conf and pg_ident.conf (Julien Rouhaud) + + + +These are controlled by "include", "include_if_exists", and "include_dir". System views pg_hba_file_rules and pg_ident_file_mappings now display the file name. + + + + + + + +Add rule and map numbers to the system view pg_hba_file_rules (Julien Rouhaud) + @@ -2766,7 +2775,7 @@ Allow auto_explain to log query parameters used in executing prepared statements This is controlled by auto_explain.log_parameter_max_length, and by default query parameters will be logged with no length restriction. -SHOULD THIS BE MORE CLEARLY IDENTIFIED AS CONTROLLING THE EXECUTION OF PREPARED STATEMENTS. +SHOULD THIS BE MORE CLEARLY IDENTIFIED AS CONTROLLING THE EXECUTION OF PREPARED STATEMENTS? @@ -2841,65 +2850,6 @@ Initialization changes will require modules written for older versions of Postgr - - - - -Add pg_walinspect function pg_get_wal_block() to report WAL block information (Michael Paquier, Melanie Plageman, Bharath Rupireddy) - - - - - - - -Add output fields to pg_walinspect's function pg_get_wal_block_info() (Bharath Rupireddy, Peter Geoghegan) - - - - - - - -Change how pg_walinspect functions pg_get_wal_records_info(), pg_get_wal_stats(), and pg_get_wal_block_info() interpret ending LSNs (Bharath Rupireddy) - - - -Previously ending LSNs which represent nonexistent WAL locations would generate an error, while they will now be interpreted as the end of the WAL. Functions pg_get_wal_records_info_till_end_of_wal() and -pg_get_wal_stats_till_end_of_wal() have been removed. - - - - - - - -Improve descriptions of pg_walinspect items (Melanie Plageman, Peter Geoghegan) - - - + + + +Add pg_walinspect function pg_get_wal_block() to report WAL block information (Michael Paquier, Melanie Plageman, Bharath Rupireddy) + + + + + + + +Add output fields to pg_walinspect's function pg_get_wal_block_info() (Bharath Rupireddy, Peter Geoghegan) + + + + + + + +Change how pg_walinspect functions pg_get_wal_records_info(), pg_get_wal_stats(), and pg_get_wal_block_info() interpret ending LSNs (Bharath Rupireddy) + + + +Previously ending LSNs which represent nonexistent WAL locations would generate an error, while they will now be interpreted as the end of the WAL. Functions pg_get_wal_records_info_till_end_of_wal() and +pg_get_wal_stats_till_end_of_wal() have been removed. + + + + + + + +Improve descriptions of pg_walinspect items (Melanie Plageman, Peter Geoghegan) +