diff options
Diffstat (limited to 'doc/src/sgml/release-9.6.sgml')
| -rw-r--r-- | doc/src/sgml/release-9.6.sgml | 2028 |
1 files changed, 1267 insertions, 761 deletions
diff --git a/doc/src/sgml/release-9.6.sgml b/doc/src/sgml/release-9.6.sgml index dc811c4ca5d..5e358ef4b4d 100644 --- a/doc/src/sgml/release-9.6.sgml +++ b/doc/src/sgml/release-9.6.sgml @@ -1,6 +1,512 @@ <!-- doc/src/sgml/release-9.6.sgml --> <!-- See header comment in release.sgml about typical markup --> + <sect1 id="release-9-6-6"> + <title>Release 9.6.6</title> + + <formalpara> + <title>Release date:</title> + <para>2017-11-09</para> + </formalpara> + + <para> + This release contains a variety of fixes from 9.6.5. + For information about new features in the 9.6 major release, see + <xref linkend="release-9-6">. + </para> + + <sect2> + <title>Migration to Version 9.6.6</title> + + <para> + A dump/restore is not required for those running 9.6.X. + </para> + + <para> + However, if you use BRIN indexes, see the first changelog entry below. + </para> + + <para> + Also, if you are upgrading from a version earlier than 9.6.4, + see <xref linkend="release-9-6-4">. + </para> + </sect2> + + <sect2> + <title>Changes</title> + + <itemizedlist> + + <listitem> + <para> + Fix BRIN index summarization to handle concurrent table extension + correctly (Álvaro Herrera) + </para> + + <para> + Previously, a race condition allowed some table rows to be omitted from + the index. It may be necessary to reindex existing BRIN indexes to + recover from past occurrences of this problem. + </para> + </listitem> + + <listitem> + <para> + Fix possible failures during concurrent updates of a BRIN index + (Tom Lane) + </para> + + <para> + These race conditions could result in errors like <quote>invalid index + offnum</quote> or <quote>inconsistent range map</quote>. + </para> + </listitem> + + <listitem> + <para> + Fix crash when logical decoding is invoked from a SPI-using function, + in particular any function written in a PL language + (Tom Lane) + </para> + </listitem> + + <listitem> + <para> + Fix incorrect query results when multiple <literal>GROUPING + SETS</literal> columns contain the same simple variable (Tom Lane) + </para> + </listitem> + + <listitem> + <para> + Fix incorrect parallelization decisions for nested queries + (Amit Kapila, Kuntal Ghosh) + </para> + </listitem> + + <listitem> + <para> + Fix parallel query handling to not fail when a recently-used role is + dropped (Amit Kapila) + </para> + </listitem> + + <listitem> + <para> + Fix <function>json_build_array()</function>, + <function>json_build_object()</function>, and their <type>jsonb</type> + equivalents to handle explicit <literal>VARIADIC</literal> arguments + correctly (Michael Paquier) + </para> + </listitem> + + <listitem> +<!-- +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: master [7769fc000] 2017-09-27 17:05:53 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [07ea925e2] 2017-09-27 17:05:53 -0400 +Branch: REL9_6_STABLE [def03e4bf] 2017-09-27 17:05:53 -0400 +Branch: REL9_5_STABLE [ad56dbd6c] 2017-09-27 17:05:53 -0400 +Branch: REL9_4_STABLE [c38575edc] 2017-09-27 17:05:53 -0400 +Branch: REL9_3_STABLE [2e82fba0e] 2017-09-27 17:05:54 -0400 +Branch: REL9_2_STABLE [72d4fd08e] 2017-09-27 17:05:54 -0400 +--> + <para> + Properly reject attempts to convert infinite float values to + type <type>numeric</type> (Tom Lane, KaiGai Kohei) + </para> + + <para> + Previously the behavior was platform-dependent. + </para> + </listitem> + + <listitem> + <para> + Fix corner-case crashes when columns have been added to the end of a + view (Tom Lane) + </para> + </listitem> + + <listitem> + <para> + Record proper dependencies when a view or rule + contains <structname>FieldSelect</structname> + or <structname>FieldStore</structname> expression nodes (Tom Lane) + </para> + + <para> + Lack of these dependencies could allow a column or data + type <command>DROP</command> to go through when it ought to fail, + thereby causing later uses of the view or rule to get errors. + This patch does not do anything to protect existing views/rules, + only ones created in the future. + </para> + </listitem> + + <listitem> + <para> + Correctly detect hashability of range data types (Tom Lane) + </para> + + <para> + The planner mistakenly assumed that any range type could be hashed + for use in hash joins or hash aggregation, but actually it must check + whether the range's subtype has hash support. This does not affect any + of the built-in range types, since they're all hashable anyway. + </para> + </listitem> + + <listitem> +<!-- +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: master [6f44fe7f1] 2017-09-17 15:28:51 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [244b4a37e] 2017-09-17 15:28:51 -0400 +Branch: REL9_6_STABLE [86e4ebb9a] 2017-09-17 15:28:51 -0400 +Branch: REL9_5_STABLE [eeff68396] 2017-09-17 15:28:51 -0400 +--> + <para> + Correctly ignore <structname>RelabelType</structname> expression nodes + when determining relation distinctness (David Rowley) + </para> + + <para> + This allows the intended optimization to occur when a subquery has + a result column of type <type>varchar</type>. + </para> + </listitem> + + <listitem> + <para> + Prevent sharing transition states between ordered-set aggregates + (David Rowley) + </para> + + <para> + This causes a crash with the built-in ordered-set aggregates, and + probably with user-written ones as well. v11 and later will include + provisions for dealing with such cases safely, but in released + branches, just disable the optimization. + </para> + </listitem> + + <listitem> + <para> + Prevent <varname>idle_in_transaction_session_timeout</varname> from + being ignored when a <varname>statement_timeout</varname> occurred + earlier (Lukas Fittl) + </para> + </listitem> + + <listitem> + <para> + Fix low-probability loss of <command>NOTIFY</command> messages due to + XID wraparound (Marko Tiikkaja, Tom Lane) + </para> + + <para> + If a session executed no queries, but merely listened for + notifications, for more than 2 billion transactions, it started to miss + some notifications from concurrently-committing transactions. + </para> + </listitem> + + <listitem> +<!-- +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: master [899bd785c] 2017-09-25 16:09:19 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [4621c7f7a] 2017-09-25 16:09:19 -0400 +Branch: REL9_6_STABLE [175061222] 2017-09-25 16:09:20 -0400 +Branch: REL9_5_STABLE [05297416f] 2017-09-25 16:09:20 -0400 +Branch: REL9_4_STABLE [3a07a6f3e] 2017-09-25 16:09:20 -0400 +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: master [5ea96efaa] 2017-09-26 13:42:53 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [d29f30d8c] 2017-09-26 13:43:00 -0400 +Branch: REL9_6_STABLE [12ac252f9] 2017-09-26 13:43:07 -0400 +Branch: REL9_5_STABLE [06852f215] 2017-09-26 13:43:12 -0400 +Branch: REL9_4_STABLE [e5c058e2e] 2017-09-26 13:43:17 -0400 +--> + <para> + Avoid <systemitem>SIGBUS</systemitem> crash on Linux when a DSM memory + request exceeds the space available in <systemitem>tmpfs</systemitem> + (Thomas Munro) + </para> + </listitem> + + <listitem> + <para> + Reduce the frequency of data flush requests during bulk file copies to + avoid performance problems on macOS, particularly with its new APFS + file system (Tom Lane) + </para> + </listitem> + + <listitem> +<!-- +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: master [27c6619e9] 2017-09-17 14:50:01 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [66fe509be] 2017-09-17 14:50:01 -0400 +Branch: REL9_6_STABLE [c0d21bdb8] 2017-09-17 14:50:01 -0400 +Branch: REL9_5_STABLE [825fac5d3] 2017-09-17 14:50:01 -0400 +Branch: REL9_4_STABLE [bc0974703] 2017-09-17 14:50:01 -0400 +Branch: REL9_3_STABLE [b1be33593] 2017-09-17 14:50:01 -0400 +Branch: REL9_2_STABLE [4cd6cd21d] 2017-09-17 14:50:01 -0400 +--> + <para> + Prevent low-probability crash in processing of nested trigger firings + (Tom Lane) + </para> + </listitem> + + <listitem> + <para> + Allow <command>COPY</command>'s <literal>FREEZE</literal> option to + work when the transaction isolation level is <literal>REPEATABLE + READ</literal> or higher (Noah Misch) + </para> + + <para> + This case was unintentionally broken by a previous bug fix. + </para> + </listitem> + + <listitem> +<!-- +Author: Peter Eisentraut <peter_e@gmx.net> +Branch: master [aa6b7b72d] 2017-09-22 17:10:36 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [3d7f11a0f] 2017-09-23 10:03:05 -0400 +Branch: REL9_6_STABLE [a1f30ecc5] 2017-09-23 10:03:36 -0400 +Branch: REL9_5_STABLE [acae13faa] 2017-09-23 10:04:55 -0400 +Branch: REL9_4_STABLE [9bf049946] 2017-09-23 10:05:28 -0400 +Branch: REL9_3_STABLE [e0f5710c5] 2017-09-23 10:05:40 -0400 +Branch: REL9_2_STABLE [2eb84e54a] 2017-09-23 10:14:30 -0400 +--> + <para> + Correctly restore the umask setting when file creation fails + in <command>COPY</command> or <function>lo_export()</function> + (Peter Eisentraut) + </para> + </listitem> + + <listitem> +<!-- +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: master [714805010] 2017-09-21 18:13:11 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [a2b1eb234] 2017-09-21 18:13:11 -0400 +Branch: REL9_6_STABLE [ea31541f5] 2017-09-21 18:13:11 -0400 +Branch: REL9_5_STABLE [122289a66] 2017-09-21 18:13:11 -0400 +Branch: REL9_4_STABLE [b572b435c] 2017-09-21 18:13:11 -0400 +Branch: REL9_3_STABLE [a09d8be7d] 2017-09-21 18:13:11 -0400 +Branch: REL9_2_STABLE [e56facd8b] 2017-09-21 18:13:11 -0400 +--> + <para> + Give a better error message for duplicate column names + in <command>ANALYZE</command> (Nathan Bossart) + </para> + </listitem> + + <listitem> +<!-- +Author: Robert Haas <rhaas@postgresql.org> +Branch: master [81276fdd3] 2017-09-14 17:19:04 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [a2a61f633] 2017-09-14 16:44:01 -0400 +Branch: REL9_6_STABLE [353328ad1] 2017-09-14 16:47:11 -0400 +--> + <para> + Add missing cases in <function>GetCommandLogLevel()</function>, + preventing errors when certain SQL commands are used while + <varname>log_statement</varname> is set to <literal>ddl</literal> + (Michael Paquier) + </para> + </listitem> + + <listitem> +<!-- +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: REL9_6_STABLE [2ac598874] 2017-10-17 12:15:08 -0400 +Branch: REL9_5_STABLE [9e20276e1] 2017-10-17 12:15:08 -0400 +Branch: REL9_4_STABLE [38f17e8ee] 2017-10-17 12:15:08 -0400 +Branch: REL9_3_STABLE [06b2a73ed] 2017-10-17 12:15:08 -0400 +--> + <para> + Fix mis-parsing of the last line in a + non-newline-terminated <filename>pg_hba.conf</filename> file + (Tom Lane) + </para> + </listitem> + + <listitem> + <para> + Fix <function>AggGetAggref()</function> to return the + correct <structname>Aggref</structname> nodes to aggregate final + functions whose transition calculations have been merged (Tom Lane) + </para> + </listitem> + + <listitem> +<!-- +Author: Stephen Frost <sfrost@snowman.net> +Branch: master [d2e40b310] 2017-09-13 20:02:09 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [68a7c24fd] 2017-09-13 20:04:43 -0400 +Branch: REL9_6_STABLE [caae416aa] 2017-09-13 20:02:27 -0400 +--> + <para> + Fix <application>pg_dump</application> to ensure that it + emits <command>GRANT</command> commands in a valid order + (Stephen Frost) + </para> + </listitem> + + <listitem> + <para> + Fix <application>pg_basebackup</application>'s matching of tablespace + paths to canonicalize both paths before comparing (Michael Paquier) + </para> + + <para> + This is particularly helpful on Windows. + </para> + </listitem> + + <listitem> + <para> + Fix <application>libpq</application> to not require user's home + directory to exist (Tom Lane) + </para> + + <para> + In v10, failure to find the home directory while trying to + read <filename>~/.pgpass</filename> was treated as a hard error, + but it should just cause that file to not be found. Both v10 and + previous release branches made the same mistake when + reading <filename>~/.pg_service.conf</filename>, though this was less + obvious since that file is not sought unless a service name is + specified. + </para> + </listitem> + + <listitem> +<!-- +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: master [2e70d6b5e] 2017-08-29 15:18:01 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [b481b39b8] 2017-08-29 15:18:01 -0400 +Branch: REL9_6_STABLE [bc95e5874] 2017-08-29 15:18:01 -0400 +Branch: REL9_5_STABLE [dfd1042c6] 2017-08-29 15:18:01 -0400 +Branch: REL9_4_STABLE [1c53722ff] 2017-08-29 15:18:01 -0400 +Branch: REL9_3_STABLE [d391fb6c3] 2017-08-29 15:18:01 -0400 +Branch: REL9_2_STABLE [a07058a6d] 2017-08-29 15:18:01 -0400 +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: master [9d6b160d7] 2017-09-01 15:14:46 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [f2fe1cbef] 2017-09-01 15:14:18 -0400 +Branch: REL9_6_STABLE [3a0f8e7d3] 2017-09-01 15:14:18 -0400 +Branch: REL9_5_STABLE [1305186de] 2017-09-01 15:14:18 -0400 +Branch: REL9_4_STABLE [53863ebeb] 2017-09-01 15:14:18 -0400 +Branch: REL9_3_STABLE [dd344de67] 2017-09-01 15:14:18 -0400 +Branch: REL9_2_STABLE [f60a236ba] 2017-09-01 15:14:18 -0400 +--> + <para> + Fix <application>libpq</application> to guard against integer + overflow in the row count of a <structname>PGresult</structname> + (Michael Paquier) + </para> + </listitem> + + <listitem> +<!-- +Author: Michael Meskes <meskes@postgresql.org> +Branch: master [35e156882] 2017-09-12 04:53:36 +0200 +Branch: REL_10_STABLE Release: REL_10_0 [75fbf8ad1] 2017-09-18 23:07:18 +0200 +Branch: REL9_6_STABLE [59b5a3e5c] 2017-09-18 23:07:34 +0200 +Branch: REL9_5_STABLE [3a5aa7de3] 2017-09-18 23:07:44 +0200 +Branch: REL9_4_STABLE [e5b8b771e] 2017-09-18 23:08:17 +0200 +Branch: REL9_3_STABLE [149cfdb3a] 2017-09-18 23:08:24 +0200 +--> + <para> + Fix <application>ecpg</application>'s handling of out-of-scope cursor + declarations with pointer or array variables (Michael Meskes) + </para> + </listitem> + + <listitem> + <para> + In ecpglib, correctly handle backslashes in string literals depending + on whether <varname>standard_conforming_strings</varname> is set + (Tsunakawa Takayuki) + </para> + </listitem> + + <listitem> + <para> + Make ecpglib's Informix-compatibility mode ignore fractional digits in + integer input strings, as expected (Gao Zengqi, Michael Meskes) + </para> + </listitem> + + <listitem> +<!-- +Author: Michael Meskes <meskes@postgresql.org> +Branch: master [a772624b1] 2017-08-26 12:57:21 +0200 +Branch: REL_10_STABLE Release: REL_10_0 [38d7cb67f] 2017-09-14 00:47:03 +0200 +Branch: REL9_6_STABLE [839ee1811] 2017-09-14 01:17:03 +0200 +Author: Michael Meskes <meskes@postgresql.org> +Branch: master [04fbe0e45] 2017-08-26 19:11:58 +0200 +Branch: REL_10_STABLE Release: REL_10_0 [eaf7001eb] 2017-09-14 00:47:08 +0200 +Branch: REL9_6_STABLE [407e66078] 2017-09-14 01:17:15 +0200 +--> + <para> + Fix <application>ecpg</application>'s regression tests to work reliably + on Windows (Christian Ullrich, Michael Meskes) + </para> + </listitem> + + <listitem> +<!-- +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: master [47f849a3c] 2017-09-22 00:04:29 -0400 +Branch: REL_10_STABLE Release: REL_10_0 [3876b16ce] 2017-09-22 00:04:21 -0400 +Branch: REL9_6_STABLE [e25f4401d] 2017-09-22 00:04:21 -0400 +Branch: REL9_5_STABLE [89f02e17a] 2017-09-22 00:04:21 -0400 +Branch: REL9_4_STABLE [dbd6099fb] 2017-09-22 00:04:21 -0400 +Branch: REL9_3_STABLE [2020f90bf] 2017-09-22 00:04:21 -0400 +Branch: REL9_2_STABLE [a07105afa] 2017-09-22 00:04:21 -0400 +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: master [24a1897ab] 2017-10-23 17:54:09 -0400 +Branch: REL_10_STABLE [dffe7fbc2] 2017-10-23 17:54:09 -0400 +Branch: REL9_6_STABLE [173b7a4a7] 2017-10-23 17:54:09 -0400 +Branch: REL9_5_STABLE [4b433a8b0] 2017-10-23 17:54:09 -0400 +Branch: REL9_4_STABLE [876e076eb] 2017-10-23 17:54:09 -0400 +Branch: REL9_3_STABLE [9c74dd2d5] 2017-10-23 17:54:09 -0400 +Branch: REL9_2_STABLE [1317d1301] 2017-10-23 17:54:09 -0400 +--> + <para> + Sync our copy of the timezone library with IANA release tzcode2017c + (Tom Lane) + </para> + + <para> + This fixes various issues; the only one likely to be user-visible + is that the default DST rules for a POSIX-style zone name, if + no <filename>posixrules</filename> file exists in the timezone data + directory, now match current US law rather than what it was a dozen + years ago. + </para> + </listitem> + + <listitem> + <para> + Update time zone data files to <application>tzdata</application> + release 2017c for DST law changes in Fiji, Namibia, Northern Cyprus, + Sudan, Tonga, and Turks & Caicos Islands, plus historical + corrections for Alaska, Apia, Burma, Calcutta, Detroit, Ireland, + Namibia, and Pago Pago. + </para> + </listitem> + + </itemizedlist> + + </sect2> + </sect1> + <sect1 id="release-9-6-5"> <title>Release 9.6.5</title> @@ -46,20 +552,20 @@ Branch: REL9_2_STABLE [98e6784aa] 2017-08-15 19:33:04 -0400 --> <para> Show foreign tables - in <structname>information_schema</>.<structname>table_privileges</> + in <structname>information_schema</structname>.<structname>table_privileges</structname> view (Peter Eisentraut) </para> <para> - All other relevant <structname>information_schema</> views include + All other relevant <structname>information_schema</structname> views include foreign tables, but this one ignored them. </para> <para> - Since this view definition is installed by <application>initdb</>, + Since this view definition is installed by <application>initdb</application>, merely upgrading will not fix the problem. If you need to fix this in an existing installation, you can, as a superuser, do this - in <application>psql</>: + in <application>psql</application>: <programlisting> SET search_path TO information_schema; CREATE OR REPLACE VIEW table_privileges AS @@ -98,7 +604,7 @@ CREATE OR REPLACE VIEW table_privileges AS OR grantee.rolname = 'PUBLIC'); </programlisting> This must be repeated in each database to be fixed, - including <literal>template0</>. + including <literal>template0</literal>. </para> </listitem> @@ -114,14 +620,14 @@ Branch: REL9_2_STABLE [8ae41ceae] 2017-08-14 15:43:20 -0400 --> <para> Clean up handling of a fatal exit (e.g., due to receipt - of <systemitem>SIGTERM</>) that occurs while trying to execute - a <command>ROLLBACK</> of a failed transaction (Tom Lane) + of <systemitem>SIGTERM</systemitem>) that occurs while trying to execute + a <command>ROLLBACK</command> of a failed transaction (Tom Lane) </para> <para> This situation could result in an assertion failure. In production builds, the exit would still occur, but it would log an unexpected - message about <quote>cannot drop active portal</>. + message about <quote>cannot drop active portal</quote>. </para> </listitem> @@ -156,7 +662,7 @@ Branch: REL9_2_STABLE [4e704aac1] 2017-08-09 17:03:10 -0400 </para> <para> - Certain <command>ALTER</> commands that change the definition of a + Certain <command>ALTER</command> commands that change the definition of a composite type or domain type are supposed to fail if there are any stored values of that type in the database, because they lack the infrastructure needed to update or check such values. Previously, @@ -189,7 +695,7 @@ Branch: REL9_4_STABLE [59dde9fed] 2017-08-19 13:39:38 -0400 Branch: REL9_3_STABLE [ece4bd901] 2017-08-19 13:39:38 -0400 --> <para> - Fix crash in <application>pg_restore</> when using parallel mode and + Fix crash in <application>pg_restore</application> when using parallel mode and using a list file to select a subset of items to restore (Fabrízio de Royes Mello) </para> @@ -206,13 +712,13 @@ Branch: REL9_3_STABLE [f8bc6b2f6] 2017-08-16 13:30:09 +0200 Branch: REL9_2_STABLE [60b135c82] 2017-08-16 13:30:20 +0200 --> <para> - Change <application>ecpg</>'s parser to allow <literal>RETURNING</> + Change <application>ecpg</application>'s parser to allow <literal>RETURNING</literal> clauses without attached C variables (Michael Meskes) </para> <para> - This allows <application>ecpg</> programs to contain SQL constructs - that use <literal>RETURNING</> internally (for example, inside a CTE) + This allows <application>ecpg</application> programs to contain SQL constructs + that use <literal>RETURNING</literal> internally (for example, inside a CTE) rather than using it to define values to be returned to the client. </para> </listitem> @@ -225,7 +731,7 @@ Branch: REL_10_STABLE [a6b174f55] 2017-08-16 13:27:21 +0200 Branch: REL9_6_STABLE [954490fec] 2017-08-16 13:28:10 +0200 --> <para> - Change <application>ecpg</>'s parser to recognize backslash + Change <application>ecpg</application>'s parser to recognize backslash continuation of C preprocessor command lines (Michael Meskes) </para> </listitem> @@ -253,12 +759,12 @@ Branch: REL9_2_STABLE [f7e4783dd] 2017-08-17 13:15:46 -0400 <para> This fix avoids possible crashes of PL/Perl due to inconsistent - assumptions about the width of <type>time_t</> values. + assumptions about the width of <type>time_t</type> values. A side-effect that may be visible to extension developers is - that <literal>_USE_32BIT_TIME_T</> is no longer defined globally - in <productname>PostgreSQL</> Windows builds. This is not expected - to cause problems, because type <type>time_t</> is not used - in any <productname>PostgreSQL</> API definitions. + that <literal>_USE_32BIT_TIME_T</literal> is no longer defined globally + in <productname>PostgreSQL</productname> Windows builds. This is not expected + to cause problems, because type <type>time_t</type> is not used + in any <productname>PostgreSQL</productname> API definitions. </para> </listitem> @@ -270,7 +776,7 @@ Branch: REL9_6_STABLE [fc2aafe4a] 2017-08-09 12:06:08 -0400 Branch: REL9_5_STABLE [a784d5f21] 2017-08-09 12:06:14 -0400 --> <para> - Fix <literal>make check</> to behave correctly when invoked via a + Fix <literal>make check</literal> to behave correctly when invoked via a non-GNU make program (Thomas Munro) </para> </listitem> @@ -329,7 +835,7 @@ Branch: REL9_2_STABLE [e255e97a2] 2017-08-07 07:09:32 -0700 --> <para> Further restrict visibility - of <structname>pg_user_mappings</>.<structfield>umoptions</>, to + of <structname>pg_user_mappings</structname>.<structfield>umoptions</structfield>, to protect passwords stored as user mapping options (Noah Misch) </para> @@ -337,11 +843,11 @@ Branch: REL9_2_STABLE [e255e97a2] 2017-08-07 07:09:32 -0700 <para> The fix for CVE-2017-7486 was incorrect: it allowed a user to see the options in her own user mapping, even if she did not - have <literal>USAGE</> permission on the associated foreign server. + have <literal>USAGE</literal> permission on the associated foreign server. Such options might include a password that had been provided by the server owner rather than the user herself. - Since <structname>information_schema.user_mapping_options</> does not - show the options in such cases, <structname>pg_user_mappings</> + Since <structname>information_schema.user_mapping_options</structname> does not + show the options in such cases, <structname>pg_user_mappings</structname> should not either. (CVE-2017-7547) </para> @@ -356,15 +862,15 @@ Branch: REL9_2_STABLE [e255e97a2] 2017-08-07 07:09:32 -0700 <step> <para> Restart the postmaster after adding <literal>allow_system_table_mods - = true</> to <filename>postgresql.conf</>. (In versions - supporting <command>ALTER SYSTEM</>, you can use that to make the + = true</literal> to <filename>postgresql.conf</filename>. (In versions + supporting <command>ALTER SYSTEM</command>, you can use that to make the configuration change, but you'll still need a restart.) </para> </step> <step> <para> - In <emphasis>each</> database of the cluster, + In <emphasis>each</emphasis> database of the cluster, run the following commands as superuser: <programlisting> SET search_path = pg_catalog; @@ -395,15 +901,15 @@ CREATE OR REPLACE VIEW pg_user_mappings AS <step> <para> - Do not forget to include the <literal>template0</> - and <literal>template1</> databases, or the vulnerability will still - exist in databases you create later. To fix <literal>template0</>, + Do not forget to include the <literal>template0</literal> + and <literal>template1</literal> databases, or the vulnerability will still + exist in databases you create later. To fix <literal>template0</literal>, you'll need to temporarily make it accept connections. - In <productname>PostgreSQL</> 9.5 and later, you can use + In <productname>PostgreSQL</productname> 9.5 and later, you can use <programlisting> ALTER DATABASE template0 WITH ALLOW_CONNECTIONS true; </programlisting> - and then after fixing <literal>template0</>, undo that with + and then after fixing <literal>template0</literal>, undo that with <programlisting> ALTER DATABASE template0 WITH ALLOW_CONNECTIONS false; </programlisting> @@ -417,7 +923,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0'; <step> <para> - Finally, remove the <literal>allow_system_table_mods</> configuration + Finally, remove the <literal>allow_system_table_mods</literal> configuration setting, and again restart the postmaster. </para> </step> @@ -440,16 +946,16 @@ Branch: REL9_2_STABLE [06651648a] 2017-08-07 17:04:17 +0300 </para> <para> - <application>libpq</> ignores empty password specifications, and does + <application>libpq</application> ignores empty password specifications, and does not transmit them to the server. So, if a user's password has been set to the empty string, it's impossible to log in with that password - via <application>psql</> or other <application>libpq</>-based + via <application>psql</application> or other <application>libpq</application>-based clients. An administrator might therefore believe that setting the password to empty is equivalent to disabling password login. - However, with a modified or non-<application>libpq</>-based client, + However, with a modified or non-<application>libpq</application>-based client, logging in could be possible, depending on which authentication method is configured. In particular the most common - method, <literal>md5</>, accepted empty passwords. + method, <literal>md5</literal>, accepted empty passwords. Change the server to reject empty passwords in all cases. (CVE-2017-7546) </para> @@ -464,13 +970,13 @@ Branch: REL9_5_STABLE [873741c68] 2017-08-07 10:19:21 -0400 Branch: REL9_4_STABLE [f1cda6d6c] 2017-08-07 10:19:22 -0400 --> <para> - Make <function>lo_put()</> check for <literal>UPDATE</> privilege on + Make <function>lo_put()</function> check for <literal>UPDATE</literal> privilege on the target large object (Tom Lane, Michael Paquier) </para> <para> - <function>lo_put()</> should surely require the same permissions - as <function>lowrite()</>, but the check was missing, allowing any + <function>lo_put()</function> should surely require the same permissions + as <function>lowrite()</function>, but the check was missing, allowing any user to change the data in a large object. (CVE-2017-7548) </para> @@ -485,12 +991,12 @@ Branch: REL9_5_STABLE [fd376afc9] 2017-06-15 12:30:02 -0400 --> <para> Correct the documentation about the process for upgrading standby - servers with <application>pg_upgrade</> (Bruce Momjian) + servers with <application>pg_upgrade</application> (Bruce Momjian) </para> <para> The previous documentation instructed users to start/stop the primary - server after running <application>pg_upgrade</> but before syncing + server after running <application>pg_upgrade</application> but before syncing the standby servers. This sequence is unsafe. </para> </listitem> @@ -697,7 +1203,7 @@ Branch: REL9_2_STABLE [81bf7b5b1] 2017-06-21 14:13:58 -0700 --> <para> Fix possible creation of an invalid WAL segment when a standby is - promoted just after it processes an <literal>XLOG_SWITCH</> WAL + promoted just after it processes an <literal>XLOG_SWITCH</literal> WAL record (Andres Freund) </para> </listitem> @@ -711,7 +1217,7 @@ Branch: REL9_5_STABLE [446914f6b] 2017-06-30 12:00:03 -0400 Branch: REL9_4_STABLE [5aa8db014] 2017-06-30 12:00:03 -0400 --> <para> - Fix <application>walsender</> to exit promptly when client requests + Fix <application>walsender</application> to exit promptly when client requests shutdown (Tom Lane) </para> </listitem> @@ -731,7 +1237,7 @@ Branch: REL9_3_STABLE [45d067d50] 2017-06-05 19:18:16 -0700 Branch: REL9_2_STABLE [133b1920c] 2017-06-05 19:18:16 -0700 --> <para> - Fix <systemitem>SIGHUP</> and <systemitem>SIGUSR1</> handling in + Fix <systemitem>SIGHUP</systemitem> and <systemitem>SIGUSR1</systemitem> handling in walsender processes (Petr Jelinek, Andres Freund) </para> </listitem> @@ -761,7 +1267,7 @@ Branch: REL9_3_STABLE [cb59949f6] 2017-06-26 17:31:56 -0400 Branch: REL9_2_STABLE [e96adaacd] 2017-06-26 17:31:56 -0400 --> <para> - Fix unnecessarily slow restarts of <application>walreceiver</> + Fix unnecessarily slow restarts of <application>walreceiver</application> processes due to race condition in postmaster (Tom Lane) </para> </listitem> @@ -880,7 +1386,7 @@ Branch: REL9_3_STABLE [aea1a3f0e] 2017-07-12 18:00:04 -0400 Branch: REL9_2_STABLE [75670ec37] 2017-07-12 18:00:04 -0400 --> <para> - Fix cases where an <command>INSERT</> or <command>UPDATE</> assigns + Fix cases where an <command>INSERT</command> or <command>UPDATE</command> assigns to more than one element of a column that is of domain-over-array type (Tom Lane) </para> @@ -896,7 +1402,7 @@ Branch: REL9_4_STABLE [dc777f9db] 2017-06-27 17:51:11 -0400 Branch: REL9_3_STABLE [66dee28b4] 2017-06-27 17:51:11 -0400 --> <para> - Allow window functions to be used in sub-<literal>SELECT</>s that + Allow window functions to be used in sub-<literal>SELECT</literal>s that are within the arguments of an aggregate function (Tom Lane) </para> </listitem> @@ -908,7 +1414,7 @@ Branch: master [7086be6e3] 2017-07-24 15:57:24 -0400 Branch: REL9_6_STABLE [971faefc2] 2017-07-24 16:24:42 -0400 --> <para> - Ensure that a view's <literal>CHECK OPTIONS</> clause is enforced + Ensure that a view's <literal>CHECK OPTIONS</literal> clause is enforced properly when the underlying table is a foreign table (Etsuro Fujita) </para> @@ -930,12 +1436,12 @@ Branch: REL9_2_STABLE [da9165686] 2017-05-26 15:16:59 -0400 --> <para> Move autogenerated array types out of the way during - <command>ALTER ... RENAME</> (Vik Fearing) + <command>ALTER ... RENAME</command> (Vik Fearing) </para> <para> Previously, we would rename a conflicting autogenerated array type - out of the way during <command>CREATE</>; this fix extends that + out of the way during <command>CREATE</command>; this fix extends that behavior to renaming operations. </para> </listitem> @@ -948,7 +1454,7 @@ Branch: REL9_6_STABLE [b35cce914] 2017-05-15 11:33:44 -0400 Branch: REL9_5_STABLE [53a1aa9f9] 2017-05-15 11:33:45 -0400 --> <para> - Fix dangling pointer in <command>ALTER TABLE</> when there is a + Fix dangling pointer in <command>ALTER TABLE</command> when there is a comment on a constraint belonging to the table (David Rowley) </para> @@ -969,8 +1475,8 @@ Branch: REL9_3_STABLE [b7d1bc820] 2017-08-03 21:29:36 -0400 Branch: REL9_2_STABLE [22eb38caa] 2017-08-03 21:42:46 -0400 --> <para> - Ensure that <command>ALTER USER ... SET</> accepts all the syntax - variants that <command>ALTER ROLE ... SET</> does (Peter Eisentraut) + Ensure that <command>ALTER USER ... SET</command> accepts all the syntax + variants that <command>ALTER ROLE ... SET</command> does (Peter Eisentraut) </para> </listitem> @@ -981,18 +1487,18 @@ Branch: master [86705aa8c] 2017-08-03 13:24:48 -0400 Branch: REL9_6_STABLE [1f220c390] 2017-08-03 13:25:32 -0400 --> <para> - Allow a foreign table's <literal>CHECK</> constraints to be - initially <literal>NOT VALID</> (Amit Langote) + Allow a foreign table's <literal>CHECK</literal> constraints to be + initially <literal>NOT VALID</literal> (Amit Langote) </para> <para> - <command>CREATE TABLE</> silently drops <literal>NOT VALID</> - specifiers for <literal>CHECK</> constraints, reasoning that the + <command>CREATE TABLE</command> silently drops <literal>NOT VALID</literal> + specifiers for <literal>CHECK</literal> constraints, reasoning that the table must be empty so the constraint can be validated immediately. - But this is wrong for <command>CREATE FOREIGN TABLE</>, where there's + But this is wrong for <command>CREATE FOREIGN TABLE</command>, where there's no reason to suppose that the underlying table is empty, and even if it is it's no business of ours to decide that the constraint can be - treated as valid going forward. Skip this <quote>optimization</> for + treated as valid going forward. Skip this <quote>optimization</quote> for foreign tables. </para> </listitem> @@ -1009,14 +1515,14 @@ Branch: REL9_2_STABLE [ac93a78b0] 2017-06-16 11:46:26 +0300 --> <para> Properly update dependency info when changing a datatype I/O - function's argument or return type from <type>opaque</> to the + function's argument or return type from <type>opaque</type> to the correct type (Heikki Linnakangas) </para> <para> - <command>CREATE TYPE</> updates I/O functions declared in this + <command>CREATE TYPE</command> updates I/O functions declared in this long-obsolete style, but it forgot to record a dependency on the - type, allowing a subsequent <command>DROP TYPE</> to leave broken + type, allowing a subsequent <command>DROP TYPE</command> to leave broken function definitions behind. </para> </listitem> @@ -1028,7 +1534,7 @@ Branch: master [34aebcf42] 2017-06-02 19:11:15 -0700 Branch: REL9_6_STABLE [8a7cd781e] 2017-06-02 19:11:23 -0700 --> <para> - Allow parallelism in the query plan when <command>COPY</> copies from + Allow parallelism in the query plan when <command>COPY</command> copies from a query's result (Andres Freund) </para> </listitem> @@ -1044,8 +1550,8 @@ Branch: REL9_3_STABLE [11854dee0] 2017-07-12 22:04:08 +0300 Branch: REL9_2_STABLE [40ba61b44] 2017-07-12 22:04:15 +0300 --> <para> - Reduce memory usage when <command>ANALYZE</> processes - a <type>tsvector</> column (Heikki Linnakangas) + Reduce memory usage when <command>ANALYZE</command> processes + a <type>tsvector</type> column (Heikki Linnakangas) </para> </listitem> @@ -1061,7 +1567,7 @@ Branch: REL9_2_STABLE [798d2321e] 2017-05-21 13:05:17 -0400 --> <para> Fix unnecessary precision loss and sloppy rounding when multiplying - or dividing <type>money</> values by integers or floats (Tom Lane) + or dividing <type>money</type> values by integers or floats (Tom Lane) </para> </listitem> @@ -1077,7 +1583,7 @@ Branch: REL9_2_STABLE [a047270d5] 2017-05-24 15:28:35 -0400 --> <para> Tighten checks for whitespace in functions that parse identifiers, - such as <function>regprocedurein()</> (Tom Lane) + such as <function>regprocedurein()</function> (Tom Lane) </para> <para> @@ -1103,13 +1609,13 @@ Branch: REL9_3_STABLE [0d8f015e7] 2017-07-31 12:38:35 -0400 Branch: REL9_2_STABLE [456c7dff2] 2017-07-31 12:38:35 -0400 --> <para> - Use relevant <literal>#define</> symbols from Perl while - compiling <application>PL/Perl</> (Ashutosh Sharma, Tom Lane) + Use relevant <literal>#define</literal> symbols from Perl while + compiling <application>PL/Perl</application> (Ashutosh Sharma, Tom Lane) </para> <para> This avoids portability problems, typically manifesting as - a <quote>handshake</> mismatch during library load, when working with + a <quote>handshake</quote> mismatch during library load, when working with recent Perl versions. </para> </listitem> @@ -1124,7 +1630,7 @@ Branch: REL9_4_STABLE [1fe1fc449] 2017-06-07 14:04:49 +0300 Branch: REL9_3_STABLE [f2fa0c651] 2017-06-07 14:04:44 +0300 --> <para> - In <application>libpq</>, reset GSS/SASL and SSPI authentication + In <application>libpq</application>, reset GSS/SASL and SSPI authentication state properly after a failed connection attempt (Michael Paquier) </para> @@ -1146,9 +1652,9 @@ Branch: REL9_3_STABLE [6bc710f6d] 2017-05-17 12:24:19 -0400 Branch: REL9_2_STABLE [07477130e] 2017-05-17 12:24:19 -0400 --> <para> - In <application>psql</>, fix failure when <command>COPY FROM STDIN</> + In <application>psql</application>, fix failure when <command>COPY FROM STDIN</command> is ended with a keyboard EOF signal and then another <command>COPY - FROM STDIN</> is attempted (Thomas Munro) + FROM STDIN</command> is attempted (Thomas Munro) </para> <para> @@ -1167,8 +1673,8 @@ Branch: REL9_4_STABLE [b93217653] 2017-08-03 17:36:43 -0400 Branch: REL9_3_STABLE [035bb8222] 2017-08-03 17:36:23 -0400 --> <para> - Fix <application>pg_dump</> and <application>pg_restore</> to - emit <command>REFRESH MATERIALIZED VIEW</> commands last (Tom Lane) + Fix <application>pg_dump</application> and <application>pg_restore</application> to + emit <command>REFRESH MATERIALIZED VIEW</command> commands last (Tom Lane) </para> <para> @@ -1190,8 +1696,8 @@ Branch: REL9_5_STABLE [12f1e523a] 2017-08-03 14:55:17 -0400 Branch: REL9_4_STABLE [69ad12b58] 2017-08-03 14:55:17 -0400 --> <para> - Improve <application>pg_dump</>/<application>pg_restore</>'s - reporting of error conditions originating in <application>zlib</> + Improve <application>pg_dump</application>/<application>pg_restore</application>'s + reporting of error conditions originating in <application>zlib</application> (Vladimir Kunschikov, Álvaro Herrera) </para> </listitem> @@ -1206,7 +1712,7 @@ Branch: REL9_4_STABLE [502ead3d6] 2017-07-22 20:20:10 -0400 Branch: REL9_3_STABLE [68a22bc69] 2017-07-22 20:20:10 -0400 --> <para> - Fix <application>pg_dump</> with the <option>--clean</> option to + Fix <application>pg_dump</application> with the <option>--clean</option> option to drop event triggers as expected (Tom Lane) </para> @@ -1224,8 +1730,8 @@ Branch: master [4500edc7e] 2017-06-28 10:33:57 -0400 Branch: REL9_6_STABLE [a2de017b3] 2017-06-28 10:34:01 -0400 --> <para> - Fix <application>pg_dump</> with the <option>--clean</> option to not - fail when the <literal>public</> schema doesn't exist (Stephen Frost) + Fix <application>pg_dump</application> with the <option>--clean</option> option to not + fail when the <literal>public</literal> schema doesn't exist (Stephen Frost) </para> </listitem> @@ -1240,7 +1746,7 @@ Branch: REL9_3_STABLE [a561254e4] 2017-05-26 12:51:05 -0400 Branch: REL9_2_STABLE [f62e1eff5] 2017-05-26 12:51:06 -0400 --> <para> - Fix <application>pg_dump</> to not emit invalid SQL for an empty + Fix <application>pg_dump</application> to not emit invalid SQL for an empty operator class (Daniel Gustafsson) </para> </listitem> @@ -1256,7 +1762,7 @@ Branch: REL9_3_STABLE [2943c04f7] 2017-06-19 11:03:16 -0400 Branch: REL9_2_STABLE [c10cbf77a] 2017-06-19 11:03:21 -0400 --> <para> - Fix <application>pg_dump</> output to stdout on Windows (Kuntal Ghosh) + Fix <application>pg_dump</application> output to stdout on Windows (Kuntal Ghosh) </para> <para> @@ -1276,14 +1782,14 @@ Branch: REL9_3_STABLE [b6d640047] 2017-07-24 15:16:31 -0400 Branch: REL9_2_STABLE [d9874fde8] 2017-07-24 15:16:31 -0400 --> <para> - Fix <function>pg_get_ruledef()</> to print correct output for - the <literal>ON SELECT</> rule of a view whose columns have been + Fix <function>pg_get_ruledef()</function> to print correct output for + the <literal>ON SELECT</literal> rule of a view whose columns have been renamed (Tom Lane) </para> <para> - In some corner cases, <application>pg_dump</> relies - on <function>pg_get_ruledef()</> to dump views, so that this error + In some corner cases, <application>pg_dump</application> relies + on <function>pg_get_ruledef()</function> to dump views, so that this error could result in dump/reload failures. </para> </listitem> @@ -1299,7 +1805,7 @@ Branch: REL9_3_STABLE [e947838ae] 2017-07-20 11:29:36 -0400 --> <para> Fix dumping of outer joins with empty constraints, such as the result - of a <literal>NATURAL LEFT JOIN</> with no common columns (Tom Lane) + of a <literal>NATURAL LEFT JOIN</literal> with no common columns (Tom Lane) </para> </listitem> @@ -1314,7 +1820,7 @@ Branch: REL9_3_STABLE [0ecc407d9] 2017-07-13 19:24:44 -0400 Branch: REL9_2_STABLE [bccfb1776] 2017-07-13 19:24:44 -0400 --> <para> - Fix dumping of function expressions in the <literal>FROM</> clause in + Fix dumping of function expressions in the <literal>FROM</literal> clause in cases where the expression does not deparse into something that looks like a function call (Tom Lane) </para> @@ -1331,7 +1837,7 @@ Branch: REL9_3_STABLE [f3633689f] 2017-07-14 16:03:23 +0300 Branch: REL9_2_STABLE [4b994a96c] 2017-07-14 16:03:27 +0300 --> <para> - Fix <application>pg_basebackup</> output to stdout on Windows + Fix <application>pg_basebackup</application> output to stdout on Windows (Haribabu Kommi) </para> @@ -1349,12 +1855,12 @@ Branch: REL9_6_STABLE [73fbf3d3d] 2017-07-21 22:04:55 -0400 Branch: REL9_5_STABLE [ed367be64] 2017-07-21 22:05:07 -0400 --> <para> - Fix <application>pg_rewind</> to correctly handle files exceeding 2GB + Fix <application>pg_rewind</application> to correctly handle files exceeding 2GB (Kuntal Ghosh, Michael Paquier) </para> <para> - Ordinarily such files won't appear in <productname>PostgreSQL</> data + Ordinarily such files won't appear in <productname>PostgreSQL</productname> data directories, but they could be present in some cases. </para> </listitem> @@ -1370,8 +1876,8 @@ Branch: REL9_3_STABLE [5c890645d] 2017-06-20 13:20:02 -0400 Branch: REL9_2_STABLE [65beccae5] 2017-06-20 13:20:02 -0400 --> <para> - Fix <application>pg_upgrade</> to ensure that the ending WAL record - does not have <xref linkend="guc-wal-level"> = <literal>minimum</> + Fix <application>pg_upgrade</application> to ensure that the ending WAL record + does not have <xref linkend="guc-wal-level"> = <literal>minimum</literal> (Bruce Momjian) </para> @@ -1389,7 +1895,7 @@ Branch: REL9_6_STABLE [d3ca4b4b4] 2017-06-05 16:10:07 -0700 Branch: REL9_5_STABLE [25653c171] 2017-06-05 16:10:07 -0700 --> <para> - Fix <application>pg_xlogdump</>'s computation of WAL record length + Fix <application>pg_xlogdump</application>'s computation of WAL record length (Andres Freund) </para> </listitem> @@ -1409,9 +1915,9 @@ Branch: REL9_4_STABLE [a648fc70a] 2017-07-21 14:20:43 -0400 Branch: REL9_3_STABLE [6d9de660d] 2017-07-21 14:20:43 -0400 --> <para> - In <filename>postgres_fdw</>, re-establish connections to remote - servers after <command>ALTER SERVER</> or <command>ALTER USER - MAPPING</> commands (Kyotaro Horiguchi) + In <filename>postgres_fdw</filename>, re-establish connections to remote + servers after <command>ALTER SERVER</command> or <command>ALTER USER + MAPPING</command> commands (Kyotaro Horiguchi) </para> <para> @@ -1430,7 +1936,7 @@ Branch: REL9_4_STABLE [c02c450cf] 2017-06-07 15:40:35 -0400 Branch: REL9_3_STABLE [fc267a0c3] 2017-06-07 15:41:05 -0400 --> <para> - In <filename>postgres_fdw</>, allow cancellation of remote + In <filename>postgres_fdw</filename>, allow cancellation of remote transaction control commands (Robert Haas, Rafia Sabih) </para> @@ -1449,7 +1955,7 @@ Branch: REL9_5_STABLE [6f2fe2468] 2017-05-11 14:51:38 -0400 Branch: REL9_4_STABLE [5c633f76b] 2017-05-11 14:51:46 -0400 --> <para> - Increase <literal>MAX_SYSCACHE_CALLBACKS</> to provide more room for + Increase <literal>MAX_SYSCACHE_CALLBACKS</literal> to provide more room for extensions (Tom Lane) </para> </listitem> @@ -1465,7 +1971,7 @@ Branch: REL9_3_STABLE [cee7238de] 2017-06-01 13:32:56 -0400 Branch: REL9_2_STABLE [a378b9bc2] 2017-06-01 13:32:56 -0400 --> <para> - Always use <option>-fPIC</>, not <option>-fpic</>, when building + Always use <option>-fPIC</option>, not <option>-fpic</option>, when building shared libraries with gcc (Tom Lane) </para> @@ -1492,8 +1998,8 @@ Branch: REL9_3_STABLE [da30fa603] 2017-06-05 20:40:47 -0400 Branch: REL9_2_STABLE [f964a7c5a] 2017-06-05 20:41:01 -0400 --> <para> - In MSVC builds, handle the case where the <application>openssl</> - library is not within a <filename>VC</> subdirectory (Andrew Dunstan) + In MSVC builds, handle the case where the <application>openssl</application> + library is not within a <filename>VC</filename> subdirectory (Andrew Dunstan) </para> </listitem> @@ -1508,13 +2014,13 @@ Branch: REL9_3_STABLE [2c7d2114b] 2017-05-12 10:24:16 -0400 Branch: REL9_2_STABLE [614f83c12] 2017-05-12 10:24:36 -0400 --> <para> - In MSVC builds, add proper include path for <application>libxml2</> + In MSVC builds, add proper include path for <application>libxml2</application> header files (Andrew Dunstan) </para> <para> This fixes a former need to move things around in standard Windows - installations of <application>libxml2</>. + installations of <application>libxml2</application>. </para> </listitem> @@ -1530,7 +2036,7 @@ Branch: REL9_2_STABLE [4885e5c88] 2017-07-23 23:53:55 -0700 --> <para> In MSVC builds, recognize a Tcl library that is - named <filename>tcl86.lib</> (Noah Misch) + named <filename>tcl86.lib</filename> (Noah Misch) </para> </listitem> @@ -1551,8 +2057,8 @@ Branch: REL9_5_STABLE [7eb4124da] 2017-07-16 11:27:07 -0400 Branch: REL9_4_STABLE [9c3f502b4] 2017-07-16 11:27:15 -0400 --> <para> - In MSVC builds, honor <literal>PROVE_FLAGS</> settings - on <filename>vcregress.pl</>'s command line (Andrew Dunstan) + In MSVC builds, honor <literal>PROVE_FLAGS</literal> settings + on <filename>vcregress.pl</filename>'s command line (Andrew Dunstan) </para> </listitem> @@ -1589,7 +2095,7 @@ Branch: REL9_4_STABLE [9c3f502b4] 2017-07-16 11:27:15 -0400 <para> Also, if you are using third-party replication tools that depend - on <quote>logical decoding</>, see the fourth changelog entry below. + on <quote>logical decoding</quote>, see the fourth changelog entry below. </para> <para> @@ -1615,18 +2121,18 @@ Branch: REL9_2_STABLE [99cbb0bd9] 2017-05-08 07:24:28 -0700 --> <para> Restrict visibility - of <structname>pg_user_mappings</>.<structfield>umoptions</>, to + of <structname>pg_user_mappings</structname>.<structfield>umoptions</structfield>, to protect passwords stored as user mapping options (Michael Paquier, Feike Steenbergen) </para> <para> The previous coding allowed the owner of a foreign server object, - or anyone he has granted server <literal>USAGE</> permission to, + or anyone he has granted server <literal>USAGE</literal> permission to, to see the options for all user mappings associated with that server. This might well include passwords for other users. Adjust the view definition to match the behavior of - <structname>information_schema.user_mapping_options</>, namely that + <structname>information_schema.user_mapping_options</structname>, namely that these options are visible to the user being mapped, or if the mapping is for <literal>PUBLIC</literal> and the current user is the server owner, or if the current user is a superuser. @@ -1665,7 +2171,7 @@ Branch: REL9_3_STABLE [703da1795] 2017-05-08 11:19:08 -0400 <para> Some selectivity estimation functions in the planner will apply user-defined operators to values obtained - from <structname>pg_statistic</>, such as most common values and + from <structname>pg_statistic</structname>, such as most common values and histogram entries. This occurs before table permissions are checked, so a nefarious user could exploit the behavior to obtain these values for table columns he does not have permission to read. To fix, @@ -1687,17 +2193,17 @@ Branch: REL9_4_STABLE [ed36c1fe1] 2017-05-08 07:24:27 -0700 Branch: REL9_3_STABLE [3eab81127] 2017-05-08 07:24:28 -0700 --> <para> - Restore <application>libpq</>'s recognition of - the <envar>PGREQUIRESSL</> environment variable (Daniel Gustafsson) + Restore <application>libpq</application>'s recognition of + the <envar>PGREQUIRESSL</envar> environment variable (Daniel Gustafsson) </para> <para> Processing of this environment variable was unintentionally dropped - in <productname>PostgreSQL</> 9.3, but its documentation remained. + in <productname>PostgreSQL</productname> 9.3, but its documentation remained. This creates a security hazard, since users might be relying on the environment variable to force SSL-encrypted connections, but that would no longer be guaranteed. Restore handling of the variable, - but give it lower priority than <envar>PGSSLMODE</>, to avoid + but give it lower priority than <envar>PGSSLMODE</envar>, to avoid breaking configurations that work correctly with post-9.3 code. (CVE-2017-7485) </para> @@ -1748,7 +2254,7 @@ Branch: REL9_3_STABLE [6bd7816e7] 2017-03-14 12:08:14 -0400 Branch: REL9_2_STABLE [b2ae1d6c4] 2017-03-14 12:10:36 -0400 --> <para> - Fix possible corruption of <quote>init forks</> of unlogged indexes + Fix possible corruption of <quote>init forks</quote> of unlogged indexes (Robert Haas, Michael Paquier) </para> @@ -1770,7 +2276,7 @@ Branch: REL9_3_STABLE [856580873] 2017-04-23 13:10:57 -0400 Branch: REL9_2_STABLE [952e33b05] 2017-04-23 13:10:58 -0400 --> <para> - Fix incorrect reconstruction of <structname>pg_subtrans</> entries + Fix incorrect reconstruction of <structname>pg_subtrans</structname> entries when a standby server replays a prepared but uncommitted two-phase transaction (Tom Lane) </para> @@ -1778,7 +2284,7 @@ Branch: REL9_2_STABLE [952e33b05] 2017-04-23 13:10:58 -0400 <para> In most cases this turned out to have no visible ill effects, but in corner cases it could result in circular references - in <structname>pg_subtrans</>, potentially causing infinite loops + in <structname>pg_subtrans</structname>, potentially causing infinite loops in queries that examine rows modified by the two-phase transaction. </para> </listitem> @@ -1792,7 +2298,7 @@ Branch: REL9_5_STABLE [feb659cce] 2017-02-22 08:29:44 +0900 Branch: REL9_4_STABLE [a3eb715a3] 2017-02-22 08:29:57 +0900 --> <para> - Avoid possible crash in <application>walsender</> due to failure + Avoid possible crash in <application>walsender</application> due to failure to initialize a string buffer (Stas Kelvich, Fujii Masao) </para> </listitem> @@ -1840,7 +2346,7 @@ Branch: REL9_5_STABLE [dba1f310a] 2017-04-24 12:16:58 -0400 Branch: REL9_4_STABLE [436b560b8] 2017-04-24 12:16:58 -0400 --> <para> - Fix postmaster's handling of <function>fork()</> failure for a + Fix postmaster's handling of <function>fork()</function> failure for a background worker process (Tom Lane) </para> @@ -1858,7 +2364,7 @@ Branch: master [89deca582] 2017-04-07 12:18:38 -0400 Branch: REL9_6_STABLE [c0a493e17] 2017-04-07 12:18:38 -0400 --> <para> - Fix possible <quote>no relation entry for relid 0</> error when + Fix possible <quote>no relation entry for relid 0</quote> error when planning nested set operations (Tom Lane) </para> </listitem> @@ -1886,7 +2392,7 @@ Branch: REL9_6_STABLE [6c73b390b] 2017-04-17 15:29:00 -0400 Branch: REL9_5_STABLE [6f0f98bb0] 2017-04-17 15:29:00 -0400 --> <para> - Avoid applying <quote>physical targetlist</> optimization to custom + Avoid applying <quote>physical targetlist</quote> optimization to custom scans (Dmitry Ivanov, Tom Lane) </para> @@ -1905,13 +2411,13 @@ Branch: REL9_6_STABLE [92b15224b] 2017-05-06 21:46:41 -0400 Branch: REL9_5_STABLE [d617c7629] 2017-05-06 21:46:56 -0400 --> <para> - Use the correct sub-expression when applying a <literal>FOR ALL</> + Use the correct sub-expression when applying a <literal>FOR ALL</literal> row-level-security policy (Stephen Frost) </para> <para> - In some cases the <literal>WITH CHECK</> restriction would be applied - when the <literal>USING</> restriction is more appropriate. + In some cases the <literal>WITH CHECK</literal> restriction would be applied + when the <literal>USING</literal> restriction is more appropriate. </para> </listitem> @@ -1934,7 +2440,7 @@ Branch: REL9_2_STABLE [c9d6c564f] 2017-05-02 18:05:54 -0400 Due to lack of a cache flush step between commands in an extension script file, non-utility queries might not see the effects of an immediately preceding catalog change, such as <command>ALTER TABLE - ... RENAME</>. + ... RENAME</command>. </para> </listitem> @@ -1950,12 +2456,12 @@ Branch: REL9_2_STABLE [27a8c8033] 2017-02-12 16:05:23 -0500 --> <para> Skip tablespace privilege checks when <command>ALTER TABLE ... ALTER - COLUMN TYPE</> rebuilds an existing index (Noah Misch) + COLUMN TYPE</command> rebuilds an existing index (Noah Misch) </para> <para> The command failed if the calling user did not currently have - <literal>CREATE</> privilege for the tablespace containing the index. + <literal>CREATE</literal> privilege for the tablespace containing the index. That behavior seems unhelpful, so skip the check, allowing the index to be rebuilt where it is. </para> @@ -1972,13 +2478,13 @@ Branch: REL9_3_STABLE [954744f7a] 2017-04-28 14:53:56 -0400 Branch: REL9_2_STABLE [f60f0c8fe] 2017-04-28 14:55:42 -0400 --> <para> - Fix <command>ALTER TABLE ... VALIDATE CONSTRAINT</> to not recurse - to child tables when the constraint is marked <literal>NO INHERIT</> + Fix <command>ALTER TABLE ... VALIDATE CONSTRAINT</command> to not recurse + to child tables when the constraint is marked <literal>NO INHERIT</literal> (Amit Langote) </para> <para> - This fix prevents unwanted <quote>constraint does not exist</> failures + This fix prevents unwanted <quote>constraint does not exist</quote> failures when no matching constraint is present in the child tables. </para> </listitem> @@ -1991,7 +2497,7 @@ Branch: REL9_6_STABLE [943140d57] 2017-03-06 16:50:47 -0500 Branch: REL9_5_STABLE [420d9ec0a] 2017-03-06 16:50:47 -0500 --> <para> - Avoid dangling pointer in <command>COPY ... TO</> when row-level + Avoid dangling pointer in <command>COPY ... TO</command> when row-level security is active for the source table (Tom Lane) </para> @@ -2009,8 +2515,8 @@ Branch: REL9_6_STABLE [68f7b91e5] 2017-03-04 16:09:33 -0500 Branch: REL9_5_STABLE [807df31d1] 2017-03-04 16:09:33 -0500 --> <para> - Avoid accessing an already-closed relcache entry in <command>CLUSTER</> - and <command>VACUUM FULL</> (Tom Lane) + Avoid accessing an already-closed relcache entry in <command>CLUSTER</command> + and <command>VACUUM FULL</command> (Tom Lane) </para> <para> @@ -2032,14 +2538,14 @@ Branch: master [64ae420b2] 2017-03-17 14:35:54 +0000 Branch: REL9_6_STABLE [733488dc6] 2017-03-17 14:46:15 +0000 --> <para> - Fix <command>VACUUM</> to account properly for pages that could not + Fix <command>VACUUM</command> to account properly for pages that could not be scanned due to conflicting page pins (Andrew Gierth) </para> <para> This tended to lead to underestimation of the number of tuples in the table. In the worst case of a small heavily-contended - table, <command>VACUUM</> could incorrectly report that the table + table, <command>VACUUM</command> could incorrectly report that the table contained no tuples, leading to very bad planning choices. </para> </listitem> @@ -2067,13 +2573,13 @@ Branch: master [d5286aa90] 2017-03-21 16:23:10 +0300 Branch: REL9_6_STABLE [a4d07d2e9] 2017-03-21 16:24:10 +0300 --> <para> - Fix incorrect support for certain <type>box</> operators in SP-GiST + Fix incorrect support for certain <type>box</type> operators in SP-GiST (Nikita Glukhov) </para> <para> - SP-GiST index scans using the operators <literal>&<</> - <literal>&></> <literal>&<|</> and <literal>|&></> + SP-GiST index scans using the operators <literal>&<</literal> + <literal>&></literal> <literal>&<|</literal> and <literal>|&></literal> would yield incorrect answers. </para> </listitem> @@ -2087,12 +2593,12 @@ Branch: REL9_5_STABLE [d68a2b20a] 2017-04-05 23:51:28 -0400 Branch: REL9_4_STABLE [8851bcf88] 2017-04-05 23:51:28 -0400 --> <para> - Fix integer-overflow problems in <type>interval</> comparison (Kyotaro + Fix integer-overflow problems in <type>interval</type> comparison (Kyotaro Horiguchi, Tom Lane) </para> <para> - The comparison operators for type <type>interval</> could yield wrong + The comparison operators for type <type>interval</type> could yield wrong answers for intervals larger than about 296000 years. Indexes on columns containing such large values should be reindexed, since they may be corrupt. @@ -2110,13 +2616,13 @@ Branch: REL9_3_STABLE [6e86b448f] 2017-05-04 21:31:12 -0400 Branch: REL9_2_STABLE [a48d47908] 2017-05-04 22:39:23 -0400 --> <para> - Fix <function>cursor_to_xml()</> to produce valid output - with <replaceable>tableforest</> = false + Fix <function>cursor_to_xml()</function> to produce valid output + with <replaceable>tableforest</replaceable> = false (Thomas Munro, Peter Eisentraut) </para> <para> - Previously it failed to produce a wrapping <literal><table></> + Previously it failed to produce a wrapping <literal><table></literal> element. </para> </listitem> @@ -2134,8 +2640,8 @@ Branch: REL9_5_STABLE [cf73c6bfc] 2017-02-09 15:49:57 -0500 Branch: REL9_4_STABLE [86ef376bb] 2017-02-09 15:49:58 -0500 --> <para> - Fix roundoff problems in <function>float8_timestamptz()</> - and <function>make_interval()</> (Tom Lane) + Fix roundoff problems in <function>float8_timestamptz()</function> + and <function>make_interval()</function> (Tom Lane) </para> <para> @@ -2155,7 +2661,7 @@ Branch: REL9_6_STABLE [1ec36a9eb] 2017-04-16 20:49:40 -0400 Branch: REL9_5_STABLE [b6e6ae1dc] 2017-04-16 20:50:31 -0400 --> <para> - Fix <function>pg_get_object_address()</> to handle members of operator + Fix <function>pg_get_object_address()</function> to handle members of operator families correctly (Álvaro Herrera) </para> </listitem> @@ -2167,12 +2673,12 @@ Branch: master [78874531b] 2017-03-24 13:53:40 +0300 Branch: REL9_6_STABLE [8de6278d3] 2017-03-24 13:55:02 +0300 --> <para> - Fix cancelling of <function>pg_stop_backup()</> when attempting to stop + Fix cancelling of <function>pg_stop_backup()</function> when attempting to stop a non-exclusive backup (Michael Paquier, David Steele) </para> <para> - If <function>pg_stop_backup()</> was cancelled while waiting for a + If <function>pg_stop_backup()</function> was cancelled while waiting for a non-exclusive backup to end, related state was left inconsistent; a new exclusive backup could not be started, and there were other minor problems. @@ -2196,7 +2702,7 @@ Branch: REL9_3_STABLE [07987304d] 2017-05-07 11:35:05 -0400 Branch: REL9_2_STABLE [9061680f0] 2017-05-07 11:35:11 -0400 --> <para> - Improve performance of <structname>pg_timezone_names</> view + Improve performance of <structname>pg_timezone_names</structname> view (Tom Lane, David Rowley) </para> </listitem> @@ -2226,13 +2732,13 @@ Branch: REL9_3_STABLE [3f613c6a4] 2017-02-21 17:51:28 -0500 Branch: REL9_2_STABLE [775227590] 2017-02-21 17:51:28 -0500 --> <para> - Fix sloppy handling of corner-case errors from <function>lseek()</> - and <function>close()</> (Tom Lane) + Fix sloppy handling of corner-case errors from <function>lseek()</function> + and <function>close()</function> (Tom Lane) </para> <para> Neither of these system calls are likely to fail in typical situations, - but if they did, <filename>fd.c</> could get quite confused. + but if they did, <filename>fd.c</filename> could get quite confused. </para> </listitem> @@ -2273,8 +2779,8 @@ Branch: REL9_3_STABLE [04207ef76] 2017-03-13 20:52:05 +0100 Branch: REL9_2_STABLE [d8c207437] 2017-03-13 20:52:16 +0100 --> <para> - Fix <application>ecpg</> to support <command>COMMIT PREPARED</> - and <command>ROLLBACK PREPARED</> (Masahiko Sawada) + Fix <application>ecpg</application> to support <command>COMMIT PREPARED</command> + and <command>ROLLBACK PREPARED</command> (Masahiko Sawada) </para> </listitem> @@ -2290,7 +2796,7 @@ Branch: REL9_2_STABLE [731afc91f] 2017-03-10 10:52:01 +0100 --> <para> Fix a double-free error when processing dollar-quoted string literals - in <application>ecpg</> (Michael Meskes) + in <application>ecpg</application> (Michael Meskes) </para> </listitem> @@ -2300,8 +2806,8 @@ Author: Teodor Sigaev <teodor@sigaev.ru> Branch: REL9_6_STABLE [2ed391f95] 2017-03-24 19:23:13 +0300 --> <para> - Fix <application>pgbench</> to handle the combination - of <option>--connect</> and <option>--rate</> options correctly + Fix <application>pgbench</application> to handle the combination + of <option>--connect</option> and <option>--rate</option> options correctly (Fabien Coelho) </para> </listitem> @@ -2313,8 +2819,8 @@ Branch: master [ef2662394] 2017-03-07 11:36:42 -0500 Branch: REL9_6_STABLE [0e2c85d13] 2017-03-07 11:36:35 -0500 --> <para> - Fix <application>pgbench</> to honor the long-form option - spelling <option>--builtin</>, as per its documentation (Tom Lane) + Fix <application>pgbench</application> to honor the long-form option + spelling <option>--builtin</option>, as per its documentation (Tom Lane) </para> </listitem> @@ -2325,15 +2831,15 @@ Branch: master [330b84d8c] 2017-03-06 23:29:02 -0500 Branch: REL9_6_STABLE [e961341cc] 2017-03-06 23:29:08 -0500 --> <para> - Fix <application>pg_dump</>/<application>pg_restore</> to correctly - handle privileges for the <literal>public</> schema when - using <option>--clean</> option (Stephen Frost) + Fix <application>pg_dump</application>/<application>pg_restore</application> to correctly + handle privileges for the <literal>public</literal> schema when + using <option>--clean</option> option (Stephen Frost) </para> <para> Other schemas start out with no privileges granted, - but <literal>public</> does not; this requires special-case treatment - when it is dropped and restored due to the <option>--clean</> option. + but <literal>public</literal> does not; this requires special-case treatment + when it is dropped and restored due to the <option>--clean</option> option. </para> </listitem> @@ -2348,7 +2854,7 @@ Branch: REL9_3_STABLE [783acfd4d] 2017-03-06 19:33:59 -0500 Branch: REL9_2_STABLE [0ab75448e] 2017-03-06 19:33:59 -0500 --> <para> - In <application>pg_dump</>, fix incorrect schema and owner marking for + In <application>pg_dump</application>, fix incorrect schema and owner marking for comments and security labels of some types of database objects (Giuseppe Broccolo, Tom Lane) </para> @@ -2368,12 +2874,12 @@ Branch: master [39370e6a0] 2017-02-17 15:06:28 -0500 Branch: REL9_6_STABLE [4e8b2fd33] 2017-02-17 15:06:34 -0500 --> <para> - Fix typo in <application>pg_dump</>'s query for initial privileges + Fix typo in <application>pg_dump</application>'s query for initial privileges of a procedural language (Peter Eisentraut) </para> <para> - This resulted in <application>pg_dump</> always believing that the + This resulted in <application>pg_dump</application> always believing that the language had no initial privileges. Since that's true for most procedural languages, ill effects from this bug are probably rare. </para> @@ -2390,13 +2896,13 @@ Branch: REL9_3_STABLE [0c0a95c2f] 2017-03-10 14:15:09 -0500 Branch: REL9_2_STABLE [e6d2ba419] 2017-03-10 14:15:09 -0500 --> <para> - Avoid emitting an invalid list file in <literal>pg_restore -l</> + Avoid emitting an invalid list file in <literal>pg_restore -l</literal> when SQL object names contain newlines (Tom Lane) </para> <para> Replace newlines by spaces, which is sufficient to make the output - valid for <literal>pg_restore -L</>'s purposes. + valid for <literal>pg_restore -L</literal>'s purposes. </para> </listitem> @@ -2411,8 +2917,8 @@ Branch: REL9_3_STABLE [7f831f09b] 2017-03-06 17:04:29 -0500 Branch: REL9_2_STABLE [e864cd25b] 2017-03-06 17:04:55 -0500 --> <para> - Fix <application>pg_upgrade</> to transfer comments and security labels - attached to <quote>large objects</> (blobs) (Stephen Frost) + Fix <application>pg_upgrade</application> to transfer comments and security labels + attached to <quote>large objects</quote> (blobs) (Stephen Frost) </para> <para> @@ -2433,13 +2939,13 @@ Branch: REL9_2_STABLE [0276da5eb] 2017-03-12 19:36:28 -0400 --> <para> Improve error handling - in <filename>contrib/adminpack</>'s <function>pg_file_write()</> + in <filename>contrib/adminpack</filename>'s <function>pg_file_write()</function> function (Noah Misch) </para> <para> Notably, it failed to detect errors reported - by <function>fclose()</>. + by <function>fclose()</function>. </para> </listitem> @@ -2454,7 +2960,7 @@ Branch: REL9_3_STABLE [f6cfc14e5] 2017-03-11 13:33:22 -0800 Branch: REL9_2_STABLE [c4613c3f4] 2017-03-11 13:33:30 -0800 --> <para> - In <filename>contrib/dblink</>, avoid leaking the previous unnamed + In <filename>contrib/dblink</filename>, avoid leaking the previous unnamed connection when establishing a new unnamed connection (Joe Conway) </para> </listitem> @@ -2479,7 +2985,7 @@ Branch: REL9_4_STABLE [b179684c7] 2017-04-13 17:18:35 -0400 Branch: REL9_3_STABLE [5be58cc89] 2017-04-13 17:18:35 -0400 --> <para> - Fix <filename>contrib/pg_trgm</>'s extraction of trigrams from regular + Fix <filename>contrib/pg_trgm</filename>'s extraction of trigrams from regular expressions (Tom Lane) </para> @@ -2497,7 +3003,7 @@ Branch: master [332bec1e6] 2017-04-24 22:50:07 -0400 Branch: REL9_6_STABLE [86e640a69] 2017-04-26 09:14:21 -0400 --> <para> - In <filename>contrib/postgres_fdw</>, allow join conditions that + In <filename>contrib/postgres_fdw</filename>, allow join conditions that contain shippable extension-provided functions to be pushed to the remote server (David Rowley, Ashutosh Bapat) </para> @@ -2555,7 +3061,7 @@ Branch: REL9_3_STABLE [dc93cafca] 2017-05-01 11:54:02 -0400 Branch: REL9_2_STABLE [c96ccc40e] 2017-05-01 11:54:08 -0400 --> <para> - Update time zone data files to <application>tzdata</> release 2017b + Update time zone data files to <application>tzdata</application> release 2017b for DST law changes in Chile, Haiti, and Mongolia, plus historical corrections for Ecuador, Kazakhstan, Liberia, and Spain. Switch to numeric abbreviations for numerous time zones in South @@ -2569,9 +3075,9 @@ Branch: REL9_2_STABLE [c96ccc40e] 2017-05-01 11:54:08 -0400 or no currency among the local population. They are in process of reversing that policy in favor of using numeric UTC offsets in zones where there is no evidence of real-world use of an English - abbreviation. At least for the time being, <productname>PostgreSQL</> + abbreviation. At least for the time being, <productname>PostgreSQL</productname> will continue to accept such removed abbreviations for timestamp input. - But they will not be shown in the <structname>pg_timezone_names</> + But they will not be shown in the <structname>pg_timezone_names</structname> view nor used for output. </para> </listitem> @@ -2593,15 +3099,15 @@ Branch: REL9_2_STABLE [82e7d3dfd] 2017-05-07 11:57:41 -0400 <para> The Microsoft MSVC build scripts neglected to install - the <filename>posixrules</> file in the timezone directory tree. + the <filename>posixrules</filename> file in the timezone directory tree. This resulted in the timezone code falling back to its built-in rule about what DST behavior to assume for a POSIX-style time zone name. For historical reasons that still corresponds to the DST rules the USA was using before 2007 (i.e., change on first Sunday in April and last Sunday in October). With this fix, a POSIX-style zone name will use the current and historical DST transition dates of - the <literal>US/Eastern</> zone. If you don't want that, remove - the <filename>posixrules</> file, or replace it with a copy of some + the <literal>US/Eastern</literal> zone. If you don't want that, remove + the <filename>posixrules</filename> file, or replace it with a copy of some other zone file (see <xref linkend="datatype-timezones">). Note that due to caching, you may need to restart the server to get such changes to take effect. @@ -2663,15 +3169,15 @@ Branch: REL9_2_STABLE [bcd7b47c2] 2017-02-06 13:20:25 -0500 --> <para> Fix a race condition that could cause indexes built - with <command>CREATE INDEX CONCURRENTLY</> to be corrupt + with <command>CREATE INDEX CONCURRENTLY</command> to be corrupt (Pavan Deolasee, Tom Lane) </para> <para> - If <command>CREATE INDEX CONCURRENTLY</> was used to build an index + If <command>CREATE INDEX CONCURRENTLY</command> was used to build an index that depends on a column not previously indexed, then rows updated by transactions that ran concurrently with - the <command>CREATE INDEX</> command could have received incorrect + the <command>CREATE INDEX</command> command could have received incorrect index entries. If you suspect this may have happened, the most reliable solution is to rebuild affected indexes after installing this update. @@ -2695,7 +3201,7 @@ Branch: REL9_4_STABLE [3e844a34b] 2016-11-15 15:55:36 -0500 Backends failed to account for this snapshot when advertising their oldest xmin, potentially allowing concurrent vacuuming operations to remove data that was still needed. This led to transient failures - along the lines of <quote>cache lookup failed for relation 1255</>. + along the lines of <quote>cache lookup failed for relation 1255</quote>. </para> </listitem> @@ -2711,7 +3217,7 @@ Branch: REL9_5_STABLE [ed8e8b814] 2017-01-09 18:19:29 -0300 </para> <para> - The WAL record emitted for a BRIN <quote>revmap</> page when moving an + The WAL record emitted for a BRIN <quote>revmap</quote> page when moving an index tuple to a different page was incorrect. Replay would make the related portion of the index useless, forcing it to be recomputed. </para> @@ -2728,13 +3234,13 @@ Branch: REL9_3_STABLE [8e403f215] 2016-12-08 14:16:47 -0500 Branch: REL9_2_STABLE [a00ac6299] 2016-12-08 14:19:25 -0500 --> <para> - Unconditionally WAL-log creation of the <quote>init fork</> for an + Unconditionally WAL-log creation of the <quote>init fork</quote> for an unlogged table (Michael Paquier) </para> <para> Previously, this was skipped when <xref linkend="guc-wal-level"> - = <literal>minimal</>, but actually it's necessary even in that case + = <literal>minimal</literal>, but actually it's necessary even in that case to ensure that the unlogged table is properly reset to empty after a crash. </para> @@ -2816,7 +3322,7 @@ Branch: master [93eb619cd] 2016-12-17 02:22:15 +0900 Branch: REL9_6_STABLE [6c75fb6b3] 2016-12-17 02:25:47 +0900 --> <para> - Disallow setting the <replaceable>num_sync</> field to zero in + Disallow setting the <replaceable>num_sync</replaceable> field to zero in <xref linkend="guc-synchronous-standby-names"> (Fujii Masao) </para> @@ -2867,7 +3373,7 @@ Branch: REL9_6_STABLE [20064c0ec] 2017-01-29 23:05:09 -0500 --> <para> Fix tracking of initial privileges for extension member objects so - that it works correctly with <command>ALTER EXTENSION ... ADD/DROP</> + that it works correctly with <command>ALTER EXTENSION ... ADD/DROP</command> (Stephen Frost) </para> @@ -2875,7 +3381,7 @@ Branch: REL9_6_STABLE [20064c0ec] 2017-01-29 23:05:09 -0500 An object's current privileges at the time it is added to the extension will now be considered its default privileges; only later changes in its privileges will be dumped by - subsequent <application>pg_dump</> runs. + subsequent <application>pg_dump</application> runs. </para> </listitem> @@ -2890,7 +3396,7 @@ Branch: REL9_3_STABLE [8f67a6c22] 2016-11-23 13:45:56 -0500 Branch: REL9_2_STABLE [05975ab0a] 2016-11-23 13:45:56 -0500 --> <para> - Make sure <command>ALTER TABLE</> preserves index tablespace + Make sure <command>ALTER TABLE</command> preserves index tablespace assignments when rebuilding indexes (Tom Lane, Michael Paquier) </para> @@ -2912,7 +3418,7 @@ Branch: REL9_4_STABLE [3a9a8c408] 2016-10-26 17:05:06 -0400 <para> Fix incorrect updating of trigger function properties when changing a foreign-key constraint's deferrability properties with <command>ALTER - TABLE ... ALTER CONSTRAINT</> (Tom Lane) + TABLE ... ALTER CONSTRAINT</command> (Tom Lane) </para> <para> @@ -2937,8 +3443,8 @@ Branch: REL9_2_STABLE [6a363a4c2] 2016-11-25 13:44:48 -0500 </para> <para> - This avoids <quote>could not find trigger <replaceable>NNN</></quote> - or <quote>relation <replaceable>NNN</> has no triggers</quote> errors. + This avoids <quote>could not find trigger <replaceable>NNN</replaceable></quote> + or <quote>relation <replaceable>NNN</replaceable> has no triggers</quote> errors. </para> </listitem> @@ -2950,15 +3456,15 @@ Branch: REL9_6_STABLE [4e563a1f6] 2017-01-09 19:26:58 -0300 Branch: REL9_5_STABLE [4d4ab6ccd] 2017-01-09 19:26:58 -0300 --> <para> - Fix <command>ALTER TABLE ... SET DATA TYPE ... USING</> when child + Fix <command>ALTER TABLE ... SET DATA TYPE ... USING</command> when child table has different column ordering than the parent (Álvaro Herrera) </para> <para> - Failure to adjust the column numbering in the <literal>USING</> + Failure to adjust the column numbering in the <literal>USING</literal> expression led to errors, - typically <quote>attribute <replaceable>N</> has wrong type</quote>. + typically <quote>attribute <replaceable>N</replaceable> has wrong type</quote>. </para> </listitem> @@ -2974,7 +3480,7 @@ Branch: REL9_2_STABLE [6c4cf2be8] 2017-01-04 18:00:12 -0500 --> <para> Fix processing of OID column when a table with OIDs is associated to - a parent with OIDs via <command>ALTER TABLE ... INHERIT</> (Amit + a parent with OIDs via <command>ALTER TABLE ... INHERIT</command> (Amit Langote) </para> @@ -2992,8 +3498,8 @@ Branch: master [1ead0208b] 2016-12-22 16:23:38 -0500 Branch: REL9_6_STABLE [68330c8b4] 2016-12-22 16:23:34 -0500 --> <para> - Ensure that <command>CREATE TABLE ... LIKE ... WITH OIDS</> creates - a table with OIDs, whether or not the <literal>LIKE</>-referenced + Ensure that <command>CREATE TABLE ... LIKE ... WITH OIDS</command> creates + a table with OIDs, whether or not the <literal>LIKE</literal>-referenced table(s) have OIDs (Tom Lane) </para> </listitem> @@ -3007,7 +3513,7 @@ Branch: REL9_5_STABLE [78a98b767] 2016-12-21 17:02:47 +0000 Branch: REL9_4_STABLE [cad24980e] 2016-12-21 17:03:54 +0000 --> <para> - Fix <command>CREATE OR REPLACE VIEW</> to update the view query + Fix <command>CREATE OR REPLACE VIEW</command> to update the view query before attempting to apply the new view options (Dean Rasheed) </para> @@ -3028,7 +3534,7 @@ Branch: REL9_3_STABLE [0e3aadb68] 2016-12-22 17:09:00 -0500 --> <para> Report correct object identity during <command>ALTER TEXT SEARCH - CONFIGURATION</> (Artur Zakirov) + CONFIGURATION</command> (Artur Zakirov) </para> <para> @@ -3046,8 +3552,8 @@ Branch: REL9_5_STABLE [7816d1356] 2016-11-24 15:39:55 -0300 --> <para> Fix commit timestamp mechanism to not fail when queried about - the special XIDs <literal>FrozenTransactionId</> - and <literal>BootstrapTransactionId</> (Craig Ringer) + the special XIDs <literal>FrozenTransactionId</literal> + and <literal>BootstrapTransactionId</literal> (Craig Ringer) </para> </listitem> @@ -3068,8 +3574,8 @@ Branch: REL9_5_STABLE [6e00ba1e1] 2016-11-10 15:00:58 -0500 <para> The symptom was spurious <quote>ON CONFLICT is not supported on table - ... used as a catalog table</> errors when the target - of <command>INSERT ... ON CONFLICT</> is a view with cascade option. + ... used as a catalog table</quote> errors when the target + of <command>INSERT ... ON CONFLICT</command> is a view with cascade option. </para> </listitem> @@ -3081,8 +3587,8 @@ Branch: REL9_6_STABLE [da05d0ebc] 2016-12-04 15:02:46 -0500 Branch: REL9_5_STABLE [25c06a1ed] 2016-12-04 15:02:48 -0500 --> <para> - Fix incorrect <quote>target lists can have at most <replaceable>N</> - entries</quote> complaint when using <literal>ON CONFLICT</> with + Fix incorrect <quote>target lists can have at most <replaceable>N</replaceable> + entries</quote> complaint when using <literal>ON CONFLICT</literal> with wide tables (Tom Lane) </para> </listitem> @@ -3094,8 +3600,8 @@ Branch: master [da8f3ebf3] 2016-11-02 14:32:13 -0400 Branch: REL9_6_STABLE [f4d865f22] 2016-11-02 14:32:13 -0400 --> <para> - Fix spurious <quote>query provides a value for a dropped column</> - errors during <command>INSERT</> or <command>UPDATE</> on a table + Fix spurious <quote>query provides a value for a dropped column</quote> + errors during <command>INSERT</command> or <command>UPDATE</command> on a table with a dropped column (Tom Lane) </para> </listitem> @@ -3110,13 +3616,13 @@ Branch: REL9_4_STABLE [44c8b4fcd] 2016-11-20 14:26:19 -0500 Branch: REL9_3_STABLE [71db302ec] 2016-11-20 14:26:19 -0500 --> <para> - Prevent multicolumn expansion of <replaceable>foo</><literal>.*</> in - an <command>UPDATE</> source expression (Tom Lane) + Prevent multicolumn expansion of <replaceable>foo</replaceable><literal>.*</literal> in + an <command>UPDATE</command> source expression (Tom Lane) </para> <para> This led to <quote>UPDATE target count mismatch --- internal - error</>. Now the syntax is understood as a whole-row variable, + error</quote>. Now the syntax is understood as a whole-row variable, as it would be in other contexts. </para> </listitem> @@ -3133,12 +3639,12 @@ Branch: REL9_2_STABLE [082d1fb9e] 2016-12-09 12:01:14 -0500 --> <para> Ensure that column typmods are determined accurately for - multi-row <literal>VALUES</> constructs (Tom Lane) + multi-row <literal>VALUES</literal> constructs (Tom Lane) </para> <para> This fixes problems occurring when the first value in a column has a - determinable typmod (e.g., length for a <type>varchar</> value) but + determinable typmod (e.g., length for a <type>varchar</type> value) but later values don't share the same limit. </para> </listitem> @@ -3162,8 +3668,8 @@ Branch: REL9_2_STABLE [6e2c21ec5] 2016-12-21 17:39:33 -0500 Normally, a Unicode surrogate leading character must be followed by a Unicode surrogate trailing character, but the check for this was missed if the leading character was the last character in a Unicode - string literal (<literal>U&'...'</>) or Unicode identifier - (<literal>U&"..."</>). + string literal (<literal>U&'...'</literal>) or Unicode identifier + (<literal>U&"..."</literal>). </para> </listitem> @@ -3174,7 +3680,7 @@ Branch: master [db80acfc9] 2016-12-20 09:20:17 +0200 Branch: REL9_6_STABLE [ce92fc4e2] 2016-12-20 09:20:30 +0200 --> <para> - Fix execution of <literal>DISTINCT</> and ordered aggregates when + Fix execution of <literal>DISTINCT</literal> and ordered aggregates when multiple such aggregates are able to share the same transition state (Heikki Linnakangas) </para> @@ -3189,7 +3695,7 @@ Branch: master [260443847] 2016-12-19 13:49:50 -0500 Branch: REL9_6_STABLE [3f07eff10] 2016-12-19 13:49:45 -0500 --> <para> - Fix implementation of phrase search operators in <type>tsquery</> + Fix implementation of phrase search operators in <type>tsquery</type> (Tom Lane) </para> @@ -3218,7 +3724,7 @@ Branch: REL9_2_STABLE [fe6120f9b] 2017-01-26 12:17:47 -0500 --> <para> Ensure that a purely negative text search query, such - as <literal>!foo</>, matches empty <type>tsvector</>s (Tom Dunstan) + as <literal>!foo</literal>, matches empty <type>tsvector</type>s (Tom Dunstan) </para> <para> @@ -3238,7 +3744,7 @@ Branch: REL9_3_STABLE [79e1a9efa] 2016-12-11 13:09:57 -0500 Branch: REL9_2_STABLE [f4ccee408] 2016-12-11 13:09:57 -0500 --> <para> - Prevent crash when <function>ts_rewrite()</> replaces a non-top-level + Prevent crash when <function>ts_rewrite()</function> replaces a non-top-level subtree with an empty query (Artur Zakirov) </para> </listitem> @@ -3254,7 +3760,7 @@ Branch: REL9_3_STABLE [407d513df] 2016-10-30 17:35:43 -0400 Branch: REL9_2_STABLE [606e16a7f] 2016-10-30 17:35:43 -0400 --> <para> - Fix performance problems in <function>ts_rewrite()</> (Tom Lane) + Fix performance problems in <function>ts_rewrite()</function> (Tom Lane) </para> </listitem> @@ -3269,7 +3775,7 @@ Branch: REL9_3_STABLE [77a22f898] 2016-10-30 15:24:40 -0400 Branch: REL9_2_STABLE [b0f8a273e] 2016-10-30 15:24:40 -0400 --> <para> - Fix <function>ts_rewrite()</>'s handling of nested NOT operators + Fix <function>ts_rewrite()</function>'s handling of nested NOT operators (Tom Lane) </para> </listitem> @@ -3283,7 +3789,7 @@ Branch: REL9_5_STABLE [7151e72d7] 2016-10-30 12:27:41 -0400 --> <para> Improve speed of user-defined aggregates that - use <function>array_append()</> as transition function (Tom Lane) + use <function>array_append()</function> as transition function (Tom Lane) </para> </listitem> @@ -3298,7 +3804,7 @@ Branch: REL9_3_STABLE [ee9cb284a] 2017-01-05 11:33:51 -0500 Branch: REL9_2_STABLE [e0d59c6ef] 2017-01-05 11:33:51 -0500 --> <para> - Fix <function>array_fill()</> to handle empty arrays properly (Tom Lane) + Fix <function>array_fill()</function> to handle empty arrays properly (Tom Lane) </para> </listitem> @@ -3310,8 +3816,8 @@ Branch: REL9_6_STABLE [79c89f1f4] 2016-12-09 12:42:17 -0300 Branch: REL9_5_STABLE [581b09c72] 2016-12-09 12:42:17 -0300 --> <para> - Fix possible crash in <function>array_position()</> - or <function>array_positions()</> when processing arrays of records + Fix possible crash in <function>array_position()</function> + or <function>array_positions()</function> when processing arrays of records (Junseok Yang) </para> </listitem> @@ -3327,7 +3833,7 @@ Branch: REL9_3_STABLE [e71fe8470] 2016-12-16 12:53:22 +0200 Branch: REL9_2_STABLE [c8f8ed5c2] 2016-12-16 12:53:27 +0200 --> <para> - Fix one-byte buffer overrun in <function>quote_literal_cstr()</> + Fix one-byte buffer overrun in <function>quote_literal_cstr()</function> (Heikki Linnakangas) </para> @@ -3348,8 +3854,8 @@ Branch: REL9_3_STABLE [f64b11fa0] 2017-01-17 17:32:20 +0900 Branch: REL9_2_STABLE [c73157ca0] 2017-01-17 17:32:45 +0900 --> <para> - Prevent multiple calls of <function>pg_start_backup()</> - and <function>pg_stop_backup()</> from running concurrently (Michael + Prevent multiple calls of <function>pg_start_backup()</function> + and <function>pg_stop_backup()</function> from running concurrently (Michael Paquier) </para> @@ -3368,7 +3874,7 @@ Branch: REL9_5_STABLE [74e67bbad] 2017-01-18 15:21:52 -0500 --> <para> Disable transform that attempted to remove no-op <literal>AT TIME - ZONE</> conversions (Tom Lane) + ZONE</literal> conversions (Tom Lane) </para> <para> @@ -3388,15 +3894,15 @@ Branch: REL9_3_STABLE [583599839] 2016-12-27 15:43:54 -0500 Branch: REL9_2_STABLE [beae7d5f0] 2016-12-27 15:43:55 -0500 --> <para> - Avoid discarding <type>interval</>-to-<type>interval</> casts + Avoid discarding <type>interval</type>-to-<type>interval</type> casts that aren't really no-ops (Tom Lane) </para> <para> In some cases, a cast that should result in zeroing out - low-order <type>interval</> fields was mistakenly deemed to be a + low-order <type>interval</type> fields was mistakenly deemed to be a no-op and discarded. An example is that casting from <type>INTERVAL - MONTH</> to <type>INTERVAL YEAR</> failed to clear the months field. + MONTH</type> to <type>INTERVAL YEAR</type> failed to clear the months field. </para> </listitem> @@ -3432,7 +3938,7 @@ Branch: master [4212cb732] 2016-12-06 11:11:54 -0500 Branch: REL9_6_STABLE [ebe5dc9e0] 2016-12-06 11:43:12 -0500 --> <para> - Allow statements prepared with <command>PREPARE</> to be given + Allow statements prepared with <command>PREPARE</command> to be given parallel plans (Amit Kapila, Tobias Bussmann) </para> </listitem> @@ -3501,7 +4007,7 @@ Branch: REL9_6_STABLE [7defc3b97] 2016-11-10 11:31:56 -0500 --> <para> Fix the plan generated for sorted partial aggregation with a constant - <literal>GROUP BY</> clause (Tom Lane) + <literal>GROUP BY</literal> clause (Tom Lane) </para> </listitem> @@ -3512,8 +4018,8 @@ Branch: master [1f542a2ea] 2016-12-13 13:20:37 -0500 Branch: REL9_6_STABLE [997a2994e] 2016-12-13 13:20:16 -0500 --> <para> - Fix <quote>could not find plan for CTE</> planner error when dealing - with a <literal>UNION ALL</> containing CTE references (Tom Lane) + Fix <quote>could not find plan for CTE</quote> planner error when dealing + with a <literal>UNION ALL</literal> containing CTE references (Tom Lane) </para> </listitem> @@ -3530,7 +4036,7 @@ Branch: REL9_6_STABLE [b971a98ce] 2017-02-02 19:11:27 -0500 <para> The typical consequence of this mistake was a <quote>plan should not - reference subplan's variable</> error. + reference subplan's variable</quote> error. </para> </listitem> @@ -3561,7 +4067,7 @@ Branch: master [bec96c82f] 2017-01-19 12:06:21 -0500 Branch: REL9_6_STABLE [fd081cabf] 2017-01-19 12:06:27 -0500 --> <para> - Fix <application>pg_dump</> to emit the data of a sequence that is + Fix <application>pg_dump</application> to emit the data of a sequence that is marked as an extension configuration table (Michael Paquier) </para> </listitem> @@ -3573,14 +4079,14 @@ Branch: master [e2090d9d2] 2017-01-31 16:24:11 -0500 Branch: REL9_6_STABLE [eb5e9d90d] 2017-01-31 16:24:14 -0500 --> <para> - Fix mishandling of <command>ALTER DEFAULT PRIVILEGES ... REVOKE</> - in <application>pg_dump</> (Stephen Frost) + Fix mishandling of <command>ALTER DEFAULT PRIVILEGES ... REVOKE</command> + in <application>pg_dump</application> (Stephen Frost) </para> <para> - <application>pg_dump</> missed issuing the - required <literal>REVOKE</> commands in cases where <command>ALTER - DEFAULT PRIVILEGES</> had been used to reduce privileges to less than + <application>pg_dump</application> missed issuing the + required <literal>REVOKE</literal> commands in cases where <command>ALTER + DEFAULT PRIVILEGES</command> had been used to reduce privileges to less than they would normally be. </para> </listitem> @@ -3602,7 +4108,7 @@ Branch: REL9_3_STABLE [fc03f7dd1] 2016-12-21 13:47:28 -0500 Branch: REL9_2_STABLE [59a389891] 2016-12-21 13:47:32 -0500 --> <para> - Fix <application>pg_dump</> to dump user-defined casts and transforms + Fix <application>pg_dump</application> to dump user-defined casts and transforms that use built-in functions (Stephen Frost) </para> </listitem> @@ -3616,15 +4122,15 @@ Branch: REL9_5_STABLE [a7864037d] 2016-11-17 14:59:23 -0500 Branch: REL9_4_STABLE [e69b532be] 2016-11-17 14:59:26 -0500 --> <para> - Fix <application>pg_restore</> with <option>--create --if-exists</> + Fix <application>pg_restore</application> with <option>--create --if-exists</option> to behave more sanely if an archive contains - unrecognized <command>DROP</> commands (Tom Lane) + unrecognized <command>DROP</command> commands (Tom Lane) </para> <para> This doesn't fix any live bug, but it may improve the behavior in - future if <application>pg_restore</> is used with an archive - generated by a later <application>pg_dump</> version. + future if <application>pg_restore</application> is used with an archive + generated by a later <application>pg_dump</application> version. </para> </listitem> @@ -3637,7 +4143,7 @@ Branch: REL9_5_STABLE [bc53d7130] 2016-12-19 10:16:02 +0100 Branch: REL9_4_STABLE [f6508827a] 2016-12-19 10:16:12 +0100 --> <para> - Fix <application>pg_basebackup</>'s rate limiting in the presence of + Fix <application>pg_basebackup</application>'s rate limiting in the presence of slow I/O (Antonin Houska) </para> @@ -3656,8 +4162,8 @@ Branch: REL9_5_STABLE [6d779e05a] 2016-11-07 15:03:56 +0100 Branch: REL9_4_STABLE [5556420d4] 2016-11-07 15:04:23 +0100 --> <para> - Fix <application>pg_basebackup</>'s handling of - symlinked <filename>pg_stat_tmp</> and <filename>pg_replslot</> + Fix <application>pg_basebackup</application>'s handling of + symlinked <filename>pg_stat_tmp</filename> and <filename>pg_replslot</filename> subdirectories (Magnus Hagander, Michael Paquier) </para> </listitem> @@ -3673,7 +4179,7 @@ Branch: REL9_3_STABLE [92929a3e3] 2016-10-27 12:00:05 -0400 Branch: REL9_2_STABLE [629575fa2] 2016-10-27 12:14:07 -0400 --> <para> - Fix possible <application>pg_basebackup</> failure on standby + Fix possible <application>pg_basebackup</application> failure on standby server when including WAL files (Amit Kapila, Robert Haas) </para> </listitem> @@ -3685,10 +4191,10 @@ Branch: master [dbdfd114f] 2016-11-25 18:36:10 -0500 Branch: REL9_6_STABLE [255bcd27f] 2016-11-25 18:36:10 -0500 --> <para> - Improve <application>initdb</> to insert the correct + Improve <application>initdb</application> to insert the correct platform-specific default values for - the <replaceable>xxx</><literal>_flush_after</> parameters - into <filename>postgresql.conf</> (Fabien Coelho, Tom Lane) + the <replaceable>xxx</replaceable><literal>_flush_after</literal> parameters + into <filename>postgresql.conf</filename> (Fabien Coelho, Tom Lane) </para> <para> @@ -3706,7 +4212,7 @@ Branch: REL9_5_STABLE [c472f2a33] 2016-12-22 15:01:39 -0500 --> <para> Fix possible mishandling of expanded arrays in domain check - constraints and <literal>CASE</> execution (Tom Lane) + constraints and <literal>CASE</literal> execution (Tom Lane) </para> <para> @@ -3762,14 +4268,14 @@ Branch: REL9_3_STABLE [9c0b04f18] 2016-11-06 14:43:14 -0500 Branch: REL9_2_STABLE [92b7b1058] 2016-11-06 14:43:14 -0500 --> <para> - Fix PL/Tcl to support triggers on tables that have <literal>.tupno</> + Fix PL/Tcl to support triggers on tables that have <literal>.tupno</literal> as a column name (Tom Lane) </para> <para> This matches the (previously undocumented) behavior of - PL/Tcl's <command>spi_exec</> and <command>spi_execp</> commands, - namely that a magic <literal>.tupno</> column is inserted only if + PL/Tcl's <command>spi_exec</command> and <command>spi_execp</command> commands, + namely that a magic <literal>.tupno</literal> column is inserted only if there isn't a real column named that. </para> </listitem> @@ -3785,7 +4291,7 @@ Branch: REL9_3_STABLE [46b6f3fff] 2016-11-15 16:17:19 -0500 Branch: REL9_2_STABLE [13aa9af37] 2016-11-15 16:17:19 -0500 --> <para> - Allow DOS-style line endings in <filename>~/.pgpass</> files, + Allow DOS-style line endings in <filename>~/.pgpass</filename> files, even on Unix (Vik Fearing) </para> @@ -3806,7 +4312,7 @@ Branch: REL9_3_STABLE [1df8b3fe8] 2016-12-22 08:32:25 +0100 Branch: REL9_2_STABLE [501c91074] 2016-12-22 08:34:07 +0100 --> <para> - Fix one-byte buffer overrun if <application>ecpg</> is given a file + Fix one-byte buffer overrun if <application>ecpg</application> is given a file name that ends with a dot (Takayuki Tsunakawa) </para> </listitem> @@ -3819,11 +4325,11 @@ Branch: REL9_6_STABLE [6a8c67f50] 2016-12-25 16:04:47 -0500 --> <para> Fix incorrect error reporting for duplicate data - in <application>psql</>'s <command>\crosstabview</> (Tom Lane) + in <application>psql</application>'s <command>\crosstabview</command> (Tom Lane) </para> <para> - <application>psql</> sometimes quoted the wrong row and/or column + <application>psql</application> sometimes quoted the wrong row and/or column values when complaining about multiple entries for the same crosstab cell. </para> @@ -3840,8 +4346,8 @@ Branch: REL9_3_STABLE [2022d594d] 2016-12-23 21:01:48 -0500 Branch: REL9_2_STABLE [26b55d669] 2016-12-23 21:01:51 -0500 --> <para> - Fix <application>psql</>'s tab completion for <command>ALTER DEFAULT - PRIVILEGES</> (Gilles Darold, Stephen Frost) + Fix <application>psql</application>'s tab completion for <command>ALTER DEFAULT + PRIVILEGES</command> (Gilles Darold, Stephen Frost) </para> </listitem> @@ -3852,8 +4358,8 @@ Branch: master [404e66758] 2016-11-28 11:51:30 -0500 Branch: REL9_6_STABLE [28735cc72] 2016-11-28 11:51:35 -0500 --> <para> - Fix <application>psql</>'s tab completion for <command>ALTER TABLE t - ALTER c DROP ...</> (Kyotaro Horiguchi) + Fix <application>psql</application>'s tab completion for <command>ALTER TABLE t + ALTER c DROP ...</command> (Kyotaro Horiguchi) </para> </listitem> @@ -3868,9 +4374,9 @@ Branch: REL9_3_STABLE [82eb5c514] 2016-12-07 12:19:56 -0500 Branch: REL9_2_STABLE [1ec5cc025] 2016-12-07 12:19:57 -0500 --> <para> - In <application>psql</>, treat an empty or all-blank setting of - the <envar>PAGER</> environment variable as meaning <quote>no - pager</> (Tom Lane) + In <application>psql</application>, treat an empty or all-blank setting of + the <envar>PAGER</envar> environment variable as meaning <quote>no + pager</quote> (Tom Lane) </para> <para> @@ -3890,8 +4396,8 @@ Branch: REL9_3_STABLE [9b8507bfa] 2016-12-22 09:47:25 -0800 Branch: REL9_2_STABLE [44de099f8] 2016-12-22 09:46:46 -0800 --> <para> - Improve <filename>contrib/dblink</>'s reporting of - low-level <application>libpq</> errors, such as out-of-memory + Improve <filename>contrib/dblink</filename>'s reporting of + low-level <application>libpq</application> errors, such as out-of-memory (Joe Conway) </para> </listitem> @@ -3906,14 +4412,14 @@ Branch: REL9_4_STABLE [cb687e0ac] 2016-12-22 09:19:08 -0800 Branch: REL9_3_STABLE [bd46cce21] 2016-12-22 09:18:50 -0800 --> <para> - Teach <filename>contrib/dblink</> to ignore irrelevant server options - when it uses a <filename>contrib/postgres_fdw</> foreign server as + Teach <filename>contrib/dblink</filename> to ignore irrelevant server options + when it uses a <filename>contrib/postgres_fdw</filename> foreign server as the source of connection options (Corey Huinker) </para> <para> Previously, if the foreign server object had options that were not - also <application>libpq</> connection options, an error occurred. + also <application>libpq</application> connection options, an error occurred. </para> </listitem> @@ -3927,7 +4433,7 @@ Branch: REL9_6_STABLE [2a8783e44] 2016-11-02 00:09:28 -0400 Branch: REL9_5_STABLE [af636d7b5] 2016-11-02 00:09:28 -0400 --> <para> - Fix portability problems in <filename>contrib/pageinspect</>'s + Fix portability problems in <filename>contrib/pageinspect</filename>'s functions for GIN indexes (Peter Eisentraut, Tom Lane) </para> </listitem> @@ -4016,7 +4522,7 @@ Branch: REL9_3_STABLE [2b133be04] 2017-01-30 11:41:02 -0500 Branch: REL9_2_STABLE [ef878cc2c] 2017-01-30 11:41:09 -0500 --> <para> - Update time zone data files to <application>tzdata</> release 2016j + Update time zone data files to <application>tzdata</application> release 2016j for DST law changes in northern Cyprus (adding a new zone Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga, and Antarctica/Casey. @@ -4083,7 +4589,7 @@ Branch: REL9_3_STABLE [1c02ee314] 2016-10-19 15:00:34 +0300 crash recovery, or to be written incorrectly on a standby server. Bogus entries in a free space map could lead to attempts to access pages that have been truncated away from the relation itself, typically - producing errors like <quote>could not read block <replaceable>XXX</>: + producing errors like <quote>could not read block <replaceable>XXX</replaceable>: read only 0 of 8192 bytes</quote>. Checksum failures in the visibility map are also possible, if checksumming is enabled. </para> @@ -4091,7 +4597,7 @@ Branch: REL9_3_STABLE [1c02ee314] 2016-10-19 15:00:34 +0300 <para> Procedures for determining whether there is a problem and repairing it if so are discussed at - <ulink url="https://wiki.postgresql.org/wiki/Free_Space_Map_Problems"></>. + <ulink url="https://wiki.postgresql.org/wiki/Free_Space_Map_Problems"></ulink>. </para> </listitem> @@ -4102,7 +4608,7 @@ Branch: master [5afcd2aa7] 2016-09-30 20:40:55 -0400 Branch: REL9_6_STABLE [b6d906073] 2016-09-30 20:39:06 -0400 --> <para> - Fix possible data corruption when <application>pg_upgrade</> rewrites + Fix possible data corruption when <application>pg_upgrade</application> rewrites a relation visibility map into 9.6 format (Tom Lane) </para> @@ -4112,20 +4618,20 @@ Branch: REL9_6_STABLE [b6d906073] 2016-09-30 20:39:06 -0400 Windows, the old map was read using text mode, leading to incorrect results if the map happened to contain consecutive bytes that matched a carriage return/line feed sequence. The latter error would almost - always lead to a <application>pg_upgrade</> failure due to the map + always lead to a <application>pg_upgrade</application> failure due to the map file appearing to be the wrong length. </para> <para> If you are using a big-endian machine (many non-Intel architectures - are big-endian) and have used <application>pg_upgrade</> to upgrade + are big-endian) and have used <application>pg_upgrade</application> to upgrade from a pre-9.6 release, you should assume that all visibility maps are incorrect and need to be regenerated. It is sufficient to truncate each relation's visibility map - with <filename>contrib/pg_visibility</>'s - <function>pg_truncate_visibility_map()</> function. + with <filename>contrib/pg_visibility</filename>'s + <function>pg_truncate_visibility_map()</function> function. For more information see - <ulink url="https://wiki.postgresql.org/wiki/Visibility_Map_Problems"></>. + <ulink url="https://wiki.postgresql.org/wiki/Visibility_Map_Problems"></ulink>. </para> </listitem> @@ -4138,7 +4644,7 @@ Branch: REL9_5_STABLE [65d85b8f9] 2016-10-23 18:36:13 -0400 --> <para> Don't throw serialization errors for self-conflicting insertions - in <command>INSERT ... ON CONFLICT</> (Thomas Munro, Peter Geoghegan) + in <command>INSERT ... ON CONFLICT</command> (Thomas Munro, Peter Geoghegan) </para> </listitem> @@ -4150,7 +4656,7 @@ Branch: REL9_6_STABLE [a5f0bd77a] 2016-10-17 12:13:35 +0300 --> <para> Fix use-after-free hazard in execution of aggregate functions - using <literal>DISTINCT</> (Peter Geoghegan) + using <literal>DISTINCT</literal> (Peter Geoghegan) </para> <para> @@ -4185,7 +4691,7 @@ Branch: REL9_6_STABLE [190765a05] 2016-10-03 16:23:02 -0400 Branch: REL9_5_STABLE [647a86e37] 2016-10-03 16:23:12 -0400 --> <para> - Fix <command>COPY</> with a column name list from a table that has + Fix <command>COPY</command> with a column name list from a table that has row-level security enabled (Adam Brightwell) </para> </listitem> @@ -4201,14 +4707,14 @@ Branch: REL9_3_STABLE [edb514306] 2016-10-20 17:18:09 -0400 Branch: REL9_2_STABLE [f17c26dbd] 2016-10-20 17:18:14 -0400 --> <para> - Fix <command>EXPLAIN</> to emit valid XML when + Fix <command>EXPLAIN</command> to emit valid XML when <xref linkend="guc-track-io-timing"> is on (Markus Winand) </para> <para> Previously the XML output-format option produced syntactically invalid - tags such as <literal><I/O-Read-Time></>. That is now - rendered as <literal><I-O-Read-Time></>. + tags such as <literal><I/O-Read-Time></literal>. That is now + rendered as <literal><I-O-Read-Time></literal>. </para> </listitem> @@ -4220,7 +4726,7 @@ Branch: REL9_6_STABLE [03f2bf70a] 2016-10-13 19:46:06 -0400 Branch: REL9_5_STABLE [3cd504254] 2016-10-13 19:45:58 -0400 --> <para> - Fix statistics update for <command>TRUNCATE</> in a prepared + Fix statistics update for <command>TRUNCATE</command> in a prepared transaction (Stas Kelvich) </para> </listitem> @@ -4242,16 +4748,16 @@ Branch: REL9_3_STABLE [f0bf0f233] 2016-10-13 17:05:15 -0400 Branch: REL9_2_STABLE [6f2db29ec] 2016-10-13 17:05:15 -0400 --> <para> - Fix bugs in merging inherited <literal>CHECK</> constraints while + Fix bugs in merging inherited <literal>CHECK</literal> constraints while creating or altering a table (Tom Lane, Amit Langote) </para> <para> - Allow identical <literal>CHECK</> constraints to be added to a parent + Allow identical <literal>CHECK</literal> constraints to be added to a parent and child table in either order. Prevent merging of a valid - constraint from the parent table with a <literal>NOT VALID</> + constraint from the parent table with a <literal>NOT VALID</literal> constraint on the child. Likewise, prevent merging of a <literal>NO - INHERIT</> child constraint with an inherited constraint. + INHERIT</literal> child constraint with an inherited constraint. </para> </listitem> @@ -4264,8 +4770,8 @@ Branch: REL9_5_STABLE [f50fa46cc] 2016-10-03 16:40:27 -0400 --> <para> Show a sensible value - in <structname>pg_settings</>.<structfield>unit</> - for <varname>min_wal_size</> and <varname>max_wal_size</> (Tom Lane) + in <structname>pg_settings</structname>.<structfield>unit</structfield> + for <varname>min_wal_size</varname> and <varname>max_wal_size</varname> (Tom Lane) </para> </listitem> @@ -4276,7 +4782,7 @@ Branch: master [9c4cc9e2c] 2016-10-13 00:25:48 -0400 Branch: REL9_6_STABLE [0e9e64c07] 2016-10-13 00:25:28 -0400 --> <para> - Fix replacement of array elements in <function>jsonb_set()</> + Fix replacement of array elements in <function>jsonb_set()</function> (Tom Lane) </para> @@ -4364,7 +4870,7 @@ Branch: REL9_4_STABLE [6d3cbbf59] 2016-10-13 15:07:11 -0400 </para> <para> - This avoids possible failures during <function>munmap()</> on systems + This avoids possible failures during <function>munmap()</function> on systems with atypical default huge page sizes. Except in crash-recovery cases, there were no ill effects other than a log message. </para> @@ -4390,7 +4896,7 @@ Branch: REL9_1_STABLE [e84e4761f] 2016-10-07 12:53:51 +0300 --> <para> Don't try to share SSL contexts across multiple connections - in <application>libpq</> (Heikki Linnakangas) + in <application>libpq</application> (Heikki Linnakangas) </para> <para> @@ -4411,12 +4917,12 @@ Branch: REL9_2_STABLE [7397f62e7] 2016-10-10 10:35:58 -0400 Branch: REL9_1_STABLE [fb6825fe5] 2016-10-10 10:35:58 -0400 --> <para> - Avoid corner-case memory leak in <application>libpq</> (Tom Lane) + Avoid corner-case memory leak in <application>libpq</application> (Tom Lane) </para> <para> The reported problem involved leaking an error report - during <function>PQreset()</>, but there might be related cases. + during <function>PQreset()</function>, but there might be related cases. </para> </listitem> @@ -4428,7 +4934,7 @@ Branch: REL9_6_STABLE [bac56dbe0] 2016-10-03 10:07:39 -0400 Branch: REL9_5_STABLE [0f259bd17] 2016-10-03 10:07:39 -0400 --> <para> - In <application>pg_upgrade</>, check library loadability in name order + In <application>pg_upgrade</application>, check library loadability in name order (Tom Lane) </para> @@ -4446,13 +4952,13 @@ Branch: master [e8bdee277] 2016-10-02 14:31:28 -0400 Branch: REL9_6_STABLE [f40334b85] 2016-10-02 14:31:28 -0400 --> <para> - Fix <application>pg_upgrade</> to work correctly for extensions + Fix <application>pg_upgrade</application> to work correctly for extensions containing index access methods (Tom Lane) </para> <para> To allow this, the server has been extended to support <command>ALTER - EXTENSION ADD/DROP ACCESS METHOD</>. That functionality should have + EXTENSION ADD/DROP ACCESS METHOD</command>. That functionality should have been included in the original patch to support dynamic creation of access methods, but it was overlooked. </para> @@ -4465,7 +4971,7 @@ Branch: master [f002ed2b8] 2016-09-30 20:40:56 -0400 Branch: REL9_6_STABLE [53fbeed40] 2016-09-30 20:40:27 -0400 --> <para> - Improve error reporting in <application>pg_upgrade</>'s file + Improve error reporting in <application>pg_upgrade</application>'s file copying/linking/rewriting steps (Tom Lane, Álvaro Herrera) </para> </listitem> @@ -4477,7 +4983,7 @@ Branch: master [4806f26f9] 2016-10-07 09:51:18 -0400 Branch: REL9_6_STABLE [1749332ec] 2016-10-07 09:51:28 -0400 --> <para> - Fix <application>pg_dump</> to work against pre-7.4 servers + Fix <application>pg_dump</application> to work against pre-7.4 servers (Amit Langote, Tom Lane) </para> </listitem> @@ -4490,8 +4996,8 @@ Branch: REL9_6_STABLE [2933ed036] 2016-10-07 14:35:41 +0300 Branch: REL9_5_STABLE [010a1b561] 2016-10-07 14:35:45 +0300 --> <para> - Disallow specifying both <option>--source-server</> - and <option>--source-target</> options to <application>pg_rewind</> + Disallow specifying both <option>--source-server</option> + and <option>--source-target</option> options to <application>pg_rewind</application> (Michael Banck) </para> </listitem> @@ -4504,12 +5010,12 @@ Branch: REL9_6_STABLE [aab809664] 2016-10-06 13:34:38 +0300 Branch: REL9_5_STABLE [69da71254] 2016-10-06 13:34:32 +0300 --> <para> - Make <application>pg_rewind</> turn off <varname>synchronous_commit</> + Make <application>pg_rewind</application> turn off <varname>synchronous_commit</varname> in its session on the source server (Michael Banck, Michael Paquier) </para> <para> - This allows <application>pg_rewind</> to work even when the source + This allows <application>pg_rewind</application> to work even when the source server is using synchronous replication that is not working for some reason. </para> @@ -4525,8 +5031,8 @@ Branch: REL9_4_STABLE [da3f71a08] 2016-09-30 11:22:49 +0200 Branch: REL9_3_STABLE [4bff35cca] 2016-09-30 11:23:25 +0200 --> <para> - In <application>pg_xlogdump</>, retry opening new WAL segments when - using <option>--follow</> option (Magnus Hagander) + In <application>pg_xlogdump</application>, retry opening new WAL segments when + using <option>--follow</option> option (Magnus Hagander) </para> <para> @@ -4542,7 +5048,7 @@ Branch: master [9a109452d] 2016-10-01 16:32:54 -0400 Branch: REL9_6_STABLE [f4e787c82] 2016-10-01 16:32:55 -0400 --> <para> - Fix <filename>contrib/pg_visibility</> to report the correct TID for + Fix <filename>contrib/pg_visibility</filename> to report the correct TID for a corrupt tuple that has been the subject of a rolled-back update (Tom Lane) </para> @@ -4556,7 +5062,7 @@ Branch: REL9_6_STABLE [68fb75e10] 2016-10-01 13:35:20 -0400 --> <para> Fix makefile dependencies so that parallel make - of <application>PL/Python</> by itself will succeed reliably + of <application>PL/Python</application> by itself will succeed reliably (Pavel Raiskup) </para> </listitem> @@ -4594,7 +5100,7 @@ Branch: REL9_2_STABLE [a03339aef] 2016-10-19 17:57:01 -0400 Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400 --> <para> - Update time zone data files to <application>tzdata</> release 2016h + Update time zone data files to <application>tzdata</application> release 2016h for DST law changes in Palestine and Turkey, plus historical corrections for Turkey and some regions of Russia. Switch to numeric abbreviations for some time zones in Antarctica, @@ -4607,15 +5113,15 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400 or no currency among the local population. They are in process of reversing that policy in favor of using numeric UTC offsets in zones where there is no evidence of real-world use of an English - abbreviation. At least for the time being, <productname>PostgreSQL</> + abbreviation. At least for the time being, <productname>PostgreSQL</productname> will continue to accept such removed abbreviations for timestamp input. - But they will not be shown in the <structname>pg_timezone_names</> + But they will not be shown in the <structname>pg_timezone_names</structname> view nor used for output. </para> <para> - In this update, <literal>AMT</> is no longer shown as being in use to - mean Armenia Time. Therefore, we have changed the <literal>Default</> + In this update, <literal>AMT</literal> is no longer shown as being in use to + mean Armenia Time. Therefore, we have changed the <literal>Default</literal> abbreviation set to interpret it as Amazon Time, thus UTC-4 not UTC+4. </para> </listitem> @@ -4637,7 +5143,7 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400 <title>Overview</title> <para> - Major enhancements in <productname>PostgreSQL</> 9.6 include: + Major enhancements in <productname>PostgreSQL</productname> 9.6 include: </para> <!-- Items in this list summarize one or more items below --> @@ -4671,15 +5177,15 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400 <listitem> <para> - <filename>postgres_fdw</> now supports remote joins, sorts, - <command>UPDATE</>s, and <command>DELETE</>s + <filename>postgres_fdw</filename> now supports remote joins, sorts, + <command>UPDATE</command>s, and <command>DELETE</command>s </para> </listitem> <listitem> <para> Substantial performance improvements, especially in the area of - scalability on multi-<acronym>CPU</>-socket servers + scalability on multi-<acronym>CPU</acronym>-socket servers </para> </listitem> @@ -4714,7 +5220,7 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400 --> <para> Improve the <link - linkend="pg-stat-activity-view"><structname>pg_stat_activity</></link> + linkend="pg-stat-activity-view"><structname>pg_stat_activity</structname></link> view's information about what a process is waiting for (Amit Kapila, Ildus Kurbangaliev) </para> @@ -4722,10 +5228,10 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400 <para> Historically a process has only been shown as waiting if it was waiting for a heavyweight lock. Now waits for lightweight locks - and buffer pins are also shown in <structname>pg_stat_activity</>. + and buffer pins are also shown in <structname>pg_stat_activity</structname>. Also, the type of lock being waited for is now visible. - These changes replace the <structfield>waiting</> column with - <structfield>wait_event_type</> and <structfield>wait_event</>. + These changes replace the <structfield>waiting</structfield> column with + <structfield>wait_event_type</structfield> and <structfield>wait_event</structfield>. </para> </listitem> @@ -4735,14 +5241,14 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400 --> <para> In <link - linkend="functions-formatting-table"><function>to_char()</></>, + linkend="functions-formatting-table"><function>to_char()</function></link>, do not count a minus sign (when needed) as part of the field width for time-related fields (Bruce Momjian) </para> <para> - For example, <literal>to_char('-4 years'::interval, 'YY')</> - now returns <literal>-04</>, rather than <literal>-4</>. + For example, <literal>to_char('-4 years'::interval, 'YY')</literal> + now returns <literal>-04</literal>, rather than <literal>-4</literal>. </para> </listitem> @@ -4752,18 +5258,18 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400 --> <para> Make <link - linkend="functions-datetime-table"><function>extract()</></> behave + linkend="functions-datetime-table"><function>extract()</function></link> behave more reasonably with infinite inputs (Vitaly Burovoy) </para> <para> - Historically the <function>extract()</> function just returned + Historically the <function>extract()</function> function just returned zero given an infinite timestamp, regardless of the given field name. Make it return <literal>infinity</literal> or <literal>-infinity</literal> as appropriate when the requested field is one that is monotonically increasing (e.g, - <literal>year</>, <literal>epoch</>), or <literal>NULL</> when - it is not (e.g., <literal>day</>, <literal>hour</>). Also, + <literal>year</literal>, <literal>epoch</literal>), or <literal>NULL</literal> when + it is not (e.g., <literal>day</literal>, <literal>hour</literal>). Also, throw the expected error for bad field names. </para> </listitem> @@ -4774,9 +5280,9 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400 This commit is also listed under libpq and psql --> <para> - Remove PL/pgSQL's <quote>feature</> that suppressed the - innermost line of <literal>CONTEXT</> for messages emitted by - <command>RAISE</> commands (Pavel Stehule) + Remove PL/pgSQL's <quote>feature</quote> that suppressed the + innermost line of <literal>CONTEXT</literal> for messages emitted by + <command>RAISE</command> commands (Pavel Stehule) </para> <para> @@ -4791,13 +5297,13 @@ This commit is also listed under libpq and psql --> <para> Fix the default text search parser to allow leading digits - in <literal>email</> and <literal>host</> tokens (Artur Zakirov) + in <literal>email</literal> and <literal>host</literal> tokens (Artur Zakirov) </para> <para> In most cases this will result in few changes in the parsing of text. But if you have data where such addresses occur frequently, - it may be worth rebuilding dependent <type>tsvector</> columns + it may be worth rebuilding dependent <type>tsvector</type> columns and indexes so that addresses of this form will be found properly by text searches. </para> @@ -4809,8 +5315,8 @@ This commit is also listed under libpq and psql 2016-03-16 [9a206d063] Improve script generating unaccent rules --> <para> - Extend <link linkend="unaccent"><filename>contrib/unaccent</></>'s - standard <filename>unaccent.rules</> file to handle all diacritics + Extend <link linkend="unaccent"><filename>contrib/unaccent</filename></link>'s + standard <filename>unaccent.rules</filename> file to handle all diacritics known to Unicode, and to expand ligatures correctly (Thomas Munro, Léonard Benedetti) </para> @@ -4819,7 +5325,7 @@ This commit is also listed under libpq and psql 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 <type>tsvector</> columns and indexes that depend on the + to rebuild <type>tsvector</type> columns and indexes that depend on the result. </para> </listitem> @@ -4830,15 +5336,15 @@ This commit is also listed under libpq and psql --> <para> Remove the long-deprecated - <literal>CREATEUSER</>/<literal>NOCREATEUSER</> options from - <command>CREATE ROLE</> and allied commands (Tom Lane) + <literal>CREATEUSER</literal>/<literal>NOCREATEUSER</literal> options from + <command>CREATE ROLE</command> and allied commands (Tom Lane) </para> <para> - <literal>CREATEUSER</> actually meant <literal>SUPERUSER</>, + <literal>CREATEUSER</literal> actually meant <literal>SUPERUSER</literal>, for ancient backwards-compatibility reasons. This has been a constant source of confusion for people who (reasonably) expect - it to mean <literal>CREATEROLE</>. It has been deprecated for + it to mean <literal>CREATEROLE</literal>. It has been deprecated for ten years now, so fix the problem by removing it. </para> </listitem> @@ -4850,13 +5356,13 @@ This commit is also listed under libpq and psql 2016-05-08 [7df974ee0] Disallow superuser names starting with 'pg_' in initdb --> <para> - Treat role names beginning with <literal>pg_</> as reserved + Treat role names beginning with <literal>pg_</literal> as reserved (Stephen Frost) </para> <para> User creation of such role names is now disallowed. This prevents - conflicts with built-in roles created by <application>initdb</>. + conflicts with built-in roles created by <application>initdb</application>. </para> </listitem> @@ -4866,16 +5372,16 @@ This commit is also listed under libpq and psql --> <para> Change a column name in the - <structname>information_schema</>.<structname>routines</> - view from <structfield>result_cast_character_set_name</> - to <structfield>result_cast_char_set_name</> (Clément + <structname>information_schema</structname>.<structname>routines</structname> + view from <structfield>result_cast_character_set_name</structfield> + to <structfield>result_cast_char_set_name</structfield> (Clément Prévost) </para> <para> 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 <structname>information_schema</> views. + style, as do other <structname>information_schema</structname> views. </para> </listitem> @@ -4884,7 +5390,7 @@ This commit is also listed under libpq and psql 2015-12-08 [d5563d7df] psql: Support multiple -c and -f options, and allow mixi --> <para> - <application>psql</>'s <option>-c</option> option no longer implies + <application>psql</application>'s <option>-c</option> option no longer implies <option>--no-psqlrc</option> (Pavel Stehule, Catalin Iacob) </para> @@ -4893,7 +5399,7 @@ This commit is also listed under libpq and psql Write <option>--no-psqlrc</option> (or its abbreviation <option>-X</option>) explicitly to obtain the old behavior. Scripts so modified will still work with old - versions of <application>psql</>. + versions of <application>psql</application>. </para> </listitem> @@ -4902,7 +5408,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 --> <para> - Improve <application>pg_restore</>'s <option>-t</option> option to + Improve <application>pg_restore</application>'s <option>-t</option> option to match all types of relations, not only plain tables (Craig Ringer) </para> </listitem> @@ -4912,17 +5418,17 @@ This commit is also listed under libpq and psql 2016-02-12 [59a884e98] Change delimiter used for display of NextXID --> <para> - Change the display format used for <literal>NextXID</> in - <application>pg_controldata</> and related places (Joe Conway, + Change the display format used for <literal>NextXID</literal> in + <application>pg_controldata</application> and related places (Joe Conway, Bruce Momjian) </para> <para> Display epoch-and-transaction-ID values in the format - <replaceable>number</><literal>:</><replaceable>number</>. + <replaceable>number</replaceable><literal>:</literal><replaceable>number</replaceable>. The previous format - <replaceable>number</><literal>/</><replaceable>number</> was - confusingly similar to that used for <acronym>LSN</>s. + <replaceable>number</replaceable><literal>/</literal><replaceable>number</replaceable> was + confusingly similar to that used for <acronym>LSN</acronym>s. </para> </listitem> @@ -4940,8 +5446,8 @@ and many others in the same vein Many of the standard extensions have been updated to allow their functions to be executed within parallel query worker processes. These changes will not take effect in - databases <application>pg_upgrade</>'d from prior versions unless - you apply <command>ALTER EXTENSION UPDATE</> to each such extension + databases <application>pg_upgrade</application>'d from prior versions unless + you apply <command>ALTER EXTENSION UPDATE</command> to each such extension (in each database of a cluster). </para> </listitem> @@ -5002,7 +5508,7 @@ and many others in the same vein </para> <para> - With 9.6, <productname>PostgreSQL</> introduces initial support + With 9.6, <productname>PostgreSQL</productname> introduces initial support for parallel execution of large queries. Only strictly read-only queries where the driving table is accessed via a sequential scan can be parallelized. Hash joins and nested loops can be performed @@ -5048,7 +5554,7 @@ and many others in the same vein 2015-09-02 [30bb26b5e] Allow usage of huge maintenance_work_mem for GIN build. --> <para> - Allow <link linkend="GIN"><acronym>GIN</></> index builds to + Allow <link linkend="gin"><acronym>GIN</acronym></link> index builds to make effective use of <xref linkend="guc-maintenance-work-mem"> settings larger than 1 GB (Robert Abraham, Teodor Sigaev) </para> @@ -5076,7 +5582,7 @@ and many others in the same vein --> <para> Add <link - linkend="functions-admin-index"><function>gin_clean_pending_list()</></> + linkend="functions-admin-index"><function>gin_clean_pending_list()</function></link> function to allow manual invocation of pending-list cleanup for a GIN index (Jeff Janes) </para> @@ -5094,7 +5600,7 @@ and many others in the same vein --> <para> Improve handling of dead index tuples in <link - linkend="GiST">GiST</> indexes (Anastasia Lubennikova) + linkend="gist">GiST</link> indexes (Anastasia Lubennikova) </para> <para> @@ -5110,8 +5616,8 @@ and many others in the same vein 2016-03-30 [acdf2a8b3] Introduce SP-GiST operator class over box. --> <para> - Add an <link linkend="SPGiST">SP-GiST</link> operator class for - type <type>box</> (Alexander Lebedev) + Add an <link linkend="spgist">SP-GiST</link> operator class for + type <type>box</type> (Alexander Lebedev) </para> </listitem> @@ -5137,10 +5643,10 @@ and many others in the same vein </para> <para> - The new approach makes better use of the <acronym>CPU</> cache + The new approach makes better use of the <acronym>CPU</acronym> cache for typical cache sizes and data volumes. Where necessary, the behavior can be adjusted via the new configuration parameter - <xref linkend="guc-replacement-sort-tuples">. + <literal>replacement_sort_tuples</literal>. </para> </listitem> @@ -5162,17 +5668,17 @@ and many others in the same vein 2016-02-17 [f1f5ec1ef] Reuse abbreviated keys in ordered [set] aggregates. --> <para> - Speed up sorting of <type>uuid</>, <type>bytea</>, and - <type>char(n)</> fields by using <quote>abbreviated</> keys + Speed up sorting of <type>uuid</type>, <type>bytea</type>, and + <type>char(n)</type> fields by using <quote>abbreviated</quote> keys (Peter Geoghegan) </para> <para> Support for abbreviated keys has also been added to the non-default operator classes <link - linkend="indexes-opclass"><literal>text_pattern_ops</></>, - <literal>varchar_pattern_ops</>, and - <literal>bpchar_pattern_ops</>. Processing of ordered-set + linkend="indexes-opclass"><literal>text_pattern_ops</literal></link>, + <literal>varchar_pattern_ops</literal>, and + <literal>bpchar_pattern_ops</literal>. Processing of ordered-set aggregates can also now exploit abbreviated keys. </para> </listitem> @@ -5182,8 +5688,8 @@ and many others in the same vein 2015-12-16 [b648b7034] Speed up CREATE INDEX CONCURRENTLY's TID sort. --> <para> - Speed up <command>CREATE INDEX CONCURRENTLY</> by treating - <acronym>TID</>s as 64-bit integers during sorting (Peter + Speed up <command>CREATE INDEX CONCURRENTLY</command> by treating + <acronym>TID</acronym>s as 64-bit integers during sorting (Peter Geoghegan) </para> </listitem> @@ -5203,7 +5709,7 @@ and many others in the same vein 2015-09-03 [4aec49899] Assorted code review for recent ProcArrayLock patch. --> <para> - Reduce contention for the <literal>ProcArrayLock</> (Amit Kapila, + Reduce contention for the <literal>ProcArrayLock</literal> (Amit Kapila, Robert Haas) </para> </listitem> @@ -5234,7 +5740,7 @@ and many others in the same vein --> <para> Use atomic operations, rather than a spinlock, to protect an - <literal>LWLock</>'s wait queue (Andres Freund) + <literal>LWLock</literal>'s wait queue (Andres Freund) </para> </listitem> @@ -5244,7 +5750,7 @@ and many others in the same vein --> <para> Partition the shared hash table freelist to reduce contention on - multi-<acronym>CPU</>-socket servers (Aleksander Alekseev) + multi-<acronym>CPU</acronym>-socket servers (Aleksander Alekseev) </para> </listitem> @@ -5280,14 +5786,14 @@ and many others in the same vein 2016-04-04 [391159e03] Partially revert commit 3d3bf62f30200500637b24fdb7b992a9 --> <para> - Improve <command>ANALYZE</>'s estimates for columns with many nulls + Improve <command>ANALYZE</command>'s estimates for columns with many nulls (Tomas Vondra, Alex Shulgin) </para> <para> - Previously <command>ANALYZE</> tended to underestimate the number - of non-<literal>NULL</> distinct values in a column with many - <literal>NULL</>s, and was also inaccurate in computing the + Previously <command>ANALYZE</command> tended to underestimate the number + of non-<literal>NULL</literal> distinct values in a column with many + <literal>NULL</literal>s, and was also inaccurate in computing the most-common values. </para> </listitem> @@ -5314,13 +5820,13 @@ and many others in the same vein </para> <para> - If a table <literal>t</> has a foreign key restriction, say - <literal>(a,b) REFERENCES r (x,y)</>, then a <literal>WHERE</> - condition such as <literal>t.a = r.x AND t.b = r.y</> cannot - select more than one <literal>r</> row per <literal>t</> row. - The planner formerly considered these <literal>AND</> conditions + If a table <literal>t</literal> has a foreign key restriction, say + <literal>(a,b) REFERENCES r (x,y)</literal>, then a <literal>WHERE</literal> + condition such as <literal>t.a = r.x AND t.b = r.y</literal> cannot + select more than one <literal>r</literal> row per <literal>t</literal> row. + The planner formerly considered these <literal>AND</literal> conditions to be independent and would often drastically misestimate - selectivity as a result. Now it compares the <literal>WHERE</> + selectivity as a result. Now it compares the <literal>WHERE</literal> conditions to applicable foreign key constraints and produces better estimates. </para> @@ -5331,7 +5837,7 @@ and many others in the same vein </sect4> <sect4> - <title><command>VACUUM</></title> + <title><command>VACUUM</command></title> <itemizedlist> @@ -5361,7 +5867,7 @@ and many others in the same vein <para> If necessary, vacuum can be forced to process all-frozen - pages using the new <literal>DISABLE_PAGE_SKIPPING</> option. + pages using the new <literal>DISABLE_PAGE_SKIPPING</literal> option. Normally this should never be needed, but it might help in recovering from visibility-map corruption. </para> @@ -5372,7 +5878,7 @@ and many others in the same vein 2015-12-30 [e84290823] Avoid useless truncation attempts during VACUUM. --> <para> - Avoid useless heap-truncation attempts during <command>VACUUM</> + Avoid useless heap-truncation attempts during <command>VACUUM</command> (Jeff Janes, Tom Lane) </para> @@ -5401,19 +5907,19 @@ and many others in the same vein 2016-08-07 [9ee1cf04a] Fix TOAST access failure in RETURNING queries. --> <para> - Allow old <acronym>MVCC</> snapshots to be invalidated after a + Allow old <acronym>MVCC</acronym> snapshots to be invalidated after a configurable timeout (Kevin Grittner) </para> <para> Normally, deleted tuples cannot be physically removed by - vacuuming until the last transaction that could <quote>see</> + vacuuming until the last transaction that could <quote>see</quote> them is gone. A transaction that stays open for a long time can thus cause considerable table bloat because space cannot be recycled. This feature allows setting a time-based limit, via the new configuration parameter <xref linkend="guc-old-snapshot-threshold">, on how long an - <acronym>MVCC</> snapshot is guaranteed to be valid. After that, + <acronym>MVCC</acronym> snapshot is guaranteed to be valid. After that, dead tuples are candidates for removal. A transaction using an outdated snapshot will get an error if it attempts to read a page that potentially could have contained such data. @@ -5425,12 +5931,12 @@ and many others in the same vein 2016-02-11 [d4c3a156c] Remove GROUP BY columns that are functionally dependent --> <para> - Ignore <literal>GROUP BY</> columns that are + Ignore <literal>GROUP BY</literal> columns that are functionally dependent on other columns (David Rowley) </para> <para> - If a <literal>GROUP BY</> clause includes all columns of a + If a <literal>GROUP BY</literal> clause includes all columns of a non-deferred primary key, as well as other columns of the same table, those other columns are redundant and can be dropped from the grouping. This saves computation in many common cases. @@ -5443,17 +5949,17 @@ and many others in the same vein --> <para> Allow use of an <link linkend="indexes-index-only-scans">index-only - scan</link> on a partial index when the index's <literal>WHERE</> + scan</link> on a partial index when the index's <literal>WHERE</literal> clause references columns that are not indexed (Tomas Vondra, Kyotaro Horiguchi) </para> <para> For example, an index defined by <command>CREATE INDEX tidx_partial - ON t(b) WHERE a > 0</> can now be used for an index-only scan by - a query that specifies <literal>WHERE a > 0</> and does not - otherwise use <literal>a</>. Previously this was disallowed - because <literal>a</> is not listed as an index column. + ON t(b) WHERE a > 0</command> can now be used for an index-only scan by + a query that specifies <literal>WHERE a > 0</literal> and does not + otherwise use <literal>a</literal>. Previously this was disallowed + because <literal>a</literal> is not listed as an index column. </para> </listitem> @@ -5493,7 +5999,7 @@ and many others in the same vein </para> <para> - <productname>PostgreSQL</> writes data to the kernel's disk cache, + <productname>PostgreSQL</productname> writes data to the kernel's disk cache, from where it will be flushed to physical storage in due time. Many operating systems are not smart about managing this and allow large amounts of dirty data to accumulate before deciding to flush @@ -5504,11 +6010,11 @@ and many others in the same vein </para> <para> - On Linux, <function>sync_file_range()</> is used for this purpose, + On Linux, <function>sync_file_range()</function> is used for this purpose, 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 <function>msync()</> - or <function>posix_fadvise()</>, but those interfaces have some + platforms if they have <function>msync()</function> + or <function>posix_fadvise()</function>, but those interfaces have some undesirable side-effects so the feature is disabled by default on non-Linux platforms. </para> @@ -5533,7 +6039,7 @@ and many others in the same vein </para> <para> - For example, <command>SELECT AVG(x), VARIANCE(x) FROM tab</> can use + For example, <command>SELECT AVG(x), VARIANCE(x) FROM tab</command> can use a single per-row computation for both aggregates. </para> </listitem> @@ -5544,7 +6050,7 @@ and many others in the same vein --> <para> Speed up visibility tests for recently-created tuples by checking - the current transaction's snapshot, not <structname>pg_clog</>, to + the current transaction's snapshot, not <structname>pg_clog</structname>, to decide if the source transaction should be considered committed (Jeff Janes, Tom Lane) </para> @@ -5570,9 +6076,9 @@ and many others in the same vein </para> <para> - Two-phase commit information is now written only to <acronym>WAL</> - during <command>PREPARE TRANSACTION</>, and will be read back from - <acronym>WAL</> during <command>COMMIT PREPARED</> if that happens + Two-phase commit information is now written only to <acronym>WAL</acronym> + during <command>PREPARE TRANSACTION</command>, and will be read back from + <acronym>WAL</acronym> during <command>COMMIT PREPARED</command> 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. @@ -5603,8 +6109,8 @@ and many others in the same vein 2016-02-06 [aa2387e2f] Improve speed of timestamp/time/date output functions. --> <para> - Improve speed of the output functions for <type>timestamp</>, - <type>time</>, and <type>date</> data types (David Rowley, + Improve speed of the output functions for <type>timestamp</type>, + <type>time</type>, and <type>date</type> data types (David Rowley, Andres Freund) </para> </listitem> @@ -5615,7 +6121,7 @@ and many others in the same vein --> <para> Avoid some unnecessary cancellations of hot-standby queries - during replay of actions that take <literal>AccessExclusive</> + during replay of actions that take <literal>AccessExclusive</literal> locks (Jeff Janes) </para> </listitem> @@ -5649,8 +6155,8 @@ and many others in the same vein 2015-07-05 [6c82d8d1f] Further reduce overhead for passing plpgsql variables to --> <para> - Speed up expression evaluation in <application>PL/pgSQL</> by - keeping <literal>ParamListInfo</> entries for simple variables + Speed up expression evaluation in <application>PL/pgSQL</application> by + keeping <literal>ParamListInfo</literal> entries for simple variables valid at all times (Tom Lane) </para> </listitem> @@ -5660,7 +6166,7 @@ and many others in the same vein 2015-07-06 [4f33621f3] Don't set SO_SNDBUF on recent Windows versions that have --> <para> - Avoid reducing the <literal>SO_SNDBUF</> setting below its default + Avoid reducing the <literal>SO_SNDBUF</literal> setting below its default on recent Windows versions (Chen Huajun) </para> </listitem> @@ -5696,8 +6202,8 @@ and many others in the same vein --> <para> Add <link - linkend="pg-stat-progress-vacuum-view"><structname>pg_stat_progress_vacuum</></link> - system view to provide progress reporting for <command>VACUUM</> + linkend="pg-stat-progress-vacuum-view"><structname>pg_stat_progress_vacuum</structname></link> + system view to provide progress reporting for <command>VACUUM</command> operations (Amit Langote, Robert Haas, Vinayak Pokale, Rahila Syed) </para> </listitem> @@ -5708,11 +6214,11 @@ and many others in the same vein --> <para> Add <link - linkend="functions-controldata"><function>pg_control_system()</></>, - <function>pg_control_checkpoint()</>, - <function>pg_control_recovery()</>, and - <function>pg_control_init()</> functions to expose fields of - <filename>pg_control</> to <acronym>SQL</> (Joe Conway, Michael + linkend="functions-controldata"><function>pg_control_system()</function></link>, + <function>pg_control_checkpoint()</function>, + <function>pg_control_recovery()</function>, and + <function>pg_control_init()</function> functions to expose fields of + <filename>pg_control</filename> to <acronym>SQL</acronym> (Joe Conway, Michael Paquier) </para> </listitem> @@ -5722,15 +6228,15 @@ and many others in the same vein 2016-02-17 [a5c43b886] Add new system view, pg_config --> <para> - Add <link linkend="view-pg-config"><structname>pg_config</></link> + Add <link linkend="view-pg-config"><structname>pg_config</structname></link> system view (Joe Conway) </para> <para> This view exposes the same information available from - the <application>pg_config</> command-line utility, + the <application>pg_config</application> command-line utility, namely assorted compile-time configuration information for - <productname>PostgreSQL</>. + <productname>PostgreSQL</productname>. </para> </listitem> @@ -5739,8 +6245,8 @@ and many others in the same vein 2015-08-10 [3f811c2d6] Add confirmed_flush column to pg_replication_slots. --> <para> - Add a <structfield>confirmed_flush_lsn</> column to the <link - linkend="view-pg-replication-slots"><structname>pg_replication_slots</></link> + Add a <structfield>confirmed_flush_lsn</structfield> column to the <link + linkend="view-pg-replication-slots"><structname>pg_replication_slots</structname></link> system view (Marko Tiikkaja) </para> </listitem> @@ -5753,9 +6259,9 @@ and many others in the same vein --> <para> Add <link - linkend="pg-stat-wal-receiver-view"><structname>pg_stat_wal_receiver</></link> + linkend="pg-stat-wal-receiver-view"><structname>pg_stat_wal_receiver</structname></link> system view to provide information about the state of a hot-standby - server's <acronym>WAL</> receiver process (Michael Paquier) + server's <acronym>WAL</acronym> receiver process (Michael Paquier) </para> </listitem> @@ -5765,7 +6271,7 @@ and many others in the same vein --> <para> Add <link - linkend="functions-info-session-table"><function>pg_blocking_pids()</></> + linkend="functions-info-session-table"><function>pg_blocking_pids()</function></link> function to reliably identify which sessions block which others (Tom Lane) </para> @@ -5774,7 +6280,7 @@ and many others in the same vein 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 <structname>pg_locks</> view. However, it is unreasonably + on the <structname>pg_locks</structname> 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 old approach entirely impractical, since locks might be held or awaited by child worker @@ -5788,7 +6294,7 @@ and many others in the same vein --> <para> Add function <link - linkend="functions-admin-backup-table"><function>pg_current_xlog_flush_location()</></> + linkend="functions-admin-backup-table"><function>pg_current_xlog_flush_location()</function></link> to expose the current transaction log flush location (Tomas Vondra) </para> </listitem> @@ -5799,8 +6305,8 @@ and many others in the same vein --> <para> Add function <link - linkend="functions-info-session-table"><function>pg_notification_queue_usage()</></> - to report how full the <command>NOTIFY</> queue is (Brendan Jurd) + linkend="functions-info-session-table"><function>pg_notification_queue_usage()</function></link> + to report how full the <command>NOTIFY</command> queue is (Brendan Jurd) </para> </listitem> @@ -5816,7 +6322,7 @@ and many others in the same vein 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 <quote>grand total</> + a very large report. There is also a <quote>grand total</quote> summary line now. </para> </listitem> @@ -5826,7 +6332,7 @@ and many others in the same vein </sect4> <sect4> - <title><acronym>Authentication</></title> + <title><acronym>Authentication</acronym></title> <itemizedlist> @@ -5835,15 +6341,15 @@ and many others in the same vein 2016-04-08 [34c33a1f0] Add BSD authentication method. --> <para> - Add a <link linkend="auth-bsd"><acronym>BSD</> authentication + Add a <link linkend="auth-bsd"><acronym>BSD</acronym> authentication method</link> to allow use of - the <systemitem class="osname">BSD</> Authentication service for - <productname>PostgreSQL</> client authentication (Marisa Emerson) + the <systemitem class="osname">BSD</systemitem> Authentication service for + <productname>PostgreSQL</productname> client authentication (Marisa Emerson) </para> <para> BSD Authentication is currently only available on <systemitem - class="osname">OpenBSD</>. + class="osname">OpenBSD</systemitem>. </para> </listitem> @@ -5852,9 +6358,9 @@ and many others in the same vein 2016-04-08 [2f1d2b7a7] Set PAM_RHOST item for PAM authentication --> <para> - When using <link linkend="auth-pam"><acronym>PAM</> + When using <link linkend="auth-pam"><acronym>PAM</acronym> authentication</link>, provide the client IP address or host name - to <acronym>PAM</> modules via the <literal>PAM_RHOST</> item + to <acronym>PAM</acronym> modules via the <literal>PAM_RHOST</literal> item (Grzegorz Sampolski) </para> </listitem> @@ -5870,7 +6376,7 @@ and many others in the same vein <para> All ordinarily-reachable password authentication failure cases - should now provide specific <literal>DETAIL</> fields in the log. + should now provide specific <literal>DETAIL</literal> fields in the log. </para> </listitem> @@ -5879,7 +6385,7 @@ and many others in the same vein 2015-09-06 [643beffe8] Support RADIUS passwords up to 128 characters --> <para> - Support <link linkend="auth-radius"><acronym>RADIUS</> passwords</> + Support <link linkend="auth-radius"><acronym>RADIUS</acronym> passwords</link> up to 128 characters long (Marko Tiikkaja) </para> </listitem> @@ -5889,11 +6395,11 @@ and many others in the same vein 2016-04-08 [35e2e357c] Add authentication parameters compat_realm and upn_usena --> <para> - Add new <link linkend="sspi-auth"><acronym>SSPI</> + Add new <link linkend="sspi-auth"><acronym>SSPI</acronym> authentication</link> parameters - <varname>compat_realm</> and <varname>upn_username</> to control - whether <productname>NetBIOS</> or <productname>Kerberos</> - realm names and user names are used during <acronym>SSPI</> + <varname>compat_realm</varname> and <varname>upn_username</varname> to control + whether <productname>NetBIOS</productname> or <productname>Kerberos</productname> + realm names and user names are used during <acronym>SSPI</acronym> authentication (Christian Ullrich) </para> </listitem> @@ -5939,7 +6445,7 @@ and many others in the same vein 2015-09-08 [1aba62ec6] Allow per-tablespace effective_io_concurrency --> <para> - Allow <varname>effective_io_concurrency</> to be set per-tablespace + Allow <varname>effective_io_concurrency</varname> to be set per-tablespace to support cases where different tablespaces have different I/O characteristics (Julien Rouhaud) </para> @@ -5951,7 +6457,7 @@ and many others in the same vein 2015-09-07 [b1e1862a1] Coordinate log_line_prefix options 'm' and 'n' to share --> <para> - Add <xref linkend="guc-log-line-prefix"> option <literal>%n</> to + Add <xref linkend="guc-log-line-prefix"> option <literal>%n</literal> to print the current time in Unix epoch form, with milliseconds (Tomas Vondra, Jeff Davis) </para> @@ -5966,7 +6472,7 @@ and many others in the same vein Add <xref linkend="guc-syslog-sequence-numbers"> and <xref linkend="guc-syslog-split-messages"> configuration parameters to provide more control over the message format when logging to - <systemitem>syslog</> (Peter Eisentraut) + <systemitem>syslog</systemitem> (Peter Eisentraut) </para> </listitem> @@ -5975,16 +6481,16 @@ and many others in the same vein 2016-03-18 [b555ed810] Merge wal_level "archive" and "hot_standby" into new nam --> <para> - Merge the <literal>archive</> and <literal>hot_standby</> values + Merge the <literal>archive</literal> and <literal>hot_standby</literal> values of the <xref linkend="guc-wal-level"> configuration parameter - into a single new value <literal>replica</> (Peter Eisentraut) + into a single new value <literal>replica</literal> (Peter Eisentraut) </para> <para> Making a distinction between these settings is no longer useful, and merging them is a step towards a planned future simplification of replication setup. The old names are still accepted but are - converted to <literal>replica</> internally. + converted to <literal>replica</literal> internally. </para> </listitem> @@ -5993,15 +6499,15 @@ and many others in the same vein 2016-02-02 [7d17e683f] Add support for systemd service notifications --> <para> - Add configure option <option>--with-systemd</> to enable - calling <function>sd_notify()</> at server start and stop (Peter + Add configure option <option>--with-systemd</option> to enable + calling <function>sd_notify()</function> at server start and stop (Peter Eisentraut) </para> <para> - This allows the use of <application>systemd</> service units of - type <literal>notify</>, which greatly simplifies the management - of <productname>PostgreSQL</> under <application>systemd</>. + This allows the use of <application>systemd</application> service units of + type <literal>notify</literal>, which greatly simplifies the management + of <productname>PostgreSQL</productname> under <application>systemd</application>. </para> </listitem> @@ -6010,17 +6516,17 @@ and many others in the same vein 2016-03-19 [9a83564c5] Allow SSL server key file to have group read access if o --> <para> - Allow the server's <acronym>SSL</> key file to have group read - access if it is owned by <literal>root</> (Christoph Berg) + Allow the server's <acronym>SSL</acronym> key file to have group read + access if it is owned by <literal>root</literal> (Christoph Berg) </para> <para> Formerly, we insisted the key file be owned by the - user running the <productname>PostgreSQL</> server, but + user running the <productname>PostgreSQL</productname> server, but that is inconvenient on some systems (such as <systemitem - class="osname">Debian</>) that are configured to manage + class="osname">Debian</systemitem>) that are configured to manage certificates centrally. Therefore, allow the case where the key - file is owned by <literal>root</> and has group read access. + file is owned by <literal>root</literal> and has group read access. It is up to the operating system administrator to ensure that the group does not include any untrusted users. </para> @@ -6085,8 +6591,8 @@ XXX this is pending backpatch, may need to remove 2016-04-26 [c6ff84b06] Emit invalidations to standby for transactions without x --> <para> - Ensure that invalidation messages are recorded in <acronym>WAL</> - even when issued by a transaction that has no <acronym>XID</> + Ensure that invalidation messages are recorded in <acronym>WAL</acronym> + even when issued by a transaction that has no <acronym>XID</acronym> assigned (Andres Freund) </para> @@ -6102,7 +6608,7 @@ XXX this is pending backpatch, may need to remove 2016-04-28 [e2c79e14d] Prevent multiple cleanup process for pending list in GIN --> <para> - Prevent multiple processes from trying to clean a <acronym>GIN</> + Prevent multiple processes from trying to clean a <acronym>GIN</acronym> index's pending list concurrently (Teodor Sigaev, Jeff Janes) </para> @@ -6147,13 +6653,13 @@ XXX this is pending backpatch, may need to remove 2016-03-29 [314cbfc5d] Add new replication mode synchronous_commit = 'remote_ap --> <para> - Add new setting <literal>remote_apply</> for configuration + Add new setting <literal>remote_apply</literal> for configuration parameter <xref linkend="guc-synchronous-commit"> (Thomas Munro) </para> <para> In this mode, the master waits for the transaction to be - <emphasis>applied</> on the standby server, not just written + <emphasis>applied</emphasis> on the standby server, not just written to disk. That means that you can count on a transaction started on the standby to see all commits previously acknowledged by the master. @@ -6168,14 +6674,14 @@ XXX this is pending backpatch, may need to remove <para> Add a feature to the replication protocol, and a corresponding option to <link - linkend="functions-replication-table"><function>pg_create_physical_replication_slot()</></>, - to allow reserving <acronym>WAL</> immediately when creating a + linkend="functions-replication-table"><function>pg_create_physical_replication_slot()</function></link>, + to allow reserving <acronym>WAL</acronym> immediately when creating a replication slot (Gurjeet Singh, Michael Paquier) </para> <para> This allows the creation of a replication slot to guarantee - that all the <acronym>WAL</> needed for a base backup will be + that all the <acronym>WAL</acronym> needed for a base backup will be available. </para> </listitem> @@ -6186,13 +6692,13 @@ XXX this is pending backpatch, may need to remove --> <para> Add a <option>--slot</option> option to - <link linkend="app-pgbasebackup"><application>pg_basebackup</></> + <link linkend="app-pgbasebackup"><application>pg_basebackup</application></link> (Peter Eisentraut) </para> <para> - This lets <application>pg_basebackup</> use a replication - slot defined for <acronym>WAL</> streaming. After the base + This lets <application>pg_basebackup</application> use a replication + slot defined for <acronym>WAL</acronym> streaming. After the base backup completes, selecting the same slot for regular streaming replication allows seamless startup of the new standby server. </para> @@ -6205,8 +6711,8 @@ XXX this is pending backpatch, may need to remove --> <para> Extend <link - linkend="functions-admin-backup-table"><function>pg_start_backup()</></> - and <function>pg_stop_backup()</> to support non-exclusive backups + linkend="functions-admin-backup-table"><function>pg_start_backup()</function></link> + and <function>pg_stop_backup()</function> to support non-exclusive backups (Magnus Hagander) </para> </listitem> @@ -6226,14 +6732,14 @@ XXX this is pending backpatch, may need to remove --> <para> Allow functions that return sets of tuples to return simple - <literal>NULL</>s (Andrew Gierth, Tom Lane) + <literal>NULL</literal>s (Andrew Gierth, Tom Lane) </para> <para> - In the context of <literal>SELECT FROM function(...)</>, a function + In the context of <literal>SELECT FROM function(...)</literal>, a function that returned a set of composite values was previously not allowed - to return a plain <literal>NULL</> value as part of the set. - Now that is allowed and interpreted as a row of <literal>NULL</>s. + to return a plain <literal>NULL</literal> value as part of the set. + Now that is allowed and interpreted as a row of <literal>NULL</literal>s. This avoids corner-case errors with, for example, unnesting an array of composite values. </para> @@ -6245,14 +6751,14 @@ XXX this is pending backpatch, may need to remove --> <para> Fully support array subscripts and field selections in the - target column list of an <command>INSERT</> with multiple - <literal>VALUES</> rows (Tom Lane) + target column list of an <command>INSERT</command> with multiple + <literal>VALUES</literal> rows (Tom Lane) </para> <para> Previously, such cases failed if the same target column was mentioned more than once, e.g., <literal>INSERT INTO tab (x[1], - x[2]) VALUES (...)</>. + x[2]) VALUES (...)</literal>. </para> </listitem> @@ -6262,16 +6768,16 @@ XXX this is pending backpatch, may need to remove 2016-03-25 [d543170f2] Don't split up SRFs when choosing to postpone SELECT out --> <para> - When appropriate, postpone evaluation of <command>SELECT</> - output expressions until after an <literal>ORDER BY</> sort + When appropriate, postpone evaluation of <command>SELECT</command> + output expressions until after an <literal>ORDER BY</literal> sort (Konstantin Knizhnik) </para> <para> This change ensures that volatile or expensive functions in the output list are executed in the order suggested by <literal>ORDER - BY</>, and that they are not evaluated more times than required - when there is a <literal>LIMIT</> clause. Previously, these + BY</literal>, and that they are not evaluated more times than required + when there is a <literal>LIMIT</literal> 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. @@ -6289,9 +6795,9 @@ XXX this is pending backpatch, may need to remove </para> <para> - This change allows command tags, e.g. <command>SELECT</>, to + This change allows command tags, e.g. <command>SELECT</command>, to correctly report tuple counts larger than 4 billion. This also - applies to PL/pgSQL's <command>GET DIAGNOSTICS ... ROW_COUNT</> + applies to PL/pgSQL's <command>GET DIAGNOSTICS ... ROW_COUNT</command> command. </para> </listitem> @@ -6302,17 +6808,17 @@ XXX this is pending backpatch, may need to remove --> <para> Avoid doing encoding conversions by converting through the - <literal>MULE_INTERNAL</> encoding (Tom Lane) + <literal>MULE_INTERNAL</literal> encoding (Tom Lane) </para> <para> Previously, many conversions for Cyrillic and Central European single-byte encodings were done by converting to a - related <literal>MULE_INTERNAL</> coding scheme and then to the + related <literal>MULE_INTERNAL</literal> coding scheme and then to the destination encoding. Aside from being inefficient, this meant that when the conversion encountered an untranslatable character, the error message would confusingly complain about failure to - convert to or from <literal>MULE_INTERNAL</>, rather than the + convert to or from <literal>MULE_INTERNAL</literal>, rather than the user-visible encoding. </para> </listitem> @@ -6331,7 +6837,7 @@ XXX this is pending backpatch, may need to remove <para> Previously, the foreign join pushdown infrastructure left the question of security entirely up to individual foreign data - wrappers, but that made it too easy for an <acronym>FDW</> to + wrappers, but that made it too easy for an <acronym>FDW</acronym> 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 @@ -6353,13 +6859,13 @@ XXX this is pending backpatch, may need to remove 2015-11-27 [92e38182d] COPY (INSERT/UPDATE/DELETE .. RETURNING ..) --> <para> - Allow <command>COPY</> to copy the output of an - <literal>INSERT</>/<literal>UPDATE</>/<literal>DELETE</> - ... <literal>RETURNING</> query (Marko Tiikkaja) + Allow <command>COPY</command> to copy the output of an + <literal>INSERT</literal>/<literal>UPDATE</literal>/<literal>DELETE</literal> + ... <literal>RETURNING</literal> query (Marko Tiikkaja) </para> <para> - Previously, an intermediate <acronym>CTE</> had to be written to + Previously, an intermediate <acronym>CTE</acronym> had to be written to get this result. </para> </listitem> @@ -6369,16 +6875,16 @@ XXX this is pending backpatch, may need to remove 2016-04-05 [f2fcad27d] Support ALTER THING .. DEPENDS ON EXTENSION --> <para> - Introduce <command>ALTER <replaceable>object</> DEPENDS ON + Introduce <command>ALTER <replaceable>object</replaceable> DEPENDS ON EXTENSION</command> (Abhijit Menon-Sen) </para> <para> This command allows a database object to be marked as depending on an extension, so that it will be dropped automatically if - the extension is dropped (without needing <literal>CASCADE</>). + the extension is dropped (without needing <literal>CASCADE</literal>). However, the object is not part of the extension, and thus will - be dumped separately by <application>pg_dump</>. + be dumped separately by <application>pg_dump</application>. </para> </listitem> @@ -6387,7 +6893,7 @@ XXX this is pending backpatch, may need to remove 2015-11-19 [bc4996e61] Make ALTER .. SET SCHEMA do nothing, instead of throwing --> <para> - Make <command>ALTER <replaceable>object</> SET SCHEMA</> do nothing + Make <command>ALTER <replaceable>object</replaceable> SET SCHEMA</command> do nothing when the object is already in the requested schema, rather than throwing an error as it historically has for most object types (Marti Raudsepp) @@ -6411,8 +6917,8 @@ XXX this is pending backpatch, may need to remove 2015-07-29 [2cd40adb8] Add IF NOT EXISTS processing to ALTER TABLE ADD COLUMN --> <para> - Add an <option>IF NOT EXISTS</> option to <command>ALTER TABLE - ADD COLUMN</> (Fabrízio de Royes Mello) + Add an <option>IF NOT EXISTS</option> option to <command>ALTER TABLE + ADD COLUMN</command> (Fabrízio de Royes Mello) </para> </listitem> @@ -6422,7 +6928,7 @@ XXX this is pending backpatch, may need to remove 2016-03-10 [fcb4bfddb] Reduce lock level for altering fillfactor --> <para> - Reduce the lock strength needed by <command>ALTER TABLE</> + Reduce the lock strength needed by <command>ALTER TABLE</command> when setting fillfactor and autovacuum-related relation options (Fabrízio de Royes Mello, Simon Riggs) </para> @@ -6434,7 +6940,7 @@ XXX this is pending backpatch, may need to remove --> <para> Introduce <link linkend="sql-create-access-method"><command>CREATE - ACCESS METHOD</></> to allow extensions to create index access + ACCESS METHOD</command></link> to allow extensions to create index access methods (Alexander Korotkov, Petr Jelínek) </para> </listitem> @@ -6444,7 +6950,7 @@ XXX this is pending backpatch, may need to remove 2015-10-03 [b67aaf21e] Add CASCADE support for CREATE EXTENSION. --> <para> - Add a <literal>CASCADE</> option to <command>CREATE + Add a <literal>CASCADE</literal> option to <command>CREATE EXTENSION</command> to automatically create any extensions the requested one depends on (Petr Jelínek) </para> @@ -6455,7 +6961,7 @@ XXX this is pending backpatch, may need to remove 2015-10-05 [b943f502b] Have CREATE TABLE LIKE add OID column if any LIKEd table --> <para> - Make <command>CREATE TABLE ... LIKE</> include an <type>OID</> + Make <command>CREATE TABLE ... LIKE</command> include an <type>OID</type> column if any source table has one (Bruce Momjian) </para> </listitem> @@ -6465,14 +6971,14 @@ XXX this is pending backpatch, may need to remove 2015-12-16 [f27a6b15e] Mark CHECK constraints declared NOT VALID valid if creat --> <para> - If a <literal>CHECK</> constraint is declared <literal>NOT VALID</> + If a <literal>CHECK</literal> constraint is declared <literal>NOT VALID</literal> in a table creation command, automatically mark it as valid (Amit Langote, Amul Sul) </para> <para> This is safe because the table has no existing rows. This matches - the longstanding behavior of <literal>FOREIGN KEY</> constraints. + the longstanding behavior of <literal>FOREIGN KEY</literal> constraints. </para> </listitem> @@ -6481,16 +6987,16 @@ XXX this is pending backpatch, may need to remove 2016-03-25 [c94959d41] Fix DROP OPERATOR to reset oprcom/oprnegate links to the --> <para> - Fix <command>DROP OPERATOR</> to clear - <structname>pg_operator</>.<structfield>oprcom</> and - <structname>pg_operator</>.<structfield>oprnegate</> links to + Fix <command>DROP OPERATOR</command> to clear + <structname>pg_operator</structname>.<structfield>oprcom</structfield> and + <structname>pg_operator</structname>.<structfield>oprnegate</structfield> links to the dropped operator (Roma Sokolov) </para> <para> Formerly such links were left as-is, which could pose a problem in the somewhat unlikely event that the dropped operator's - <type>OID</> was reused for another operator. + <type>OID</type> was reused for another operator. </para> </listitem> @@ -6499,13 +7005,13 @@ XXX this is pending backpatch, may need to remove 2016-07-11 [4d042999f] Print a given subplan only once in EXPLAIN. --> <para> - Do not show the same subplan twice in <command>EXPLAIN</> output + Do not show the same subplan twice in <command>EXPLAIN</command> output (Tom Lane) </para> <para> In certain cases, typically involving SubPlan nodes in index - conditions, <command>EXPLAIN</> would print data for the same + conditions, <command>EXPLAIN</command> would print data for the same subplan twice. </para> </listitem> @@ -6516,7 +7022,7 @@ XXX this is pending backpatch, may need to remove --> <para> Disallow creation of indexes on system columns, except for - <type>OID</> columns (David Rowley) + <type>OID</type> columns (David Rowley) </para> <para> @@ -6550,8 +7056,8 @@ XXX this is pending backpatch, may need to remove checks that would throw an error if they were called by a non-superuser. This forced the use of superuser roles for some relatively pedestrian tasks. The hard-wired error checks - are now gone in favor of making <application>initdb</> revoke the - default public <literal>EXECUTE</> privilege on these functions. + are now gone in favor of making <application>initdb</application> revoke the + default public <literal>EXECUTE</literal> privilege on these functions. This allows installations to choose to grant usage of such functions to trusted roles that do not need all superuser privileges. @@ -6569,7 +7075,7 @@ XXX this is pending backpatch, may need to remove </para> <para> - Currently the only such role is <literal>pg_signal_backend</>, + Currently the only such role is <literal>pg_signal_backend</literal>, but more are expected to be added in future. </para> </listitem> @@ -6591,19 +7097,19 @@ XXX this is pending backpatch, may need to remove 2016-06-27 [6734a1cac] Change predecence of phrase operator. --> <para> - Improve <link linkend="textsearch">full-text search</> to support + Improve <link linkend="textsearch">full-text search</link> 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) </para> <para> - A phrase-search query can be specified in <type>tsquery</> - input using the new operators <literal><-></> and - <literal><<replaceable>N</>></literal>. The former means + A phrase-search query can be specified in <type>tsquery</type> + input using the new operators <literal><-></literal> and + <literal><<replaceable>N</replaceable>></literal>. The former means that the lexemes before and after it must appear adjacent to each other in that order. The latter means they must be exactly - <replaceable>N</> lexemes apart. + <replaceable>N</replaceable> lexemes apart. </para> </listitem> @@ -6613,7 +7119,7 @@ XXX this is pending backpatch, may need to remove --> <para> Allow omitting one or both boundaries in an array slice specifier, - e.g. <literal>array_col[3:]</> (Yury Zhuravlev) + e.g. <literal>array_col[3:]</literal> (Yury Zhuravlev) </para> <para> @@ -6634,19 +7140,19 @@ XXX this is pending backpatch, may need to remove <para> This change prevents unexpected out-of-range errors for - <type>timestamp with time zone</> values very close to the - implementation limits. Previously, the <quote>same</> value might - be accepted or not depending on the <varname>timezone</> setting, + <type>timestamp with time zone</type> values very close to the + implementation limits. Previously, the <quote>same</quote> value might + be accepted or not depending on the <varname>timezone</varname> setting, meaning that a dump and reload could fail on a value that had been accepted when presented. Now the limits are enforced according - to the equivalent <acronym>UTC</> time, not local time, so as to - be independent of <varname>timezone</>. + to the equivalent <acronym>UTC</acronym> time, not local time, so as to + be independent of <varname>timezone</varname>. </para> <para> - Also, <productname>PostgreSQL</> is now more careful to detect + Also, <productname>PostgreSQL</productname> is now more careful to detect overflow in operations that compute new date or timestamp values, - such as <type>date</> <literal>+</> <type>integer</>. + such as <type>date</type> <literal>+</literal> <type>integer</type>. </para> </listitem> @@ -6655,14 +7161,14 @@ XXX this is pending backpatch, may need to remove 2016-03-30 [50861cd68] Improve portability of I/O behavior for the geometric ty --> <para> - For geometric data types, make sure <literal>infinity</> and - <literal>NaN</> component values are treated consistently during + For geometric data types, make sure <literal>infinity</literal> and + <literal>NaN</literal> component values are treated consistently during input and output (Tom Lane) </para> <para> Such values will now always print the same as they would in - a simple <type>float8</> column, and be accepted the same way + a simple <type>float8</type> column, and be accepted the same way on input. Previously the behavior was platform-dependent. </para> </listitem> @@ -6675,8 +7181,8 @@ XXX this is pending backpatch, may need to remove --> <para> Upgrade - the <link linkend="textsearch-ispell-dictionary"><literal>ispell</></> - dictionary type to handle modern <productname>Hunspell</> files and + the <link linkend="textsearch-ispell-dictionary"><literal>ispell</literal></link> + dictionary type to handle modern <productname>Hunspell</productname> files and support more languages (Artur Zakirov) </para> </listitem> @@ -6687,7 +7193,7 @@ XXX this is pending backpatch, may need to remove --> <para> Implement look-behind constraints - in <link linkend="functions-posix-regexp">regular expressions</> + in <link linkend="functions-posix-regexp">regular expressions</link> (Tom Lane) </para> @@ -6706,12 +7212,12 @@ XXX this is pending backpatch, may need to remove --> <para> In regular expressions, if an apparent three-digit octal escape - <literal>\</><replaceable>nnn</> would exceed 377 (255 decimal), + <literal>\</literal><replaceable>nnn</replaceable> would exceed 377 (255 decimal), assume it is a two-digit octal escape instead (Tom Lane) </para> <para> - This makes the behavior match current <application>Tcl</> releases. + This makes the behavior match current <application>Tcl</application> releases. </para> </listitem> @@ -6720,8 +7226,8 @@ XXX this is pending backpatch, may need to remove 2015-11-07 [c5e86ea93] Add "xid <> xid" and "xid <> int4" operators. --> <para> - Add transaction ID operators <type>xid</> <literal><></> - <type>xid</> and <type>xid</> <literal><></> <type>int4</>, + Add transaction ID operators <type>xid</type> <literal><></literal> + <type>xid</type> and <type>xid</type> <literal><></literal> <type>int4</type>, for consistency with the corresponding equality operators (Michael Paquier) </para> @@ -6742,9 +7248,9 @@ XXX this is pending backpatch, may need to remove --> <para> Add <link - linkend="functions-json-processing-table"><function>jsonb_insert()</></> - function to insert a new element into a <type>jsonb</> array, - or a not-previously-existing key into a <type>jsonb</> object + linkend="functions-json-processing-table"><function>jsonb_insert()</function></link> + function to insert a new element into a <type>jsonb</type> array, + or a not-previously-existing key into a <type>jsonb</type> object (Dmitry Dolgov) </para> </listitem> @@ -6755,9 +7261,9 @@ XXX this is pending backpatch, may need to remove 2016-05-05 [18a02ad2a] Fix corner-case loss of precision in numeric pow() calcu --> <para> - Improve the accuracy of the <function>ln()</>, <function>log()</>, - <function>exp()</>, and <function>pow()</> functions for type - <type>numeric</> (Dean Rasheed) + Improve the accuracy of the <function>ln()</function>, <function>log()</function>, + <function>exp()</function>, and <function>pow()</function> functions for type + <type>numeric</type> (Dean Rasheed) </para> </listitem> @@ -6767,8 +7273,8 @@ XXX this is pending backpatch, may need to remove --> <para> Add a <link - linkend="functions-math-func-table"><function>scale(numeric)</></> - function to extract the display scale of a <type>numeric</> value + linkend="functions-math-func-table"><function>scale(numeric)</function></link> + function to extract the display scale of a <type>numeric</type> value (Marko Tiikkaja) </para> </listitem> @@ -6783,8 +7289,8 @@ XXX this is pending backpatch, may need to remove <para> For example, <link - linkend="functions-math-trig-table"><function>sind()</></> - measures its argument in degrees, whereas <function>sin()</> + linkend="functions-math-trig-table"><function>sind()</function></link> + measures its argument in degrees, whereas <function>sin()</function> measures in radians. These functions go to some lengths to deliver exact results for values where an exact result can be expected, for instance <literal>sind(30) = 0.5</literal>. @@ -6796,15 +7302,15 @@ XXX this is pending backpatch, may need to remove 2016-01-22 [fd5200c3d] Improve cross-platform consistency of Inf/NaN handling i --> <para> - Ensure that trigonometric functions handle <literal>infinity</> - and <literal>NaN</> inputs per the <acronym>POSIX</> standard + Ensure that trigonometric functions handle <literal>infinity</literal> + and <literal>NaN</literal> inputs per the <acronym>POSIX</acronym> standard (Dean Rasheed) </para> <para> - The <acronym>POSIX</> standard says that these functions should - return <literal>NaN</> for <literal>NaN</> input, and should throw - an error for out-of-range inputs including <literal>infinity</>. + The <acronym>POSIX</acronym> standard says that these functions should + return <literal>NaN</literal> for <literal>NaN</literal> input, and should throw + an error for out-of-range inputs including <literal>infinity</literal>. Previously our behavior varied across platforms. </para> </listitem> @@ -6815,9 +7321,9 @@ XXX this is pending backpatch, may need to remove --> <para> Make <link - linkend="functions-datetime-table"><function>to_timestamp(float8)</></> - convert float <literal>infinity</> to - timestamp <literal>infinity</> (Vitaly Burovoy) + linkend="functions-datetime-table"><function>to_timestamp(float8)</function></link> + convert float <literal>infinity</literal> to + timestamp <literal>infinity</literal> (Vitaly Burovoy) </para> <para> @@ -6831,15 +7337,15 @@ XXX this is pending backpatch, may need to remove 2016-05-05 [0b9a23443] Rename tsvector delete() to ts_delete(), and filter() to --> <para> - Add new functions for <type>tsvector</> data (Stas Kelvich) + Add new functions for <type>tsvector</type> data (Stas Kelvich) </para> <para> The new functions are <link - linkend="textsearch-functions-table"><function>ts_delete()</></>, - <function>ts_filter()</>, <function>unnest()</>, - <function>tsvector_to_array()</>, <function>array_to_tsvector()</>, - and a variant of <function>setweight()</> that sets the weight + linkend="textsearch-functions-table"><function>ts_delete()</function></link>, + <function>ts_filter()</function>, <function>unnest()</function>, + <function>tsvector_to_array()</function>, <function>array_to_tsvector()</function>, + and a variant of <function>setweight()</function> that sets the weight only for specified lexeme(s). </para> </listitem> @@ -6849,11 +7355,11 @@ XXX this is pending backpatch, may need to remove 2015-09-17 [9acb9007d] Fix oversight in tsearch type check --> <para> - Allow <link linkend="textsearch-statistics"><function>ts_stat()</></> - and <link linkend="textsearch-update-triggers"><function>tsvector_update_trigger()</></> + Allow <link linkend="textsearch-statistics"><function>ts_stat()</function></link> + and <link linkend="textsearch-update-triggers"><function>tsvector_update_trigger()</function></link> to operate on values that are of types binary-compatible with the expected argument type, not just exactly that type; for example - allow <type>citext</> where <type>text</> is expected (Teodor + allow <type>citext</type> where <type>text</type> is expected (Teodor Sigaev) </para> </listitem> @@ -6864,14 +7370,14 @@ XXX this is pending backpatch, may need to remove --> <para> Add variadic functions <link - linkend="functions-comparison-func-table"><function>num_nulls()</></> - and <function>num_nonnulls()</> that count the number of their + linkend="functions-comparison-func-table"><function>num_nulls()</function></link> + and <function>num_nonnulls()</function> that count the number of their arguments that are null or non-null (Marko Tiikkaja) </para> <para> - An example usage is <literal>CHECK(num_nonnulls(a,b,c) = 1)</> - which asserts that exactly one of a,b,c is not <literal>NULL</>. + An example usage is <literal>CHECK(num_nonnulls(a,b,c) = 1)</literal> + which asserts that exactly one of a,b,c is not <literal>NULL</literal>. These functions can also be used to count the number of null or nonnull elements in an array. </para> @@ -6883,8 +7389,8 @@ XXX this is pending backpatch, may need to remove --> <para> Add function <link - linkend="functions-string-other"><function>parse_ident()</></> - to split a qualified, possibly quoted <acronym>SQL</> identifier + linkend="functions-string-other"><function>parse_ident()</function></link> + to split a qualified, possibly quoted <acronym>SQL</acronym> identifier into its parts (Pavel Stehule) </para> </listitem> @@ -6895,15 +7401,15 @@ XXX this is pending backpatch, may need to remove --> <para> In <link - linkend="functions-formatting-table"><function>to_number()</></>, - interpret a <literal>V</> format code as dividing by 10 to the - power of the number of digits following <literal>V</> (Bruce + linkend="functions-formatting-table"><function>to_number()</function></link>, + interpret a <literal>V</literal> format code as dividing by 10 to the + power of the number of digits following <literal>V</literal> (Bruce Momjian) </para> <para> This makes it operate in an inverse fashion to - <function>to_char()</>. + <function>to_char()</function>. </para> </listitem> @@ -6913,8 +7419,8 @@ XXX this is pending backpatch, may need to remove --> <para> Make the <link - linkend="functions-info-catalog-table"><function>to_reg*()</></> - functions accept type <type>text</> not <type>cstring</> + linkend="functions-info-catalog-table"><function>to_reg*()</function></link> + functions accept type <type>text</type> not <type>cstring</type> (Petr Korobeinikov) </para> @@ -6930,16 +7436,16 @@ XXX this is pending backpatch, may need to remove --> <para> Add <link - linkend="functions-admin-dbsize"><function>pg_size_bytes()</></> + linkend="functions-admin-dbsize"><function>pg_size_bytes()</function></link> function to convert human-readable size strings to numbers (Pavel Stehule, Vitaly Burovoy, Dean Rasheed) </para> <para> This function converts strings like those produced by - <function>pg_size_pretty()</> into bytes. An example + <function>pg_size_pretty()</function> into bytes. An example usage is <literal>SELECT oid::regclass FROM pg_class WHERE - pg_total_relation_size(oid) > pg_size_bytes('10 GB')</>. + pg_total_relation_size(oid) > pg_size_bytes('10 GB')</literal>. </para> </listitem> @@ -6949,7 +7455,7 @@ XXX this is pending backpatch, may need to remove --> <para> In <link - linkend="functions-admin-dbsize"><function>pg_size_pretty()</></>, + linkend="functions-admin-dbsize"><function>pg_size_pretty()</function></link>, format negative numbers similarly to positive ones (Adrian Vondendriesch) </para> @@ -6965,14 +7471,14 @@ XXX this is pending backpatch, may need to remove 2015-07-02 [10fb48d66] Add an optional missing_ok argument to SQL function curr --> <para> - Add an optional <replaceable>missing_ok</> argument to the <link - linkend="functions-admin-set-table"><function>current_setting()</></> + Add an optional <replaceable>missing_ok</replaceable> argument to the <link + linkend="functions-admin-set-table"><function>current_setting()</function></link> function (David Christensen) </para> <para> This allows avoiding an error for an unrecognized parameter - name, instead returning a <literal>NULL</>. + name, instead returning a <literal>NULL</literal>. </para> </listitem> @@ -6984,16 +7490,16 @@ XXX this is pending backpatch, may need to remove --> <para> Change various catalog-inspection functions to return - <literal>NULL</> for invalid input (Michael Paquier) + <literal>NULL</literal> for invalid input (Michael Paquier) </para> <para> <link - linkend="functions-info-catalog-table"><function>pg_get_viewdef()</></> - now returns <literal>NULL</> if given an invalid view <type>OID</>, - and several similar functions likewise return <literal>NULL</> for + linkend="functions-info-catalog-table"><function>pg_get_viewdef()</function></link> + now returns <literal>NULL</literal> if given an invalid view <type>OID</type>, + and several similar functions likewise return <literal>NULL</literal> for bad input. Previously, such cases usually led to <quote>cache - lookup failed</> errors, which are not meant to occur in + lookup failed</quote> errors, which are not meant to occur in user-facing cases. </para> </listitem> @@ -7004,13 +7510,13 @@ XXX this is pending backpatch, may need to remove --> <para> Fix <link - linkend="pg-replication-origin-xact-reset"><function>pg_replication_origin_xact_reset()</></> + linkend="pg-replication-origin-xact-reset"><function>pg_replication_origin_xact_reset()</function></link> to not have any arguments (Fujii Masao) </para> <para> The documentation said that it has no arguments, and the C code did - not expect any arguments, but the entry in <structname>pg_proc</> + not expect any arguments, but the entry in <structname>pg_proc</structname> mistakenly specified two arguments. </para> </listitem> @@ -7030,7 +7536,7 @@ XXX this is pending backpatch, may need to remove --> <para> In <link linkend="plpgsql">PL/pgSQL</link>, detect mismatched - <command>CONTINUE</> and <command>EXIT</> statements while + <command>CONTINUE</command> and <command>EXIT</command> statements while compiling a function, rather than at execution time (Jim Nasby) </para> @@ -7043,7 +7549,7 @@ XXX this is pending backpatch, may need to remove 2016-07-02 [3a4a33ad4] PL/Python: Report argument parsing errors using exceptio --> <para> - Extend <application>PL/Python</>'s error-reporting and + Extend <application>PL/Python</application>'s error-reporting and message-reporting functions to allow specifying additional message fields besides the primary error message (Pavel Stehule) </para> @@ -7055,7 +7561,7 @@ XXX this is pending backpatch, may need to remove --> <para> Allow PL/Python functions to call themselves recursively - via <application>SPI</>, and fix the behavior when multiple + via <application>SPI</application>, and fix the behavior when multiple set-returning PL/Python functions are called within one query (Alexey Grishchenko, Tom Lane) </para> @@ -7077,14 +7583,14 @@ XXX this is pending backpatch, may need to remove 2016-03-02 [e2609323e] Make PL/Tcl require Tcl 8.4 or later. --> <para> - Modernize <application>PL/Tcl</> to use Tcl's <quote>object</> - <acronym>API</>s instead of simple strings (Jim Nasby, Karl + Modernize <application>PL/Tcl</application> to use Tcl's <quote>object</quote> + <acronym>API</acronym>s instead of simple strings (Jim Nasby, Karl Lehenbauer) </para> <para> This can improve performance substantially in some cases. - Note that <application>PL/Tcl</> now requires Tcl 8.4 or later. + Note that <application>PL/Tcl</application> now requires Tcl 8.4 or later. </para> </listitem> @@ -7094,8 +7600,8 @@ XXX this is pending backpatch, may need to remove 2016-03-25 [cd37bb785] Improve PL/Tcl errorCode facility by providing decoded n --> <para> - In <application>PL/Tcl</>, make database-reported errors return - additional information in Tcl's <varname>errorCode</> global + In <application>PL/Tcl</application>, make database-reported errors return + additional information in Tcl's <varname>errorCode</varname> global variable (Jim Nasby, Tom Lane) </para> @@ -7110,15 +7616,15 @@ XXX this is pending backpatch, may need to remove 2016-03-02 [c8c7c93de] Fix PL/Tcl's encoding conversion logic. --> <para> - Fix <application>PL/Tcl</> to perform encoding conversion between - the database encoding and <literal>UTF-8</>, which is what Tcl + Fix <application>PL/Tcl</application> to perform encoding conversion between + the database encoding and <literal>UTF-8</literal>, which is what Tcl expects (Tom Lane) </para> <para> Previously, strings were passed through without conversion, - leading to misbehavior with non-<literal>ASCII</> characters when - the database encoding was not <literal>UTF-8</>. + leading to misbehavior with non-<literal>ASCII</literal> characters when + the database encoding was not <literal>UTF-8</literal>. </para> </listitem> @@ -7137,7 +7643,7 @@ XXX this is pending backpatch, may need to remove --> <para> Add a nonlocalized version of - the <link linkend="protocol-error-fields">severity field</> in + the <link linkend="protocol-error-fields">severity field</link> in error and notice messages (Tom Lane) </para> @@ -7154,17 +7660,17 @@ XXX this is pending backpatch, may need to remove This commit is also listed under psql and PL/pgSQL --> <para> - Introduce a feature in <application>libpq</> whereby the - <literal>CONTEXT</> field of messages can be suppressed, either + Introduce a feature in <application>libpq</application> whereby the + <literal>CONTEXT</literal> field of messages can be suppressed, either always or only for non-error messages (Pavel Stehule) </para> <para> The default behavior of <link - linkend="libpq-pqerrormessage"><function>PQerrorMessage()</></> - is now to print <literal>CONTEXT</> + linkend="libpq-pqerrormessage"><function>PQerrorMessage()</function></link> + is now to print <literal>CONTEXT</literal> only for errors. The new function <link - linkend="libpq-pqseterrorcontextvisibility"><function>PQsetErrorContextVisibility()</></> + linkend="libpq-pqseterrorcontextvisibility"><function>PQsetErrorContextVisibility()</function></link> can be used to adjust this. </para> </listitem> @@ -7174,14 +7680,14 @@ This commit is also listed under psql and PL/pgSQL 2016-04-03 [e3161b231] Add libpq support for recreating an error message with d --> <para> - Add support in <application>libpq</> for regenerating an error + Add support in <application>libpq</application> for regenerating an error message with a different verbosity level (Alex Shulgin) </para> <para> This is done with the new function <link - linkend="libpq-pqresultverboseerrormessage"><function>PQresultVerboseErrorMessage()</></>. - This supports <application>psql</>'s new <literal>\errverbose</> + linkend="libpq-pqresultverboseerrormessage"><function>PQresultVerboseErrorMessage()</function></link>. + This supports <application>psql</application>'s new <literal>\errverbose</literal> feature, and may be useful for other clients as well. </para> </listitem> @@ -7191,13 +7697,13 @@ This commit is also listed under psql and PL/pgSQL 2015-11-27 [40cb21f70] Improve PQhost() to return useful data for default Unix- --> <para> - Improve <application>libpq</>'s <link - linkend="libpq-pqhost"><function>PQhost()</></> function to return + Improve <application>libpq</application>'s <link + linkend="libpq-pqhost"><function>PQhost()</function></link> function to return useful data for default Unix-socket connections (Tom Lane) </para> <para> - Previously it would return <literal>NULL</> if no explicit host + Previously it would return <literal>NULL</literal> if no explicit host specification had been given; now it returns the default socket directory path. </para> @@ -7208,7 +7714,7 @@ This commit is also listed under psql and PL/pgSQL 2016-02-16 [fc1ae7d2e] Change ecpg lexer to accept comments with line breaks in --> <para> - Fix <application>ecpg</>'s lexer to handle line breaks within + Fix <application>ecpg</application>'s lexer to handle line breaks within comments starting on preprocessor directive lines (Michael Meskes) </para> </listitem> @@ -7227,9 +7733,9 @@ 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 --> <para> - Add a <option>--strict-names</> option - to <link linkend="APP-PGDUMP"><application>pg_dump</></> - and <link linkend="APP-PGRESTORE"><application>pg_restore</></> + Add a <option>--strict-names</option> option + to <link linkend="app-pgdump"><application>pg_dump</application></link> + and <link linkend="app-pgrestore"><application>pg_restore</application></link> (Pavel Stehule) </para> @@ -7249,7 +7755,7 @@ This commit is also listed under psql and PL/pgSQL 2016-05-06 [e1b120a8c] Only issue LOCK TABLE commands when necessary --> <para> - In <application>pg_dump</>, dump locally-made changes of privilege + In <application>pg_dump</application>, dump locally-made changes of privilege assignments for system objects (Stephen Frost) </para> @@ -7257,7 +7763,7 @@ This commit is also listed under psql and PL/pgSQL While it has always been possible for a superuser to change the privilege assignments for built-in or extension-created objects, such changes were formerly lost in a dump and reload. - Now, <application>pg_dump</> recognizes and dumps such changes. + Now, <application>pg_dump</application> recognizes and dumps such changes. (This works only when dumping from a 9.6 or later server, however.) </para> </listitem> @@ -7267,7 +7773,7 @@ This commit is also listed under psql and PL/pgSQL 2016-09-08 [31eb14504] Allow pg_dump to dump non-extension members of an extens --> <para> - Allow <application>pg_dump</> to dump non-extension-owned objects + Allow <application>pg_dump</application> to dump non-extension-owned objects that are within an extension-owned schema (Martín Marqués) </para> @@ -7283,7 +7789,7 @@ This commit is also listed under psql and PL/pgSQL 2016-04-06 [3b3fcc4ee] pg_dump: Add table qualifications to some tags --> <para> - In <application>pg_dump</> output, include the table name in object + In <application>pg_dump</application> output, include the table name in object tags for object types that are only uniquely named per-table (for example, triggers) (Peter Eisentraut) </para> @@ -7292,7 +7798,7 @@ This commit is also listed under psql and PL/pgSQL </itemizedlist> <sect4> - <title><xref linkend="APP-PSQL"></title> + <title><xref linkend="app-psql"></title> <itemizedlist> @@ -7308,7 +7814,7 @@ this commit is also listed in the compatibility section <para> The specified operations are carried out in the order in which the - options are given, and then <application>psql</> terminates. + options are given, and then <application>psql</application> terminates. </para> </listitem> @@ -7317,7 +7823,7 @@ this commit is also listed in the compatibility section 2016-04-08 [c09b18f21] Support \crosstabview in psql --> <para> - Add a <command>\crosstabview</> command that prints the results of + Add a <command>\crosstabview</command> command that prints the results of a query in a cross-tabulated display (Daniel Vérité) </para> @@ -7333,13 +7839,13 @@ this commit is also listed in the compatibility section 2016-04-03 [3cc38ca7d] Add psql \errverbose command to see last server error at --> <para> - Add an <literal>\errverbose</> command that shows the last server + Add an <literal>\errverbose</literal> command that shows the last server error at full verbosity (Alex Shulgin) </para> <para> This is useful after getting an unexpected error — you - no longer need to adjust the <varname>VERBOSITY</> variable and + no longer need to adjust the <varname>VERBOSITY</varname> variable and recreate the failure in order to see error fields that are not shown by default. </para> @@ -7351,13 +7857,13 @@ this commit is also listed in the compatibility section 2016-05-06 [9b66aa006] Fix psql's \ev and \sv commands so that they handle view --> <para> - Add <literal>\ev</> and <literal>\sv</> commands for editing and + Add <literal>\ev</literal> and <literal>\sv</literal> commands for editing and showing view definitions (Petr Korobeinikov) </para> <para> - These are parallel to the existing <literal>\ef</> and - <literal>\sf</> commands for functions. + These are parallel to the existing <literal>\ef</literal> and + <literal>\sf</literal> commands for functions. </para> </listitem> @@ -7366,7 +7872,7 @@ this commit is also listed in the compatibility section 2016-04-04 [2bbe9112a] Add a \gexec command to psql for evaluation of computed --> <para> - Add a <command>\gexec</> command that executes a query and + Add a <command>\gexec</command> command that executes a query and re-submits the result(s) as new queries (Corey Huinker) </para> </listitem> @@ -7376,9 +7882,9 @@ this commit is also listed in the compatibility section 2015-10-05 [2145a7660] psql: allow \pset C in setting the title, matches \C --> <para> - Allow <literal>\pset C <replaceable>string</></literal> + Allow <literal>\pset C <replaceable>string</replaceable></literal> to set the table title, for consistency with <literal>\C - <replaceable>string</></literal> (Bruce Momjian) + <replaceable>string</replaceable></literal> (Bruce Momjian) </para> </listitem> @@ -7387,7 +7893,7 @@ this commit is also listed in the compatibility section 2016-03-11 [69ab7b9d6] psql: Don't automatically use expanded format when there --> <para> - In <literal>\pset expanded auto</> mode, do not use expanded + In <literal>\pset expanded auto</literal> mode, do not use expanded format for query results with only one column (Andreas Karlsson, Robert Haas) </para> @@ -7399,16 +7905,16 @@ this commit is also listed in the compatibility section 2016-06-15 [9901d8ac2] Use strftime("%c") to format timestamps in psql's \watch --> <para> - Improve the headers output by the <command>\watch</> command + Improve the headers output by the <command>\watch</command> command (Michael Paquier, Tom Lane) </para> <para> - Include the <command>\pset title</> string if one has + Include the <command>\pset title</command> string if one has been set, and shorten the prefabricated part of the - header to be <literal><replaceable>timestamp</> (every - <replaceable>N</>s)</literal>. Also, the timestamp format now - obeys <application>psql</>'s locale environment. + header to be <literal><replaceable>timestamp</replaceable> (every + <replaceable>N</replaceable>s)</literal>. Also, the timestamp format now + obeys <application>psql</application>'s locale environment. </para> </listitem> @@ -7456,7 +7962,7 @@ this commit is also listed in the compatibility section 2015-07-07 [275f05c99] Add psql PROMPT variable showing the pid of the connecte --> <para> - Add a <literal>PROMPT</> option <literal>%p</> to insert the + Add a <literal>PROMPT</literal> option <literal>%p</literal> to insert the process ID of the connected backend (Julien Rouhaud) </para> </listitem> @@ -7467,13 +7973,13 @@ this commit is also listed in the compatibility section This commit is also listed under libpq and PL/pgSQL --> <para> - Introduce a feature whereby the <literal>CONTEXT</> field of + Introduce a feature whereby the <literal>CONTEXT</literal> field of messages can be suppressed, either always or only for non-error messages (Pavel Stehule) </para> <para> - Printing <literal>CONTEXT</> only for errors is now the default + Printing <literal>CONTEXT</literal> only for errors is now the default behavior. This can be changed by setting the special variable <varname>SHOW_CONTEXT</varname>. </para> @@ -7484,7 +7990,7 @@ This commit is also listed under libpq and PL/pgSQL 2016-07-11 [a670c24c3] Improve output of psql's \df+ command. --> <para> - Make <command>\df+</> show function access privileges and + Make <command>\df+</command> show function access privileges and parallel-safety attributes (Michael Paquier) </para> </listitem> @@ -7503,7 +8009,7 @@ This commit is also listed under libpq and PL/pgSQL 2016-03-20 [68ab8e8ba] SQL commands in pgbench scripts are now ended by semicol --> <para> - SQL commands in <application>pgbench</> scripts are now ended by + SQL commands in <application>pgbench</application> scripts are now ended by semicolons, not newlines (Kyotaro Horiguchi, Tom Lane) </para> @@ -7512,7 +8018,7 @@ This commit is also listed under libpq and PL/pgSQL Existing custom scripts will need to be modified to add a semicolon 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 <application>pgbench</>.) + of <application>pgbench</application>.) </para> </listitem> @@ -7525,7 +8031,7 @@ This commit is also listed under libpq and PL/pgSQL --> <para> Support floating-point arithmetic, as well as some <link - linkend="pgbench-builtin-functions">built-in functions</>, in + linkend="pgbench-builtin-functions">built-in functions</link>, in expressions in backslash commands (Fabien Coelho) </para> </listitem> @@ -7535,18 +8041,18 @@ This commit is also listed under libpq and PL/pgSQL 2016-03-29 [ad9566470] pgbench: Remove \setrandom. --> <para> - Replace <command>\setrandom</> with built-in functions (Fabien + Replace <command>\setrandom</command> with built-in functions (Fabien Coelho) </para> <para> The new built-in functions include <link - linkend="pgbench-functions"><function>random()</></>, - <function>random_exponential()</>, and - <function>random_gaussian()</>, which perform the same work as - <command>\setrandom</>, but are easier to use since they can be + linkend="pgbench-functions"><function>random()</function></link>, + <function>random_exponential()</function>, and + <function>random_gaussian()</function>, which perform the same work as + <command>\setrandom</command>, but are easier to use since they can be embedded in larger expressions. Since these additions have made - <command>\setrandom</> obsolete, remove it. + <command>\setrandom</command> obsolete, remove it. </para> </listitem> @@ -7561,8 +8067,8 @@ This commit is also listed under libpq and PL/pgSQL </para> <para> - This is done with the new <option>-b</> switch, which works - similarly to <option>-f</> for custom scripts. + This is done with the new <option>-b</option> switch, which works + similarly to <option>-f</option> for custom scripts. </para> </listitem> @@ -7577,7 +8083,7 @@ This commit is also listed under libpq and PL/pgSQL </para> <para> - When multiple scripts are specified, each <application>pgbench</> + When multiple scripts are specified, each <application>pgbench</application> transaction randomly chooses one to execute. Formerly this was always done with uniform probability, but now different selection probabilities can be specified for different scripts. @@ -7604,7 +8110,7 @@ This commit is also listed under libpq and PL/pgSQL 2015-09-16 [1def9063c] pgbench progress with timestamp --> <para> - Add a <option>--progress-timestamp</> option to report progress + Add a <option>--progress-timestamp</option> option to report progress with Unix epoch timestamps, instead of time since the run started (Fabien Coelho) </para> @@ -7615,8 +8121,8 @@ This commit is also listed under libpq and PL/pgSQL 2015-07-03 [ba3deeefb] Lift the limitation that # of clients must be a multiple --> <para> - Allow the number of client connections (<option>-c</>) to not - be an exact multiple of the number of threads (<option>-j</>) + Allow the number of client connections (<option>-c</option>) to not + be an exact multiple of the number of threads (<option>-j</option>) (Fabien Coelho) </para> </listitem> @@ -7626,13 +8132,13 @@ This commit is also listed under libpq and PL/pgSQL 2016-03-09 [accf7616f] pgbench: When -T is used, don't wait for transactions be --> <para> - When the <option>-T</> option is used, stop promptly at the end + When the <option>-T</option> option is used, stop promptly at the end of the specified time (Fabien Coelho) </para> <para> Previously, specifying a low transaction rate could cause - <application>pgbench</> to wait significantly longer than + <application>pgbench</application> to wait significantly longer than specified. </para> </listitem> @@ -7653,15 +8159,15 @@ This commit is also listed under libpq and PL/pgSQL 2015-12-17 [66d947b9d] Adjust behavior of single-user -j mode for better initdb --> <para> - Improve error reporting during <application>initdb</>'s + Improve error reporting during <application>initdb</application>'s post-bootstrap phase (Tom Lane) </para> <para> Previously, an error here led to reporting the entire input - file as the <quote>failing query</>; now just the current + file as the <quote>failing query</quote>; now just the current query is reported. To get the desired behavior, queries in - <application>initdb</>'s input files must be separated by blank + <application>initdb</application>'s input files must be separated by blank lines. </para> </listitem> @@ -7672,7 +8178,7 @@ This commit is also listed under libpq and PL/pgSQL 2016-08-30 [d9720e437] Fix initdb misbehavior when user mis-enters superuser pa --> <para> - Speed up <application>initdb</> by using just one + Speed up <application>initdb</application> by using just one standalone-backend session for all the post-bootstrap steps (Tom Lane) </para> @@ -7683,7 +8189,7 @@ This commit is also listed under libpq and PL/pgSQL 2015-12-01 [e50cda784] Use pg_rewind when target timeline was switched --> <para> - Improve <link linkend="app-pgrewind"><application>pg_rewind</></> + Improve <link linkend="app-pgrewind"><application>pg_rewind</application></link> so that it can work when the target timeline changes (Alexander Korotkov) </para> @@ -7709,7 +8215,7 @@ This commit is also listed under libpq and PL/pgSQL --> <para> Remove obsolete - <function>heap_formtuple</>/<function>heap_modifytuple</>/<function>heap_deformtuple</> + <function>heap_formtuple</function>/<function>heap_modifytuple</function>/<function>heap_deformtuple</function> functions (Peter Geoghegan) </para> </listitem> @@ -7719,16 +8225,16 @@ This commit is also listed under libpq and PL/pgSQL 2016-08-27 [b9fe6cbc8] Add macros to make AllocSetContextCreate() calls simpler --> <para> - Add macros to make <function>AllocSetContextCreate()</> calls simpler + Add macros to make <function>AllocSetContextCreate()</function> calls simpler and safer (Tom Lane) </para> <para> Writing out the individual sizing parameters for a memory context is now deprecated in favor of using one of the new - macros <symbol>ALLOCSET_DEFAULT_SIZES</>, - <symbol>ALLOCSET_SMALL_SIZES</>, - or <symbol>ALLOCSET_START_SMALL_SIZES</>. + macros <symbol>ALLOCSET_DEFAULT_SIZES</symbol>, + <symbol>ALLOCSET_SMALL_SIZES</symbol>, + or <symbol>ALLOCSET_START_SMALL_SIZES</symbol>. Existing code continues to work, however. </para> </listitem> @@ -7738,7 +8244,7 @@ This commit is also listed under libpq and PL/pgSQL 2015-08-05 [de6fd1c89] Rely on inline functions even if that causes warnings in --> <para> - Unconditionally use <literal>static inline</> functions in header + Unconditionally use <literal>static inline</literal> functions in header files (Andres Freund) </para> @@ -7759,7 +8265,7 @@ This commit is also listed under libpq and PL/pgSQL 2016-05-06 [6bd356c33] Add TAP tests for pg_dump --> <para> - Improve <application>TAP</> testing infrastructure (Michael + Improve <application>TAP</application> testing infrastructure (Michael Paquier, Craig Ringer, Álvaro Herrera, Stephen Frost) </para> @@ -7774,7 +8280,7 @@ This commit is also listed under libpq and PL/pgSQL 2015-09-11 [aa65de042] When trace_lwlocks is used, identify individual lwlocks --> <para> - Make <varname>trace_lwlocks</> identify individual locks by name + Make <varname>trace_lwlocks</varname> identify individual locks by name (Robert Haas) </para> </listitem> @@ -7786,7 +8292,7 @@ This commit is also listed under libpq and PL/pgSQL 2016-01-05 [4f18010af] Convert psql's tab completion for backslash commands to --> <para> - Improve <application>psql</>'s tab-completion code infrastructure + Improve <application>psql</application>'s tab-completion code infrastructure (Thomas Munro, Michael Paquier) </para> @@ -7801,7 +8307,7 @@ This commit is also listed under libpq and PL/pgSQL 2016-01-05 [efa318bcf] Make pg_shseclabel available in early backend startup --> <para> - Nail the <structname>pg_shseclabel</> system catalog into cache, + Nail the <structname>pg_shseclabel</structname> system catalog into cache, so that it is available for access during connection authentication (Adam Brightwell) </para> @@ -7820,21 +8326,21 @@ This commit is also listed under libpq and PL/pgSQL --> <para> Restructure <link linkend="indexam">index access - method <acronym>API</></> to hide most of it at - the <application>C</> level (Alexander Korotkov, Andrew Gierth) + method <acronym>API</acronym></link> to hide most of it at + the <application>C</application> level (Alexander Korotkov, Andrew Gierth) </para> <para> - This change modernizes the index <acronym>AM API</> to look more + This change modernizes the index <acronym>AM API</acronym> to look more like the designs we have adopted for foreign data wrappers and - tablesample handlers. This simplifies the <application>C</> code + tablesample handlers. This simplifies the <application>C</application> code and makes it much more practical to define index access methods in installable extensions. A consequence is that most of the columns - of the <structname>pg_am</> system catalog have disappeared. + of the <structname>pg_am</structname> system catalog have disappeared. New <link linkend="functions-info-catalog-table">inspection functions</link> have been added to allow SQL queries to determine index AM properties that used to be discoverable - from <structname>pg_am</>. + from <structname>pg_am</structname>. </para> </listitem> @@ -7844,14 +8350,14 @@ This commit is also listed under libpq and PL/pgSQL --> <para> Add <link - linkend="catalog-pg-init-privs"><structname>pg_init_privs</></> + linkend="catalog-pg-init-privs"><structname>pg_init_privs</structname></link> system catalog to hold original privileges - of <application>initdb</>-created and extension-created objects + of <application>initdb</application>-created and extension-created objects (Stephen Frost) </para> <para> - This infrastructure allows <application>pg_dump</> to dump changes + This infrastructure allows <application>pg_dump</application> to dump changes that an installation may have made in privileges attached to system objects. Formerly, such changes would be lost in a dump and reload, but now they are preserved. @@ -7863,14 +8369,14 @@ This commit is also listed under libpq and PL/pgSQL 2016-02-04 [c1772ad92] Change the way that LWLocks for extensions are allocated --> <para> - Change the way that extensions allocate custom <literal>LWLocks</> + Change the way that extensions allocate custom <literal>LWLocks</literal> (Amit Kapila, Robert Haas) </para> <para> - The <function>RequestAddinLWLocks()</> function is removed, - and replaced by <function>RequestNamedLWLockTranche()</>. - This allows better identification of custom <literal>LWLocks</>, + The <function>RequestAddinLWLocks()</function> function is removed, + and replaced by <function>RequestNamedLWLockTranche()</function>. + This allows better identification of custom <literal>LWLocks</literal>, and is less error-prone. </para> </listitem> @@ -7894,7 +8400,7 @@ This commit is also listed under libpq and PL/pgSQL </para> <para> - This change allows <application>FDW</>s or custom scan providers + This change allows <application>FDW</application>s or custom scan providers to store data in a plan tree in a more convenient format than was previously possible. </para> @@ -7911,7 +8417,7 @@ This commit is also listed under libpq and PL/pgSQL --> <para> Make the planner deal with post-scan/join query steps by generating - and comparing <literal>Paths</>, replacing a lot of ad-hoc logic + and comparing <literal>Paths</literal>, replacing a lot of ad-hoc logic (Tom Lane) </para> @@ -7961,7 +8467,7 @@ This commit is also listed under libpq and PL/pgSQL 2016-03-24 [c1156411a] Move psql's psqlscan.l into src/fe_utils. --> <para> - Separate out <application>psql</>'s <application>flex</> lexer to + Separate out <application>psql</application>'s <application>flex</application> lexer to make it usable by other client programs (Tom Lane, Kyotaro Horiguchi) </para> @@ -7970,12 +8476,12 @@ This commit is also listed under libpq and PL/pgSQL This eliminates code duplication for programs that need to be able to parse SQL commands well enough to identify command boundaries. Doing that in full generality is more painful than one could - wish, and up to now only <application>psql</> has really gotten + wish, and up to now only <application>psql</application> has really gotten it right among our supported client programs. </para> <para> - A new source-code subdirectory <filename>src/fe_utils/</> has + A new source-code subdirectory <filename>src/fe_utils/</filename> has been created to hold this and other code that is shared across our client programs. Formerly such sharing was accomplished by symbolic linking or copying source files at build time, which @@ -7988,7 +8494,7 @@ This commit is also listed under libpq and PL/pgSQL 2016-03-21 [98a64d0bd] Introduce WaitEventSet API. --> <para> - Introduce <literal>WaitEventSet</> <acronym>API</> to allow + Introduce <literal>WaitEventSet</literal> <acronym>API</acronym> to allow efficient waiting for event sets that usually do not change from one wait to the next (Andres Freund, Amit Kapila) </para> @@ -7999,16 +8505,16 @@ This commit is also listed under libpq and PL/pgSQL 2016-04-01 [65578341a] Add Generic WAL interface --> <para> - Add a generic interface for writing <acronym>WAL</> records + Add a generic interface for writing <acronym>WAL</acronym> records (Alexander Korotkov, Petr Jelínek, Markus Nullmeier) </para> <para> - This change allows extensions to write <acronym>WAL</> records for + This change allows extensions to write <acronym>WAL</acronym> records for changes to pages using a standard layout. The problem of needing to - replay <acronym>WAL</> without access to the extension is solved by + replay <acronym>WAL</acronym> without access to the extension is solved by having generic replay code. This allows extensions to implement, - for example, index access methods and have <acronym>WAL</> + for example, index access methods and have <acronym>WAL</acronym> support for them. </para> </listitem> @@ -8018,13 +8524,13 @@ This commit is also listed under libpq and PL/pgSQL 2016-04-06 [3fe3511d0] Generic Messages for Logical Decoding --> <para> - Support generic <acronym>WAL</> messages for logical decoding + Support generic <acronym>WAL</acronym> messages for logical decoding (Petr Jelínek, Andres Freund) </para> <para> This feature allows extensions to insert data into the - <acronym>WAL</> stream that can be read by logical-decoding + <acronym>WAL</acronym> stream that can be read by logical-decoding plugins, but is not connected to physical data restoration. </para> </listitem> @@ -8036,12 +8542,12 @@ This commit is also listed under libpq and PL/pgSQL --> <para> Allow SP-GiST operator classes to store an arbitrary - <quote>traversal value</> while descending the index (Alexander + <quote>traversal value</quote> while descending the index (Alexander Lebedev, Teodor Sigaev) </para> <para> - This is somewhat like the <quote>reconstructed value</>, but it + This is somewhat like the <quote>reconstructed value</quote>, but it could be any arbitrary chunk of data, not necessarily of the same data type as the indexed column. </para> @@ -8052,12 +8558,12 @@ This commit is also listed under libpq and PL/pgSQL 2016-04-04 [66229ac00] Introduce a LOG_SERVER_ONLY ereport level, which is neve --> <para> - Introduce a <literal>LOG_SERVER_ONLY</> message level for - <function>ereport()</> (David Steele) + Introduce a <literal>LOG_SERVER_ONLY</literal> message level for + <function>ereport()</function> (David Steele) </para> <para> - This level acts like <literal>LOG</> except that the message is + This level acts like <literal>LOG</literal> except that the message is never sent to the client. It is meant for use in auditing and similar applications. </para> @@ -8068,14 +8574,14 @@ This commit is also listed under libpq and PL/pgSQL 2016-07-01 [548af97fc] Provide and use a makefile target to build all generated --> <para> - Provide a <filename>Makefile</> target to build all generated + Provide a <filename>Makefile</filename> target to build all generated headers (Michael Paquier, Tom Lane) </para> <para> - <literal>submake-generated-headers</> can now be invoked to ensure + <literal>submake-generated-headers</literal> can now be invoked to ensure that generated backend header files are up-to-date. This is - useful in subdirectories that might be built <quote>standalone</>. + useful in subdirectories that might be built <quote>standalone</quote>. </para> </listitem> @@ -8104,8 +8610,8 @@ This commit is also listed under libpq and PL/pgSQL 2016-03-13 [7a8d87483] Rename auto_explain.sample_ratio to sample_rate --> <para> - Add configuration parameter <literal>auto_explain.sample_rate</> to - allow <link linkend="auto-explain"><filename>contrib/auto_explain</></> + Add configuration parameter <literal>auto_explain.sample_rate</literal> to + allow <link linkend="auto-explain"><filename>contrib/auto_explain</filename></link> to capture just a configurable fraction of all queries (Craig Ringer, Julien Rouhaud) </para> @@ -8121,7 +8627,7 @@ This commit is also listed under libpq and PL/pgSQL 2016-04-01 [9ee014fc8] Bloom index contrib module --> <para> - Add <link linkend="bloom"><filename>contrib/bloom</></> module that + Add <link linkend="bloom"><filename>contrib/bloom</filename></link> module that implements an index access method based on Bloom filtering (Teodor Sigaev, Alexander Korotkov) </para> @@ -8139,7 +8645,7 @@ This commit is also listed under libpq and PL/pgSQL 2015-12-28 [81ee726d8] Code and docs review for cube kNN support. --> <para> - In <link linkend="cube"><filename>contrib/cube</></>, introduce + In <link linkend="cube"><filename>contrib/cube</filename></link>, introduce distance operators for cubes, and support kNN-style searches in GiST indexes on cube columns (Stas Kelvich) </para> @@ -8150,19 +8656,19 @@ This commit is also listed under libpq and PL/pgSQL 2016-02-03 [41d2c081c] Make hstore_to_jsonb_loose match hstore_to_json_loose on --> <para> - Make <filename>contrib/hstore</>'s <link - linkend="hstore-func-table"><function>hstore_to_jsonb_loose()</></> - and <function>hstore_to_json_loose()</> functions agree on what + Make <filename>contrib/hstore</filename>'s <link + linkend="hstore-func-table"><function>hstore_to_jsonb_loose()</function></link> + and <function>hstore_to_json_loose()</function> functions agree on what is a number (Tom Lane) </para> <para> - Previously, <function>hstore_to_jsonb_loose()</> would convert - numeric-looking strings to <acronym>JSON</> numbers, rather than - strings, even if they did not exactly match the <acronym>JSON</> + Previously, <function>hstore_to_jsonb_loose()</function> would convert + numeric-looking strings to <acronym>JSON</acronym> numbers, rather than + strings, even if they did not exactly match the <acronym>JSON</acronym> syntax specification for numbers. This was inconsistent with - <function>hstore_to_json_loose()</>, so tighten the test to match - the <acronym>JSON</> syntax. + <function>hstore_to_json_loose()</function>, so tighten the test to match + the <acronym>JSON</acronym> syntax. </para> </listitem> @@ -8172,7 +8678,7 @@ This commit is also listed under libpq and PL/pgSQL --> <para> Add selectivity estimation functions for - <link linkend="intarray"><filename>contrib/intarray</></> operators + <link linkend="intarray"><filename>contrib/intarray</filename></link> operators to improve plans for queries using those operators (Yury Zhuravlev, Alexander Korotkov) </para> @@ -8184,10 +8690,10 @@ This commit is also listed under libpq and PL/pgSQL --> <para> Make <link - linkend="pageinspect"><filename>contrib/pageinspect</></>'s - <function>heap_page_items()</> function show the raw data in each - tuple, and add new functions <function>tuple_data_split()</> and - <function>heap_page_item_attrs()</> for inspection of individual + linkend="pageinspect"><filename>contrib/pageinspect</filename></link>'s + <function>heap_page_items()</function> function show the raw data in each + tuple, and add new functions <function>tuple_data_split()</function> and + <function>heap_page_item_attrs()</function> for inspection of individual tuple fields (Nikolay Shaplov) </para> </listitem> @@ -8197,9 +8703,9 @@ This commit is also listed under libpq and PL/pgSQL 2016-03-09 [188f359d3] pgcrypto: support changing S2K iteration count --> <para> - Add an optional <literal>S2K</> iteration count parameter to - <link linkend="pgcrypto"><filename>contrib/pgcrypto</></>'s - <function>pgp_sym_encrypt()</> function (Jeff Janes) + Add an optional <literal>S2K</literal> iteration count parameter to + <link linkend="pgcrypto"><filename>contrib/pgcrypto</filename></link>'s + <function>pgp_sym_encrypt()</function> function (Jeff Janes) </para> </listitem> @@ -8208,8 +8714,8 @@ This commit is also listed under libpq and PL/pgSQL 2016-03-16 [f576b17cd] Add word_similarity to pg_trgm contrib module. --> <para> - Add support for <quote>word similarity</> to - <link linkend="pgtrgm"><filename>contrib/pg_trgm</></> + Add support for <quote>word similarity</quote> to + <link linkend="pgtrgm"><filename>contrib/pg_trgm</filename></link> (Alexander Korotkov, Artur Zakirov) </para> @@ -8226,14 +8732,14 @@ This commit is also listed under libpq and PL/pgSQL --> <para> Add configuration parameter - <varname>pg_trgm.similarity_threshold</> for - <filename>contrib/pg_trgm</>'s similarity threshold (Artur Zakirov) + <varname>pg_trgm.similarity_threshold</varname> for + <filename>contrib/pg_trgm</filename>'s similarity threshold (Artur Zakirov) </para> <para> This threshold has always been configurable, but formerly it was - controlled by special-purpose functions <function>set_limit()</> - and <function>show_limit()</>. Those are now deprecated. + controlled by special-purpose functions <function>set_limit()</function> + and <function>show_limit()</function>. Those are now deprecated. </para> </listitem> @@ -8242,7 +8748,7 @@ This commit is also listed under libpq and PL/pgSQL 2015-07-20 [97f301464] This supports the triconsistent function for pg_trgm GIN --> <para> - Improve <filename>contrib/pg_trgm</>'s GIN operator class to + Improve <filename>contrib/pg_trgm</filename>'s GIN operator class to speed up index searches in which both common and rare keys appear (Jeff Janes) </para> @@ -8254,7 +8760,7 @@ This commit is also listed under libpq and PL/pgSQL --> <para> Improve performance of similarity searches in - <filename>contrib/pg_trgm</> GIN indexes (Christophe Fornaroli) + <filename>contrib/pg_trgm</filename> GIN indexes (Christophe Fornaroli) </para> </listitem> @@ -8265,7 +8771,7 @@ This commit is also listed under libpq and PL/pgSQL --> <para> Add <link - linkend="pgvisibility"><filename>contrib/pg_visibility</></> module + linkend="pgvisibility"><filename>contrib/pg_visibility</filename></link> module to allow examining table visibility maps (Robert Haas) </para> </listitem> @@ -8275,9 +8781,9 @@ This commit is also listed under libpq and PL/pgSQL 2015-09-07 [49124613f] contrib/sslinfo: add ssl_extension_info SRF --> <para> - Add <link linkend="sslinfo"><function>ssl_extension_info()</></> - function to <filename>contrib/sslinfo</>, to print information - about <acronym>SSL</> extensions present in the <literal>X509</> + Add <link linkend="sslinfo"><function>ssl_extension_info()</function></link> + function to <filename>contrib/sslinfo</filename>, to print information + about <acronym>SSL</acronym> extensions present in the <literal>X509</literal> certificate used for the current connection (Dmitry Voronin) </para> </listitem> @@ -8285,7 +8791,7 @@ This commit is also listed under libpq and PL/pgSQL </itemizedlist> <sect4> - <title><link linkend="postgres-fdw"><filename>postgres_fdw</></></title> + <title><link linkend="postgres-fdw"><filename>postgres_fdw</filename></link></title> <itemizedlist> @@ -8332,12 +8838,12 @@ This commit is also listed under libpq and PL/pgSQL 2016-03-18 [0bf3ae88a] Directly modify foreign tables. --> <para> - When feasible, perform <command>UPDATE</> or <command>DELETE</> + When feasible, perform <command>UPDATE</command> or <command>DELETE</command> entirely on the remote server (Etsuro Fujita) </para> <para> - Formerly, remote updates involved sending a <command>SELECT FOR UPDATE</> + Formerly, remote updates involved sending a <command>SELECT FOR UPDATE</command> 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 @@ -8355,7 +8861,7 @@ This commit is also listed under libpq and PL/pgSQL </para> <para> - Formerly, <filename>postgres_fdw</> always fetched 100 rows at + Formerly, <filename>postgres_fdw</filename> always fetched 100 rows at a time from remote queries; now that behavior is configurable. </para> </listitem> |