diff --git a/doc/src/sgml/release-10.sgml b/doc/src/sgml/release-10.sgml
index f7744b344d6..3ea33ca58b0 100644
--- a/doc/src/sgml/release-10.sgml
+++ b/doc/src/sgml/release-10.sgml
@@ -47,292 +47,306 @@
-
-
-
-pg_upgrade>-ed hash indexes from previous major Postgres versions must be rebuilt.
-
+
+
+
+ pg_upgrade>-ed hash indexes from previous major
+ Postgres versions must be rebuilt.
+
-
-Major hash storage improvements necessitated this requirement.
-
-
+
+ Major hash storage improvements necessitated this requirement.
+
+
-
-
-
-Change the default log directory> from pg_log> to log> (Andreas
-Karlsson)
-
-
+
+
+
+ Change the default log
+ directory> from pg_log> to log> (Andreas
+ Karlsson)
+
+
-
-
-
-Rename pg_xlog> to pg_wal>> (Michael Paquier)
-
+
+
+
+ Rename pg_xlog> to pg_wal>> (Michael Paquier)
+
-
-This prevents the write-ahead log directory from being confused as
-containing server activity logs, and erroneously truncated.
-
-
+
+ This prevents the write-ahead log directory from being confused as
+ containing server activity logs, and erroneously truncated.
+
+
-
-
-
-Rename SQL> functions, tools, and options that reference xlog> to wal>
-(Robert Haas)
-
+
+
+
+ Rename SQL> functions, tools, and options that reference
+ xlog> to wal> (Robert Haas)
+
-
-For example, pg_switch_xlog()> becomes pg_switch_wal()>, pg_receivexlog>
-becomes pg_receivewal>, and
-
+
+ For example, pg_switch_xlog()> becomes
+ pg_switch_wal()>, pg_receivexlog>
+ becomes pg_receivewal>, and
+
-
-
-
-Rename transaction status directory pg_clog> directory to pg_xact>
-(Michael Paquier)
-
-
+
+
+
+ Rename transaction status directory pg_clog> directory
+ to pg_xact> (Michael Paquier)
+
+
-
-
-
-Allow COALESCE> and CASE> to return multiple rows when evaluating
-set-returning functions (Andres Freund).
-
+
+
+
+ Allow COALESCE> and CASE> to return multiple
+ rows when evaluating set-returning functions (Andres Freund).
+
-
-This also prevents conditionals like CASE> from controlling the
-execution of set-returning functions because set-returning functions
-are now executed earlier.
-
-
+
+ This also prevents conditionals like CASE> from
+ controlling the execution of set-returning functions because
+ set-returning functions are now executed earlier.
+
+
-
-
-
-Have > stream the WAL> needed to restore the backup by
-default (Magnus Hagander)
-
+
+
+
+ Have > stream the
+ WAL> needed to restore the backup by default (Magnus
+ Hagander)
+
-
-This changes the pg_basebackup>
-
+
+ This changes the pg_basebackup>
+
-X>/
--xlog-method> default to stream>.
+ An option value none> has been added to recreate the old
+ behavior. The pg_basebackup> option
-x>
+ has been removed (use
-X> fetch).
+
+
-
-
-
-Make all > actions wait by default for completion (Peter Eisentraut)
-
+
+
+
+ Make all > actions wait
+ by default for completion (Peter Eisentraut)
+
-
-Previously some pg_ctl> actions didn't wait for completion, and required
-the use of
-w> to do so.
-
-
+
+ Previously some pg_ctl> actions didn't wait for
+ completion, and required the use of
-w> to do so.
+
+
-
-
-
-Allow multi-dimensional arrays to be passed into PL/Python functions,
-and returned as nested Python lists (Alexey Grishchenko, Dave Cramer,
-Heikki Linnakangas)
-
+
+
+
+ Allow multi-dimensional arrays to be passed into PL/Python functions,
+ and returned as nested Python lists (Alexey Grishchenko, Dave Cramer,
+ Heikki Linnakangas)
+
-
-This makes a backwards-incompatible change to the handling of composite
-types in arrays. Previously, you could return an array of composite types
-as "[[col1, col2], [col1, col2]]", but now that is interpreted as a two-
-dimensional array. Composite types in arrays must now be returned as
-Python tuples, not lists, to resolve the ambiguity. I.e. "[(col1, col2),
-(col1, col2)]". See the documentation for more details. CLARIFY
-
-
+
+ This makes a backwards-incompatible change to the handling of
+ composite types in arrays. Previously, you could return an array of
+ composite types as "[[col1, col2], [col1, col2]]", but now that is
+ interpreted as a two- dimensional array. Composite types in arrays
+ must now be returned as Python tuples, not lists, to resolve the
+ ambiguity. I.e. "[(col1, col2), (col1, col2)]". See the documentation
+ for more details. CLARIFY
+
+
-
-
-
-Remove PL/Tcl's "module" auto-loading facility (Tom Lane)
-
+
+
+
+ Remove PL/Tcl's "module" auto-loading facility (Tom Lane)
+
-
-Replaced by new PL/Tcl startup GUC>s.
-
-
+
+ Replaced by new PL/Tcl startup GUC>s.
+
+
-
-
-
-Remove sql_inheritance> GUC> (Robert Haas)
-
+
+
+
+ Remove sql_inheritance> GUC> (Robert Haas)
+
-
-Changing this from the default value caused queries referencing parent
-tables to not include children tables. The SQL> standard requires such
-behavior and this has been the default since Postgres 7.1.
-
-
+
+ Changing this from the default value caused queries referencing
+ parent tables to not include children tables. The SQL>
+ standard requires such behavior and this has been the default since
+ Postgres 7.1.
+
+
-
-
-
-Add GUC>s and
-
-to control parallel operation (Amit Kapila, Robert Haas)
-
+
+
+
+ Add GUC>s
+ and to control
+ parallel operation (Amit Kapila, Robert Haas)
+
-
-This replaces min_parallel_relation_size>, which was too generic.
-
-
+
+ This replaces min_parallel_relation_size>, which was
+ too generic.
+
+
-
-
-
-Remove pg_dump>/pg_dumpall> support for dumping from pre-8.0 servers (Tom
-Lane)
-
+
+
+
+ Remove pg_dump>/pg_dumpall> support
+ for dumping from pre-8.0 servers (Tom Lane)
+
-
-Users needing dump support for pre-8.0 servers need to use dump binaries
-from Postgres 9.6.
-
-
+
+ Users needing dump support for pre-8.0 servers need to use dump
+ binaries from Postgres 9.6.
+
+
-
-
-
-Remove support for floating-point datetimes/timestamps (Tom Lane)
-
+
+
+
+ Remove support for floating-point datetimes/timestamps (Tom Lane)
+
-
-This removes configure's
--disable-integer-datetimes> option.
-Floating-point datetimes/timestamps have not been the default
-since Postgres 8.3 and have few advantages.
-
-
+
+ This removes configure's
--disable-integer-datetimes>
+ option. Floating-point datetimes/timestamps have not been the
+ default since Postgres 8.3 and have few advantages.
+
+
-
-
-
-Remove support for client/server protocol version 1.0 (Tom Lane)
-
+
+
+
+ Remove support for client/server protocol version 1.0 (Tom Lane)
+
-
-This protocol hasn't had client support since Postgres 6.3.
-
-
+
+ This protocol hasn't had client support since Postgres 6.3.
+
+
-
-
-
-Remove contrib/tsearch2 (Robert Haas)
-
+
+
+
+ Remove contrib/tsearch2 (Robert Haas)
+
-
-This removes compatibility with the contrib version of full text search
-that shipped in pre-8.3 Postgres versions.
-
-
+
+ This removes compatibility with the contrib version of full text
+ search that shipped in pre-8.3 Postgres versions.
+
+
-
-
-
-Remove createlang and droplang command-line applications (Peter Eisentraut)
-
-
+
+
+
+ Remove createlang and droplang command-line applications (Peter
+ Eisentraut)
+
+
-
-
-
-Remove support for version-0 function calling conventions (Andres
-Freund)
-
-
+
+
+
+ Remove support for version-0 function calling conventions (Andres
+ Freund)
+
+
-
-
-
-Remove SCO> and Unixware> ports (Tom Lane)
-
-
+
+
+
+ Remove SCO> and Unixware> ports (Tom Lane)
+
+
@@ -343,7 +357,7 @@ Remove SCO> and Unixware
Below you will find a detailed account of the changes between
- PostgreSQL 10 and the previous major
+ PostgreSQL 10 and the previous major
release.
@@ -355,91 +369,94 @@ Remove SCO> and Unixware
-
-
-
-Support parallel btree index scans (Rahila Syed, Amit Kapila, Robert
-Haas)
-
+
+
+
+ Support parallel btree index scans (Rahila Syed, Amit Kapila,
+ Robert Haas)
+
-
-Allows btree index pages to be checked by separate parallel workers.
-
-
+
+ Allows btree index pages to be checked by separate parallel
+ workers.
+
+
-
-
-
-Support parallel bitmap heap scans (Dilip Kumar)
-
+
+
+
+ Support parallel bitmap heap scans (Dilip Kumar)
+
-
-This allows a single index scan to dispatch parallel workers to process
-different areas of the heap.
-
-
+
+ This allows a single index scan to dispatch parallel workers to
+ process different areas of the heap.
+
+
-
-
-
-Allow merge joins to be performed in parallel (Dilip Kumar)
-
-
+
+
+
+ Allow merge joins to be performed in parallel (Dilip Kumar)
+
+
-
-
-
-Improve ability of parallel workers to return pre-sorted data (Rushabh
-Lathia)
-
-
+
+
+
+ Improve ability of parallel workers to return pre-sorted data
+ (Rushabh Lathia)
+
+
-
-
-
-Increase parallel query usage in procedural language functions (Robert
-Haas, Rafia Sabih)
-
-
+
+
+
+ Increase parallel query usage in procedural language functions
+ (Robert Haas, Rafia Sabih)
+
+
-
-
-
-Add GUC> to limit the number of worker processes
-that can be used for parallelism (Julien Rouhaud)
-
+
+
+
+ Add GUC>
+ to limit the number of worker processes that can be used for
+ parallelism (Julien Rouhaud)
+
-
-This can be set lower than to reserve worker
-processes for non-parallel purposes.
-
-
+
+ This can be set lower than to reserve worker processes
+ for non-parallel purposes.
+
+
@@ -450,201 +467,209 @@ processes for non-parallel purposes.
-
-
-
-Add full text search support for JSON> and JSONB> (Dmitry Dolgov)
-
+
+
+
+ Add full text search support for JSON> and JSONB>
+ (Dmitry Dolgov)
+
-
-This is accessed via ts_headline()> and to_tsvector>. RIGHT SECTION?
-
-
+
+ This is accessed via ts_headline()> and
+ to_tsvector>. RIGHT SECTION?
+
+
-
-
-
-Add SP-GiST> index support for INET> and CIDR> data types (Emre Hasegeli)
-
+
+
+
+ Add SP-GiST> index support for INET> and
+ CIDR> data types (Emre Hasegeli)
+
-
-These data types already had GiST support.
-
-
+
+ These data types already had GiST support.
+
+
-
-
-
-Reduce page locking during vacuuming of GIN> indexes (Andrey Borodin)
-
-
+
+
+
+ Reduce page locking during vacuuming of GIN> indexes
+ (Andrey Borodin)
+
+
-
-
-
-Cause BRIN> index summarization to happen more aggressively (Álvaro
-Herrera)
-
+
+
+
+ Cause BRIN> index summarization to happen more
+ aggressively (Álvaro Herrera)
+
-
-Specifically, summarize the previous page range when a new page range is
-created.
-
-
+
+ Specifically, summarize the previous page range when a new page
+ range is created.
+
+
-
-
-
-Add function brin_desummarize_range()> to remove BRIN> summarization of a
-specified range (Álvaro Herrera)
-
+
+
+
+ Add function brin_desummarize_range()> to remove
+ BRIN> summarization of a specified range (Álvaro
+ Herrera)
+
-
-This allows future BRIN> index summarization to be more compact. CLARIFY
-
-
+
+ This allows future BRIN> index summarization to be
+ more compact. CLARIFY
+
+
-
-
- Hash Indexes
-
-
-
-
-
-
-Add write-ahead logging support to hash indexes (Amit Kapila)
-
-
-
-This makes hash indexes crash-safe and replicated, and removes the
-warning message about their use.
-
-
-
-
-
-
-Improve hash bucket split performance by reducing locking requirements
-(Amit Kapila, Mithun Cy)
-
-
-
-Also cache hash index meta-information for faster lookups.
-
-
-
-
-
-
-Improve efficiency of hash index growth (Amit Kapila, Mithun Cy)
-
-
-
-
-
-
-Allow single-page hash pruning (Ashutosh Sharma)
-
-
-
-
-
-
-
-
-
-
-
- Locking
+
+
+ Hash Indexes
-
-
-
-Only check for REFERENCES> permission on referenced tables (Tom Lane)
-
+
+
+
+ Add write-ahead logging support to hash indexes (Amit Kapila)
+
-
-Previously REFERENCES> permission on the referencing table was also
-required.
-
-
+
+ This makes hash indexes crash-safe and replicated, and removes
+ the warning message about their use.
+
+
-
-
-
-Reduce locking required for adding values to enum types (Andrew Dunstan,
-Tom Lane)
-
+
+
+
+ Improve hash bucket split performance by reducing locking
+ requirements (Amit Kapila, Mithun Cy)
+
-
-Previously it was impossible to run ALTER TYPE ... ADD VALUE> in a
-transaction block unless the enum type was created in the same block.
-Now, only references to uncommitted enum values from other transactions
-is prohibited.
-
-
+
+ Also cache hash index meta-information for faster lookups.
+
+
-
-
-
-Allow tuning of predicate lock promotion thresholds (Dagfinn Ilmari
-Mannsåker)
-
+
+
+
+ Improve efficiency of hash index growth (Amit Kapila, Mithun Cy)
+
+
-
-The new settings are and
-max_pred_locks_per_page>.
-
-
+
+
+
+ Allow single-page hash pruning (Ashutosh Sharma)
+
+
-
+
+
+
+
+
+
+
+
+ Locking
+
+
+
+
+
+
+ Only check for REFERENCES> permission on referenced
+ tables (Tom Lane)
+
+
+
+ Previously REFERENCES> permission on the referencing
+ table was also required.
+
+
+
+
+
+
+ Reduce locking required for adding values to enum types (Andrew
+ Dunstan, Tom Lane)
+
+
+
+ Previously it was impossible to run ALTER TYPE ... ADD
+ VALUE> in a transaction block unless the enum type was created
+ in the same block. Now, only references to uncommitted enum
+ values from other transactions is prohibited.
+
+
+
+
+
+
+ Allow tuning of predicate lock promotion thresholds (Dagfinn
+ Ilmari Mannsåker)
+
+
+
+ The new settings are and
+ max_pred_locks_per_page>.
+
+
+
+
@@ -653,129 +678,134 @@ The new settings are and
-
-
-
-Add the ability to compute a correlation ratio and the number of
-distinct values on several columns (Tomas Vondra, David Rowley)
-
+
+
+
+ Add the ability to compute a correlation ratio and the number of
+ distinct values on several columns (Tomas Vondra, David Rowley)
+
-
-New commands are CREATE>>,
-ALTER>>, and
-DROP STATISTICS>>. This is helpful in
-estimating query memory usage and when combining the statistics from
-individual columns.
-
-
+
+ New commands are CREATE>>,
+ ALTER>>, and
+ DROP STATISTICS>>.
+ This is helpful in
+ estimating query memory usage and when combining the statistics
+ from individual columns.
+
+
-
-
-
-Improve planner matching of boolean indexes (Tom Lane)
-
-
+
+
+
+ Improve planner matching of boolean indexes (Tom Lane)
+
+
-
-
-
-Improve performance of queries referencing row-level security
-restrictions (Tom Lane)
-
+
+
+
+ Improve performance of queries referencing row-level security
+ restrictions (Tom Lane)
+
-
-The optimizer now has more flexibility in reordering executor behavior.
-
-
+
+ The optimizer now has more flexibility in reordering executor
+ behavior.
+
+
-
+ General Performance
-
-
-
-Speed up SUM()> calculations (Heikki Linnakangas)
-
+
+
+
+ Speed up SUM()> calculations (Heikki Linnakangas)
+
-
-This uses an optimized numeric accumulator.
-
-
+
+ This uses an optimized numeric accumulator.
+
+
-
-
-
-Improve the performance of character encoding conversions by using radix
-trees (Kyotaro Horiguchi, Heikki Linnakangas)
-
-
+
+
+
+ Improve the performance of character encoding conversions by
+ using radix trees (Kyotaro Horiguchi, Heikki Linnakangas)
+
+
-
-
-
-Reduce the function call overhead during query execution (Andres Freund)
-
+
+
+
+ Reduce the function call overhead during query execution (Andres
+ Freund)
+
-
-This is particularly helpful for queries that process many rows.
-
-
+
+ This is particularly helpful for queries that process many rows.
+
+
-
-
-
-Improve the performance of grouping sets (Andrew Gierth)
-
-
+
+
+
+ Improve the performance of grouping sets (Andrew Gierth)
+
+
-
-
-
-Use uniqueness guarantees to optimize certain join types (David Rowley)
-
-
+
+
+
+ Use uniqueness guarantees to optimize certain join types (David
+ Rowley)
+
+
-
-
-
-Improve sort performance of the macaddr data type (Brandur Leach)
-
-
+
+
+
+ Improve sort performance of the macaddr data type (Brandur Leach)
+
+
@@ -786,266 +816,288 @@ Improve sort performance of the macaddr data type (Brandur Leach)
-
-
-
-Add pg_sequences>> view to show all sequences (Peter Eisentraut)
-
-
+
+
+
+ Add pg_sequences>> view
+ to show all sequences (Peter Eisentraut)
+
+
-
-
-
-Create a pg_sequence>> system catalog to store sequence metadata
-(Peter Eisentraut)
-
+
+
+
+ Create a pg_sequence>>
+ system catalog to store sequence metadata (Peter Eisentraut)
+
-
-Sequence metadata includes start, increment, etc, which is now
-transactional. Sequence counters are still stored in separate heap
-relations.
-
-
+
+ Sequence metadata includes start, increment, etc, which is now
+ transactional. Sequence counters are still stored in separate
+ heap relations.
+
+
-
-
-
-Allow explicit control over EXPLAIN>>'s display of planning and execution
-time (Ashutosh Bapat)
-
+
+
+
+ Allow explicit control over EXPLAIN>>'s display of planning and
+ execution time (Ashutosh Bapat)
+
-
-By default planning and execution is display by EXPLAIN ANALYZE> and not
-display in other cases. The new EXPLAIN> option SUMMARY> allows explicit
-control of this.
-
-
+
+ By default planning and execution is display by EXPLAIN
+ ANALYZE> and not display in other cases. The new
+ EXPLAIN> option SUMMARY> allows explicit
+ control of this.
+
+
-
-
-
-Properly update the statistics collector during REFRESH MATERIALIZED VIEW>>
-(Jim Mlodgenski)
-
-
+
+
+
+ Properly update the statistics collector during REFRESH MATERIALIZED
+ VIEW>> (Jim Mlodgenski)
+
+
-
-
-
-Add default monitoring roles (Dave Page)
-
+
+
+
+ Add default monitoring roles (Dave Page)
+
-
-New roles pg_monitor>, pg_read_all_settings>, pg_read_all_stats>, and
-pg_stat_scan_tables> allow simplified permission configuration.
-
-
+
+ New roles pg_monitor>, pg_read_all_settings>,
+ pg_read_all_stats>, and pg_stat_scan_tables>
+ allow simplified permission configuration.
+
+
-
-
-
+
+
+ Logging
-
-
-
-Change default to include current timestamp with milliseconds
-and the process id (Christoph Berg)
-
+
+
+
+ Change default to include
+ current timestamp with milliseconds and the process id (Christoph
+ Berg)
+
-
-The previous default was not to output a prefix.
-
-
+
+ The previous default was not to output a prefix.
+
+
-
-
-
-Add functions to return the log and WAL> directory names (Dave Page)
-
+
+
+
+ Add functions to return the log and WAL> directory
+ names (Dave Page)
+
-
-The new functions are pg_ls_logdir()>> and
-pg_ls_waldir()>> and can be
-executed by non-super users with the proper permissions.
-
-
+
+ The new functions are pg_ls_logdir()>>
+ and
+ pg_ls_waldir()>>
+ and can be
+ executed by non-super users with the proper permissions.
+
+
-
-
-
-Add function pg_current_logfile()>> to read syslog's current stderr and
-csvlog output file names (Gilles Darold)
-
-
+
+
+
+ Add function pg_current_logfile()>>
+ to read syslog's current stderr and csvlog output file names
+ (Gilles Darold)
+
+
-
-
-
-Report the address and port number of successful startup socket binding
-in the server logs (Tom Lane)
-
+
+
+
+ Report the address and port number of successful startup socket
+ binding in the server logs (Tom Lane)
+
-
-Also, report bind socket failure details in the server logs.
-
-
+
+ Also, report bind socket failure details in the server logs.
+
+
-
-
-
-Reduce log chatter about the starting and stopping of launcher
-subprocesses (Tom Lane)
-
+
+
+
+ Reduce log chatter about the starting and stopping of launcher
+ subprocesses (Tom Lane)
+
-
-These are now DEBUG1>-level messages.
-
-
+
+ These are now DEBUG1>-level messages.
+
+
-
-
-
-Reduce message verbosity of lower-numbered debug levels controlled by
- (Robert Haas)
-
+
+
+
+ Reduce message verbosity of lower-numbered debug levels
+ controlled by
+ (Robert Haas)
+
-
-This also changes the verbosity of debug levels.
-
-
+
+ This also changes the verbosity of debug levels.
+
+
-
-
-
+
+
+
+ pg_stat_activity>
-
-
-
-Add pg_stat_activity> reporting of latch wait states (Michael Paquier,
-Robert Haas)
-
+
+
+
+ Add pg_stat_activity> reporting of latch wait states
+ (Michael Paquier, Robert Haas)
+
-
-This includes the remaining wait events, like client reads, client
-writes, and synchronous replication.
-
-
+
+ This includes the remaining wait events, like client reads,
+ client writes, and synchronous replication.
+
+
-
-
-
-Add pg_stat_activity> reporting of waits on reads, writes, and fsyncs
-(Rushabh Lathia)
-
-
+
+
+
+ Add pg_stat_activity> reporting of waits on reads,
+ writes, and fsyncs (Rushabh Lathia)
+
+
-
-
-
-Show auxiliary processes and background workers in pg_stat_activity>
-(Kuntal Ghosh)
-
+
+
+
+ Show auxiliary processes and background workers in
+ pg_stat_activity> (Kuntal Ghosh)
+
-
-New column backend_type> identifies the process type.
-
-
+
+ New column backend_type> identifies the process
+ type.
+
+
-
-
-
-Display walsender processes in pg_stat_activity> (Michael Paquier)
-
+
+
+
+ Display walsender processes in pg_stat_activity>
+ (Michael Paquier)
+
-
-This simplifies monitoring.
-
-
+
+ This simplifies monitoring.
+
+
-
-
-
-Allow pg_stat_activity> to show the source query being executed by parallel workers
-(Rafia Sabih)
-
-
+
+
+
+ Allow pg_stat_activity> to show the source query
+ being executed by parallel workers (Rafia Sabih)
+
+
-
-
-
-Rename pg_stat_activity>.wait_event_type> values LWLockTranche> and
-LWLockNamed> to LWLock> (Robert Haas)
-
+
+
+
+ Rename
+ pg_stat_activity>.wait_event_type>
+ values LWLockTranche> and
+ LWLockNamed> to LWLock> (Robert Haas)
+
-
-This makes the output more consistent.
-
-
+
+ This makes the output more consistent.
+
+
-
-
+
+
@@ -1053,71 +1105,75 @@ This makes the output more consistent.
-
-
-
-Add SCRAM-SHA-256>> support for password negotiation and storage (Michael
-Paquier, Heikki Linnakangas)
-
+
+
+
+ Add SCRAM-SHA-256>>
+ support for password negotiation and storage (Michael Paquier,
+ Heikki Linnakangas)
+
-
-This proves better security than the existing md5> negotiation and
-storage method.
-
-
+
+ This proves better security than the existing md5>
+ negotiation and storage method.
+
+
-
-
-
-Change GUC> from boolean> to enum> (Michael Paquier)
-
+
+
+
+ Change GUC>
+ from boolean> to enum> (Michael Paquier)
+
-
-This was necessary to support additional password hashing options.
-
-
+
+ This was necessary to support additional password hashing options.
+
+
-
-
-
-Add view pg_hba_file_rules>> to display the contents of pg_hba.conf>
-(Haribabu Kommi)
-
+
+
+
+ Add view pg_hba_file_rules>>
+ to display the contents of pg_hba.conf> (Haribabu
+ Kommi)
+
-
-This shows the file contents, not the currently active settings.
-
-
+
+ This shows the file contents, not the currently active settings.
+
+
-
-
-
-Support multiple RADIUS> servers (Magnus Hagander)
-
+
+
+
+ Support multiple RADIUS> servers (Magnus Hagander)
+
-
-All the RADIUS> related parameters are now plural and support a
-comma-separated list of servers.
-
-
+
+ All the RADIUS> related parameters are now plural and
+ support a comma-separated list of servers.
+
+
@@ -1128,67 +1184,70 @@ comma-separated list of servers.
-
-
-
-Allow SSL> configuration to be updated at SIGHUP> (Andreas Karlsson, Tom Lane)
-
+
+
+
+ Allow SSL> configuration to be updated at
+ SIGHUP> (Andreas Karlsson, Tom Lane)
+
-
-This allows SSL> to be reconfigured without a server restart by using
-pg_ctl reload>, SELECT pg_reload_conf()>, or sending a
-SIGHUP> signal.
-Reload SSL> configuration updates do not work if the SSL> key requires a
-passphrase.
-
-
+
+ This allows SSL> to be reconfigured without a server
+ restart by using pg_ctl reload>, SELECT
+ pg_reload_conf()>, or sending a SIGHUP> signal.
+ Reload SSL> configuration updates do not work if the
+ SSL> key requires a passphrase.
+
+
-
-
-
-Remove documented restriction about using large shared buffers on
-Windows> (Takayuki Tsunakawa)
-
-
+
+
+
+ Remove documented restriction about using large shared buffers on
+ Windows> (Takayuki Tsunakawa)
+
+
-
-
-
-Reduce locking required to change table params (Simon Riggs, Fabrízio
-Mello)
-
+
+
+
+ Reduce locking required to change table params (Simon Riggs,
+ Fabrízio Mello)
+
-
-For example, changing a table's setting can now
-be done with a more lightweight lock.
-
-
+
+ For example, changing a table's setting can now be done
+ with a more lightweight lock.
+
+
-
-
-
-Make the maximum value of effectively unlimited
-(Jim Nasby)
-
-
+
+
+
+ Make the maximum value of effectively unlimited
+ (Jim Nasby)
+
+
@@ -1199,86 +1258,88 @@ Make the maximum value of effectively
-
-
-
-Perform an fsync on the directory after creating or unlinking files
-(Michael Paquier)
-
+
+
+
+ Perform an fsync on the directory after creating or unlinking files
+ (Michael Paquier)
+
-
-This reduces the risk of data loss after a power failure.
-
-
+
+ This reduces the risk of data loss after a power failure.
+
+
-
-
-
-Remove orphaned temporary tables more aggressively (Robert Haas, Tom Lane)
-
+
+
+
+ Remove orphaned temporary tables more aggressively (Robert Haas,
+ Tom Lane)
+
-
-Previously such tables were removed only when necessary. SECTION?
-
-
+
+ Previously such tables were removed only when necessary. SECTION?
+
+
-
+
-
+ Write-Ahead Log> (WAL>)
-
-
-
-Prevent checkpoints and WAL> archiving on otherwise-idle systems (Michael
-Paquier)
-
-
+
+
+
+ Prevent checkpoints and WAL> archiving on
+ otherwise-idle systems (Michael Paquier)
+
+
-
-
-
-Add GUC> to add details to WAL> that can be
-sanity-checked on the standby (Kuntal Ghosh, Robert
-Haas)
-
+
+
+
+ Add GUC>
+ to add details to WAL> that can be sanity-checked on
+ the standby (Kuntal Ghosh, Robert Haas)
+
-
-Any sanity-check failure generates a fatal error on the standby.
-
-
+
+ Any sanity-check failure generates a fatal error on the standby.
+
+
-
-
-
-Increase the maximum configurable WAL> size to 1 gigabyte (Beena Emerson)
-
-
+
+
+
+ Increase the maximum configurable WAL> size to 1
+ gigabyte (Beena Emerson)
+
+
-
-
+
+
@@ -1287,383 +1348,405 @@ Increase the maximum configurable WAL> size to 1 gigabyte (Beena Emer
Replication and Recovery
-
+
-
-
-
-Add the ability to logically replicate> tables to standby servers (Petr
-Jelinek)
-
+
+
+
+ Add the ability to logically
+ replicate> tables to standby servers (Petr Jelinek)
+
-
-This allows more fine-grained replication options, including replication
-between different major versions of Postgres and selective-table
-replication.
-
-
+
+ This allows more fine-grained replication options, including
+ replication between different major versions of Postgres and
+ selective-table replication.
+
+
-
-
-
-Allow waiting for commit acknowledgement from standby servers
-irrespective of the order they appear in
-(Masahiko Sawada)
-
+
+
+
+ Allow waiting for commit acknowledgement from standby
+ servers irrespective of the order they appear in (Masahiko Sawada)
+
-
-Previously the server always waited for the active standbys that
-appeared first in synchronous_standby_names>. The new
-synchronous_standby_names> keyword ANY> allows waiting for any number of
-standbys irrespective of their ordering. This is known as quorum commit.
+
+ Previously the server always waited for the active standbys that
+ appeared first in synchronous_standby_names>. The new
+ synchronous_standby_names> keyword ANY> allows
+ waiting for any number of standbys irrespective of their ordering.
+ This is known as quorum commit.
+
+
-
-
+
+
+
+ Reduce configuration necessary to perform streaming backup and
+ replication (Magnus Hagander)
+
-
-
-
-Reduce configuration necessary to perform streaming backup and
-replication (Magnus Hagander)
-
+
+ Specifically, defaults were changed for , ,
+ and .
+
+
-
-Specifically, defaults were changed for ,
-, and
-.
-
-
+
+
+
+ Enable replication from localhost connections by default in
+ pg_hba.conf>>
+ (Michael Paquier)
+
-
-
-
-Enable replication from localhost connections by default in pg_hba.conf>>
-(Michael Paquier)
-
+
+ Previously pg_hba.conf>'s replication connection
+ lines were commented out. This is particularly useful for
+ >.
+
+
-
-Previously pg_hba.conf>'s replication connection lines were commented
-out. This is particularly useful for >.
-
-
+
+
+
+ Add columns to pg_stat_replication>>
+ to report replication delay times (Thomas Munro)
+
-
-
-
-Add columns to pg_stat_replication>> to report replication delay times
-(Thomas Munro)
-
+
+ The new columns are write_lag>,
+ flush_lag>, and replay_lag>.
+
+
-
-The new columns are write_lag>, flush_lag>, and replay_lag>.
-
-
+
+
+
+ Add specification of a Log Sequence Number (LSN>)
+ stopping point in
+ recovery.conf>>
+ (Michael Paquier)
+
-
-
-
-Add specification of a Log Sequence Number (LSN>) stopping point in
-recovery.conf>> (Michael Paquier)
-
+
+ Previously only specification of the stop name, time, timeline,
+ xid, and immediate were supported.
+
+
-
-Previously only specification of the stop name, time, timeline, xid,
-and immediate were supported.
-
-
+
+
+
+ Allow users to disable pg_stop_backup()>>'s
+ waiting for all WAL> to be archived (David Steele)
+
-
-
-
-Allow users to disable pg_stop_backup()>>'s waiting for all WAL> to be
-archived (David Steele)
-
+
+ An optional second argument to pg_stop_backup()>
+ controls that behavior.
+
+
-
-An optional second argument to pg_stop_backup()> controls that behavior.
-
-
+
+
+
+ Allow creation of temporary replication slots>
+ (Petr Jelinek)
+
-
-
-
-Allow creation of temporary replication slots> (Petr Jelinek)
-
+
+ Temporary slots are automatically removed on session exit or error.
+
+
-
-Temporary slots are automatically removed on session exit or error.
-
-
+
+
+
+ Improve performance of hot standby replay with better tracking of
+ Access Exclusive locks (Simon Riggs, David Rowley)
+
+
-
-
-
-Improve performance of hot standby replay with better tracking of
-Access Exclusive locks (Simon Riggs, David Rowley)
-
-
+
+
+
+ Speed up two-phase commit recovery performance (Stas Kelvich,
+ Nikhil Sontakke, Michael Paquier)
+
+
-
-
-
-Speed up two-phase commit recovery performance (Stas Kelvich, Nikhil
-Sontakke, Michael Paquier)
-
-
-
-
+ Queries
-
+
-
-
-
-Allow ROW> to supply values to UPDATE ... SET (column_list)> (Tom Lane)
-
+
+
+
+ Allow ROW> to supply values to UPDATE ... SET
+ (column_list)> (Tom Lane)
+
-
-Also allow row values to be supplied by table.*.
-
-
+
+ Also allow row values to be supplied by table.*.
+
+
-
-
-
-Fix regular expression locale class handling for bytes greater than U+7FF>
-(Tom Lane)
-
+
+
+
+ Fix regular expression locale class handling for bytes greater
+ than U+7FF> (Tom Lane)
+
-
-Previously such classes were not recognized.
-
-
+
+ Previously such classes were not recognized.
+
+
-
+ Utility Commands
-
+
-
-
-
-Add table partitioning syntax> that automatically creates partition
-constraints and INSERT> routing (Amit Langote)
-
+
+
+
+ Add table partitioning
+ syntax> that automatically creates partition constraints and
+ INSERT> routing (Amit Langote)
+
-
-The syntax supports range and list partitioning.
-
-
+
+ The syntax supports range and list partitioning.
+
+
-
-
-
-Add AFTER> trigger> transition table to record changed rows (Kevin Grittner)
-
+
+
+
+ Add AFTER> trigger>
+ transition table to record changed rows (Kevin Grittner)
+
-
-Transition table contents are accessible from server-side languages.
-
-
+
+ Transition table contents are accessible from server-side languages.
+
+
-
-
-
-Allow restrictive row-level security policies> (Stephen Frost)
-
+
+
+
+ Allow restrictive row-level
+ security policies> (Stephen Frost)
+
-
-Previously all security policies were permissive, meaning that any
-matching policy allowed access. Optional restrictive policies must
-match for access to be granted. These policy types can be combined.
-
-
+
+ Previously all security policies were permissive, meaning that any
+ matching policy allowed access. Optional restrictive policies must
+ match for access to be granted. These policy types can be combined.
+
+
-
-
-
-Allow default permissions> on schemas (Matheus Oliveira)
-
+
+
+
+ Allow default
+ permissions> on schemas (Matheus Oliveira)
+
-
-This is done using the ALTER DEFAULT PRIVILEGES> command.
-
-
+
+ This is done using the ALTER DEFAULT PRIVILEGES> command.
+
+
-
-
-
-Add CREATE SEQUENCE AS>> command to create a sequence matching
-an integer data type (Peter Eisentraut)
-
+
+
+
+ Add CREATE SEQUENCE
+ AS>> command to create a sequence matching an integer data type
+ (Peter Eisentraut)
+
-
-This simplifies the creation of sequences matching the range of base
-columns.
-
-
+
+ This simplifies the creation of sequences matching the range of
+ base columns.
+
+
-
-
-
-Allow COPY view FROM> on views with INSTEAD INSERT> triggers (Haribabu
-Kommi)
-
+
+
+
+ Allow COPY view FROM> on views with INSTEAD
+ INSERT> triggers (Haribabu Kommi)
+
-
-The triggers are fed the rows from COPY>.
-
-
+
+ The triggers are fed the rows from COPY>.
+
+
-
-
-
-Allow the specification of a function name without arguments in DDL>
-commands, when unique (Peter Eisentraut)
-
+
+
+
+ Allow the specification of a function name without arguments in
+ DDL> commands, when unique (Peter Eisentraut)
+
-
-For example, allow DROP FUNCTION>> on a function name without arguments if
-there is only one function with that name. This is required by the SQL>
-standard.
-
-
+
+ For example, allow DROP
+ FUNCTION>> on a function name without arguments if there
+ is only one function with that name. This is required by the
+ SQL> standard.
+
+
-
-
-
-Allow multiple functions, operators, and aggregates to be dropped with a
-single DROP> command (Peter Eisentraut)
-
-
+
+
+
+ Allow multiple functions, operators, and aggregates to be dropped
+ with a single DROP> command (Peter Eisentraut)
+
+
-
-
-
-Add IF NOT EXISTS> for CREATE SERVER>> and
-CREATE USER MAPPING>> (Anastasia
-Lubennikova)
-
-
+
+
+
+ Add IF NOT EXISTS> for CREATE SERVER>> and
+ CREATE USER
+ MAPPING>> (Anastasia
+ Lubennikova)
+
+
-
-
-
-Add IF NOT EXISTS> clause to CREATE COLLATION>> (Peter Eisentraut)
-
-
+
+
+
+ Add IF NOT EXISTS> clause to CREATE COLLATION>>
+ (Peter Eisentraut)
+
+
-
-
-
-Have VACUUM VERBOSE>> report the number of skipped frozen pages (Masahiko
-Sawada)
-
+
+
+
+ Have VACUUM VERBOSE>>
+ report the number of skipped frozen pages (Masahiko Sawada)
+
-
-This information is also included in output.
-
-
+
+ This information is also included in output.
+
+
-
-
-
-Fix check_srf_call_placement()> to handle VALUES> cases correctly (Tom
-Lane)
-
+
+
+
+ Fix check_srf_call_placement()> to handle
+ VALUES> cases correctly (Tom Lane)
+
-
-NEED TEXT.
-
-
+
+ NEED TEXT.
+
+
@@ -1674,85 +1757,95 @@ NEED TEXT.
-
-
-
-Add support for EUI-64> MAC> addresses as MACADDR8>> (Haribabu Kommi)
-
+
+
+
+ Add support for EUI-64> MAC> addresses as
+ MACADDR8>> (Haribabu
+ Kommi)
+
-
-This complements support for EUI-48> MAC> addresses as macaddr>.
-
-
+
+ This complements support for EUI-48> MAC>
+ addresses as macaddr>.
+
+
-
-
-
-Add identity columns> for assigning a numeric value to columns on insert
-(Peter Eisentraut)
-
+
+
+
+ Add identity columns> for
+ assigning a numeric value to columns on insert (Peter Eisentraut)
+
-
-These are similar to SERIAL> columns, but are SQL> standard compliant.
-
-
+
+ These are similar to SERIAL> columns, but are
+ SQL> standard compliant.
+
+
-
-
-
-Allow ENUM>> values to be renamed (Dagfinn Ilmari Mannsåker)
-
+
+
+
+ Allow ENUM>> values to be
+ renamed (Dagfinn Ilmari Mannsåker)
+
-
-This uses the syntax ALTER TYPE ... RENAME VALUE>>.
-
-
+
+ This uses the syntax ALTER
+ TYPE ... RENAME VALUE>>.
+
+
-
-
-
-Properly treat array pseudotypes (anyarray>) as arrays in to_json()>> and to_jsonb()> (Andrew
-Dunstan)
-
+
+
+
+ Properly treat array pseudotypes
+ (anyarray>) as arrays in to_json()>>
+ and to_jsonb()> (Andrew Dunstan)
+
-
-Previously "anyarray" values were converted to JSON> strings.
-
-
+
+ Previously "anyarray" values were converted to JSON>
+ strings.
+
+
-
-
-
-Add MONEY>> operators for multiplication and division with INT8> values
-(Peter Eisentraut)
-
-
+
+
+
+ Add MONEY>> operators
+ for multiplication and division with INT8> values (Peter
+ Eisentraut)
+
+
-
-
-
-More strictly check the MONEY> type for overflow operations (Peter
-Eisentraut)
-
-
+
+
+
+ More strictly check the MONEY> type for overflow operations
+ (Peter Eisentraut)
+
+
@@ -1761,130 +1854,142 @@ Eisentraut)
Functions
-
+
-
-
-
-Add simplified regexp_match()>> function (Emre Hasegeli)
-
+
+
+
+ Add simplified regexp_match()>>
+ function (Emre Hasegeli)
+
-
-Similar to regexp_matches()>, but only returns results from the first
-match so it is easier use for simple cases.
-
-
+
+ Similar to regexp_matches()>, but only returns results
+ from the first match so it is easier use for simple cases.
+
+
-
-
-
-Add support for converting XML>-formatted data into a row set (Pavel
-Stehule, Álvaro Herrera)
-
+
+
+
+ Add support for converting XML>-formatted data into a row
+ set (Pavel Stehule, Álvaro Herrera)
+
-
-This is done by referencing the new XMLTABLE>> function.
-
-
+
+ This is done by referencing the new XMLTABLE>>
+ function.
+
+
-
-
-
-Add version of jsonb's delete operator> that takes an array of keys to delete
-(Magnus Hagander)
-
+
+
+
+ Add version of jsonb's delete operator> that takes
+ an array of keys to delete (Magnus Hagander)
+
-
-The JSONB> delete operator also now supports arrays.
-
-
+
+ The JSONB> delete operator also now supports arrays.
+
+
-
-
-
-Improve json_populate_record>> and friends operate recursively (Nikita
-Glukhov)
-
+
+
+
+ Improve json_populate_record>>
+ and friends operate recursively (Nikita Glukhov)
+
-
-CLARIFY
-
-
+
+ CLARIFY
+
+
-
-
-
-Add function txid_current_ifassigned()>> to return NULL> if no transaction
-id has been assigned (Craig Ringer)
-
+
+
+
+ Add function txid_current_ifassigned()>>
+ to return NULL> if no transaction id has been assigned
+ (Craig Ringer)
+
-
-This is different from txid_current()>>, which always returns a
-transaction id by assigning one if necessary. This can be also run on
-standby servers.
-
-
+
+ This is different from txid_current()>>,
+ which always returns a transaction id by assigning one if necessary.
+ This can be also run on standby servers.
+
+
-
-
-
-Add function txid_status()>> to check if a transaction was committed
-(Craig Ringer)
-
+
+
+
+ Add function txid_status()>>
+ to check if a transaction was committed (Craig Ringer)
+
-
-This is useful for checking after an abrupt disconnection if your
-previous transaction committed and you just didn't receive the
-acknowledgement.
-
-
+
+ This is useful for checking after an abrupt disconnection if
+ your previous transaction committed and you just didn't receive
+ the acknowledgement.
+
+
-
-
-
-Allow make_date()>> to interpret negative years as BC> years (Álvaro
-Herrera)
-
-
+
+
+
+ Allow make_date()>>
+ to interpret negative years as BC> years (Álvaro
+ Herrera)
+
+
-
-
-
-Have to_timestamp()> and to_date()> check input values for validity
-(Artur Zakirov)
-
+
+
+
+ Have to_timestamp()> and to_date()> check
+ input values for validity (Artur Zakirov)
+
-
-Previously to_date('2009-06-40','YYYY-MM-DD')> was accepted and returned
-'2009-07-10'. It will now generate an error.
-
-
+
+ Previously to_date('2009-06-40','YYYY-MM-DD')> was
+ accepted and returned '2009-07-10'. It will now generate an error.
+
+
-
+
@@ -1893,99 +1998,102 @@ Previously to_date('2009-06-40','YYYY-MM-DD')> was accepted and retu
-
-
-
-Allow the PL/Python plan object to call cursor and execute methods
-(Peter Eisentraut)
-
+
+
+
+ Allow the PL/Python plan object to call cursor and execute methods
+ (Peter Eisentraut)
+
-
-This is a more object oriented style.
-
-
+
+ This is a more object oriented style.
+
+
-
-
-
-Allow PL/pgSQL's GET DIAGNOSTICS> to retrieve values into array elements
-(Tom Lane)
-
-
+
+
+
+ Allow PL/pgSQL's GET DIAGNOSTICS> to retrieve values
+ into array elements (Tom Lane)
+
+
-
-
+
+ Remove SPI> functions SPI_push()>,
+ SPI_pop()>, SPI_restore_connection()>
+ as unnecessary (Tom Lane)
+
--->
-
-Remove SPI> functions SPI_push()>, SPI_pop()>, SPI_restore_connection()> as
-unnecessary (Tom Lane)
-
-
-
-Their functionality now happens automatically. Also, SPI_palloc()> now
-requires an active connection.
-
-
+
+ Their functionality now happens automatically. Also,
+ SPI_palloc()> now requires an active connection.
+
+
- PL/Tcl>
+ PL/Tcl>
-
+
-
-
-
-Allow PL/Tcl functions to return composite types and sets (Jim Nasby)
-
-
+
+
+
+ Allow PL/Tcl functions to return composite types and sets
+ (Jim Nasby)
+
+
-
-
-
-Add a subtransaction command to PL/Tcl (Victor Wagner)
-
+
+
+
+ Add a subtransaction command to PL/Tcl (Victor Wagner)
+
-
-This allows PL/Tcl queries to fail without aborting the entire function.
-
-
+
+ This allows PL/Tcl queries to fail without aborting the entire
+ function.
+
+
-
-
-
-Add GUC>s to allow initialization routines to be called on PL/Tcl startup
-(Tom Lane)
-
+
+
+
+ Add GUC>s to allow initialization routines to be called
+ on PL/Tcl startup (Tom Lane)
+
-
-The GUC>s are pltcl.start_proc> and pltclu.start_proc>.
-
-
+
+ The GUC>s are pltcl.start_proc> and
+ pltclu.start_proc>.
+
+
-
-
+
+
-
+
@@ -1993,64 +2101,69 @@ The GUC>s are pltcl.start_proc> and pltclu.start_
-
-
-
-Allow libpq to connect to multiple specified> host names (Robert Haas)
-
+
+
+
+ Allow libpq to connect to multiple specified> host names
+ (Robert Haas)
+
-
-libpq will connect with the first responsive host name.
-
-
+
+ libpq will connect with the first responsive host name.
+
+
-
-
-
-Allow the libpq connection string to request a read/write host> (Victor
-Wagner, Mithun Cy)
-
+
+
+
+ Allow the libpq connection string to request a read/write host>
+ (Victor Wagner, Mithun Cy)
+
-
-This is useful when multiple libpq host names are specified, and is
-controlled by libpq connection parameter
target_session_attrs>.
-
-
+
+ This is useful when multiple libpq host names are
+ specified, and is controlled by libpq connection parameter
+
target_session_attrs>.
+
+
-
-
-
-Allow password file name> to be specified as a libpq connection parameter
-(Julian Markwort)
-
+
+
+
+ Allow password file name>
+ to be specified as a libpq connection parameter (Julian Markwort)
+
-
-Previously this could only be specified via an environment variable.
-
-
+
+ Previously this could only be specified via an environment variable.
+
+
-
-
-
-ecpg preprocessor version changed from 4.12 to 10 (Tom Lane)
-
+
+
+
+ ecpg preprocessor version changed from 4.12 to 10 (Tom Lane)
+
-
-The ecpg version now matches the Postgres distribution version number.
-
-
+
+ The ecpg version now matches the Postgres distribution version
+ number.
+
+
@@ -2059,138 +2172,143 @@ The ecpg version now matches the Postgres distribution version number.
Client Applications
-
-
+
+
-
+
-
-
-
-Add conditional branch support to psql> (Corey Huinker)
-
+
+
+
+ Add conditional branch support to psql> (Corey
+ Huinker)
+
-
-The new syntax uses \if, \elif, \else, and \endif. This is particularly
-helpful for scripting.
-
-
+
+ The new syntax uses \if, \elif, \else, and \endif. This is
+ particularly helpful for scripting.
+
+
-
-
-
-Add psql> \gx command to perform \g(execute) in expanded mode (\x)
-(Christoph Berg)
-
-
+
+
+
+ Add psql> \gx command to perform \g(execute)
+ in expanded mode (\x) (Christoph Berg)
+
+
-
-
-
-Improve psql>'s \d (relation) and \dD (domain) commands to specify
-collation, nullable, and default in separate columns (Peter Eisentraut)
-
+
+
+
+ Improve psql>'s \d (relation) and \dD (domain)
+ commands to specify collation, nullable, and default in separate
+ columns (Peter Eisentraut)
+
-
-Previous they were in a single "Modifiers" column.
-
-
+
+ Previous they were in a single "Modifiers" column.
+
+
-
-
-
-Expand psql> colon variables when used in backtick-executed contexts (Tom Lane)
-
+
+
+
+ Expand psql> colon variables when used in
+ backtick-executed contexts (Tom Lane)
+
-
-This is particularly useful for the new psql> conditional branch support
-commands.
-
-
+
+ This is particularly useful for the new psql>
+ conditional branch support commands.
+
+
-
-
-
-Prevent psql> special variables from being set to invalid values (Daniel
-Vérité, Tom Lane)
-
+
+
+
+ Prevent psql> special variables from being set to
+ invalid values (Daniel Vérité, Tom Lane)
+
-
-Previously setting psql> special variables to invalid values produced the
-default behavior. \set and \unset of special variables now sets them to
-"on" and its default value, rather than a zero-length string and
-undefined. Also have \set always display values for FETCH_COUNT>,
-HISTSIZE>, and IGNOREEOF>.
-
-
+
+ Previously setting psql> special variables
+ to invalid values produced the default behavior. \set and
+ \unset of special variables now sets them to "on" and its
+ default value, rather than a zero-length string and undefined.
+ Also have \set always display values for FETCH_COUNT>,
+ HISTSIZE>, and IGNOREEOF>.
+
+
-
-
-
-Fix psql> \p to always print what would be executed by \g or \w (Daniel
-Vérité)
-
+
+
+
+ Fix psql> \p to always print what would be executed
+ by \g or \w (Daniel Vérité)
+
-
-Previously \p didn't properly print the reverted-to command after a
-buffer contents reset. CLARIFY?
-
-
+
+ Previously \p didn't properly print the reverted-to command after
+ a buffer contents reset. CLARIFY?
+
+
-
-
-
-Improve psql>'s tab completion (Jeff Janes, Ian Barwick, Andreas Karlsson,
-Sehrope Sarkuni, Thomas Munro, Kevin Grittner, Dagfinn Ilmari Mannsåker)
-
-
+
+
+
+ Improve psql>'s tab completion (Jeff Janes,
+ Ian Barwick, Andreas Karlsson, Sehrope Sarkuni, Thomas Munro,
+ Kevin Grittner, Dagfinn Ilmari Mannsåker)
+
+
-
+
@@ -2199,27 +2317,27 @@ Sehrope Sarkuni, Thomas Munro, Kevin Grittner, Dagfinn Ilmari Mannsåker)
-
-
-
-Add pgbench option
--log-prefix> to control the log file prefix (Masahiko
-Sawada)
-
-
+
+
+
+ Add pgbench option
--log-prefix> to control the log
+ file prefix (Masahiko Sawada)
+
+
-
-
-
-Allow pgbench's meta commands to span multiple lines via a
-line-terminating backslash (Fabien Coelho)
-
-
+
+
+
+ Allow pgbench's meta commands to span multiple lines via a
+ line-terminating backslash (Fabien Coelho)
+
+
@@ -2232,421 +2350,445 @@ line-terminating backslash (Fabien Coelho)
-
-
-
-Add pg_receivewal>> option
-Z>/
--compress> to support compression (Michael
-Paquier)
-
-
+
+
+
+ Add pg_receivewal>>
+ option
-Z>/
--compress> to support compression
+ (Michael Paquier)
+
+
-
-
-
-Add pg_recvlogical>> option (
--endpos>) to specify the ending position
-(Craig Ringer)
-
+
+
+
+ Add pg_recvlogical>> option
+ (
--endpos>) to specify the ending position (Craig Ringer)
+
-
-This complements the existing
--startpos> option.
-
-
+
+ This complements the existing
--startpos> option.
+
+
-
-
-
-Rename initdb>> options
--noclean> and
--nosync> to be spelled
--no-clean>
-and
--no-sync> (Vik Fearing, Peter Eisentraut)
-
+
+
+
+ Rename initdb>>
+ options
--noclean> and
--nosync> to be spelled
+
--no-clean> and
--no-sync> (Vik Fearing,
+ Peter Eisentraut)
+
-
-The old spellings are still supported.
-
-
+
+ The old spellings are still supported.
+
+
- pg_dump>>, pg_dumpall>>.
- pg_restore>>
+ pg_dump>>, pg_dumpall>>.
+ pg_restore>>
-
+
-
-
-
-Allow pg_restore> to exclude schemas (Michael Banck)
-
+
+
+
+ Allow pg_restore> to exclude schemas (Michael Banck)
+
-
-This added a new
-N>/
--exclude-schema> option.
-
-
+
+ This added a new
-N>/
--exclude-schema> option.
+
+
-
-
-
-Add
--no-blobs> option to
-pg_dump> (Guillaume Lelarge)
-
+
+
+
+ Add
--no-blobs> option to
+ pg_dump> (Guillaume Lelarge)
+
-
-This suppresses the dumping of large objects.
-
-
+
+ This suppresses the dumping of large objects.
+
+
-
-
-
-Add pg_dumpall> option
--no-role-passwords> to dump roles without user
-passwords (Robins Tharakan, Simon Riggs)
-
+
+
+
+ Add pg_dumpall> option
+
--no-role-passwords> to dump roles without user passwords
+ (Robins Tharakan, Simon Riggs)
+
-
-This allows easier dumping for less-privileged users.
-
-
+
+ This allows easier dumping for less-privileged users.
+
+
-
-
-
-Issue fsync on the output files generated by pg_dump> and
-pg_dumpall> (Michael Paquier)
-
+
+
+
+ Issue fsync on the output files generated by
+ pg_dump> and
+ pg_dumpall> (Michael Paquier)
+
-
-This can be disabled with the
--no-sync> option.
-
-
+
+ This can be disabled with the
--no-sync> option.
+
+
-
+
-
-
-
+
+
+
-
+
-
-
-
-Allow pg_basebackup> to stream transaction log in tar mode (Magnus
-Hagander)
-
+
+
+
+ Allow pg_basebackup> to stream transaction log in
+ tar mode (Magnus Hagander)
+
-
-The WAL> will be stored in a separate tar file from the base backup.
-
-
+
+ The WAL> will be stored in a separate tar file from
+ the base backup.
+
+
-
-
-
-Make pg_basebackup> use temporary replication slots (Magnus Hagander)
-
+
+
+
+ Make pg_basebackup> use temporary replication slots
+ (Magnus Hagander)
+
-
-Temporary replication slots will be used by default when pg_basebackup>
-uses wal streaming with default options.
-
-
+
+ Temporary replication slots will be used by default when
+ pg_basebackup> uses wal streaming with default
+ options.
+
+
-
-
-
-Improve fsync handling of pg_basebackup> and pg_receivewal> (Michael Paquier)
-
+
+
+
+ Improve fsync handling of pg_basebackup> and
+ pg_receivewal> (Michael Paquier)
+
-
-Also add
-nosync> option to disable fsync.
-
-
+
+ Also add
-nosync> option to disable fsync.
+
+
-
-
-
-Improve pg_basebackup>'s handling of which directories to skip (David
-Steele)
-
+
+
+
+ Improve pg_basebackup>'s handling of which
+ directories to skip (David Steele)
+
-
-Also improve the documentation of skipped directories.
-
-
+
+ Also improve the documentation of skipped directories.
+
+
-
+
-
-
-
- >
-
-
-
-
-
-
-Add wait option for >'s promote operation (Peter Eisentraut)
-
-
-
-
-
-
-Add log options for pg_ctl> wait (
--wait>) and no-wait (
--no-wait>) (Vik Fearing)
-
-
-
-
-
-
-Add long options flag for pg_ctl> options> (Peter Eisentraut)
-
-
-
-It is called
+
+
+
+
+
+ Add long options flag for pg_ctl>
+ options> (Peter Eisentraut)
+
+
+
+ It is called
--options>.
+
+
+
+
+
+
Source Code
-
+
-
-
-
-New major version numbering (Peter Eisentraut, Tom Lane)
-
+
+
+
+ New major version numbering (Peter Eisentraut, Tom Lane)
+
-
-Major versions will now increase just the first number, and minor
-releases will increase just the second number. A third number will no
-longer be used in Postgres version numbers.
-
-
+
+ Major versions will now increase just the first number, and minor
+ releases will increase just the second number. A third number
+ will no longer be used in Postgres version numbers.
+
+
-
-
-
-Allow the ICU>> library to optionally be used for collation support (Peter
-Eisentraut)
-
+
+
+
+ Allow the ICU>> library to
+ optionally be used for collation support (Peter Eisentraut)
+
-
-The ICU> library has versioning that allows detection of collation
-changes between versions. It is enabled via configure option
-
--with-icu>. The default still uses the operating system's native
-collation library.
-
-
+
+ The ICU> library has versioning that allows detection
+ of collation changes between versions. It is enabled via configure
+ option
--with-icu>. The default still uses the operating
+ system's native collation library.
+
+
-
-
-
-Automatically mark all PG_FUNCTION_INFO_V1>> functions as DLLEXPORT>-ed on
-Windows> (Laurenz Albe)
-
+
+
+
+ Automatically mark all PG_FUNCTION_INFO_V1>> functions
+ as DLLEXPORT>-ed on
+ Windows> (Laurenz Albe)
+
-
-If third-party code is using extern> function declarations, they should
-also add DLLEXPORT> markers to those declarations.
-
-
+
+ If third-party code is using extern> function
+ declarations, they should also add DLLEXPORT> markers
+ to those declarations.
+
+
-
-
-
-Allow shared memory to be dynamically allocated (Thomas Munro, Robert Haas)
-
-
+
+
+
+ Allow shared memory to be dynamically allocated (Thomas Munro,
+ Robert Haas)
+
+
-
-
-
-Add slab-like memory allocator for efficient fixed-size allocations
-(Tomas Vondra)
-
-
+
+
+
+ Add slab-like memory allocator for efficient fixed-size allocations
+ (Tomas Vondra)
+
+
-
-
-
-Use POSIX> semaphores rather than SysV semaphores on Linux> and FreeBSD>
-(Tom Lane)
-
+
+
+
+ Use POSIX> semaphores rather than SysV semaphores
+ on Linux> and FreeBSD> (Tom Lane)
+
-
-This avoids some limits on SysV semaphore usage.
-
-
+
+ This avoids some limits on SysV semaphore usage.
+
+
-
-
-
-Improve support for 64-bit atomics (Andres Freund)
-
-
+
+
+
+ Improve support for 64-bit atomics (Andres Freund)
+
+
-
-
-
-Enable 64-bit atomic operations on ARM64> (Roman Shaposhnik)
-
-
+
+
+
+ Enable 64-bit atomic operations on ARM64> (Roman
+ Shaposhnik)
+
+
-
-
-
-Switch to using clock_gettime()>, if available, for duration measurements
-(Tom Lane)
-
+
+
+
+ Switch to using clock_gettime()>, if available, for
+ duration measurements (Tom Lane)
+
-
-gettimeofday()> is used if clock_gettime()> is not available.
-
-
+
+ gettimeofday()> is used if clock_gettime()>
+ is not available.
+
+
-
-
-
-Add more robust random number generators to be used for
-cryptographic secure uses (Magnus Hagander, Michael Paquier, Heikki
-Linnakangas)
-
+
+
+
+ Add more robust random number generators to be used for
+ cryptographic secure uses (Magnus Hagander, Michael Paquier,
+ Heikki Linnakangas)
+
-
-If no strong random number generator can be found, configure will fail
-unless the configure>
--disable-strong-random> is used. However, with
-this option, pgcrypto functions requiring a strong random number
-generator will be disabled.
-
-
+
+ If no strong random number generator can be found, configure
+ will fail unless the configure>
+
--disable-strong-random> is used. However, with this
+ option, pgcrypto functions requiring a strong random number
+ generator will be disabled.
+
+
-
-
-
-Overhaul documentation build process> (Alexander Lakhin, Alexander Law)
-
-
+
+
+
+ Overhaul documentation build
+ process> (Alexander Lakhin, Alexander Law)
+
+
-
-
-
-Use XSLT> to build the Postgres documentation (Peter Eisentraut)
-
+
+
+
+ Use XSLT> to build the Postgres documentation (Peter
+ Eisentraut)
+
-
-Previously Jade>, DSSSL,> and JadeTex> were used.
-
-
+
+ Previously Jade>, DSSSL,> and
+ JadeTex> were used.
+
+
-
-
-
-Build HTML> documentation using XSLT> stylesheets by default (Peter
-Eisentraut)
-
-
+
+
+
+ Build HTML> documentation using XSLT>
+ stylesheets by default (Peter Eisentraut)
+
+
@@ -2657,210 +2799,230 @@ Eisentraut)
-
-
-
-Allow file_fdw>> to read from program output as well as files (Corey Huinker, Adam Gomaa)
-
-
+
+
+
+ Allow file_fdw>> to read
+ from program output as well as files (Corey Huinker, Adam Gomaa)
+
+
-
-
-
-Push aggregates to foreign data wrapper servers, where possible (Jeevan
-Chalke, Ashutosh Bapat)
-
+
+
+
+ Push aggregates to foreign data wrapper servers, where possible
+ (Jeevan Chalke, Ashutosh Bapat)
+
-
-This reduces the amount of data that must be passed from the foreign
-data wrapper server, and offloads aggregate computation from the
-requesting server. The postgres_fdw>> is able to perform this
-optimization.
-
-
+
+ This reduces the amount of data that must be passed
+ from the foreign data wrapper server, and offloads
+ aggregate computation from the requesting server. The postgres_fdw>> is able to
+ perform this optimization.
+
+
-
-
-
-Allow push down of FULL JOIN> queries containing subqueries in the
-FROM> clause to foreign servers (Etsuro Fujita)
-
-
+
+
+
+ Allow push down of FULL JOIN> queries containing
+ subqueries in the
+ FROM> clause to foreign servers (Etsuro Fujita)
+
+
-
-
-
-Properly support OID> columns in postgres_fdw> tables (Etsuro Fujita)
-
+
+
+
+ Properly support OID> columns in
+ postgres_fdw> tables (Etsuro Fujita)
+
-
-Previously OID> columns always returned zeros.
-
-
+
+ Previously OID> columns always returned zeros.
+
+
-
-
-
-Allow btree_gist>> and btree_gin>> to index enum types
-(Andrew Dunstan)
-
+
+
+
+ Allow btree_gist>>
+ and btree_gin>> to
+ index enum types (Andrew Dunstan)
+
-
-This allows enums to be used in exclusion constraints.
-
-
+
+ This allows enums to be used in exclusion constraints.
+
+
-
-
-
-Add indexing support to btree_gist> for the UUID> data type (Paul
-Jungwirth)
-
-
+
+
+
+ Add indexing support to btree_gist> for the
+ UUID> data type (Paul Jungwirth)
+
+
-
-
-
-Add amcheck>> which can check the validity of btree indexes (Peter
-Geoghegan)
-
-
+
+
+
+ Add amcheck>> which can
+ check the validity of btree indexes (Peter Geoghegan)
+
+
-
-
-
-Show ignored constants as $N> rather than ?> in
-pg_stat_statements>> (Lukas Fittl)
-
-
+
+
+
+ Show ignored constants as $N> rather than ?>
+ in
+ pg_stat_statements>>
+ (Lukas Fittl)
+
+
-
-
-
-Improve cube>>'s handling of zero-dimensional cubes (Tom Lane)
-
+
+
+
+ Improve cube>>'s handling
+ of zero-dimensional cubes (Tom Lane)
+
-
-This also improves handling of infinite> and NaN> values.
-
-
+
+ This also improves handling of infinite> and
+ NaN> values.
+
+
-
-
-
-Allow pg_buffercache>> to run with fewer locks (Ivan Kartyshov)
-
+
+
+
+ Allow pg_buffercache>> to run
+ with fewer locks (Ivan Kartyshov)
+
-
-This allows it be less disruptive when run on production systems.
-
-
+
+ This allows it be less disruptive when run on production systems.
+
+
-
-
-
-Add pgstathashindex()> function to pgstattuple>> to view hash index
-statistics (Ashutosh Sharma)
-
-
+
+
+
+ Add pgstathashindex()> function to pgstattuple>> to view hash
+ index statistics (Ashutosh Sharma)
+
+
-
-
-
-Allow pgstattuple>> to use GRANT> permissions (Stephen Frost)
-
+
+
+
+ Allow pgstattuple>>
+ to use GRANT> permissions (Stephen Frost)
+
-
-This allows non-superusers to run these functions if permissions allow.
-
-
+
+ This allows non-superusers to run these functions if permissions
+ allow.
+
+
-
-
-
-Reduce locking when pgstattuple>> examines hash indexes (Amit Kapila)
-
-
+
+
+
+ Reduce locking when pgstattuple>> examines hash
+ indexes (Amit Kapila)
+
+
-
-
-
-Add page_checksum()> function to pageinspect>> (Tomas Vondra)
-
-
+
+
+
+ Add page_checksum()> function to pageinspect>> (Tomas Vondra)
+
+
-
-
-
-Add hash index support to pageinspect>> (Jesper Pedersen, Ashutosh
-Sharma)
-
-
+
+
+
+ Add hash index support to pageinspect>> (Jesper
+ Pedersen, Ashutosh Sharma)
+
+
-
-
-
-Add pageinspect>> function bt_page_items()> to print page items
-from a page image (Tomas Vondra)
-
+
+
+
+ Add pageinspect>>
+ function bt_page_items()> to print page items from a
+ page image (Tomas Vondra)
+
-
-Previously only block numbers were supported.
-
-
+
+ Previously only block numbers were supported.
+
+
-
+
-
+