diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index fe0b4ad0db..f6e7499776 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -18508,7 +18508,7 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup()); pg_replication_origin_drop(node_name text) - void + void Delete a previously created replication origin, including any @@ -18540,7 +18540,7 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup()); pg_replication_origin_session_setup(node_name text) - void + void Mark the current session as replaying from the given @@ -18558,7 +18558,7 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup()); pg_replication_origin_session_reset() - void + void Cancel the effects @@ -18607,7 +18607,7 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup()); pg_replication_origin_xact_setup(origin_lsn pg_lsn, origin_timestamp timestamptz) - void + void Mark the current transaction as replaying a transaction that has @@ -18626,7 +18626,7 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup()); pg_replication_origin_xact_reset() - void + void Cancel the effects of @@ -18642,7 +18642,7 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup()); pg_replication_origin_advance(node_name text, pos pg_lsn) - void + void Set replication progress for the given node to the given @@ -19102,7 +19102,7 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup()); - brin_summarize_new_values(index_oid regclass) + brin_summarize_new_values(index regclass) integer summarize page ranges not already summarized @@ -19119,8 +19119,8 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup()); - brin_summarize_new_values receives a BRIN index OID as - argument and inspects the index to find page ranges in the base table + brin_summarize_new_values accepts the OID or name of a + BRIN index and inspects the index to find page ranges in the base table that are not currently summarized by the index; for any such range it creates a new summary index tuple by scanning the table pages. It returns the number of new page range summaries that were inserted @@ -19129,12 +19129,12 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup()); gin_clean_pending_list accepts the OID or name of - a GIN index and cleans up the pending list of the specified GIN index + a GIN index and cleans up the pending list of the specified index by moving entries in it to the main GIN data structure in bulk. - It returns the number of pages cleaned up from the pending list. - Note that if the argument is a GIN index built with fastupdate - option disabled, the cleanup does not happen and the return value is 0 - because the index doesn't have a pending list. + It returns the number of pages removed from the pending list. + Note that if the argument is a GIN index built with + the fastupdate option disabled, no cleanup happens and the + return value is 0, because the index doesn't have a pending list. Please see and for details of the pending list and fastupdate option. diff --git a/doc/src/sgml/release-9.6.sgml b/doc/src/sgml/release-9.6.sgml index 6ec7583485..895d88e768 100644 --- a/doc/src/sgml/release-9.6.sgml +++ b/doc/src/sgml/release-9.6.sgml @@ -23,33 +23,33 @@ - Parallel sequential scans, joins and aggregates + Parallel execution of sequential scans, joins and aggregates - Eliminate repetitive scanning of old data by autovacuum + Autovacuum no longer performs repetitive scanning of old data - Synchronous replication now allows multiple standby servers, for + Synchronous replication now allows multiple standby servers for increased reliability - Allow full-text search for phrases (multiple adjacent words) + Full-text search can now search for phrases (multiple adjacent words) - Support foreign/remote joins, sorts, and UPDATEs in - postgres_fdw + postgres_fdw now supports remote joins, sorts, + UPDATEs, and DELETEs @@ -87,25 +87,6 @@ - - Change the column name in the - information_schema.routines - view from result_cast_character_set_name - to result_cast_char_set_name (Clément - Prévost) - - - - The SQL:2011 standard specifies the longer name, but that appears - to be a mistake, because adjacent column names use the shorter - style, as do other information_schema views. - - - - - @@ -117,7 +98,7 @@ Historically a process has only been shown as waiting if it was - waiting for a heavy weight lock. Now waits for light weight locks + waiting for a heavyweight lock. Now waits for lightweight locks and buffer pins are also shown in pg_stat_activity. Also, the type of lock being waited for is now visible. These changes replace the waiting column with @@ -149,18 +130,18 @@ Make extract() behave - more reasonably with infinite inputs (Vitaly Burovoy) + more reasonably with infinite inputs (Vitaly Burovoy) Historically the extract() function just returned zero given an infinite timestamp, regardless of the given - unit name. Make it return infinity + field name. Make it return infinity or -infinity as appropriate when the requested field is one that is monotonically increasing (e.g, year, epoch), or NULL when it is not (e.g., day, hour). Also, - throw the expected error for bad unit names. + throw the expected error for bad field names. @@ -186,8 +167,8 @@ This commit is also listed under libpq and psql 2016-03-29 [61d66c44f] Fix support of digits in email/hostnames. --> - Fix text search parser to allow leading digits in email - and host tokens (Artur Zakirov) + Fix the default text search parser to allow leading digits + in email and host tokens (Artur Zakirov) @@ -205,18 +186,18 @@ This commit is also listed under libpq and psql 2016-03-16 [9a206d063] Improve script generating unaccent rules --> - Extend contrib/unaccent's standard - unaccent.rules file to handle all diacritics - known to Unicode, and expand ligatures correctly (Thomas Munro, + Extend contrib/unaccent's + standard unaccent.rules file to handle all diacritics + known to Unicode, and to expand ligatures correctly (Thomas Munro, Léonard Benedetti) - The previous version omitted some less-common letters with - diacritic marks. It now also expands ligatures into separate - letters. Installations that use this rules file may wish to - rebuild tsvector columns and indexes that depend on - the result. + The previous version neglected to convert some less-common letters + with diacritic marks. Also, ligatures are now expanded into + separate letters. Installations that use this rules file may wish + to rebuild tsvector columns and indexes that depend on the + result. @@ -258,17 +239,38 @@ This commit is also listed under libpq and psql - Support multiple and - command-line options (Pavel Stehule, Catalin Iacob) + Change a column name in the + information_schema.routines + view from result_cast_character_set_name + to result_cast_char_set_name (Clément + Prévost) - To allow this with sane behavior, one backwards incompatibility - had to be introduced: no longer implies - . + The SQL:2011 standard specifies the longer name, but that appears + to be a mistake, because adjacent column names use the shorter + style, as do other information_schema views. + + + + + + + psql's option no longer implies + + (Pavel Stehule, Catalin Iacob) + + + + Write (or its + abbreviation ) explicitly to obtain the old + behavior. Scripts modified this way will still work with old + versions of psql. @@ -277,7 +279,7 @@ This commit is also listed under libpq and psql 2015-07-02 [5671aaca8] Improve pg_restore's -t switch to match all types of rel --> - Improve pg_restore's switch to + Improve pg_restore's option to match all types of relations, not only plain tables (Craig Ringer) @@ -287,7 +289,7 @@ This commit is also listed under libpq and psql 2016-02-12 [59a884e98] Change delimiter used for display of NextXID --> - Change the display format of NextXID in + Change the display format used for NextXID in pg_controldata and related places (Joe Conway, Bruce Momjian) @@ -383,8 +385,8 @@ This commit is also listed under libpq and psql 2015-09-16 [7aea8e4f2] Determine whether it's safe to attempt a parallel plan f --> - Provide infrastructure for marking the parallel-safe status of - functions (Robert Haas, Amit Kapila) + Provide infrastructure for marking the parallel-safety status of + functions (Robert Haas, Amit Kapila) @@ -432,8 +434,12 @@ This commit is also listed under libpq and psql Add gin_clean_pending_list() function to allow manual invocation of pending-list cleanup for a - GIN index, separately from vacuuming or analyzing the parent table - (Jeff Janes) + GIN index (Jeff Janes) + + + + Formerly, such cleanup happened only as a byproduct of vacuuming or + analyzing the parent table. @@ -711,7 +717,7 @@ This commit is also listed under libpq and psql If necessary, vacuum can be forced to process all-frozen pages using the new DISABLE_PAGE_SKIPPING option. - Normally, this should never be needed but it might help in + Normally this should never be needed, but it might help in recovering from visibility-map corruption. @@ -774,7 +780,7 @@ This commit is also listed under libpq and psql 2016-02-11 [d4c3a156c] Remove GROUP BY columns that are functionally dependent --> - Avoid computing GROUP BY columns if they are + Ignore GROUP BY columns that are functionally dependent on other columns (David Rowley) @@ -788,43 +794,21 @@ This commit is also listed under libpq and psql - - When appropriate, postpone evaluation of SELECT - output expressions until after an ORDER BY sort - (Konstantin Knizhnik) - - - - This change ensures that volatile or expensive functions in the - output list are executed in the order suggested by ORDER - BY, and that they are not evaluated more times than required - when there is a LIMIT clause. Previously, these - properties held if the ordering was performed by an index scan or - pre-merge-join sort, but not if it was performed by a top-level - sort. - - - - - Allow use of an index-only scan on a partial index when the index's WHERE - clause references columns which are not indexed (Tomas Vondra, + clause references columns that are not indexed (Tomas Vondra, Kyotaro Horiguchi) - For example, CREATE INDEX tidx_partial ON t(b) WHERE a - > 0 could not previously be used for an index-only scan by a - query that only referenced a in its WHERE - clause because a is not an indexed value like - b is. + For example, an index defined by CREATE INDEX tidx_partial + ON t(b) WHERE a > 0 can now be used for an index-only scan by + a query that specifies WHERE a > 0 and does not + otherwise use a. Previously this was disallowed + because a is not listed as an index column. @@ -875,11 +859,12 @@ This commit is also listed under libpq and psql On Linux, sync_file_range() is used for this purpose, - and the feature is on by default on Linux because that function has few - downsides. This sync capability is also available on other platforms - that have msync() or posix_fadvise(), - but those interfaces have some undesirable side-effects so the - feature is disabled by default on non-Linux platforms. + and the feature is on by default on Linux because that function has + few downsides. This flushing capability is also available on other + platforms if they have msync() + or posix_fadvise(), but those interfaces have some + undesirable side-effects so the feature is disabled by default on + non-Linux platforms. @@ -902,8 +887,8 @@ This commit is also listed under libpq and psql - For example, SELECT AVG(x), SUM(x) FROM x can use a - single per-row compuation for both aggregates. + For example, SELECT AVG(x), VARIANCE(x) FROM tab can use + a single per-row computation for both aggregates. @@ -913,9 +898,9 @@ This commit is also listed under libpq and psql --> Speed up visibility tests for recently-created tuples by checking - our transaction snapshot, not pg_clog, to decide - if the source transaction should be considered committed (Jeff - Janes, Tom Lane) + the current transaction's snapshot, not pg_clog, to + decide if the source transaction should be considered committed + (Jeff Janes, Tom Lane) @@ -940,10 +925,11 @@ This commit is also listed under libpq and psql Two-phase commit information is now written only to WAL - during PREPARE TRANSACTION, and read from - WAL during COMMIT PREPARED. A separate - state file is created only if the pending transaction does not - get committed or aborted by the time of the next checkpoint. + during PREPARE TRANSACTION, and will be read back from + WAL during COMMIT PREPARED if that happens + soon thereafter. A separate state file is created only if the + pending transaction does not get committed or aborted by the time + of the next checkpoint. @@ -1142,9 +1128,9 @@ This commit is also listed under libpq and psql This function returns an array of the process IDs of any sessions that are blocking the session with the given process ID. Historically users have obtained such information using a self-join - on the pg_locks view. However, it is unreasonably + on the pg_locks view. However, it is unreasonably tedious to do it that way with any modicum of correctness, and - the addition of parallel queries has made the approach entirely + the addition of parallel queries has made the old approach entirely impractical, since locks might be held or awaited by child worker processes rather than the session's main process. @@ -1181,7 +1167,7 @@ This commit is also listed under libpq and psql - The memory usage dump output to the postmaster log during an + The memory usage dump that is output to the postmaster log during an out-of-memory failure now summarizes statistics when there are a large number of memory contexts, rather than possibly generating a very large report. There is also a grand total @@ -1203,7 +1189,8 @@ This commit is also listed under libpq and psql 2016-04-08 [34c33a1f0] Add BSD authentication method. --> - Add an bsd authentication method to allow the use of + Add a bsd authentication + method to allow use of the BSD Authentication service for PostgreSQL client authentication (Marisa Emerson) @@ -1219,9 +1206,10 @@ This commit is also listed under libpq and psql 2016-04-08 [2f1d2b7a7] Set PAM_RHOST item for PAM authentication --> - When using PAM authentication, provide the client - IP address or host name to PAM modules via the - PAM_RHOST item (Grzegorz Sampolski) + When using PAM + authentication, provide the client IP address or host name + to PAM modules via the PAM_RHOST item + (Grzegorz Sampolski) @@ -1230,8 +1218,8 @@ This commit is also listed under libpq and psql 2016-01-07 [5e0b5dcab] Provide more detail in postmaster log for password authe --> - Provide detail in the postmaster log during more password - authentication failures (Tom Lane) + Provide detail in the postmaster log for more types of password + authentication failure (Tom Lane) @@ -1245,8 +1233,8 @@ This commit is also listed under libpq and psql 2015-09-06 [643beffe8] Support RADIUS passwords up to 128 characters --> - Support RADIUS passwords up to 128 characters long - (Marko Tiikkaja) + Support RADIUS passwords + up to 128 characters long (Marko Tiikkaja) @@ -1255,7 +1243,8 @@ This commit is also listed under libpq and psql 2016-04-08 [35e2e357c] Add authentication parameters compat_realm and upn_usena --> - Add new SSPI authentication parameters + Add new SSPI + authentication parameters compat_realm and upn_username to control whether NetBIOS or Kerberos realm names and user names are used during SSPI @@ -1302,30 +1291,13 @@ This commit is also listed under libpq and psql - - Add configure option - - - This allows the use of systemd service units of - type notify, which greatly simplifies the management - of PostgreSQL under systemd. - - - - - - Add log_line_prefix option %n to print - the current time as a Unix epoch, with milliseconds (Tomas Vondra, - Jeff Davis) + Add option %n to + print the current time in Unix epoch form, with milliseconds (Tomas + Vondra, Jeff Davis) @@ -1362,6 +1334,23 @@ This commit is also listed under libpq and psql + + Add configure option + + + This allows the use of systemd service units of + type notify, which greatly simplifies the management + of PostgreSQL under systemd. + + + + + @@ -1407,8 +1396,8 @@ This commit is also listed under libpq and psql but that is unsafe and inefficient. It also prevents a new postmaster from being started until the last old backend has exited. Backends will detect postmaster death when waiting for - client I/O, so the exit will not be instantaneous, but it in most - cases should happen no later than the end of the current query. + client I/O, so the exit will not be instantaneous, but it should + happen no later than the end of the current query. @@ -1541,7 +1530,8 @@ XXX this is pending backpatch, may need to remove --> Add a option to - pg_basebackup (Peter Eisentraut) + pg_basebackup + (Peter Eisentraut) @@ -1612,6 +1602,28 @@ XXX this is pending backpatch, may need to remove + + When appropriate, postpone evaluation of SELECT + output expressions until after an ORDER BY sort + (Konstantin Knizhnik) + + + + This change ensures that volatile or expensive functions in the + output list are executed in the order suggested by ORDER + BY, and that they are not evaluated more times than required + when there is a LIMIT clause. Previously, these + properties held if the ordering was performed by an index scan or + pre-merge-join sort, but not if it was performed by a top-level + sort. + + + + + @@ -1663,8 +1675,8 @@ XXX this is pending backpatch, may need to remove Previously, the foreign join pushdown infrastructure left the question of security entirely up to individual foreign data - wrappers, but it would be too easy for an FDW to - inadvertently open up subtle security hole. So, make it the core + wrappers, but that made it too easy for an FDW to + inadvertently create subtle security holes. So, make it the core code's job to determine which role ID will access each table, and do not attempt join pushdown unless the role is the same for all relevant relations. @@ -1707,7 +1719,7 @@ XXX this is pending backpatch, may need to remove This command allows a database object to be marked as depending - on an extension, so that it will be automatically dropped if + on an extension, so that it will be dropped automatically if the extension is dropped (without needing CASCADE). However, the object is not part of the extension, and thus will be dumped separately by pg_dump. @@ -1777,8 +1789,8 @@ XXX this is pending backpatch, may need to remove --> Add a CASCADE option to CREATE - EXTENSION to automatically create extensions it depends - on (Petr Jelínek) + EXTENSION to automatically create any extensions the + requested one depends on (Petr Jelínek) @@ -1803,7 +1815,7 @@ XXX this is pending backpatch, may need to remove - This is possible because the table has no existing rows. This matches + This is safe because the table has no existing rows. This matches the longstanding behavior of FOREIGN KEY constraints. @@ -1918,10 +1930,10 @@ XXX this is pending backpatch, may need to remove 2016-06-27 [6734a1cac] Change predecence of phrase operator. --> - Improve full-text search to support searching for phrases, that - is, lexemes appearing adjacent to each other in a specific order, - or with a specified distance between them (Teodor Sigaev, Oleg - Bartunov, Dmitry Ivanov) + Improve full-text search to support + searching for phrases, that is, lexemes appearing adjacent to each + other in a specific order, or with a specified distance between + them (Teodor Sigaev, Oleg Bartunov, Dmitry Ivanov) @@ -2001,9 +2013,10 @@ XXX this is pending backpatch, may need to remove 2016-03-17 [f4ceed6ce] Improve support of Hunspell --> - Upgrade the ispell dictionary to handle modern - Hunspell files and support more languages - (Artur Zakirov) + Upgrade + the ispell + dictionary type to handle modern Hunspell files and + support more languages (Artur Zakirov) @@ -2012,7 +2025,9 @@ XXX this is pending backpatch, may need to remove 2015-10-30 [12c9a0400] Implement lookbehind constraints in our regular-expressi --> - Implement look-behind constraints in regular expressions (Tom Lane) + Implement look-behind constraints + in regular expressions + (Tom Lane) @@ -2044,7 +2059,7 @@ XXX this is pending backpatch, may need to remove 2015-11-07 [c5e86ea93] Add "xid <> xid" and "xid <> int4" operators. --> - Add transaction id operators xid <> + Add transaction ID operators xid <> xid and xid <> int4, for consistency with the corresponding equality operators (Michael Paquier) @@ -2090,8 +2105,10 @@ XXX this is pending backpatch, may need to remove 2016-01-05 [abb173392] Add scale(numeric) --> - Add a scale(numeric) function to extract the display - scale of a numeric value (Marko Tiikkaja) + Add a scale(numeric) + function to extract the display scale of a numeric value + (Marko Tiikkaja) @@ -2109,7 +2126,7 @@ XXX this is pending backpatch, may need to remove measures its argument in degrees, whereas sin() measures in radians. These functions go to some lengths to deliver exact results for values where an exact result can be - expected, e.g. sind(30) = 0.5. + expected, for instance sind(30) = 0.5. @@ -2125,9 +2142,9 @@ XXX this is pending backpatch, may need to remove The POSIX standard says that these functions should - return NaN for NaN input, and should throw an error for - out-of-range inputs including infinity. Previously our - behavior varied across platforms. + return NaN for NaN input, and should throw + an error for out-of-range inputs including infinity. + Previously our behavior varied across platforms. @@ -2136,9 +2153,10 @@ XXX this is pending backpatch, may need to remove 2016-03-29 [e511d878f] Allow to_timestamp(float8) to convert float infinity to --> - Make to_timestamp(float8) convert float - infinity to timestamp infinity (Vitaly - Burovoy) + Make to_timestamp(float8) + convert float infinity to + timestamp infinity (Vitaly Burovoy) @@ -2170,11 +2188,12 @@ XXX this is pending backpatch, may need to remove 2015-09-17 [9acb9007d] Fix oversight in tsearch type check --> - Allow ts_stat_sql() and - tsvector_update_trigger() to operate on values that - are of types binary-compatible with the expected argument type, - not just that argument type; for example allow citext - where text is expected (Teodor Sigaev) + Allow ts_stat() + and tsvector_update_trigger() + to operate on values that are of types binary-compatible with the + expected argument type, not only that argument type; for example + allow citext where text is expected (Teodor + Sigaev) @@ -2216,8 +2235,9 @@ XXX this is pending backpatch, may need to remove In to_number(), - interpret V as dividing by 10 to the power of the - number of digits following V (Bruce Momjian) + interpret a V format code as dividing by 10 to the + power of the number of digits following V (Bruce + Momjian) @@ -2231,8 +2251,10 @@ XXX this is pending backpatch, may need to remove 2016-01-05 [ea0d494da] Make the to_reg*() functions accept text not cstring. --> - Make the to_reg*() functions accept type text - not cstring (Petr Korobeinikov) + Make the to_reg*() + functions accept type text not cstring + (Petr Korobeinikov) @@ -2289,7 +2311,7 @@ XXX this is pending backpatch, may need to remove This allows avoiding an error for an unrecognized parameter - name, and instead return a NULL. + name, instead returning a NULL. @@ -2348,7 +2370,7 @@ XXX this is pending backpatch, may need to remove In PL/pgSQL, detect mismatched CONTINUE and EXIT statements while - compiling PL/pgSQL functions, rather than at execution time + compiling a function, rather than at execution time (Jim Nasby) @@ -2453,8 +2475,9 @@ XXX this is pending backpatch, may need to remove 2016-08-26 [e796d0aba] Add a nonlocalized version of the severity field to clie --> - Add a nonlocalized version of the severity field in error and notice - messages (Tom Lane) + Add a nonlocalized version of + the severity field in + error and notice messages (Tom Lane) @@ -2495,6 +2518,8 @@ This commit is also listed under psql and PL/pgSQL + This is done with the new function PQresultVerboseErrorMessage(). This supports psql's new \errverbose feature, and may be useful for other clients as well. @@ -2541,8 +2566,10 @@ This commit is also listed under psql and PL/pgSQL 2015-09-14 [d02426029] Check existency of table/schema for -t/-n option (pg_dum --> - Add a @@ -2594,6 +2621,22 @@ This commit is also listed under psql and PL/pgSQL + + Support multiple and + command-line options (Pavel Stehule, Catalin Iacob) + + + + The specified operations are carried out in the order in which the + options are given, and then psql terminates. + + + + + @@ -2679,7 +2722,7 @@ This commit is also listed under psql and PL/pgSQL 2016-06-15 [9901d8ac2] Use strftime("%c") to format timestamps in psql's \watch --> - Improve the headers output of the \watch command + Improve the headers output by the \watch command (Michael Paquier, Tom Lane) @@ -2790,8 +2833,9 @@ This commit is also listed under libpq and PL/pgSQL This change allows SQL commands in scripts to span multiple lines. Existing custom scripts will need to be modified to add a semicolon - at the end of each line if missing. (Doing so does not break - the script for use with older versions of pgbench.) + at the end of each line that does not have one already. (Doing so + does not break the script for use with older versions + of pgbench.) @@ -2960,8 +3004,9 @@ This commit is also listed under libpq and PL/pgSQL 2015-12-01 [e50cda784] Use pg_rewind when target timeline was switched --> - Improve pg_rewind so that it can work when the - target timeline changes (Alexander Korotkov) + Improve pg_rewind + so that it can work when the target timeline changes (Alexander + Korotkov) @@ -3095,8 +3140,9 @@ This commit is also listed under libpq and PL/pgSQL 2016-08-13 [ed0097e4f] Add SQL-accessible functions for inspecting index AM pro --> - Restructure index access method API to hide most of - it at the C level (Alexander Korotkov, Andrew Gierth) + Restructure index access + method API to hide most of it at + the C level (Alexander Korotkov, Andrew Gierth) @@ -3118,9 +3164,11 @@ This commit is also listed under libpq and PL/pgSQL 2016-04-06 [6c268df12] Add new catalog called pg_init_privs --> - Add pg_init_privs system catalog to hold original - privileges of initdb-created and extension-created - objects (Stephen Frost) + Add pg_init_privs + system catalog to hold original privileges + of initdb-created and extension-created objects + (Stephen Frost) @@ -3315,7 +3363,7 @@ This commit is also listed under libpq and PL/pgSQL This is somewhat like the reconstructed value, but it - could be any arbitrary chunk of data, it need not be of the same + could be any arbitrary chunk of data, not necessarily of the same data type as the indexed column. @@ -3367,9 +3415,10 @@ This commit is also listed under libpq and PL/pgSQL 2016-03-13 [7a8d87483] Rename auto_explain.sample_ratio to sample_rate --> - Add configuration parameter auto_explain.sample_rate - to allow contrib/auto_explain to capture just a - configurable fraction of all queries (Craig Ringer, Julien Rouhaud) + Add configuration parameter auto_explain.sample_rate to + allow contrib/auto_explain + to capture just a configurable fraction of all queries (Craig + Ringer, Julien Rouhaud) @@ -3383,9 +3432,9 @@ This commit is also listed under libpq and PL/pgSQL 2016-04-01 [9ee014fc8] Bloom index contrib module --> - Add contrib/bloom module that implements an index - access method based on Bloom filtering (Teodor Sigaev, Alexander - Korotkov) + Add contrib/bloom module that + implements an index access method based on Bloom filtering (Teodor + Sigaev, Alexander Korotkov) @@ -3401,9 +3450,9 @@ This commit is also listed under libpq and PL/pgSQL 2015-12-28 [81ee726d8] Code and docs review for cube kNN support. --> - In contrib/cube, introduce distance operators for - cubes, and support kNN-style searches in GiST indexes on cube - columns (Stas Kelvich) + In contrib/cube, introduce + distance operators for cubes, and support kNN-style searches in + GiST indexes on cube columns (Stas Kelvich) @@ -3434,8 +3483,9 @@ This commit is also listed under libpq and PL/pgSQL --> Add selectivity estimation functions for - contrib/intarray operators to improve plans for - queries using those operators (Yury Zhuravlev, Alexander Korotkov) + contrib/intarray operators + to improve plans for queries using those operators (Yury Zhuravlev, + Alexander Korotkov) @@ -3470,7 +3520,8 @@ This commit is also listed under libpq and PL/pgSQL --> Add support for word similarity to - contrib/pg_trgm (Alexander Korotkov, Artur Zakirov) + contrib/pg_trgm + (Alexander Korotkov, Artur Zakirov) @@ -3486,9 +3537,8 @@ This commit is also listed under libpq and PL/pgSQL --> Add configuration parameter - pg_trgm.similarity_threshold for contrib/pg_trgm's similarity - threshold (Artur Zakirov) + pg_trgm.similarity_threshold for + contrib/pg_trgm's similarity threshold (Artur Zakirov) @@ -3525,8 +3575,9 @@ This commit is also listed under libpq and PL/pgSQL 2016-06-17 [71d05a2c7] pg_visibility: Add pg_truncate_visibility_map function. --> - Add contrib/pg_visibility module to allow examining - table visibility maps (Robert Haas) + Add contrib/pg_visibility module + to allow examining table visibility maps (Robert Haas) @@ -3545,7 +3596,7 @@ This commit is also listed under libpq and PL/pgSQL - <filename>postgres_fdw</> + <link linkend="postgres-fdw"><filename>postgres_fdw</></> @@ -3597,7 +3648,7 @@ This commit is also listed under libpq and PL/pgSQL - Formerly, this involved sending a SELECT FOR UPDATE + Formerly, remote updates involved sending a SELECT FOR UPDATE command and then updating or deleting the selected rows one-by-one. While that is still necessary if the operation requires any local processing, it can now be done remotely if all elements of the