diff options
Diffstat (limited to 'doc/src/sgml/release-9.4.sgml')
| -rw-r--r-- | doc/src/sgml/release-9.4.sgml | 2438 |
1 files changed, 1337 insertions, 1101 deletions
diff --git a/doc/src/sgml/release-9.4.sgml b/doc/src/sgml/release-9.4.sgml index c665f90ca10..ab47dc50ddd 100644 --- a/doc/src/sgml/release-9.4.sgml +++ b/doc/src/sgml/release-9.4.sgml @@ -1,6 +1,242 @@ <!-- doc/src/sgml/release-9.4.sgml --> <!-- See header comment in release.sgml about typical markup --> + <sect1 id="release-9-4-15"> + <title>Release 9.4.15</title> + + <formalpara> + <title>Release date:</title> + <para>2017-11-09</para> + </formalpara> + + <para> + This release contains a variety of fixes from 9.4.14. + For information about new features in the 9.4 major release, see + <xref linkend="release-9-4">. + </para> + + <sect2> + <title>Migration to Version 9.4.15</title> + + <para> + A dump/restore is not required for those running 9.4.X. + </para> + + <para> + However, if you are upgrading from a version earlier than 9.4.13, + see <xref linkend="release-9-4-13">. + </para> + </sect2> + + <sect2> + <title>Changes</title> + + <itemizedlist> + + <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 <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> + <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> + <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> + <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> + 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> + <para> + Correctly restore the umask setting when file creation fails + in <command>COPY</command> or <function>lo_export()</function> + (Peter Eisentraut) + </para> + </listitem> + + <listitem> + <para> + Give a better error message for duplicate column names + in <command>ANALYZE</command> (Nathan Bossart) + </para> + </listitem> + + <listitem> + <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 <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> + <para> + Fix <application>libpq</application> to guard against integer + overflow in the row count of a <structname>PGresult</structname> + (Michael Paquier) + </para> + </listitem> + + <listitem> + <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> + <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-4-14"> <title>Release 9.4.14</title> @@ -53,20 +289,20 @@ Branch: REL9_4_STABLE [b51c8efc6] 2017-08-24 15:21:32 -0700 <listitem> <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 @@ -105,21 +341,21 @@ 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> <listitem> <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> @@ -136,7 +372,7 @@ CREATE OR REPLACE VIEW table_privileges AS </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, @@ -148,7 +384,7 @@ CREATE OR REPLACE VIEW table_privileges AS <listitem> <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> @@ -156,13 +392,13 @@ CREATE OR REPLACE VIEW table_privileges AS <listitem> <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> @@ -174,12 +410,12 @@ CREATE OR REPLACE VIEW table_privileges AS <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> @@ -228,7 +464,7 @@ CREATE OR REPLACE VIEW table_privileges AS <listitem> <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> @@ -236,11 +472,11 @@ CREATE OR REPLACE VIEW table_privileges AS <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> @@ -255,15 +491,15 @@ CREATE OR REPLACE VIEW table_privileges AS <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; @@ -294,15 +530,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> @@ -316,7 +552,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> @@ -330,16 +566,16 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0'; </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> @@ -347,13 +583,13 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0'; <listitem> <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> @@ -460,21 +696,21 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0'; <listitem> <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> <listitem> <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> <listitem> <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> @@ -488,7 +724,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0'; <listitem> <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> @@ -505,7 +741,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <para> Logical decoding crashed on tuples that are wider than 64KB (after compression, but with all data in-line). The case arises only - when <literal>REPLICA IDENTITY FULL</> is enabled for a table + when <literal>REPLICA IDENTITY FULL</literal> is enabled for a table containing such tuples. </para> </listitem> @@ -553,7 +789,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -561,7 +797,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -569,56 +805,56 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> <listitem> <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> <listitem> <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> <listitem> <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> <listitem> <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> @@ -629,20 +865,20 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> @@ -655,9 +891,9 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -668,8 +904,8 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -680,15 +916,15 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> @@ -701,14 +937,14 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> @@ -719,14 +955,14 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -734,13 +970,13 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> @@ -748,7 +984,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <para> - Fix <application>pg_basebackup</> output to stdout on Windows + Fix <application>pg_basebackup</application> output to stdout on Windows (Haribabu Kommi) </para> @@ -760,8 +996,8 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -773,9 +1009,9 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -786,7 +1022,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -798,14 +1034,14 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> @@ -825,34 +1061,34 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> <listitem> <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> <listitem> <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> @@ -889,7 +1125,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <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> @@ -906,18 +1142,18 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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. @@ -941,7 +1177,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <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, @@ -955,17 +1191,17 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -996,7 +1232,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -1009,7 +1245,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -1017,21 +1253,21 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <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> <listitem> <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> <listitem> <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> @@ -1052,19 +1288,19 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 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> <listitem> <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> @@ -1072,27 +1308,27 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> @@ -1106,12 +1342,12 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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. @@ -1120,21 +1356,21 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> @@ -1146,7 +1382,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <para> - Improve performance of <structname>pg_timezone_names</> view + Improve performance of <structname>pg_timezone_names</structname> view (Tom Lane, David Rowley) </para> </listitem> @@ -1160,13 +1396,13 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> @@ -1184,21 +1420,21 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> <listitem> <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> @@ -1213,20 +1449,20 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> @@ -1238,26 +1474,26 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <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> <listitem> <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> <listitem> <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> @@ -1270,7 +1506,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700 <listitem> <para> - In <filename>contrib/postgres_fdw</>, + In <filename>contrib/postgres_fdw</filename>, transmit query cancellation requests to the remote server (Michael Paquier, Etsuro Fujita) </para> @@ -1320,7 +1556,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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 @@ -1334,9 +1570,9 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -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> @@ -1349,15 +1585,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -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. @@ -1410,15 +1646,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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. @@ -1435,19 +1671,19 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 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> <listitem> <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> @@ -1513,7 +1749,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> @@ -1528,7 +1764,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -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> @@ -1544,15 +1780,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 </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> <listitem> <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> @@ -1565,7 +1801,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> @@ -1578,7 +1814,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <para> Report correct object identity during <command>ALTER TEXT SEARCH - CONFIGURATION</> (Artur Zakirov) + CONFIGURATION</command> (Artur Zakirov) </para> <para> @@ -1608,13 +1844,13 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> @@ -1622,12 +1858,12 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> @@ -1642,15 +1878,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 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> <listitem> <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> @@ -1661,33 +1897,33 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> <listitem> <para> - Fix performance problems in <function>ts_rewrite()</> (Tom Lane) + Fix performance problems in <function>ts_rewrite()</function> (Tom Lane) </para> </listitem> <listitem> <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> <listitem> <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> <listitem> <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> @@ -1699,8 +1935,8 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> @@ -1712,15 +1948,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> @@ -1733,28 +1969,28 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> <listitem> <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> <listitem> <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> @@ -1767,15 +2003,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> <listitem> <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> @@ -1794,21 +2030,21 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> <listitem> <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> @@ -1820,23 +2056,23 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> <listitem> <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> <listitem> <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> @@ -1847,22 +2083,22 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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> <listitem> <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> @@ -1888,7 +2124,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <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. @@ -1951,7 +2187,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 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> @@ -1959,7 +2195,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <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> @@ -1970,20 +2206,20 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 </para> <para> - The typical symptom was <quote>unexpected GIN leaf action</> errors + The typical symptom was <quote>unexpected GIN leaf action</quote> errors during WAL replay. </para> </listitem> <listitem> <para> - Fix <command>SELECT FOR UPDATE/SHARE</> to correctly lock tuples that + Fix <command>SELECT FOR UPDATE/SHARE</command> to correctly lock tuples that have been updated by a subsequently-aborted transaction (Álvaro Herrera) </para> <para> - In 9.5 and later, the <command>SELECT</> would sometimes fail to + In 9.5 and later, the <command>SELECT</command> would sometimes fail to return such tuples at all. A failure has not been proven to occur in earlier releases, but might be possible with concurrent updates. </para> @@ -2017,79 +2253,79 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400 <listitem> <para> - Fix query-lifespan memory leak in a bulk <command>UPDATE</> on a table - with a <literal>PRIMARY KEY</> or <literal>REPLICA IDENTITY</> index + Fix query-lifespan memory leak in a bulk <command>UPDATE</command> on a table + with a <literal>PRIMARY KEY</literal> or <literal>REPLICA IDENTITY</literal> index (Tom Lane) </para> </listitem> <listitem> <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> <listitem> <para> Suppress printing of zeroes for unmeasured times - in <command>EXPLAIN</> (Maksim Milyutin) + in <command>EXPLAIN</command> (Maksim Milyutin) </para> <para> Certain option combinations resulted in printing zero values for times that actually aren't ever measured in that combination. Our general - policy in <command>EXPLAIN</> is not to print such fields at all, so + policy in <command>EXPLAIN</command> is not to print such fields at all, so do that consistently in all cases. </para> </listitem> <listitem> <para> - Fix timeout length when <command>VACUUM</> is waiting for exclusive + Fix timeout length when <command>VACUUM</command> is waiting for exclusive table lock so that it can truncate the table (Simon Riggs) </para> <para> The timeout was meant to be 50 milliseconds, but it was actually only - 50 microseconds, causing <command>VACUUM</> to give up on truncation + 50 microseconds, causing <command>VACUUM</command> to give up on truncation much more easily than intended. Set it to the intended value. </para> </listitem> <listitem> <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> <listitem> <para> Remove artificial restrictions on the values accepted - by <function>numeric_in()</> and <function>numeric_recv()</> + by <function>numeric_in()</function> and <function>numeric_recv()</function> (Tom Lane) </para> <para> We allow numeric values up to the limit of the storage format (more - than <literal>1e100000</>), so it seems fairly pointless - that <function>numeric_in()</> rejected scientific-notation exponents - above 1000. Likewise, it was silly for <function>numeric_recv()</> to + than <literal>1e100000</literal>), so it seems fairly pointless + that <function>numeric_in()</function> rejected scientific-notation exponents + above 1000. Likewise, it was silly for <function>numeric_recv()</function> to reject more than 1000 digits in an input value. </para> </listitem> @@ -2134,7 +2370,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <para> - Disallow starting a standalone backend with <literal>standby_mode</> + Disallow starting a standalone backend with <literal>standby_mode</literal> turned on (Michael Paquier) </para> @@ -2153,7 +2389,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <para> This failure to reset all of the fields of the slot could - prevent <command>VACUUM</> from removing dead tuples. + prevent <command>VACUUM</command> from removing dead tuples. </para> </listitem> @@ -2164,7 +2400,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -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> @@ -2178,7 +2414,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <para> Previously, the same value would be chosen every time, because it was - derived from <function>random()</> but <function>srandom()</> had not + derived from <function>random()</function> but <function>srandom()</function> had not yet been called. While relatively harmless, this was not the intended behavior. </para> @@ -2191,8 +2427,8 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 </para> <para> - Windows sometimes returns <literal>ERROR_ACCESS_DENIED</> rather - than <literal>ERROR_ALREADY_EXISTS</> when there is an existing + Windows sometimes returns <literal>ERROR_ACCESS_DENIED</literal> rather + than <literal>ERROR_ALREADY_EXISTS</literal> when there is an existing segment. This led to postmaster startup failure due to believing that the former was an unrecoverable error. </para> @@ -2201,7 +2437,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <para> Don't try to share SSL contexts across multiple connections - in <application>libpq</> (Heikki Linnakangas) + in <application>libpq</application> (Heikki Linnakangas) </para> <para> @@ -2212,30 +2448,30 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <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> <listitem> <para> - Make <application>ecpg</>'s <option>--help</> and <option>--version</> + Make <application>ecpg</application>'s <option>--help</option> and <option>--version</option> options work consistently with our other executables (Haribabu Kommi) </para> </listitem> <listitem> <para> - Fix <application>pgbench</>'s calculation of average latency + Fix <application>pgbench</application>'s calculation of average latency (Fabien Coelho) </para> <para> - The calculation was incorrect when there were <literal>\sleep</> + The calculation was incorrect when there were <literal>\sleep</literal> commands in the script, or when the test duration was specified in number of transactions rather than total time. </para> @@ -2243,12 +2479,12 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <para> - In <application>pg_dump</>, never dump range constructor functions + In <application>pg_dump</application>, never dump range constructor functions (Tom Lane) </para> <para> - This oversight led to <application>pg_upgrade</> failures with + This oversight led to <application>pg_upgrade</application> failures with extensions containing range types, due to duplicate creation of the constructor functions. </para> @@ -2256,8 +2492,8 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <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> @@ -2268,7 +2504,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <para> - Fix <application>pg_xlogdump</> to cope with a WAL file that begins + Fix <application>pg_xlogdump</application> to cope with a WAL file that begins with a continuation record spanning more than one page (Pavan Deolasee) </para> @@ -2276,15 +2512,15 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <para> - Fix <filename>contrib/pg_buffercache</> to work - when <varname>shared_buffers</> exceeds 256GB (KaiGai Kohei) + Fix <filename>contrib/pg_buffercache</filename> to work + when <varname>shared_buffers</varname> exceeds 256GB (KaiGai Kohei) </para> </listitem> <listitem> <para> - Fix <filename>contrib/intarray/bench/bench.pl</> to print the results - of the <command>EXPLAIN</> it does when given the <option>-e</> option + Fix <filename>contrib/intarray/bench/bench.pl</filename> to print the results + of the <command>EXPLAIN</command> it does when given the <option>-e</option> option (Daniel Gustafsson) </para> </listitem> @@ -2296,17 +2532,17 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 </para> <para> - When <productname>PostgreSQL</> has been configured - with <option>--enable-tap-tests</>, <quote>make install</> will now + When <productname>PostgreSQL</productname> has been configured + with <option>--enable-tap-tests</option>, <quote>make install</quote> will now install the Perl support files for TAP testing where PGXS can find them. This allows non-core extensions to - use <literal>$(prove_check)</> without extra tests. + use <literal>$(prove_check)</literal> without extra tests. </para> </listitem> <listitem> <para> - In MSVC builds, include <application>pg_recvlogical</> in a + In MSVC builds, include <application>pg_recvlogical</application> in a client-only installation (MauMau) </para> </listitem> @@ -2327,17 +2563,17 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 If a dynamic time zone abbreviation does not match any entry in the referenced time zone, treat it as equivalent to the time zone name. This avoids unexpected failures when IANA removes abbreviations from - their time zone database, as they did in <application>tzdata</> + their time zone database, as they did in <application>tzdata</application> release 2016f and seem likely to do again in the future. The consequences were not limited to not recognizing the individual abbreviation; any mismatch caused - the <structname>pg_timezone_abbrevs</> view to fail altogether. + the <structname>pg_timezone_abbrevs</structname> view to fail altogether. </para> </listitem> <listitem> <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, @@ -2350,15 +2586,15 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -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> @@ -2403,17 +2639,17 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <para> Fix possible mis-evaluation of - nested <literal>CASE</>-<literal>WHEN</> expressions (Heikki + nested <literal>CASE</literal>-<literal>WHEN</literal> expressions (Heikki Linnakangas, Michael Paquier, Tom Lane) </para> <para> - A <literal>CASE</> expression appearing within the test value - subexpression of another <literal>CASE</> could become confused about + A <literal>CASE</literal> expression appearing within the test value + subexpression of another <literal>CASE</literal> could become confused about whether its own test value was null or not. Also, inlining of a SQL function implementing the equality operator used by - a <literal>CASE</> expression could result in passing the wrong test - value to functions called within a <literal>CASE</> expression in the + a <literal>CASE</literal> expression could result in passing the wrong test + value to functions called within a <literal>CASE</literal> expression in the SQL function's body. If the test values were of different data types, a crash might result; moreover such situations could be abused to allow disclosure of portions of server memory. (CVE-2016-5423) @@ -2427,7 +2663,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 </para> <para> - Numerous places in <application>vacuumdb</> and other client programs + Numerous places in <application>vacuumdb</application> and other client programs could become confused by database and role names containing double quotes or backslashes. Tighten up quoting rules to make that safe. Also, ensure that when a conninfo string is used as a database name @@ -2436,22 +2672,22 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <para> Fix handling of paired double quotes - in <application>psql</>'s <command>\connect</> - and <command>\password</> commands to match the documentation. + in <application>psql</application>'s <command>\connect</command> + and <command>\password</command> commands to match the documentation. </para> <para> - Introduce a new <option>-reuse-previous</> option - in <application>psql</>'s <command>\connect</> command to allow + Introduce a new <option>-reuse-previous</option> option + in <application>psql</application>'s <command>\connect</command> command to allow explicit control of whether to re-use connection parameters from a previous connection. (Without this, the choice is based on whether the database name looks like a conninfo string, as before.) This allows secure handling of database names containing special - characters in <application>pg_dumpall</> scripts. + characters in <application>pg_dumpall</application> scripts. </para> <para> - <application>pg_dumpall</> now refuses to deal with database and role + <application>pg_dumpall</application> now refuses to deal with database and role names containing carriage returns or newlines, as it seems impractical to quote those characters safely on Windows. In future we may reject such names on the server side, but that step has not been taken yet. @@ -2461,40 +2697,40 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 These are considered security fixes because crafted object names containing special characters could have been used to execute commands with superuser privileges the next time a superuser - executes <application>pg_dumpall</> or other routine maintenance + executes <application>pg_dumpall</application> or other routine maintenance operations. (CVE-2016-5424) </para> </listitem> <listitem> <para> - Fix corner-case misbehaviors for <literal>IS NULL</>/<literal>IS NOT - NULL</> applied to nested composite values (Andrew Gierth, Tom Lane) + Fix corner-case misbehaviors for <literal>IS NULL</literal>/<literal>IS NOT + NULL</literal> applied to nested composite values (Andrew Gierth, Tom Lane) </para> <para> - The SQL standard specifies that <literal>IS NULL</> should return + The SQL standard specifies that <literal>IS NULL</literal> should return TRUE for a row of all null values (thus <literal>ROW(NULL,NULL) IS - NULL</> yields TRUE), but this is not meant to apply recursively - (thus <literal>ROW(NULL, ROW(NULL,NULL)) IS NULL</> yields FALSE). + NULL</literal> yields TRUE), but this is not meant to apply recursively + (thus <literal>ROW(NULL, ROW(NULL,NULL)) IS NULL</literal> yields FALSE). The core executor got this right, but certain planner optimizations treated the test as recursive (thus producing TRUE in both cases), - and <filename>contrib/postgres_fdw</> could produce remote queries + and <filename>contrib/postgres_fdw</filename> could produce remote queries that misbehaved similarly. </para> </listitem> <listitem> <para> - Make the <type>inet</> and <type>cidr</> data types properly reject + Make the <type>inet</type> and <type>cidr</type> data types properly reject IPv6 addresses with too many colon-separated fields (Tom Lane) </para> </listitem> <listitem> <para> - Prevent crash in <function>close_ps()</> - (the <type>point</> <literal>##</> <type>lseg</> operator) + Prevent crash in <function>close_ps()</function> + (the <type>point</type> <literal>##</literal> <type>lseg</type> operator) for NaN input coordinates (Tom Lane) </para> @@ -2505,19 +2741,19 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <para> - Avoid possible crash in <function>pg_get_expr()</> when inconsistent + Avoid possible crash in <function>pg_get_expr()</function> when inconsistent values are passed to it (Michael Paquier, Thomas Munro) </para> </listitem> <listitem> <para> - Fix several one-byte buffer over-reads in <function>to_number()</> + Fix several one-byte buffer over-reads in <function>to_number()</function> (Peter Eisentraut) </para> <para> - In several cases the <function>to_number()</> function would read one + In several cases the <function>to_number()</function> function would read one more character than it should from the input string. There is a small chance of a crash, if the input happens to be adjacent to the end of memory. @@ -2527,8 +2763,8 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <para> Do not run the planner on the query contained in <literal>CREATE - MATERIALIZED VIEW</> or <literal>CREATE TABLE AS</> - when <literal>WITH NO DATA</> is specified (Michael Paquier, + MATERIALIZED VIEW</literal> or <literal>CREATE TABLE AS</literal> + when <literal>WITH NO DATA</literal> is specified (Michael Paquier, Tom Lane) </para> @@ -2542,7 +2778,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <para> Avoid unsafe intermediate state during expensive paths - through <function>heap_update()</> (Masahiko Sawada, Andres Freund) + through <function>heap_update()</function> (Masahiko Sawada, Andres Freund) </para> <para> @@ -2568,15 +2804,15 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <para> - Avoid unnecessary <quote>could not serialize access</> errors when - acquiring <literal>FOR KEY SHARE</> row locks in serializable mode + Avoid unnecessary <quote>could not serialize access</quote> errors when + acquiring <literal>FOR KEY SHARE</literal> row locks in serializable mode (Álvaro Herrera) </para> </listitem> <listitem> <para> - Avoid crash in <literal>postgres -C</> when the specified variable + Avoid crash in <literal>postgres -C</literal> when the specified variable has a null string value (Michael Paquier) </para> </listitem> @@ -2619,12 +2855,12 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400 <listitem> <para> - Avoid consuming a transaction ID during <command>VACUUM</> + Avoid consuming a transaction ID during <command>VACUUM</command> (Alexander Korotkov) </para> <para> - Some cases in <command>VACUUM</> unnecessarily caused an XID to be + Some cases in <command>VACUUM</command> unnecessarily caused an XID to be assigned to the current transaction. Normally this is negligible, but if one is up against the XID wraparound limit, consuming more XIDs during anti-wraparound vacuums is a very bad thing. @@ -2640,12 +2876,12 @@ Branch: REL9_2_STABLE [294509ea9] 2016-05-25 19:39:49 -0400 Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 --> <para> - Avoid canceling hot-standby queries during <command>VACUUM FREEZE</> + Avoid canceling hot-standby queries during <command>VACUUM FREEZE</command> (Simon Riggs, Álvaro Herrera) </para> <para> - <command>VACUUM FREEZE</> on an otherwise-idle master server could + <command>VACUUM FREEZE</command> on an otherwise-idle master server could result in unnecessary cancellations of queries on its standby servers. </para> @@ -2660,15 +2896,15 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <para> The usual symptom of this bug is errors - like <quote>MultiXactId <replaceable>NNN</> has not been created + like <quote>MultiXactId <replaceable>NNN</replaceable> has not been created yet -- apparent wraparound</quote>. </para> </listitem> <listitem> <para> - When a manual <command>ANALYZE</> specifies a column list, don't - reset the table's <literal>changes_since_analyze</> counter + When a manual <command>ANALYZE</command> specifies a column list, don't + reset the table's <literal>changes_since_analyze</literal> counter (Tom Lane) </para> @@ -2680,7 +2916,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Fix <command>ANALYZE</>'s overestimation of <literal>n_distinct</> + Fix <command>ANALYZE</command>'s overestimation of <literal>n_distinct</literal> for a unique or nearly-unique column with many null entries (Tom Lane) </para> @@ -2713,7 +2949,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 </para> <para> - This mistake prevented <command>VACUUM</> from completing in some + This mistake prevented <command>VACUUM</command> from completing in some cases involving corrupt b-tree indexes. </para> </listitem> @@ -2727,8 +2963,8 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Fix <filename>contrib/btree_gin</> to handle the smallest - possible <type>bigint</> value correctly (Peter Eisentraut) + Fix <filename>contrib/btree_gin</filename> to handle the smallest + possible <type>bigint</type> value correctly (Peter Eisentraut) </para> </listitem> @@ -2741,53 +2977,53 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <para> It's planned to switch to two-part instead of three-part server version numbers for releases after 9.6. Make sure - that <function>PQserverVersion()</> returns the correct value for + that <function>PQserverVersion()</function> returns the correct value for such cases. </para> </listitem> <listitem> <para> - Fix <application>ecpg</>'s code for <literal>unsigned long long</> + Fix <application>ecpg</application>'s code for <literal>unsigned long long</literal> array elements (Michael Meskes) </para> </listitem> <listitem> <para> - In <application>pg_dump</> with both <option>-c</> and <option>-C</> - options, avoid emitting an unwanted <literal>CREATE SCHEMA public</> + In <application>pg_dump</application> with both <option>-c</option> and <option>-C</option> + options, avoid emitting an unwanted <literal>CREATE SCHEMA public</literal> command (David Johnston, Tom Lane) </para> </listitem> <listitem> <para> - Improve handling of <systemitem>SIGTERM</>/control-C in - parallel <application>pg_dump</> and <application>pg_restore</> (Tom + Improve handling of <systemitem>SIGTERM</systemitem>/control-C in + parallel <application>pg_dump</application> and <application>pg_restore</application> (Tom Lane) </para> <para> Make sure that the worker processes will exit promptly, and also arrange to send query-cancel requests to the connected backends, in case they - are doing something long-running such as a <command>CREATE INDEX</>. + are doing something long-running such as a <command>CREATE INDEX</command>. </para> </listitem> <listitem> <para> - Fix error reporting in parallel <application>pg_dump</> - and <application>pg_restore</> (Tom Lane) + Fix error reporting in parallel <application>pg_dump</application> + and <application>pg_restore</application> (Tom Lane) </para> <para> - Previously, errors reported by <application>pg_dump</> - or <application>pg_restore</> worker processes might never make it to + Previously, errors reported by <application>pg_dump</application> + or <application>pg_restore</application> worker processes might never make it to the user's console, because the messages went through the master process, and there were various deadlock scenarios that would prevent the master process from passing on the messages. Instead, just print - everything to <literal>stderr</>. In some cases this will result in + everything to <literal>stderr</literal>. In some cases this will result in duplicate messages (for instance, if all the workers report a server shutdown), but that seems better than no message. </para> @@ -2795,8 +3031,8 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Ensure that parallel <application>pg_dump</> - or <application>pg_restore</> on Windows will shut down properly + Ensure that parallel <application>pg_dump</application> + or <application>pg_restore</application> on Windows will shut down properly after an error (Kyotaro Horiguchi) </para> @@ -2808,7 +3044,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Make <application>pg_dump</> behave better when built without zlib + Make <application>pg_dump</application> behave better when built without zlib support (Kyotaro Horiguchi) </para> @@ -2820,7 +3056,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Make <application>pg_basebackup</> accept <literal>-Z 0</> as + Make <application>pg_basebackup</application> accept <literal>-Z 0</literal> as specifying no compression (Fujii Masao) </para> </listitem> @@ -2841,13 +3077,13 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Be more predictable about reporting <quote>statement timeout</> - versus <quote>lock timeout</> (Tom Lane) + Be more predictable about reporting <quote>statement timeout</quote> + versus <quote>lock timeout</quote> (Tom Lane) </para> <para> On heavily loaded machines, the regression tests sometimes failed due - to reporting <quote>lock timeout</> even though the statement timeout + to reporting <quote>lock timeout</quote> even though the statement timeout should have occurred first. </para> </listitem> @@ -2867,7 +3103,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> Update our copy of the timezone code to match - IANA's <application>tzcode</> release 2016c (Tom Lane) + IANA's <application>tzcode</application> release 2016c (Tom Lane) </para> <para> @@ -2879,7 +3115,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Update time zone data files to <application>tzdata</> release 2016f + Update time zone data files to <application>tzdata</application> release 2016f for DST law changes in Kemerovo and Novosibirsk, plus historical corrections for Azerbaijan, Belarus, and Morocco. </para> @@ -2934,7 +3170,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 using OpenSSL within a single process and not all the code involved follows the same rules for when to clear the error queue. Failures have been reported specifically when a client application - uses SSL connections in <application>libpq</> concurrently with + uses SSL connections in <application>libpq</application> concurrently with SSL connections using the PHP, Python, or Ruby wrappers for OpenSSL. It's possible for similar problems to arise within the server as well, if an extension module establishes an outgoing SSL connection. @@ -2943,7 +3179,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Fix <quote>failed to build any <replaceable>N</>-way joins</quote> + Fix <quote>failed to build any <replaceable>N</replaceable>-way joins</quote> planner error with a full join enclosed in the right-hand side of a left join (Tom Lane) </para> @@ -2957,10 +3193,10 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <para> Given a three-or-more-way equivalence class of variables, such - as <literal>X.X = Y.Y = Z.Z</>, it was possible for the planner to omit + as <literal>X.X = Y.Y = Z.Z</literal>, it was possible for the planner to omit some of the tests needed to enforce that all the variables are actually equal, leading to join rows being output that didn't satisfy - the <literal>WHERE</> clauses. For various reasons, erroneous plans + the <literal>WHERE</literal> clauses. For various reasons, erroneous plans were seldom selected in practice, so that this bug has gone undetected for a long time. </para> @@ -2981,14 +3217,14 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <para> The memory leak would typically not amount to much in simple queries, but it could be very substantial during a large GIN index build with - high <varname>maintenance_work_mem</>. + high <varname>maintenance_work_mem</varname>. </para> </listitem> <listitem> <para> - Fix possible misbehavior of <literal>TH</>, <literal>th</>, - and <literal>Y,YYY</> format codes in <function>to_timestamp()</> + Fix possible misbehavior of <literal>TH</literal>, <literal>th</literal>, + and <literal>Y,YYY</literal> format codes in <function>to_timestamp()</function> (Tom Lane) </para> @@ -3000,29 +3236,29 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Fix dumping of rules and views in which the <replaceable>array</> - argument of a <literal><replaceable>value</> <replaceable>operator</> - ANY (<replaceable>array</>)</literal> construct is a sub-SELECT + Fix dumping of rules and views in which the <replaceable>array</replaceable> + argument of a <literal><replaceable>value</replaceable> <replaceable>operator</replaceable> + ANY (<replaceable>array</replaceable>)</literal> construct is a sub-SELECT (Tom Lane) </para> </listitem> <listitem> <para> - Disallow newlines in <command>ALTER SYSTEM</> parameter values + Disallow newlines in <command>ALTER SYSTEM</command> parameter values (Tom Lane) </para> <para> The configuration-file parser doesn't support embedded newlines in string literals, so we mustn't allow them in values to be inserted - by <command>ALTER SYSTEM</>. + by <command>ALTER SYSTEM</command>. </para> </listitem> <listitem> <para> - Fix <command>ALTER TABLE ... REPLICA IDENTITY USING INDEX</> to + Fix <command>ALTER TABLE ... REPLICA IDENTITY USING INDEX</command> to work properly if an index on OID is selected (David Rowley) </para> </listitem> @@ -3048,19 +3284,19 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Make <application>pg_regress</> use a startup timeout from the - <envar>PGCTLTIMEOUT</> environment variable, if that's set (Tom Lane) + Make <application>pg_regress</application> use a startup timeout from the + <envar>PGCTLTIMEOUT</envar> environment variable, if that's set (Tom Lane) </para> <para> This is for consistency with a behavior recently added - to <application>pg_ctl</>; it eases automated testing on slow machines. + to <application>pg_ctl</application>; it eases automated testing on slow machines. </para> </listitem> <listitem> <para> - Fix <application>pg_upgrade</> to correctly restore extension + Fix <application>pg_upgrade</application> to correctly restore extension membership for operator families containing only one operator class (Tom Lane) </para> @@ -3068,20 +3304,20 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <para> In such a case, the operator family was restored into the new database, but it was no longer marked as part of the extension. This had no - immediate ill effects, but would cause later <application>pg_dump</> + immediate ill effects, but would cause later <application>pg_dump</application> runs to emit output that would cause (harmless) errors on restore. </para> </listitem> <listitem> <para> - Fix <application>pg_upgrade</> to not fail when new-cluster TOAST rules + Fix <application>pg_upgrade</application> to not fail when new-cluster TOAST rules differ from old (Tom Lane) </para> <para> - <application>pg_upgrade</> had special-case code to handle the - situation where the new <productname>PostgreSQL</> version thinks that + <application>pg_upgrade</application> had special-case code to handle the + situation where the new <productname>PostgreSQL</productname> version thinks that a table should have a TOAST table while the old version did not. That code was broken, so remove it, and instead do nothing in such cases; there seems no reason to believe that we can't get along fine without @@ -3092,22 +3328,22 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> Reduce the number of SysV semaphores used by a build configured with - <option>--disable-spinlocks</> (Tom Lane) + <option>--disable-spinlocks</option> (Tom Lane) </para> </listitem> <listitem> <para> - Rename internal function <function>strtoi()</> - to <function>strtoint()</> to avoid conflict with a NetBSD library + Rename internal function <function>strtoi()</function> + to <function>strtoint()</function> to avoid conflict with a NetBSD library function (Thomas Munro) </para> </listitem> <listitem> <para> - Fix reporting of errors from <function>bind()</> - and <function>listen()</> system calls on Windows (Tom Lane) + Fix reporting of errors from <function>bind()</function> + and <function>listen()</function> system calls on Windows (Tom Lane) </para> </listitem> @@ -3120,19 +3356,19 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Fix <function>putenv()</> to work properly with Visual Studio 2013 + Fix <function>putenv()</function> to work properly with Visual Studio 2013 (Michael Paquier) </para> </listitem> <listitem> <para> - Avoid possibly-unsafe use of Windows' <function>FormatMessage()</> + Avoid possibly-unsafe use of Windows' <function>FormatMessage()</function> function (Christian Ullrich) </para> <para> - Use the <literal>FORMAT_MESSAGE_IGNORE_INSERTS</> flag where + Use the <literal>FORMAT_MESSAGE_IGNORE_INSERTS</literal> flag where appropriate. No live bug is known to exist here, but it seems like a good idea to be careful. </para> @@ -3140,9 +3376,9 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Update time zone data files to <application>tzdata</> release 2016d + Update time zone data files to <application>tzdata</application> release 2016d for DST law changes in Russia and Venezuela. There are new zone - names <literal>Europe/Kirov</> and <literal>Asia/Tomsk</> to reflect + names <literal>Europe/Kirov</literal> and <literal>Asia/Tomsk</literal> to reflect the fact that these regions now have different time zone histories from adjacent regions. </para> @@ -3188,29 +3424,29 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> Fix incorrect handling of NULL index entries in - indexed <literal>ROW()</> comparisons (Tom Lane) + indexed <literal>ROW()</literal> comparisons (Tom Lane) </para> <para> An index search using a row comparison such as <literal>ROW(a, b) > - ROW('x', 'y')</> would stop upon reaching a NULL entry in - the <structfield>b</> column, ignoring the fact that there might be - non-NULL <structfield>b</> values associated with later values - of <structfield>a</>. + ROW('x', 'y')</literal> would stop upon reaching a NULL entry in + the <structfield>b</structfield> column, ignoring the fact that there might be + non-NULL <structfield>b</structfield> values associated with later values + of <structfield>a</structfield>. </para> </listitem> <listitem> <para> Avoid unlikely data-loss scenarios due to renaming files without - adequate <function>fsync()</> calls before and after (Michael Paquier, + adequate <function>fsync()</function> calls before and after (Michael Paquier, Tomas Vondra, Andres Freund) </para> </listitem> <listitem> <para> - Fix bug in <function>json_to_record()</> when a field of its input + Fix bug in <function>json_to_record()</function> when a field of its input object contains a sub-object with a field name matching one of the requested output column names (Tom Lane) </para> @@ -3219,7 +3455,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> Fix misformatting of negative time zone offsets - by <function>to_char()</>'s <literal>OF</> format code + by <function>to_char()</function>'s <literal>OF</literal> format code (Thomas Munro, Tom Lane) </para> </listitem> @@ -3232,7 +3468,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <para> Previously, standby servers would delay application of WAL records in - response to <varname>recovery_min_apply_delay</> even while replaying + response to <varname>recovery_min_apply_delay</varname> even while replaying the initial portion of WAL needed to make their database state valid. Since the standby is useless until it's reached a consistent database state, this was deemed unhelpful. @@ -3241,7 +3477,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Correctly handle cases where <literal>pg_subtrans</> is close to XID + Correctly handle cases where <literal>pg_subtrans</literal> is close to XID wraparound during server startup (Jeff Janes) </para> </listitem> @@ -3253,44 +3489,44 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <para> Trouble cases included tuples larger than one page when replica - identity is <literal>FULL</>, <command>UPDATE</>s that change a + identity is <literal>FULL</literal>, <command>UPDATE</command>s that change a primary key within a transaction large enough to be spooled to disk, incorrect reports of <quote>subxact logged without previous toplevel - record</>, and incorrect reporting of a transaction's commit time. + record</quote>, and incorrect reporting of a transaction's commit time. </para> </listitem> <listitem> <para> Fix planner error with nested security barrier views when the outer - view has a <literal>WHERE</> clause containing a correlated subquery + view has a <literal>WHERE</literal> clause containing a correlated subquery (Dean Rasheed) </para> </listitem> <listitem> <para> - Fix corner-case crash due to trying to free <function>localeconv()</> + Fix corner-case crash due to trying to free <function>localeconv()</function> output strings more than once (Tom Lane) </para> </listitem> <listitem> <para> - Fix parsing of affix files for <literal>ispell</> dictionaries + Fix parsing of affix files for <literal>ispell</literal> dictionaries (Tom Lane) </para> <para> The code could go wrong if the affix file contained any characters whose byte length changes during case-folding, for - example <literal>I</> in Turkish UTF8 locales. + example <literal>I</literal> in Turkish UTF8 locales. </para> </listitem> <listitem> <para> - Avoid use of <function>sscanf()</> to parse <literal>ispell</> + Avoid use of <function>sscanf()</function> to parse <literal>ispell</literal> dictionary files (Artur Zakirov) </para> @@ -3316,27 +3552,27 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> - Fix <application>psql</>'s tab completion logic to handle multibyte + Fix <application>psql</application>'s tab completion logic to handle multibyte characters properly (Kyotaro Horiguchi, Robert Haas) </para> </listitem> <listitem> <para> - Fix <application>psql</>'s tab completion for - <literal>SECURITY LABEL</> (Tom Lane) + Fix <application>psql</application>'s tab completion for + <literal>SECURITY LABEL</literal> (Tom Lane) </para> <para> - Pressing TAB after <literal>SECURITY LABEL</> might cause a crash + Pressing TAB after <literal>SECURITY LABEL</literal> might cause a crash or offering of inappropriate keywords. </para> </listitem> <listitem> <para> - Make <application>pg_ctl</> accept a wait timeout from the - <envar>PGCTLTIMEOUT</> environment variable, if none is specified on + Make <application>pg_ctl</application> accept a wait timeout from the + <envar>PGCTLTIMEOUT</envar> environment variable, if none is specified on the command line (Noah Misch) </para> @@ -3350,26 +3586,26 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> Fix incorrect test for Windows service status - in <application>pg_ctl</> (Manuel Mathar) + in <application>pg_ctl</application> (Manuel Mathar) </para> <para> The previous set of minor releases attempted to - fix <application>pg_ctl</> to properly determine whether to send log + fix <application>pg_ctl</application> to properly determine whether to send log messages to Window's Event Log, but got the test backwards. </para> </listitem> <listitem> <para> - Fix <application>pgbench</> to correctly handle the combination - of <literal>-C</> and <literal>-M prepared</> options (Tom Lane) + Fix <application>pgbench</application> to correctly handle the combination + of <literal>-C</literal> and <literal>-M prepared</literal> options (Tom Lane) </para> </listitem> <listitem> <para> - In <application>pg_upgrade</>, skip creating a deletion script when + In <application>pg_upgrade</application>, skip creating a deletion script when the new data directory is inside the old data directory (Bruce Momjian) </para> @@ -3397,21 +3633,21 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <listitem> <para> Fix multiple mistakes in the statistics returned - by <filename>contrib/pgstattuple</>'s <function>pgstatindex()</> + by <filename>contrib/pgstattuple</filename>'s <function>pgstatindex()</function> function (Tom Lane) </para> </listitem> <listitem> <para> - Remove dependency on <literal>psed</> in MSVC builds, since it's no + Remove dependency on <literal>psed</literal> in MSVC builds, since it's no longer provided by core Perl (Michael Paquier, Andrew Dunstan) </para> </listitem> <listitem> <para> - Update time zone data files to <application>tzdata</> release 2016c + Update time zone data files to <application>tzdata</application> release 2016c for DST law changes in Azerbaijan, Chile, Haiti, Palestine, and Russia (Altai, Astrakhan, Kirov, Sakhalin, Ulyanovsk regions), plus historical corrections for Lithuania, Moldova, and Russia @@ -3447,7 +3683,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400 <para> However, if you are upgrading an installation that contains any GIN - indexes that use the (non-default) <literal>jsonb_path_ops</> operator + indexes that use the (non-default) <literal>jsonb_path_ops</literal> operator class, see the first changelog entry below. </para> @@ -3471,19 +3707,19 @@ Branch: REL9_4_STABLE [788e35ac0] 2015-11-05 18:15:48 -0500 <listitem> <para> - Fix inconsistent hash calculations in <literal>jsonb_path_ops</> GIN + Fix inconsistent hash calculations in <literal>jsonb_path_ops</literal> GIN indexes (Tom Lane) </para> <para> - When processing <type>jsonb</> values that contain both scalars and + When processing <type>jsonb</type> values that contain both scalars and sub-objects at the same nesting level, for example an array containing both scalars and sub-arrays, key hash values could be calculated differently than they would be for the same key in a different context. This could result in queries not finding entries that they should find. Fixing this means that existing indexes may now be inconsistent with the new hash calculation code. Users - should <command>REINDEX</> <literal>jsonb_path_ops</> GIN indexes after + should <command>REINDEX</command> <literal>jsonb_path_ops</literal> GIN indexes after installing this update to make sure that all searches work as expected. </para> </listitem> @@ -3513,18 +3749,18 @@ Branch: REL9_1_STABLE [dea6da132] 2015-10-06 17:15:27 -0400 <listitem> <para> - Perform an immediate shutdown if the <filename>postmaster.pid</> file + Perform an immediate shutdown if the <filename>postmaster.pid</filename> file is removed (Tom Lane) </para> <para> The postmaster now checks every minute or so - that <filename>postmaster.pid</> is still there and still contains its + that <filename>postmaster.pid</filename> is still there and still contains its own PID. If not, it performs an immediate shutdown, as though it had - received <systemitem>SIGQUIT</>. The main motivation for this change + received <systemitem>SIGQUIT</systemitem>. The main motivation for this change is to ensure that failed buildfarm runs will get cleaned up without manual intervention; but it also serves to limit the bad effects if a - DBA forcibly removes <filename>postmaster.pid</> and then starts a new + DBA forcibly removes <filename>postmaster.pid</filename> and then starts a new postmaster. </para> </listitem> @@ -3541,7 +3777,7 @@ Branch: REL9_1_STABLE [08322daed] 2015-10-31 14:36:58 -0500 <listitem> <para> - In <literal>SERIALIZABLE</> transaction isolation mode, serialization + In <literal>SERIALIZABLE</literal> transaction isolation mode, serialization anomalies could be missed due to race conditions during insertions (Kevin Grittner, Thomas Munro) </para> @@ -3560,7 +3796,7 @@ Branch: REL9_1_STABLE [5f9a86b35] 2015-12-12 14:19:29 +0100 <listitem> <para> Fix failure to emit appropriate WAL records when doing <literal>ALTER - TABLE ... SET TABLESPACE</> for unlogged relations (Michael Paquier, + TABLE ... SET TABLESPACE</literal> for unlogged relations (Michael Paquier, Andres Freund) </para> @@ -3614,7 +3850,7 @@ Branch: REL9_1_STABLE [60ba32cb5] 2015-11-20 14:55:29 -0500 <listitem> <para> - Fix <command>ALTER COLUMN TYPE</> to reconstruct inherited check + Fix <command>ALTER COLUMN TYPE</command> to reconstruct inherited check constraints properly (Tom Lane) </para> </listitem> @@ -3629,7 +3865,7 @@ Branch: REL9_1_STABLE [7e29e7f55] 2015-12-21 19:49:15 -0300 <listitem> <para> - Fix <command>REASSIGN OWNED</> to change ownership of composite types + Fix <command>REASSIGN OWNED</command> to change ownership of composite types properly (Álvaro Herrera) </para> </listitem> @@ -3644,7 +3880,7 @@ Branch: REL9_1_STABLE [ab14c1383] 2015-12-21 19:16:15 -0300 <listitem> <para> - Fix <command>REASSIGN OWNED</> and <command>ALTER OWNER</> to correctly + Fix <command>REASSIGN OWNED</command> and <command>ALTER OWNER</command> to correctly update granted-permissions lists when changing owners of data types, foreign data wrappers, or foreign servers (Bruce Momjian, Álvaro Herrera) @@ -3663,7 +3899,7 @@ Branch: REL9_1_STABLE [f44c5203b] 2015-12-11 18:39:09 -0300 <listitem> <para> - Fix <command>REASSIGN OWNED</> to ignore foreign user mappings, + Fix <command>REASSIGN OWNED</command> to ignore foreign user mappings, rather than fail (Álvaro Herrera) </para> </listitem> @@ -3697,13 +3933,13 @@ Branch: REL9_3_STABLE [0a34ff7e9] 2015-12-07 17:41:45 -0500 <listitem> <para> - Fix planner's handling of <literal>LATERAL</> references (Tom + Fix planner's handling of <literal>LATERAL</literal> references (Tom Lane) </para> <para> This fixes some corner cases that led to <quote>failed to build any - N-way joins</> or <quote>could not devise a query plan</> planner + N-way joins</quote> or <quote>could not devise a query plan</quote> planner failures. </para> </listitem> @@ -3753,9 +3989,9 @@ Branch: REL9_3_STABLE [faf18a905] 2015-11-16 13:45:17 -0500 <listitem> <para> - Speed up generation of unique table aliases in <command>EXPLAIN</> and + Speed up generation of unique table aliases in <command>EXPLAIN</command> and rule dumping, and ensure that generated aliases do not - exceed <literal>NAMEDATALEN</> (Tom Lane) + exceed <literal>NAMEDATALEN</literal> (Tom Lane) </para> </listitem> @@ -3771,8 +4007,8 @@ Branch: REL9_1_STABLE [7b21d1bca] 2015-11-15 14:41:09 -0500 <listitem> <para> - Fix dumping of whole-row Vars in <literal>ROW()</> - and <literal>VALUES()</> lists (Tom Lane) + Fix dumping of whole-row Vars in <literal>ROW()</literal> + and <literal>VALUES()</literal> lists (Tom Lane) </para> </listitem> @@ -3785,8 +4021,8 @@ Branch: REL9_4_STABLE [4f33572ee] 2015-10-20 11:06:24 -0700 <listitem> <para> - Translation of minus-infinity dates and timestamps to <type>json</> - or <type>jsonb</> incorrectly rendered them as plus-infinity (Tom Lane) + Translation of minus-infinity dates and timestamps to <type>json</type> + or <type>jsonb</type> incorrectly rendered them as plus-infinity (Tom Lane) </para> </listitem> @@ -3802,7 +4038,7 @@ Branch: REL9_1_STABLE [728a2ac21] 2015-11-17 15:47:12 -0500 <listitem> <para> - Fix possible internal overflow in <type>numeric</> division + Fix possible internal overflow in <type>numeric</type> division (Dean Rasheed) </para> </listitem> @@ -3894,7 +4130,7 @@ Branch: REL9_1_STABLE [b94c2b6a6] 2015-10-16 15:36:17 -0400 <para> This causes the code to emit <quote>regular expression is too - complex</> errors in some cases that previously used unreasonable + complex</quote> errors in some cases that previously used unreasonable amounts of time and memory. </para> </listitem> @@ -3929,14 +4165,14 @@ Branch: REL9_1_STABLE [b00c79b5b] 2015-10-16 14:43:18 -0400 <listitem> <para> - Make <literal>%h</> and <literal>%r</> escapes - in <varname>log_line_prefix</> work for messages emitted due - to <varname>log_connections</> (Tom Lane) + Make <literal>%h</literal> and <literal>%r</literal> escapes + in <varname>log_line_prefix</varname> work for messages emitted due + to <varname>log_connections</varname> (Tom Lane) </para> <para> - Previously, <literal>%h</>/<literal>%r</> started to work just after a - new session had emitted the <quote>connection received</> log message; + Previously, <literal>%h</literal>/<literal>%r</literal> started to work just after a + new session had emitted the <quote>connection received</quote> log message; now they work for that message too. </para> </listitem> @@ -3959,7 +4195,7 @@ Branch: REL9_1_STABLE [b0d858359] 2015-10-13 11:21:33 -0400 <para> This oversight resulted in failure to recover from crashes - whenever <varname>logging_collector</> is turned on. + whenever <varname>logging_collector</varname> is turned on. </para> </listitem> @@ -4009,13 +4245,13 @@ Branch: REL9_1_STABLE [db462a44e] 2015-12-17 16:55:51 -0500 <listitem> <para> - In <application>psql</>, ensure that <application>libreadline</>'s idea + In <application>psql</application>, ensure that <application>libreadline</application>'s idea of the screen size is updated when the terminal window size changes (Merlin Moncure) </para> <para> - Previously, <application>libreadline</> did not notice if the window + Previously, <application>libreadline</application> did not notice if the window was resized during query output, leading to strange behavior during later input of multiline queries. </para> @@ -4023,8 +4259,8 @@ Branch: REL9_1_STABLE [db462a44e] 2015-12-17 16:55:51 -0500 <listitem> <para> - Fix <application>psql</>'s <literal>\det</> command to interpret its - pattern argument the same way as other <literal>\d</> commands with + Fix <application>psql</application>'s <literal>\det</literal> command to interpret its + pattern argument the same way as other <literal>\d</literal> commands with potentially schema-qualified patterns do (Reece Hart) </para> </listitem> @@ -4041,7 +4277,7 @@ Branch: REL9_1_STABLE [6430a11fa] 2015-11-25 17:31:54 -0500 <listitem> <para> - Avoid possible crash in <application>psql</>'s <literal>\c</> command + Avoid possible crash in <application>psql</application>'s <literal>\c</literal> command when previous connection was via Unix socket and command specifies a new hostname and same username (Tom Lane) </para> @@ -4059,21 +4295,21 @@ Branch: REL9_1_STABLE [c869a7d5b] 2015-10-12 18:30:37 -0400 <listitem> <para> - In <literal>pg_ctl start -w</>, test child process status directly + In <literal>pg_ctl start -w</literal>, test child process status directly rather than relying on heuristics (Tom Lane, Michael Paquier) </para> <para> - Previously, <application>pg_ctl</> relied on an assumption that the new - postmaster would always create <filename>postmaster.pid</> within five + Previously, <application>pg_ctl</application> relied on an assumption that the new + postmaster would always create <filename>postmaster.pid</filename> within five seconds. But that can fail on heavily-loaded systems, - causing <application>pg_ctl</> to report incorrectly that the + causing <application>pg_ctl</application> to report incorrectly that the postmaster failed to start. </para> <para> Except on Windows, this change also means that a <literal>pg_ctl start - -w</> done immediately after another such command will now reliably + -w</literal> done immediately after another such command will now reliably fail, whereas previously it would report success if done within two seconds of the first command. </para> @@ -4091,23 +4327,23 @@ Branch: REL9_1_STABLE [87deb55a4] 2015-11-08 17:31:24 -0500 <listitem> <para> - In <literal>pg_ctl start -w</>, don't attempt to use a wildcard listen + In <literal>pg_ctl start -w</literal>, don't attempt to use a wildcard listen address to connect to the postmaster (Kondo Yuta) </para> <para> - On Windows, <application>pg_ctl</> would fail to detect postmaster - startup if <varname>listen_addresses</> is set to <literal>0.0.0.0</> - or <literal>::</>, because it would try to use that value verbatim as + On Windows, <application>pg_ctl</application> would fail to detect postmaster + startup if <varname>listen_addresses</varname> is set to <literal>0.0.0.0</literal> + or <literal>::</literal>, because it would try to use that value verbatim as the address to connect to, which doesn't work. Instead assume - that <literal>127.0.0.1</> or <literal>::1</>, respectively, is the + that <literal>127.0.0.1</literal> or <literal>::1</literal>, respectively, is the right thing to use. </para> </listitem> <listitem> <para> - In <application>pg_ctl</> on Windows, check service status to decide + In <application>pg_ctl</application> on Windows, check service status to decide where to send output, rather than checking if standard output is a terminal (Michael Paquier) </para> @@ -4127,18 +4363,18 @@ Branch: REL9_1_STABLE [6df62ef43] 2015-11-23 00:32:01 -0500 <listitem> <para> - In <application>pg_dump</> and <application>pg_basebackup</>, adopt + In <application>pg_dump</application> and <application>pg_basebackup</application>, adopt the GNU convention for handling tar-archive members exceeding 8GB (Tom Lane) </para> <para> - The POSIX standard for <literal>tar</> file format does not allow + The POSIX standard for <literal>tar</literal> file format does not allow archive member files to exceed 8GB, but most modern implementations - of <application>tar</> support an extension that fixes that. Adopt - this extension so that <application>pg_dump</> with <option>-Ft</> no + of <application>tar</application> support an extension that fixes that. Adopt + this extension so that <application>pg_dump</application> with <option>-Ft</option> no longer fails on tables with more than 8GB of data, and so - that <application>pg_basebackup</> can handle files larger than 8GB. + that <application>pg_basebackup</application> can handle files larger than 8GB. In addition, fix some portability issues that could cause failures for members between 4GB and 8GB on some platforms. Potentially these problems could cause unrecoverable data loss due to unreadable backup @@ -4148,16 +4384,16 @@ Branch: REL9_1_STABLE [6df62ef43] 2015-11-23 00:32:01 -0500 <listitem> <para> - Fix assorted corner-case bugs in <application>pg_dump</>'s processing + Fix assorted corner-case bugs in <application>pg_dump</application>'s processing of extension member objects (Tom Lane) </para> </listitem> <listitem> <para> - Make <application>pg_dump</> mark a view's triggers as needing to be + Make <application>pg_dump</application> mark a view's triggers as needing to be processed after its rule, to prevent possible failure during - parallel <application>pg_restore</> (Tom Lane) + parallel <application>pg_restore</application> (Tom Lane) </para> </listitem> @@ -4180,14 +4416,14 @@ Branch: REL9_1_STABLE [e4959fb5c] 2016-01-02 19:04:45 -0500 <listitem> <para> Ensure that relation option values are properly quoted - in <application>pg_dump</> (Kouhei Sutou, Tom Lane) + in <application>pg_dump</application> (Kouhei Sutou, Tom Lane) </para> <para> A reloption value that isn't a simple identifier or number could lead to dump/reload failures due to syntax errors in CREATE statements - issued by <application>pg_dump</>. This is not an issue with any - reloption currently supported by core <productname>PostgreSQL</>, but + issued by <application>pg_dump</application>. This is not an issue with any + reloption currently supported by core <productname>PostgreSQL</productname>, but extensions could allow reloptions that cause the problem. </para> </listitem> @@ -4202,7 +4438,7 @@ Branch: REL9_3_STABLE [534a4159c] 2015-12-23 14:25:31 -0500 <listitem> <para> - Avoid repeated password prompts during parallel <application>pg_dump</> + Avoid repeated password prompts during parallel <application>pg_dump</application> (Zeus Kronion) </para> </listitem> @@ -4225,14 +4461,14 @@ Branch: REL9_1_STABLE [c36064e43] 2015-11-24 17:18:27 -0500 <listitem> <para> - Fix <application>pg_upgrade</>'s file-copying code to handle errors + Fix <application>pg_upgrade</application>'s file-copying code to handle errors properly on Windows (Bruce Momjian) </para> </listitem> <listitem> <para> - Install guards in <application>pgbench</> against corner-case overflow + Install guards in <application>pgbench</application> against corner-case overflow conditions during evaluation of script-specified division or modulo operators (Fabien Coelho, Michael Paquier) </para> @@ -4250,22 +4486,22 @@ Branch: REL9_2_STABLE [4fb9e6109] 2015-12-28 10:50:35 -0300 <listitem> <para> Fix failure to localize messages emitted - by <application>pg_receivexlog</> and <application>pg_recvlogical</> + by <application>pg_receivexlog</application> and <application>pg_recvlogical</application> (Ioseph Kim) </para> </listitem> <listitem> <para> - Avoid dump/reload problems when using both <application>plpython2</> - and <application>plpython3</> (Tom Lane) + Avoid dump/reload problems when using both <application>plpython2</application> + and <application>plpython3</application> (Tom Lane) </para> <para> - In principle, both versions of <application>PL/Python</> can be used in + In principle, both versions of <application>PL/Python</application> can be used in the same database, though not in the same session (because the two - versions of <application>libpython</> cannot safely be used concurrently). - However, <application>pg_restore</> and <application>pg_upgrade</> both + versions of <application>libpython</application> cannot safely be used concurrently). + However, <application>pg_restore</application> and <application>pg_upgrade</application> both do things that can fall foul of the same-session restriction. Work around that by changing the timing of the check. </para> @@ -4273,7 +4509,7 @@ Branch: REL9_2_STABLE [4fb9e6109] 2015-12-28 10:50:35 -0300 <listitem> <para> - Fix <application>PL/Python</> regression tests to pass with Python 3.5 + Fix <application>PL/Python</application> regression tests to pass with Python 3.5 (Peter Eisentraut) </para> </listitem> @@ -4288,29 +4524,29 @@ Branch: REL9_3_STABLE [db6e8e162] 2015-11-12 13:03:53 -0500 <listitem> <para> - Fix premature clearing of <application>libpq</>'s input buffer when + Fix premature clearing of <application>libpq</application>'s input buffer when socket EOF is seen (Tom Lane) </para> <para> - This mistake caused <application>libpq</> to sometimes not report the + This mistake caused <application>libpq</application> to sometimes not report the backend's final error message before reporting <quote>server closed the - connection unexpectedly</>. + connection unexpectedly</quote>. </para> </listitem> <listitem> <para> - Prevent certain <application>PL/Java</> parameters from being set by + Prevent certain <application>PL/Java</application> parameters from being set by non-superusers (Noah Misch) </para> <para> - This change mitigates a <application>PL/Java</> security bug - (CVE-2016-0766), which was fixed in <application>PL/Java</> by marking + This change mitigates a <application>PL/Java</application> security bug + (CVE-2016-0766), which was fixed in <application>PL/Java</application> by marking these parameters as superuser-only. To fix the security hazard for - sites that update <productname>PostgreSQL</> more frequently - than <application>PL/Java</>, make the core code aware of them also. + sites that update <productname>PostgreSQL</productname> more frequently + than <application>PL/Java</application>, make the core code aware of them also. </para> </listitem> @@ -4326,7 +4562,7 @@ Branch: REL9_1_STABLE [4b58ded74] 2015-12-14 18:48:49 +0200 <listitem> <para> - Improve <application>libpq</>'s handling of out-of-memory situations + Improve <application>libpq</application>'s handling of out-of-memory situations (Michael Paquier, Amit Kapila, Heikki Linnakangas) </para> </listitem> @@ -4343,7 +4579,7 @@ Branch: REL9_1_STABLE [a9bcd8370] 2015-10-18 10:17:12 +0200 <listitem> <para> Fix order of arguments - in <application>ecpg</>-generated <literal>typedef</> statements + in <application>ecpg</application>-generated <literal>typedef</literal> statements (Michael Meskes) </para> </listitem> @@ -4360,29 +4596,29 @@ Branch: REL9_1_STABLE [84387496f] 2015-12-01 11:42:52 -0500 <listitem> <para> - Use <literal>%g</> not <literal>%f</> format - in <application>ecpg</>'s <function>PGTYPESnumeric_from_double()</> + Use <literal>%g</literal> not <literal>%f</literal> format + in <application>ecpg</application>'s <function>PGTYPESnumeric_from_double()</function> (Tom Lane) </para> </listitem> <listitem> <para> - Fix <application>ecpg</>-supplied header files to not contain comments + Fix <application>ecpg</application>-supplied header files to not contain comments continued from a preprocessor directive line onto the next line (Michael Meskes) </para> <para> - Such a comment is rejected by <application>ecpg</>. It's not yet clear - whether <application>ecpg</> itself should be changed. + Such a comment is rejected by <application>ecpg</application>. It's not yet clear + whether <application>ecpg</application> itself should be changed. </para> </listitem> <listitem> <para> - Fix <function>hstore_to_json_loose()</>'s test for whether - an <type>hstore</> value can be converted to a JSON number (Tom Lane) + Fix <function>hstore_to_json_loose()</function>'s test for whether + an <type>hstore</type> value can be converted to a JSON number (Tom Lane) </para> <para> @@ -4403,15 +4639,15 @@ Branch: REL9_1_STABLE [1b6102eb7] 2015-12-27 13:03:19 -0300 <listitem> <para> - Ensure that <filename>contrib/pgcrypto</>'s <function>crypt()</> + Ensure that <filename>contrib/pgcrypto</filename>'s <function>crypt()</function> function can be interrupted by query cancel (Andreas Karlsson) </para> </listitem> <listitem> <para> - In <filename>contrib/postgres_fdw</>, fix bugs triggered by use - of <literal>tableoid</> in data-modifying commands (Etsuro Fujita, + In <filename>contrib/postgres_fdw</filename>, fix bugs triggered by use + of <literal>tableoid</literal> in data-modifying commands (Etsuro Fujita, Robert Haas) </para> </listitem> @@ -4433,7 +4669,7 @@ Branch: REL9_2_STABLE [7f94a5c10] 2015-12-10 10:19:31 -0500 <listitem> <para> - Accept <application>flex</> versions later than 2.5.x + Accept <application>flex</application> versions later than 2.5.x (Tom Lane, Michael Paquier) </para> @@ -4467,19 +4703,19 @@ Branch: REL9_1_STABLE [2a37a103b] 2015-12-11 16:14:48 -0500 <listitem> <para> - Install our <filename>missing</> script where PGXS builds can find it + Install our <filename>missing</filename> script where PGXS builds can find it (Jim Nasby) </para> <para> This allows sane behavior in a PGXS build done on a machine where build - tools such as <application>bison</> are missing. + tools such as <application>bison</application> are missing. </para> </listitem> <listitem> <para> - Ensure that <filename>dynloader.h</> is included in the installed + Ensure that <filename>dynloader.h</filename> is included in the installed header files in MSVC builds (Bruce Momjian, Michael Paquier) </para> </listitem> @@ -4497,11 +4733,11 @@ Branch: REL9_1_STABLE [386dcd539] 2015-12-11 19:08:40 -0500 <listitem> <para> Add variant regression test expected-output file to match behavior of - current <application>libxml2</> (Tom Lane) + current <application>libxml2</application> (Tom Lane) </para> <para> - The fix for <application>libxml2</>'s CVE-2015-7499 causes it not to + The fix for <application>libxml2</application>'s CVE-2015-7499 causes it not to output error context reports in some cases where it used to do so. This seems to be a bug, but we'll probably have to live with it for some time, so work around it. @@ -4510,7 +4746,7 @@ Branch: REL9_1_STABLE [386dcd539] 2015-12-11 19:08:40 -0500 <listitem> <para> - Update time zone data files to <application>tzdata</> release 2016a for + Update time zone data files to <application>tzdata</application> release 2016a for DST law changes in Cayman Islands, Metlakatla, and Trans-Baikal Territory (Zabaykalsky Krai), plus historical corrections for Pakistan. </para> @@ -4563,13 +4799,13 @@ Branch: REL9_3_STABLE [f8862172e] 2015-10-05 10:06:34 -0400 <listitem> <para> - Guard against stack overflows in <type>json</> parsing + Guard against stack overflows in <type>json</type> parsing (Oskari Saarenmaa) </para> <para> - If an application constructs PostgreSQL <type>json</> - or <type>jsonb</> values from arbitrary user input, the application's + If an application constructs PostgreSQL <type>json</type> + or <type>jsonb</type> values from arbitrary user input, the application's users can reliably crash the PostgreSQL server, causing momentary denial of service. (CVE-2015-5289) </para> @@ -4588,8 +4824,8 @@ Branch: REL9_0_STABLE [188e081ef] 2015-10-05 10:06:36 -0400 <listitem> <para> - Fix <filename>contrib/pgcrypto</> to detect and report - too-short <function>crypt()</> salts (Josh Kupershmidt) + Fix <filename>contrib/pgcrypto</filename> to detect and report + too-short <function>crypt()</function> salts (Josh Kupershmidt) </para> <para> @@ -4634,7 +4870,7 @@ Branch: REL9_4_STABLE [bab959906] 2015-08-02 20:09:05 +0300 <listitem> <para> Fix possible deadlock during WAL insertion - when <varname>commit_delay</> is set (Heikki Linnakangas) + when <varname>commit_delay</varname> is set (Heikki Linnakangas) </para> </listitem> @@ -4665,13 +4901,13 @@ Branch: REL9_0_STABLE [45c69178b] 2015-06-25 14:39:06 -0400 <listitem> <para> - Fix insertion of relations into the relation cache <quote>init file</> + Fix insertion of relations into the relation cache <quote>init file</quote> (Tom Lane) </para> <para> An oversight in a patch in the most recent minor releases - caused <structname>pg_trigger_tgrelid_tgname_index</> to be omitted + caused <structname>pg_trigger_tgrelid_tgname_index</structname> to be omitted from the init file. Subsequent sessions detected this, then deemed the init file to be broken and silently ignored it, resulting in a significant degradation in session startup time. In addition to fixing @@ -4711,7 +4947,7 @@ Branch: REL9_0_STABLE [2d4336cf8] 2015-09-30 23:32:23 -0400 <listitem> <para> - Improve <command>LISTEN</> startup time when there are many unread + Improve <command>LISTEN</command> startup time when there are many unread notifications (Matt Newell) </para> </listitem> @@ -4731,7 +4967,7 @@ Branch: REL9_3_STABLE [1bcc9e60a] 2015-09-25 13:16:31 -0400 </para> <para> - This was seen primarily when restoring <application>pg_dump</> output + This was seen primarily when restoring <application>pg_dump</application> output for databases with many thousands of tables. </para> </listitem> @@ -4755,7 +4991,7 @@ Branch: REL9_0_STABLE [444b2ebee] 2015-07-28 22:06:32 +0200 too many bugs in practice, both in the underlying OpenSSL library and in our usage of it. Renegotiation will be removed entirely in 9.5 and later. In the older branches, just change the default value - of <varname>ssl_renegotiation_limit</> to zero (disabled). + of <varname>ssl_renegotiation_limit</varname> to zero (disabled). </para> </listitem> @@ -4779,7 +5015,7 @@ Branch: REL9_0_STABLE [eeb0b7830] 2015-10-05 11:57:25 +0200 <listitem> <para> - Lower the minimum values of the <literal>*_freeze_max_age</> parameters + Lower the minimum values of the <literal>*_freeze_max_age</literal> parameters (Andres Freund) </para> @@ -4802,7 +5038,7 @@ Branch: REL9_0_STABLE [b09446ed7] 2015-08-04 13:12:03 -0400 <listitem> <para> - Limit the maximum value of <varname>wal_buffers</> to 2GB to avoid + Limit the maximum value of <varname>wal_buffers</varname> to 2GB to avoid server crashes (Josh Berkus) </para> </listitem> @@ -4816,8 +5052,8 @@ Branch: REL9_3_STABLE [5a56c2545] 2015-06-28 18:38:06 -0400 <listitem> <para> Avoid logging complaints when a parameter that can only be set at - server start appears multiple times in <filename>postgresql.conf</>, - and fix counting of line numbers after an <literal>include_dir</> + server start appears multiple times in <filename>postgresql.conf</filename>, + and fix counting of line numbers after an <literal>include_dir</literal> directive (Tom Lane) </para> </listitem> @@ -4835,7 +5071,7 @@ Branch: REL9_0_STABLE [a89781e34] 2015-09-21 12:12:16 -0400 <listitem> <para> - Fix rare internal overflow in multiplication of <type>numeric</> values + Fix rare internal overflow in multiplication of <type>numeric</type> values (Dean Rasheed) </para> </listitem> @@ -4862,8 +5098,8 @@ Branch: REL9_2_STABLE [8dacb29ca] 2015-10-05 10:06:35 -0400 <listitem> <para> Guard against hard-to-reach stack overflows involving record types, - range types, <type>json</>, <type>jsonb</>, <type>tsquery</>, - <type>ltxtquery</> and <type>query_int</> (Noah Misch) + range types, <type>json</type>, <type>jsonb</type>, <type>tsquery</type>, + <type>ltxtquery</type> and <type>query_int</type> (Noah Misch) </para> </listitem> @@ -4887,14 +5123,14 @@ Branch: REL9_0_STABLE [92d956f51] 2015-09-07 20:47:06 +0100 <listitem> <para> - Fix handling of <literal>DOW</> and <literal>DOY</> in datetime input + Fix handling of <literal>DOW</literal> and <literal>DOY</literal> in datetime input (Greg Stark) </para> <para> These tokens aren't meant to be used in datetime values, but previously they resulted in opaque internal error messages rather - than <quote>invalid input syntax</>. + than <quote>invalid input syntax</quote>. </para> </listitem> @@ -4936,7 +5172,7 @@ Branch: REL9_0_STABLE [b875ca09f] 2015-10-02 15:00:52 -0400 <listitem> <para> Add recursion depth protections to regular expression, <literal>SIMILAR - TO</>, and <literal>LIKE</> matching (Tom Lane) + TO</literal>, and <literal>LIKE</literal> matching (Tom Lane) </para> <para> @@ -5052,8 +5288,8 @@ Branch: REL9_0_STABLE [bd327627f] 2015-08-04 18:18:47 -0400 <listitem> <para> - Fix <quote>unexpected out-of-memory situation during sort</> errors - when using tuplestores with small <varname>work_mem</> settings (Tom + Fix <quote>unexpected out-of-memory situation during sort</quote> errors + when using tuplestores with small <varname>work_mem</varname> settings (Tom Lane) </para> </listitem> @@ -5071,7 +5307,7 @@ Branch: REL9_0_STABLE [36522d627] 2015-07-16 22:57:46 -0400 <listitem> <para> - Fix very-low-probability stack overrun in <function>qsort</> (Tom Lane) + Fix very-low-probability stack overrun in <function>qsort</function> (Tom Lane) </para> </listitem> @@ -5093,8 +5329,8 @@ Branch: REL9_0_STABLE [d637a899c] 2015-10-04 15:55:07 -0400 <listitem> <para> - Fix <quote>invalid memory alloc request size</> failure in hash joins - with large <varname>work_mem</> settings (Tomas Vondra, Tom Lane) + Fix <quote>invalid memory alloc request size</quote> failure in hash joins + with large <varname>work_mem</varname> settings (Tomas Vondra, Tom Lane) </para> </listitem> @@ -5172,9 +5408,9 @@ Branch: REL9_0_STABLE [7b4b57fc4] 2015-08-12 21:19:10 -0400 These mistakes could lead to incorrect query plans that would give wrong answers, or to assertion failures in assert-enabled builds, or to odd planner errors such as <quote>could not devise a query plan for the - given query</>, <quote>could not find pathkey item to - sort</>, <quote>plan should not reference subplan's variable</>, - or <quote>failed to assign all NestLoopParams to plan nodes</>. + given query</quote>, <quote>could not find pathkey item to + sort</quote>, <quote>plan should not reference subplan's variable</quote>, + or <quote>failed to assign all NestLoopParams to plan nodes</quote>. Thanks are due to Andreas Seltenreich and Piotr Stefaniak for fuzz testing that exposed these problems. </para> @@ -5190,7 +5426,7 @@ Branch: REL9_2_STABLE [e538e510e] 2015-06-22 18:53:27 -0400 <listitem> <para> - Improve planner's performance for <command>UPDATE</>/<command>DELETE</> + Improve planner's performance for <command>UPDATE</command>/<command>DELETE</command> on large inheritance sets (Tom Lane, Dean Rasheed) </para> </listitem> @@ -5232,12 +5468,12 @@ Branch: REL9_0_STABLE [8b53c087d] 2015-08-02 14:54:44 -0400 <para> During postmaster shutdown, ensure that per-socket lock files are removed and listen sockets are closed before we remove - the <filename>postmaster.pid</> file (Tom Lane) + the <filename>postmaster.pid</filename> file (Tom Lane) </para> <para> This avoids race-condition failures if an external script attempts to - start a new postmaster as soon as <literal>pg_ctl stop</> returns. + start a new postmaster as soon as <literal>pg_ctl stop</literal> returns. </para> </listitem> @@ -5311,7 +5547,7 @@ Branch: REL9_0_STABLE [f527c0a2a] 2015-07-28 17:34:00 -0400 <listitem> <para> - Do not print a <literal>WARNING</> when an autovacuum worker is already + Do not print a <literal>WARNING</literal> when an autovacuum worker is already gone when we attempt to signal it, and reduce log verbosity for such signals (Tom Lane) </para> @@ -5389,7 +5625,7 @@ Branch: REL9_2_STABLE [f4297f8c5] 2015-07-27 12:32:48 +0300 </para> <para> - <command>VACUUM</> attempted to recycle such pages, but did so in a + <command>VACUUM</command> attempted to recycle such pages, but did so in a way that wasn't crash-safe. </para> </listitem> @@ -5408,7 +5644,7 @@ Branch: REL9_0_STABLE [40ad78220] 2015-07-23 01:30:19 +0300 <listitem> <para> Fix off-by-one error that led to otherwise-harmless warnings - about <quote>apparent wraparound</> in subtrans/multixact truncation + about <quote>apparent wraparound</quote> in subtrans/multixact truncation (Thomas Munro) </para> </listitem> @@ -5426,8 +5662,8 @@ Branch: REL9_0_STABLE [e41718fa1] 2015-08-18 19:22:38 -0400 <listitem> <para> - Fix misreporting of <command>CONTINUE</> and <command>MOVE</> statement - types in <application>PL/pgSQL</>'s error context messages + Fix misreporting of <command>CONTINUE</command> and <command>MOVE</command> statement + types in <application>PL/pgSQL</application>'s error context messages (Pavel Stehule, Tom Lane) </para> </listitem> @@ -5444,7 +5680,7 @@ Branch: REL9_1_STABLE [ca6c2f863] 2015-09-29 10:52:22 -0400 <listitem> <para> - Fix <application>PL/Perl</> to handle non-<acronym>ASCII</> error + Fix <application>PL/Perl</application> to handle non-<acronym>ASCII</acronym> error message texts correctly (Alex Hunsaker) </para> </listitem> @@ -5467,8 +5703,8 @@ Branch: REL9_1_STABLE [1d190d095] 2015-08-21 12:21:37 -0400 <listitem> <para> - Fix <application>PL/Python</> crash when returning the string - representation of a <type>record</> result (Tom Lane) + Fix <application>PL/Python</application> crash when returning the string + representation of a <type>record</type> result (Tom Lane) </para> </listitem> @@ -5485,8 +5721,8 @@ Branch: REL9_0_STABLE [4c11967e7] 2015-07-20 14:18:08 +0200 <listitem> <para> - Fix some places in <application>PL/Tcl</> that neglected to check for - failure of <function>malloc()</> calls (Michael Paquier, Álvaro + Fix some places in <application>PL/Tcl</application> that neglected to check for + failure of <function>malloc()</function> calls (Michael Paquier, Álvaro Herrera) </para> </listitem> @@ -5503,7 +5739,7 @@ Branch: REL9_1_STABLE [2d19a0e97] 2015-08-02 22:12:51 +0300 <listitem> <para> - In <filename>contrib/isn</>, fix output of ISBN-13 numbers that begin + In <filename>contrib/isn</filename>, fix output of ISBN-13 numbers that begin with 979 (Fabien Coelho) </para> @@ -5522,7 +5758,7 @@ Branch: REL9_4_STABLE [93840f96c] 2015-10-04 17:58:30 -0400 <listitem> <para> - Improve <filename>contrib/pg_stat_statements</>' handling of + Improve <filename>contrib/pg_stat_statements</filename>' handling of query-text garbage collection (Peter Geoghegan) </para> @@ -5543,13 +5779,13 @@ Branch: REL9_3_STABLE [b7dcb2dd4] 2015-09-24 12:47:30 -0400 <listitem> <para> - Improve <filename>contrib/postgres_fdw</>'s handling of + Improve <filename>contrib/postgres_fdw</filename>'s handling of collation-related decisions (Tom Lane) </para> <para> The main user-visible effect is expected to be that comparisons - involving <type>varchar</> columns will be sent to the remote server + involving <type>varchar</type> columns will be sent to the remote server for execution in more cases than before. </para> </listitem> @@ -5567,7 +5803,7 @@ Branch: REL9_0_STABLE [2b189c7ec] 2015-07-07 18:45:31 +0300 <listitem> <para> - Improve <application>libpq</>'s handling of out-of-memory conditions + Improve <application>libpq</application>'s handling of out-of-memory conditions (Michael Paquier, Heikki Linnakangas) </para> </listitem> @@ -5603,7 +5839,7 @@ Branch: REL9_0_STABLE [d278ff3b2] 2015-06-15 14:27:39 +0200 <listitem> <para> Fix memory leaks and missing out-of-memory checks - in <application>ecpg</> (Michael Paquier) + in <application>ecpg</application> (Michael Paquier) </para> </listitem> @@ -5634,15 +5870,15 @@ Branch: REL9_0_STABLE [98d8c75f9] 2015-09-25 12:20:46 -0400 <listitem> <para> - Fix <application>psql</>'s code for locale-aware formatting of numeric + Fix <application>psql</application>'s code for locale-aware formatting of numeric output (Tom Lane) </para> <para> - The formatting code invoked by <literal>\pset numericlocale on</> + The formatting code invoked by <literal>\pset numericlocale on</literal> did the wrong thing for some uncommon cases such as numbers with an exponent but no decimal point. It could also mangle already-localized - output from the <type>money</> data type. + output from the <type>money</type> data type. </para> </listitem> @@ -5659,7 +5895,7 @@ Branch: REL9_0_STABLE [6087bf1a1] 2015-07-08 20:44:27 -0400 <listitem> <para> - Prevent crash in <application>psql</>'s <command>\c</> command when + Prevent crash in <application>psql</application>'s <command>\c</command> command when there is no current connection (Noah Misch) </para> </listitem> @@ -5675,7 +5911,7 @@ Branch: REL9_2_STABLE [3756c65a0] 2015-10-01 16:19:49 -0400 <listitem> <para> - Make <application>pg_dump</> handle inherited <literal>NOT VALID</> + Make <application>pg_dump</application> handle inherited <literal>NOT VALID</literal> check constraints correctly (Tom Lane) </para> </listitem> @@ -5692,8 +5928,8 @@ Branch: REL9_1_STABLE [af225551e] 2015-07-25 17:16:39 -0400 <listitem> <para> - Fix selection of default <application>zlib</> compression level - in <application>pg_dump</>'s directory output format (Andrew Dunstan) + Fix selection of default <application>zlib</application> compression level + in <application>pg_dump</application>'s directory output format (Andrew Dunstan) </para> </listitem> @@ -5710,8 +5946,8 @@ Branch: REL9_0_STABLE [24aed2124] 2015-09-20 20:44:34 -0400 <listitem> <para> - Ensure that temporary files created during a <application>pg_dump</> - run with <acronym>tar</>-format output are not world-readable (Michael + Ensure that temporary files created during a <application>pg_dump</application> + run with <acronym>tar</acronym>-format output are not world-readable (Michael Paquier) </para> </listitem> @@ -5729,8 +5965,8 @@ Branch: REL9_0_STABLE [52b07779d] 2015-09-11 15:51:10 -0400 <listitem> <para> - Fix <application>pg_dump</> and <application>pg_upgrade</> to support - cases where the <literal>postgres</> or <literal>template1</> database + Fix <application>pg_dump</application> and <application>pg_upgrade</application> to support + cases where the <literal>postgres</literal> or <literal>template1</literal> database is in a non-default tablespace (Marti Raudsepp, Bruce Momjian) </para> </listitem> @@ -5748,7 +5984,7 @@ Branch: REL9_0_STABLE [298d1f808] 2015-08-10 20:10:16 -0400 <listitem> <para> - Fix <application>pg_dump</> to handle object privileges sanely when + Fix <application>pg_dump</application> to handle object privileges sanely when dumping from a server too old to have a particular privilege type (Tom Lane) </para> @@ -5756,11 +5992,11 @@ Branch: REL9_0_STABLE [298d1f808] 2015-08-10 20:10:16 -0400 <para> When dumping data types from pre-9.2 servers, and when dumping functions or procedural languages from pre-7.3 - servers, <application>pg_dump</> would - produce <command>GRANT</>/<command>REVOKE</> commands that revoked the + servers, <application>pg_dump</application> would + produce <command>GRANT</command>/<command>REVOKE</command> commands that revoked the owner's grantable privileges and instead granted all privileges - to <literal>PUBLIC</>. Since the privileges involved are - just <literal>USAGE</> and <literal>EXECUTE</>, this isn't a security + to <literal>PUBLIC</literal>. Since the privileges involved are + just <literal>USAGE</literal> and <literal>EXECUTE</literal>, this isn't a security problem, but it's certainly a surprising representation of the older systems' behavior. Fix it to leave the default privilege state alone in these cases. @@ -5780,12 +6016,12 @@ Branch: REL9_0_STABLE [5d175be17] 2015-08-04 19:34:12 -0400 <listitem> <para> - Fix <application>pg_dump</> to dump shell types (Tom Lane) + Fix <application>pg_dump</application> to dump shell types (Tom Lane) </para> <para> Shell types (that is, not-yet-fully-defined types) aren't useful for - much, but nonetheless <application>pg_dump</> should dump them. + much, but nonetheless <application>pg_dump</application> should dump them. </para> </listitem> @@ -5801,7 +6037,7 @@ Branch: REL9_1_STABLE [e9a859b54] 2015-07-12 16:25:52 -0400 <listitem> <para> - Fix assorted minor memory leaks in <application>pg_dump</> and other + Fix assorted minor memory leaks in <application>pg_dump</application> and other client-side programs (Michael Paquier) </para> </listitem> @@ -5815,8 +6051,8 @@ Branch: REL9_4_STABLE [9d6352aaa] 2015-07-03 11:15:27 +0300 <listitem> <para> - Fix <application>pgbench</>'s progress-report behavior when a query, - or <application>pgbench</> itself, gets stuck (Fabien Coelho) + Fix <application>pgbench</application>'s progress-report behavior when a query, + or <application>pgbench</application> itself, gets stuck (Fabien Coelho) </para> </listitem> @@ -5845,11 +6081,11 @@ Branch: REL9_0_STABLE [b5a22d8bb] 2015-08-29 16:09:25 -0400 <listitem> <para> Fix spinlock assembly code for PPC hardware to be compatible - with <acronym>AIX</>'s native assembler (Tom Lane) + with <acronym>AIX</acronym>'s native assembler (Tom Lane) </para> <para> - Building with <application>gcc</> didn't work if <application>gcc</> + Building with <application>gcc</application> didn't work if <application>gcc</application> had been configured to use the native assembler, which is becoming more common. </para> @@ -5868,7 +6104,7 @@ Branch: REL9_0_STABLE [cdf596b1c] 2015-07-17 03:02:46 -0400 <listitem> <para> - On <acronym>AIX</>, test the <literal>-qlonglong</> compiler option + On <acronym>AIX</acronym>, test the <literal>-qlonglong</literal> compiler option rather than just assuming it's safe to use (Noah Misch) </para> </listitem> @@ -5886,7 +6122,7 @@ Branch: REL9_0_STABLE [7803d5720] 2015-07-15 21:00:31 -0400 <listitem> <para> - On <acronym>AIX</>, use <literal>-Wl,-brtllib</> link option to allow + On <acronym>AIX</acronym>, use <literal>-Wl,-brtllib</literal> link option to allow symbols to be resolved at runtime (Noah Misch) </para> @@ -5909,7 +6145,7 @@ Branch: REL9_0_STABLE [2d8c136e7] 2015-07-29 22:54:08 -0400 <listitem> <para> Avoid use of inline functions when compiling with - 32-bit <application>xlc</>, due to compiler bugs (Noah Misch) + 32-bit <application>xlc</application>, due to compiler bugs (Noah Misch) </para> </listitem> @@ -5925,7 +6161,7 @@ Branch: REL9_0_STABLE [b185c42c1] 2015-06-30 14:20:37 -0300 <listitem> <para> - Use <filename>librt</> for <function>sched_yield()</> when necessary, + Use <filename>librt</filename> for <function>sched_yield()</function> when necessary, which it is on some Solaris versions (Oskari Saarenmaa) </para> </listitem> @@ -5939,7 +6175,7 @@ Branch: REL9_4_STABLE [a0104e080] 2015-08-14 20:23:42 -0400 <listitem> <para> - Translate encoding <literal>UHC</> as Windows code page 949 + Translate encoding <literal>UHC</literal> as Windows code page 949 (Noah Misch) </para> @@ -5972,12 +6208,12 @@ Branch: REL9_4_STABLE [b2ed1682d] 2015-06-20 12:10:56 -0400 <listitem> <para> Fix postmaster startup failure due to not - copying <function>setlocale()</>'s return value (Noah Misch) + copying <function>setlocale()</function>'s return value (Noah Misch) </para> <para> This has been reported on Windows systems with the ANSI code page set - to CP936 (<quote>Chinese (Simplified, PRC)</>), and may occur with + to CP936 (<quote>Chinese (Simplified, PRC)</quote>), and may occur with other multibyte code pages. </para> </listitem> @@ -5995,7 +6231,7 @@ Branch: REL9_0_STABLE [341b877d3] 2015-07-07 16:39:25 +0300 <listitem> <para> - Fix Windows <filename>install.bat</> script to handle target directory + Fix Windows <filename>install.bat</filename> script to handle target directory names that contain spaces (Heikki Linnakangas) </para> </listitem> @@ -6013,9 +6249,9 @@ Branch: REL9_0_STABLE [29ff43adf] 2015-07-05 12:01:02 -0400 <listitem> <para> - Make the numeric form of the <productname>PostgreSQL</> version number - (e.g., <literal>90405</>) readily available to extension Makefiles, - as a variable named <varname>VERSION_NUM</> (Michael Paquier) + Make the numeric form of the <productname>PostgreSQL</productname> version number + (e.g., <literal>90405</literal>) readily available to extension Makefiles, + as a variable named <varname>VERSION_NUM</varname> (Michael Paquier) </para> </listitem> @@ -6032,10 +6268,10 @@ Branch: REL9_0_STABLE [47ac95f37] 2015-10-02 19:16:37 -0400 <listitem> <para> - Update time zone data files to <application>tzdata</> release 2015g for + Update time zone data files to <application>tzdata</application> release 2015g for DST law changes in Cayman Islands, Fiji, Moldova, Morocco, Norfolk Island, North Korea, Turkey, and Uruguay. There is a new zone name - <literal>America/Fort_Nelson</> for the Canadian Northern Rockies. + <literal>America/Fort_Nelson</literal> for the Canadian Northern Rockies. </para> </listitem> @@ -6067,7 +6303,7 @@ Branch: REL9_0_STABLE [47ac95f37] 2015-10-02 19:16:37 -0400 <para> However, if you are upgrading an installation that was previously - upgraded using a <application>pg_upgrade</> version between 9.3.0 and + upgraded using a <application>pg_upgrade</application> version between 9.3.0 and 9.3.4 inclusive, see the first changelog entry below. </para> @@ -6096,46 +6332,46 @@ Branch: REL9_3_STABLE [2a9b01928] 2015-06-05 09:34:15 -0400 </para> <para> - Recent <productname>PostgreSQL</> releases introduced mechanisms to + Recent <productname>PostgreSQL</productname> releases introduced mechanisms to protect against multixact wraparound, but some of that code did not account for the possibility that it would need to run during crash recovery, when the database may not be in a consistent state. This could result in failure to restart after a crash, or failure to start up a secondary server. The lingering effects of a previously-fixed - bug in <application>pg_upgrade</> could also cause such a failure, in - installations that had used <application>pg_upgrade</> versions + bug in <application>pg_upgrade</application> could also cause such a failure, in + installations that had used <application>pg_upgrade</application> versions between 9.3.0 and 9.3.4. </para> <para> - The <application>pg_upgrade</> bug in question was that it would - set <literal>oldestMultiXid</> to 1 in <filename>pg_control</> even + The <application>pg_upgrade</application> bug in question was that it would + set <literal>oldestMultiXid</literal> to 1 in <filename>pg_control</filename> even if the true value should be higher. With the fixes introduced in this release, such a situation will result in immediate emergency - autovacuuming until a correct <literal>oldestMultiXid</> value can + autovacuuming until a correct <literal>oldestMultiXid</literal> value can be determined. If that would pose a hardship, users can avoid it by - doing manual vacuuming <emphasis>before</> upgrading to this release. + doing manual vacuuming <emphasis>before</emphasis> upgrading to this release. In detail: <orderedlist> <listitem> <para> - Check whether <application>pg_controldata</> reports <quote>Latest - checkpoint's oldestMultiXid</> to be 1. If not, there's nothing + Check whether <application>pg_controldata</application> reports <quote>Latest + checkpoint's oldestMultiXid</quote> to be 1. If not, there's nothing to do. </para> </listitem> <listitem> <para> - Look in <filename>PGDATA/pg_multixact/offsets</> to see if there's a - file named <filename>0000</>. If there is, there's nothing to do. + Look in <filename>PGDATA/pg_multixact/offsets</filename> to see if there's a + file named <filename>0000</filename>. If there is, there's nothing to do. </para> </listitem> <listitem> <para> Otherwise, for each table that has - <structname>pg_class</>.<structfield>relminmxid</> equal to 1, - <command>VACUUM</> that table with + <structname>pg_class</structname>.<structfield>relminmxid</structfield> equal to 1, + <command>VACUUM</command> that table with both <xref linkend="guc-vacuum-multixact-freeze-min-age"> and <xref linkend="guc-vacuum-multixact-freeze-table-age"> set to zero. (You can use the vacuum cost delay parameters described @@ -6164,7 +6400,7 @@ Branch: REL9_0_STABLE [2fe1939b0] 2015-06-07 15:32:09 -0400 <para> With just the wrong timing of concurrent activity, a <command>VACUUM - FULL</> on a system catalog might fail to update the <quote>init file</> + FULL</command> on a system catalog might fail to update the <quote>init file</quote> that's used to avoid cache-loading work for new sessions. This would result in later sessions being unable to access that catalog at all. This is a very ancient bug, but it's so hard to trigger that no @@ -6185,13 +6421,13 @@ Branch: REL9_0_STABLE [dbd99c7f0] 2015-06-05 13:22:27 -0400 <listitem> <para> Avoid deadlock between incoming sessions and <literal>CREATE/DROP - DATABASE</> (Tom Lane) + DATABASE</literal> (Tom Lane) </para> <para> A new session starting in a database that is the target of - a <command>DROP DATABASE</> command, or is the template for - a <command>CREATE DATABASE</> command, could cause the command to wait + a <command>DROP DATABASE</command> command, or is the template for + a <command>CREATE DATABASE</command> command, could cause the command to wait for five seconds and then fail, even if the new session would have exited before that. </para> @@ -6284,12 +6520,12 @@ Branch: REL9_3_STABLE [c2b68b1f7] 2015-05-29 17:02:58 -0400 <listitem> <para> - Avoid failures while <function>fsync</>'ing data directory during + Avoid failures while <function>fsync</function>'ing data directory during crash restart (Abhijit Menon-Sen, Tom Lane) </para> <para> - In the previous minor releases we added a patch to <function>fsync</> + In the previous minor releases we added a patch to <function>fsync</function> everything in the data directory after a crash. Unfortunately its response to any error condition was to fail, thereby preventing the server from starting up, even when the problem was quite harmless. @@ -6301,7 +6537,7 @@ Branch: REL9_3_STABLE [c2b68b1f7] 2015-05-29 17:02:58 -0400 </para> <para> - Also apply the same rules in <literal>initdb --sync-only</>. + Also apply the same rules in <literal>initdb --sync-only</literal>. This case is less critical but it should act similarly. </para> </listitem> @@ -6316,8 +6552,8 @@ Branch: REL9_2_STABLE [f3c67aad4] 2015-05-28 11:24:37 -0400 <listitem> <para> - Fix <function>pg_get_functiondef()</> to show - functions' <literal>LEAKPROOF</> property, if set (Jeevan Chalke) + Fix <function>pg_get_functiondef()</function> to show + functions' <literal>LEAKPROOF</literal> property, if set (Jeevan Chalke) </para> </listitem> @@ -6329,7 +6565,7 @@ Branch: REL9_4_STABLE [9b74f32cd] 2015-05-22 10:31:29 -0400 <listitem> <para> - Fix <function>pushJsonbValue()</> to unpack <type>jbvBinary</> + Fix <function>pushJsonbValue()</function> to unpack <type>jbvBinary</type> objects (Andrew Dunstan) </para> @@ -6351,14 +6587,14 @@ Branch: REL9_0_STABLE [b06649b7f] 2015-05-26 22:15:00 -0400 <listitem> <para> - Remove <application>configure</>'s check prohibiting linking to a - threaded <application>libpython</> - on <systemitem class="osname">OpenBSD</> (Tom Lane) + Remove <application>configure</application>'s check prohibiting linking to a + threaded <application>libpython</application> + on <systemitem class="osname">OpenBSD</systemitem> (Tom Lane) </para> <para> The failure this restriction was meant to prevent seems to not be a - problem anymore on current <systemitem class="osname">OpenBSD</> + problem anymore on current <systemitem class="osname">OpenBSD</systemitem> versions. </para> </listitem> @@ -6390,8 +6626,8 @@ Branch: REL9_0_STABLE [b06649b7f] 2015-05-26 22:15:00 -0400 </para> <para> - However, if you use <filename>contrib/citext</>'s - <function>regexp_matches()</> functions, see the changelog entry below + However, if you use <filename>contrib/citext</filename>'s + <function>regexp_matches()</function> functions, see the changelog entry below about that. </para> @@ -6469,7 +6705,7 @@ Branch: REL9_0_STABLE [cf893530a] 2015-05-19 18:18:56 -0400 </para> <para> - Our replacement implementation of <function>snprintf()</> failed to + Our replacement implementation of <function>snprintf()</function> failed to check for errors reported by the underlying system library calls; the main case that might be missed is out-of-memory situations. In the worst case this might lead to information exposure, due to our @@ -6479,7 +6715,7 @@ Branch: REL9_0_STABLE [cf893530a] 2015-05-19 18:18:56 -0400 </para> <para> - It remains possible that some calls of the <function>*printf()</> + It remains possible that some calls of the <function>*printf()</function> family of functions are vulnerable to information disclosure if an out-of-memory error occurs at just the wrong time. We judge the risk to not be large, but will continue analysis in this area. @@ -6499,15 +6735,15 @@ Branch: REL9_0_STABLE [b84e5c017] 2015-05-18 10:02:39 -0400 <listitem> <para> - In <filename>contrib/pgcrypto</>, uniformly report decryption failures - as <quote>Wrong key or corrupt data</> (Noah Misch) + In <filename>contrib/pgcrypto</filename>, uniformly report decryption failures + as <quote>Wrong key or corrupt data</quote> (Noah Misch) </para> <para> Previously, some cases of decryption with an incorrect key could report other error message texts. It has been shown that such variance in error reports can aid attackers in recovering keys from other systems. - While it's unknown whether <filename>pgcrypto</>'s specific behaviors + While it's unknown whether <filename>pgcrypto</filename>'s specific behaviors are likewise exploitable, it seems better to avoid the risk by using a one-size-fits-all message. (CVE-2015-3167) @@ -6557,7 +6793,7 @@ Branch: REL9_3_STABLE [ddebd2119] 2015-05-11 12:16:51 -0400 <para> Under certain usage patterns, the existing defenses against this might - be insufficient, allowing <filename>pg_multixact/members</> files to be + be insufficient, allowing <filename>pg_multixact/members</filename> files to be removed too early, resulting in data loss. The fix for this includes modifying the server to fail transactions that would result in overwriting old multixact member ID data, and @@ -6578,16 +6814,16 @@ Branch: REL9_1_STABLE [801e250a8] 2015-05-05 15:50:53 -0400 <listitem> <para> - Fix incorrect declaration of <filename>contrib/citext</>'s - <function>regexp_matches()</> functions (Tom Lane) + Fix incorrect declaration of <filename>contrib/citext</filename>'s + <function>regexp_matches()</function> functions (Tom Lane) </para> <para> - These functions should return <type>setof text[]</>, like the core + These functions should return <type>setof text[]</type>, like the core functions they are wrappers for; but they were incorrectly declared as - returning just <type>text[]</>. This mistake had two results: first, + returning just <type>text[]</type>. This mistake had two results: first, if there was no match you got a scalar null result, whereas what you - should get is an empty set (zero rows). Second, the <literal>g</> flag + should get is an empty set (zero rows). Second, the <literal>g</literal> flag was effectively ignored, since you would get only one result array even if there were multiple matches. </para> @@ -6595,16 +6831,16 @@ Branch: REL9_1_STABLE [801e250a8] 2015-05-05 15:50:53 -0400 <para> While the latter behavior is clearly a bug, there might be applications depending on the former behavior; therefore the function declarations - will not be changed by default until <productname>PostgreSQL</> 9.5. + will not be changed by default until <productname>PostgreSQL</productname> 9.5. In pre-9.5 branches, the old behavior exists in version 1.0 of - the <literal>citext</> extension, while we have provided corrected - declarations in version 1.1 (which is <emphasis>not</> installed by + the <literal>citext</literal> extension, while we have provided corrected + declarations in version 1.1 (which is <emphasis>not</emphasis> installed by default). To adopt the fix in pre-9.5 branches, execute - <literal>ALTER EXTENSION citext UPDATE TO '1.1'</> in each database in - which <literal>citext</> is installed. (You can also <quote>update</> + <literal>ALTER EXTENSION citext UPDATE TO '1.1'</literal> in each database in + which <literal>citext</literal> is installed. (You can also <quote>update</quote> back to 1.0 if you need to undo that.) Be aware that either update direction will require dropping and recreating any views or rules that - use <filename>citext</>'s <function>regexp_matches()</> functions. + use <filename>citext</filename>'s <function>regexp_matches()</function> functions. </para> </listitem> @@ -6616,8 +6852,8 @@ Branch: REL9_4_STABLE [79afe6e66] 2015-02-26 12:34:43 -0500 <listitem> <para> - Render infinite dates and timestamps as <literal>infinity</> when - converting to <type>json</>, rather than throwing an error + Render infinite dates and timestamps as <literal>infinity</literal> when + converting to <type>json</type>, rather than throwing an error (Andrew Dunstan) </para> </listitem> @@ -6630,8 +6866,8 @@ Branch: REL9_4_STABLE [997066f44] 2015-05-04 12:43:16 -0400 <listitem> <para> - Fix <type>json</>/<type>jsonb</>'s <function>populate_record()</> - and <function>to_record()</> functions to handle empty input properly + Fix <type>json</type>/<type>jsonb</type>'s <function>populate_record()</function> + and <function>to_record()</function> functions to handle empty input properly (Andrew Dunstan) </para> </listitem> @@ -6671,7 +6907,7 @@ Branch: REL9_4_STABLE [79edb2981] 2015-05-03 11:30:24 -0400 <listitem> <para> Fix behavior when changing foreign key constraint deferrability status - with <literal>ALTER TABLE ... ALTER CONSTRAINT</> (Tom Lane) + with <literal>ALTER TABLE ... ALTER CONSTRAINT</literal> (Tom Lane) </para> <para> @@ -6720,7 +6956,7 @@ Branch: REL9_0_STABLE [985da346e] 2015-04-25 16:44:27 -0400 <para> This oversight in the planner has been observed to cause <quote>could - not find RelOptInfo for given relids</> errors, but it seems possible + not find RelOptInfo for given relids</quote> errors, but it seems possible that sometimes an incorrect query plan might get past that consistency check and result in silently-wrong query output. </para> @@ -6768,7 +7004,7 @@ Branch: REL9_0_STABLE [72bbca27e] 2015-02-10 20:37:31 -0500 <para> This oversight has been seen to lead to <quote>failed to join all - relations together</> errors in queries involving <literal>LATERAL</>, + relations together</quote> errors in queries involving <literal>LATERAL</literal>, and that might happen in other cases as well. </para> </listitem> @@ -6782,7 +7018,7 @@ Branch: REL9_4_STABLE [f16270ade] 2015-02-25 21:36:40 -0500 <listitem> <para> Ensure that row locking occurs properly when the target of - an <command>UPDATE</> or <command>DELETE</> is a security-barrier view + an <command>UPDATE</command> or <command>DELETE</command> is a security-barrier view (Stephen Frost) </para> </listitem> @@ -6801,7 +7037,7 @@ Branch: REL9_4_STABLE [fd3dfc236] 2015-04-28 00:18:04 +0200 <para> On some platforms, the previous coding could result in errors like - <quote>could not fsync file "pg_replslot/...": Bad file descriptor</>. + <quote>could not fsync file "pg_replslot/...": Bad file descriptor</quote>. </para> </listitem> @@ -6818,7 +7054,7 @@ Branch: REL9_0_STABLE [223a94680] 2015-04-23 21:37:09 +0300 <listitem> <para> Fix possible deadlock at startup - when <literal>max_prepared_transactions</> is too small + when <literal>max_prepared_transactions</literal> is too small (Heikki Linnakangas) </para> </listitem> @@ -6859,7 +7095,7 @@ Branch: REL9_0_STABLE [262fbcb9d] 2015-05-05 09:30:07 -0400 <listitem> <para> - Recursively <function>fsync()</> the data directory after a crash + Recursively <function>fsync()</function> the data directory after a crash (Abhijit Menon-Sen, Robert Haas) </para> @@ -6901,7 +7137,7 @@ Branch: REL9_4_STABLE [ee0d06c0b] 2015-04-03 00:07:29 -0400 <para> This oversight could result in failures in sessions that start - concurrently with a <command>VACUUM FULL</> on a system catalog. + concurrently with a <command>VACUUM FULL</command> on a system catalog. </para> </listitem> @@ -6913,7 +7149,7 @@ Branch: REL9_4_STABLE [2897e069c] 2015-03-30 13:05:35 -0400 <listitem> <para> - Fix crash in <function>BackendIdGetTransactionIds()</> when trying + Fix crash in <function>BackendIdGetTransactionIds()</function> when trying to get status for a backend process that just exited (Tom Lane) </para> </listitem> @@ -6930,13 +7166,13 @@ Branch: REL9_0_STABLE [87b7fcc87] 2015-02-23 16:14:16 +0100 <listitem> <para> - Cope with unexpected signals in <function>LockBufferForCleanup()</> + Cope with unexpected signals in <function>LockBufferForCleanup()</function> (Andres Freund) </para> <para> This oversight could result in spurious errors about <quote>multiple - backends attempting to wait for pincount 1</>. + backends attempting to wait for pincount 1</quote>. </para> </listitem> @@ -6950,7 +7186,7 @@ Branch: REL9_2_STABLE [effcaa4c2] 2015-02-15 23:26:46 -0500 <listitem> <para> - Fix crash when doing <literal>COPY IN</> to a table with check + Fix crash when doing <literal>COPY IN</literal> to a table with check constraints that contain whole-row references (Tom Lane) </para> @@ -6995,7 +7231,7 @@ Branch: REL9_4_STABLE [16be9737c] 2015-03-23 16:52:17 +0100 <listitem> <para> - Avoid busy-waiting with short <literal>recovery_min_apply_delay</> + Avoid busy-waiting with short <literal>recovery_min_apply_delay</literal> values (Andres Freund) </para> </listitem> @@ -7061,9 +7297,9 @@ Branch: REL9_0_STABLE [152c94632] 2015-03-29 15:04:38 -0400 </para> <para> - <command>ANALYZE</> executes index expressions many times; if there are + <command>ANALYZE</command> executes index expressions many times; if there are slow functions in such an expression, it's desirable to be able to - cancel the <command>ANALYZE</> before that loop finishes. + cancel the <command>ANALYZE</command> before that loop finishes. </para> </listitem> @@ -7078,10 +7314,10 @@ Branch: REL9_1_STABLE [4a4fd2b0c] 2015-03-12 13:38:49 -0400 <listitem> <para> - Ensure <structfield>tableoid</> of a foreign table is reported - correctly when a <literal>READ COMMITTED</> recheck occurs after - locking rows in <command>SELECT FOR UPDATE</>, <command>UPDATE</>, - or <command>DELETE</> (Etsuro Fujita) + Ensure <structfield>tableoid</structfield> of a foreign table is reported + correctly when a <literal>READ COMMITTED</literal> recheck occurs after + locking rows in <command>SELECT FOR UPDATE</command>, <command>UPDATE</command>, + or <command>DELETE</command> (Etsuro Fujita) </para> </listitem> @@ -7127,14 +7363,14 @@ Branch: REL9_0_STABLE [c981e5999] 2015-05-08 19:40:15 -0400 <listitem> <para> - Recommend setting <literal>include_realm</> to 1 when using + Recommend setting <literal>include_realm</literal> to 1 when using Kerberos/GSSAPI/SSPI authentication (Stephen Frost) </para> <para> Without this, identically-named users from different realms cannot be distinguished. For the moment this is only a documentation change, but - it will become the default setting in <productname>PostgreSQL</> 9.5. + it will become the default setting in <productname>PostgreSQL</productname> 9.5. </para> </listitem> @@ -7157,7 +7393,7 @@ Branch: REL9_0_STABLE [e48ce4f33] 2015-02-17 12:49:18 -0500 <listitem> <para> - Remove code for matching IPv4 <filename>pg_hba.conf</> entries to + Remove code for matching IPv4 <filename>pg_hba.conf</filename> entries to IPv4-in-IPv6 addresses (Tom Lane) </para> @@ -7170,7 +7406,7 @@ Branch: REL9_0_STABLE [e48ce4f33] 2015-02-17 12:49:18 -0500 crashes on some systems, so let's just remove it rather than fix it. (Had we chosen to fix it, that would make for a subtle and potentially security-sensitive change in the effective meaning of - IPv4 <filename>pg_hba.conf</> entries, which does not seem like a good + IPv4 <filename>pg_hba.conf</filename> entries, which does not seem like a good thing to do in minor releases.) </para> </listitem> @@ -7197,7 +7433,7 @@ Branch: REL9_4_STABLE [a1f4ade01] 2015-04-02 14:39:18 -0400 <listitem> <para> After a database crash, don't restart background workers that are - marked <literal>BGW_NEVER_RESTART</> (Amit Khandekar) + marked <literal>BGW_NEVER_RESTART</literal> (Amit Khandekar) </para> </listitem> @@ -7212,13 +7448,13 @@ Branch: REL9_1_STABLE [0d36d9f2b] 2015-02-06 11:32:42 +0200 <listitem> <para> - Report WAL flush, not insert, position in <literal>IDENTIFY_SYSTEM</> + Report WAL flush, not insert, position in <literal>IDENTIFY_SYSTEM</literal> replication command (Heikki Linnakangas) </para> <para> This avoids a possible startup failure - in <application>pg_receivexlog</>. + in <application>pg_receivexlog</application>. </para> </listitem> @@ -7236,7 +7472,7 @@ Branch: REL9_0_STABLE [78ce2dc8e] 2015-05-07 15:10:01 +0200 <para> While shutting down service on Windows, periodically send status updates to the Service Control Manager to prevent it from killing the - service too soon; and ensure that <application>pg_ctl</> will wait for + service too soon; and ensure that <application>pg_ctl</application> will wait for shutdown (Krystian Bigaj) </para> </listitem> @@ -7253,7 +7489,7 @@ Branch: REL9_0_STABLE [8878eaaa8] 2015-02-23 13:32:53 +0200 <listitem> <para> - Reduce risk of network deadlock when using <application>libpq</>'s + Reduce risk of network deadlock when using <application>libpq</application>'s non-blocking mode (Heikki Linnakangas) </para> @@ -7262,12 +7498,12 @@ Branch: REL9_0_STABLE [8878eaaa8] 2015-02-23 13:32:53 +0200 buffer every so often, in case the server has sent enough response data to cause it to block on output. (A typical scenario is that the server is sending a stream of NOTICE messages during <literal>COPY FROM - STDIN</>.) This worked properly in the normal blocking mode, but not - so much in non-blocking mode. We've modified <application>libpq</> + STDIN</literal>.) This worked properly in the normal blocking mode, but not + so much in non-blocking mode. We've modified <application>libpq</application> to opportunistically drain input when it can, but a full defense against this problem requires application cooperation: the application should watch for socket read-ready as well as write-ready conditions, - and be sure to call <function>PQconsumeInput()</> upon read-ready. + and be sure to call <function>PQconsumeInput()</function> upon read-ready. </para> </listitem> @@ -7281,7 +7517,7 @@ Branch: REL9_2_STABLE [83c3115dd] 2015-02-21 12:59:43 -0500 <listitem> <para> - In <application>libpq</>, fix misparsing of empty values in URI + In <application>libpq</application>, fix misparsing of empty values in URI connection strings (Thomas Fanghaenel) </para> </listitem> @@ -7298,7 +7534,7 @@ Branch: REL9_0_STABLE [ce2fcc58e] 2015-02-11 11:30:11 +0100 <listitem> <para> - Fix array handling in <application>ecpg</> (Michael Meskes) + Fix array handling in <application>ecpg</application> (Michael Meskes) </para> </listitem> @@ -7314,8 +7550,8 @@ Branch: REL9_0_STABLE [557fcfae3] 2015-04-01 20:00:07 -0300 <listitem> <para> - Fix <application>psql</> to sanely handle URIs and conninfo strings as - the first parameter to <command>\connect</> + Fix <application>psql</application> to sanely handle URIs and conninfo strings as + the first parameter to <command>\connect</command> (David Fetter, Andrew Dunstan, Álvaro Herrera) </para> @@ -7338,17 +7574,17 @@ Branch: REL9_0_STABLE [396ef6fd8] 2015-03-14 13:43:26 -0400 <listitem> <para> - Suppress incorrect complaints from <application>psql</> on some - platforms that it failed to write <filename>~/.psql_history</> at exit + Suppress incorrect complaints from <application>psql</application> on some + platforms that it failed to write <filename>~/.psql_history</filename> at exit (Tom Lane) </para> <para> This misbehavior was caused by a workaround for a bug in very old - (pre-2006) versions of <application>libedit</>. We fixed it by + (pre-2006) versions of <application>libedit</application>. We fixed it by removing the workaround, which will cause a similar failure to appear - for anyone still using such versions of <application>libedit</>. - Recommendation: upgrade that library, or use <application>libreadline</>. + for anyone still using such versions of <application>libedit</application>. + Recommendation: upgrade that library, or use <application>libreadline</application>. </para> </listitem> @@ -7364,7 +7600,7 @@ Branch: REL9_0_STABLE [8e70f3c40] 2015-02-10 22:38:29 -0500 <listitem> <para> - Fix <application>pg_dump</>'s rule for deciding which casts are + Fix <application>pg_dump</application>'s rule for deciding which casts are system-provided casts that should not be dumped (Tom Lane) </para> </listitem> @@ -7380,8 +7616,8 @@ Branch: REL9_1_STABLE [b0d53b2e3] 2015-02-18 11:43:00 -0500 <listitem> <para> - In <application>pg_dump</>, fix failure to honor <literal>-Z</> - compression level option together with <literal>-Fd</> + In <application>pg_dump</application>, fix failure to honor <literal>-Z</literal> + compression level option together with <literal>-Fd</literal> (Michael Paquier) </para> </listitem> @@ -7397,7 +7633,7 @@ Branch: REL9_1_STABLE [dcb467b8e] 2015-03-02 14:12:43 -0500 <listitem> <para> - Make <application>pg_dump</> consider foreign key relationships + Make <application>pg_dump</application> consider foreign key relationships between extension configuration tables while choosing dump order (Gilles Darold, Michael Paquier, Stephen Frost) </para> @@ -7417,7 +7653,7 @@ Branch: REL9_3_STABLE [d645273cf] 2015-03-06 13:27:46 -0500 <listitem> <para> - Avoid possible <application>pg_dump</> failure when concurrent sessions + Avoid possible <application>pg_dump</application> failure when concurrent sessions are creating and dropping temporary functions (Tom Lane) </para> </listitem> @@ -7434,7 +7670,7 @@ Branch: REL9_0_STABLE [7a501bcbf] 2015-02-25 12:01:12 -0500 <listitem> <para> - Fix dumping of views that are just <literal>VALUES(...)</> but have + Fix dumping of views that are just <literal>VALUES(...)</literal> but have column aliases (Tom Lane) </para> </listitem> @@ -7448,7 +7684,7 @@ Branch: REL9_4_STABLE [70fac4844] 2015-05-01 13:03:23 -0400 <listitem> <para> Ensure that a view's replication identity is correctly set - to <literal>nothing</> during dump/restore (Marko Tiikkaja) + to <literal>nothing</literal> during dump/restore (Marko Tiikkaja) </para> <para> @@ -7472,7 +7708,7 @@ Branch: REL9_3_STABLE [4e9935979] 2015-05-16 15:16:28 -0400 <listitem> <para> - In <application>pg_upgrade</>, force timeline 1 in the new cluster + In <application>pg_upgrade</application>, force timeline 1 in the new cluster (Bruce Momjian) </para> @@ -7494,7 +7730,7 @@ Branch: REL9_0_STABLE [2194aa92b] 2015-05-16 00:10:03 -0400 <listitem> <para> - In <application>pg_upgrade</>, check for improperly non-connectable + In <application>pg_upgrade</application>, check for improperly non-connectable databases before proceeding (Bruce Momjian) </para> @@ -7512,8 +7748,8 @@ Branch: REL9_0_STABLE [4ae178f60] 2015-02-11 22:06:04 -0500 <listitem> <para> - In <application>pg_upgrade</>, quote directory paths - properly in the generated <literal>delete_old_cluster</> script + In <application>pg_upgrade</application>, quote directory paths + properly in the generated <literal>delete_old_cluster</literal> script (Bruce Momjian) </para> </listitem> @@ -7530,14 +7766,14 @@ Branch: REL9_0_STABLE [85dac37ee] 2015-02-11 21:02:06 -0500 <listitem> <para> - In <application>pg_upgrade</>, preserve database-level freezing info + In <application>pg_upgrade</application>, preserve database-level freezing info properly (Bruce Momjian) </para> <para> This oversight could cause missing-clog-file errors for tables within - the <literal>postgres</> and <literal>template1</> databases. + the <literal>postgres</literal> and <literal>template1</literal> databases. </para> </listitem> @@ -7553,7 +7789,7 @@ Branch: REL9_0_STABLE [bf22a8e58] 2015-03-30 17:18:10 -0400 <listitem> <para> - Run <application>pg_upgrade</> and <application>pg_resetxlog</> with + Run <application>pg_upgrade</application> and <application>pg_resetxlog</application> with restricted privileges on Windows, so that they don't fail when run by an administrator (Muhammad Asif Naeem) </para> @@ -7571,8 +7807,8 @@ Branch: REL9_1_STABLE [d7d294f59] 2015-02-17 11:08:40 -0500 <listitem> <para> - Improve handling of <function>readdir()</> failures when scanning - directories in <application>initdb</> and <application>pg_basebackup</> + Improve handling of <function>readdir()</function> failures when scanning + directories in <application>initdb</application> and <application>pg_basebackup</application> (Marco Nenciarini) </para> </listitem> @@ -7589,7 +7825,7 @@ Branch: REL9_0_STABLE [40b0c10b7] 2015-03-15 23:22:03 -0400 <listitem> <para> - Fix slow sorting algorithm in <filename>contrib/intarray</> (Tom Lane) + Fix slow sorting algorithm in <filename>contrib/intarray</filename> (Tom Lane) </para> </listitem> @@ -7637,7 +7873,7 @@ Branch: REL9_0_STABLE [3c3749a3b] 2015-05-15 19:36:20 -0400 <listitem> <para> - Update time zone data files to <application>tzdata</> release 2015d + Update time zone data files to <application>tzdata</application> release 2015d for DST law changes in Egypt, Mongolia, and Palestine, plus historical changes in Canada and Chile. Also adopt revised zone abbreviations for the America/Adak zone (HST/HDT not HAST/HADT). @@ -7672,12 +7908,12 @@ Branch: REL9_0_STABLE [3c3749a3b] 2015-05-15 19:36:20 -0400 <para> However, if you are a Windows user and are using the <quote>Norwegian - (Bokmål)</> locale, manual action is needed after the upgrade to - replace any <quote>Norwegian (Bokmål)_Norway</> - or <quote>norwegian-bokmal</> locale names stored - in <productname>PostgreSQL</> system catalogs with the plain-ASCII - alias <quote>Norwegian_Norway</>. For details see - <ulink url="http://wiki.postgresql.org/wiki/Changes_To_Norwegian_Locale"></> + (Bokmål)</quote> locale, manual action is needed after the upgrade to + replace any <quote>Norwegian (Bokmål)_Norway</quote> + or <quote>norwegian-bokmal</quote> locale names stored + in <productname>PostgreSQL</productname> system catalogs with the plain-ASCII + alias <quote>Norwegian_Norway</quote>. For details see + <ulink url="http://wiki.postgresql.org/wiki/Changes_To_Norwegian_Locale"></ulink> </para> </sect2> @@ -7705,15 +7941,15 @@ Branch: REL9_0_STABLE [56b970f2e] 2015-02-02 10:00:52 -0500 <listitem> <para> - Fix buffer overruns in <function>to_char()</> + Fix buffer overruns in <function>to_char()</function> (Bruce Momjian) </para> <para> - When <function>to_char()</> processes a numeric formatting template - calling for a large number of digits, <productname>PostgreSQL</> + When <function>to_char()</function> processes a numeric formatting template + calling for a large number of digits, <productname>PostgreSQL</productname> would read past the end of a buffer. When processing a crafted - timestamp formatting template, <productname>PostgreSQL</> would write + timestamp formatting template, <productname>PostgreSQL</productname> would write past the end of a buffer. Either case could crash the server. We have not ruled out the possibility of attacks that lead to privilege escalation, though they seem unlikely. @@ -7733,27 +7969,27 @@ Branch: REL9_0_STABLE [9e05c5063] 2015-02-02 10:00:52 -0500 <listitem> <para> - Fix buffer overrun in replacement <function>*printf()</> functions + Fix buffer overrun in replacement <function>*printf()</function> functions (Tom Lane) </para> <para> - <productname>PostgreSQL</> includes a replacement implementation - of <function>printf</> and related functions. This code will overrun + <productname>PostgreSQL</productname> includes a replacement implementation + of <function>printf</function> and related functions. This code will overrun a stack buffer when formatting a floating point number (conversion - specifiers <literal>e</>, <literal>E</>, <literal>f</>, <literal>F</>, - <literal>g</> or <literal>G</>) with requested precision greater than + specifiers <literal>e</literal>, <literal>E</literal>, <literal>f</literal>, <literal>F</literal>, + <literal>g</literal> or <literal>G</literal>) with requested precision greater than about 500. This will crash the server, and we have not ruled out the possibility of attacks that lead to privilege escalation. A database user can trigger such a buffer overrun through - the <function>to_char()</> SQL function. While that is the only - affected core <productname>PostgreSQL</> functionality, extension + the <function>to_char()</function> SQL function. While that is the only + affected core <productname>PostgreSQL</productname> functionality, extension modules that use printf-family functions may be at risk as well. </para> <para> - This issue primarily affects <productname>PostgreSQL</> on Windows. - <productname>PostgreSQL</> uses the system implementation of these + This issue primarily affects <productname>PostgreSQL</productname> on Windows. + <productname>PostgreSQL</productname> uses the system implementation of these functions where adequate, which it is on other modern platforms. (CVE-2015-0242) </para> @@ -7778,12 +8014,12 @@ Branch: REL9_0_STABLE [0a3ee8a5f] 2015-02-02 10:00:52 -0500 <listitem> <para> - Fix buffer overruns in <filename>contrib/pgcrypto</> + Fix buffer overruns in <filename>contrib/pgcrypto</filename> (Marko Tiikkaja, Noah Misch) </para> <para> - Errors in memory size tracking within the <filename>pgcrypto</> + Errors in memory size tracking within the <filename>pgcrypto</filename> module permitted stack buffer overruns and improper dependence on the contents of uninitialized memory. The buffer overrun cases can crash the server, and we have not ruled out the possibility of @@ -7844,7 +8080,7 @@ Branch: REL9_0_STABLE [3a2063369] 2015-01-28 12:33:29 -0500 <para> Some server error messages show the values of columns that violate a constraint, such as a unique constraint. If the user does not have - <literal>SELECT</> privilege on all columns of the table, this could + <literal>SELECT</literal> privilege on all columns of the table, this could mean exposing values that the user should not be able to see. Adjust the code so that values are displayed only when they came from the SQL command or could be selected by the user. @@ -7893,20 +8129,20 @@ Branch: REL9_2_STABLE [6bf343c6e] 2015-01-16 13:10:23 +0200 <listitem> <para> - Cope with the Windows locale named <quote>Norwegian (Bokmål)</> + Cope with the Windows locale named <quote>Norwegian (Bokmål)</quote> (Heikki Linnakangas) </para> <para> Non-ASCII locale names are problematic since it's not clear what encoding they should be represented in. Map the troublesome locale - name to a plain-ASCII alias, <quote>Norwegian_Norway</>. + name to a plain-ASCII alias, <quote>Norwegian_Norway</quote>. </para> <para> - 9.4.0 mapped the troublesome name to <quote>norwegian-bokmal</>, + 9.4.0 mapped the troublesome name to <quote>norwegian-bokmal</quote>, but that turns out not to work on all Windows configurations. - <quote>Norwegian_Norway</> is now recommended instead. + <quote>Norwegian_Norway</quote> is now recommended instead. </para> </listitem> @@ -7927,7 +8163,7 @@ Branch: REL9_0_STABLE [5308e085b] 2015-01-15 18:52:38 -0500 </para> <para> - In <literal>READ COMMITTED</> mode, queries that lock or update + In <literal>READ COMMITTED</literal> mode, queries that lock or update recently-updated rows could crash as a result of this bug. </para> </listitem> @@ -7956,8 +8192,8 @@ Branch: REL9_3_STABLE [54a8abc2b] 2015-01-04 15:48:29 -0300 <listitem> <para> Fix failure to wait when a transaction tries to acquire a <literal>FOR - NO KEY EXCLUSIVE</> tuple lock, while multiple other transactions - currently hold <literal>FOR SHARE</> locks (Álvaro Herrera) + NO KEY EXCLUSIVE</literal> tuple lock, while multiple other transactions + currently hold <literal>FOR SHARE</literal> locks (Álvaro Herrera) </para> </listitem> @@ -7970,7 +8206,7 @@ Branch: REL9_3_STABLE [939f0fb67] 2015-01-15 13:18:19 -0500 <listitem> <para> - Improve performance of <command>EXPLAIN</> with large range tables + Improve performance of <command>EXPLAIN</command> with large range tables (Tom Lane) </para> </listitem> @@ -7983,41 +8219,41 @@ Branch: REL9_4_STABLE [4cbf390d5] 2015-01-30 14:44:49 -0500 <listitem> <para> - Fix <type>jsonb</> Unicode escape processing, and in consequence - disallow <literal>\u0000</> (Tom Lane) + Fix <type>jsonb</type> Unicode escape processing, and in consequence + disallow <literal>\u0000</literal> (Tom Lane) </para> <para> - Previously, the JSON Unicode escape <literal>\u0000</> was accepted + Previously, the JSON Unicode escape <literal>\u0000</literal> was accepted and was stored as those six characters; but that is indistinguishable - from what is stored for the input <literal>\\u0000</>, resulting in + from what is stored for the input <literal>\\u0000</literal>, resulting in ambiguity. Moreover, in cases where de-escaped textual output is - expected, such as the <literal>->></> operator, the sequence was - printed as <literal>\u0000</>, which does not meet the expectation + expected, such as the <literal>->></literal> operator, the sequence was + printed as <literal>\u0000</literal>, which does not meet the expectation that JSON escaping would be removed. (Consistent behavior would - require emitting a zero byte, but <productname>PostgreSQL</> does not + require emitting a zero byte, but <productname>PostgreSQL</productname> does not support zero bytes embedded in text strings.) 9.4.0 included an ill-advised attempt to improve this situation by adjusting JSON output conversion rules; but of course that could not fix the fundamental ambiguity, and it turned out to break other usages of Unicode escape sequences. Revert that, and to avoid the core problem, - reject <literal>\u0000</> in <type>jsonb</> input. + reject <literal>\u0000</literal> in <type>jsonb</type> input. </para> <para> - If a <type>jsonb</> column contains a <literal>\u0000</> value stored + If a <type>jsonb</type> column contains a <literal>\u0000</literal> value stored with 9.4.0, it will henceforth read out as though it - were <literal>\\u0000</>, which is the other valid interpretation of + were <literal>\\u0000</literal>, which is the other valid interpretation of the data stored by 9.4.0 for this case. </para> <para> - The <type>json</> type did not have the storage-ambiguity problem, but + The <type>json</type> type did not have the storage-ambiguity problem, but it did have the problem of inconsistent de-escaped textual output. - Therefore <literal>\u0000</> will now also be rejected - in <type>json</> values when conversion to de-escaped form is + Therefore <literal>\u0000</literal> will now also be rejected + in <type>json</type> values when conversion to de-escaped form is required. This change does not break the ability to - store <literal>\u0000</> in <type>json</> columns so long as no + store <literal>\u0000</literal> in <type>json</type> columns so long as no processing is done on the values. This is exactly parallel to the cases in which non-ASCII Unicode escapes are allowed when the database encoding is not UTF8. @@ -8036,14 +8272,14 @@ Branch: REL9_0_STABLE [cebb3f032] 2015-01-17 22:37:32 -0500 <listitem> <para> - Fix namespace handling in <function>xpath()</> (Ali Akbar) + Fix namespace handling in <function>xpath()</function> (Ali Akbar) </para> <para> - Previously, the <type>xml</> value resulting from - an <function>xpath()</> call would not have namespace declarations if + Previously, the <type>xml</type> value resulting from + an <function>xpath()</function> call would not have namespace declarations if the namespace declarations were attached to an ancestor element in the - input <type>xml</> value, rather than to the specific element being + input <type>xml</type> value, rather than to the specific element being returned. Propagate the ancestral declaration so that the result is correct when considered in isolation. </para> @@ -8063,7 +8299,7 @@ Branch: REL9_3_STABLE [527ff8baf] 2015-01-30 12:30:43 -0500 </para> <para> - This patch fixes corner-case <quote>unexpected operator NNNN</> planner + This patch fixes corner-case <quote>unexpected operator NNNN</quote> planner errors, and improves the selectivity estimates for some other cases. </para> </listitem> @@ -8081,7 +8317,7 @@ Branch: REL9_4_STABLE [4e241f7cd] 2014-12-30 14:53:03 +0200 </para> <para> - 9.4.0 could fail with <quote>index row size exceeds maximum</> errors + 9.4.0 could fail with <quote>index row size exceeds maximum</quote> errors for data that previous versions would accept. </para> </listitem> @@ -8111,7 +8347,7 @@ Branch: REL9_1_STABLE [37e0f13f2] 2015-01-29 19:37:22 +0200 <listitem> <para> Fix possible crash when using - nonzero <varname>gin_fuzzy_search_limit</> (Heikki Linnakangas) + nonzero <varname>gin_fuzzy_search_limit</varname> (Heikki Linnakangas) </para> </listitem> @@ -8139,7 +8375,7 @@ Branch: REL9_4_STABLE [b337d9657] 2015-01-15 20:52:18 +0200 <listitem> <para> Fix incorrect replay of WAL parameter change records that report - changes in the <varname>wal_log_hints</> setting (Petr Jelinek) + changes in the <varname>wal_log_hints</varname> setting (Petr Jelinek) </para> </listitem> @@ -8155,7 +8391,7 @@ Branch: REL9_0_STABLE [a1a8d0249] 2015-01-19 23:01:46 -0500 <listitem> <para> - Change <quote>pgstat wait timeout</> warning message to be LOG level, + Change <quote>pgstat wait timeout</quote> warning message to be LOG level, and rephrase it to be more understandable (Tom Lane) </para> @@ -8164,7 +8400,7 @@ Branch: REL9_0_STABLE [a1a8d0249] 2015-01-19 23:01:46 -0500 case, but it occurs often enough on our slower buildfarm members to be a nuisance. Reduce it to LOG level, and expend a bit more effort on the wording: it now reads <quote>using stale statistics instead of - current ones because stats collector is not responding</>. + current ones because stats collector is not responding</quote>. </para> </listitem> @@ -8180,7 +8416,7 @@ Branch: REL9_0_STABLE [2e4946169] 2015-01-07 22:46:20 -0500 <listitem> <para> - Warn if macOS's <function>setlocale()</> starts an unwanted extra + Warn if macOS's <function>setlocale()</function> starts an unwanted extra thread inside the postmaster (Noah Misch) </para> </listitem> @@ -8193,18 +8429,18 @@ Branch: REL9_4_STABLE [733728ff3] 2015-01-11 12:35:47 -0500 <listitem> <para> - Fix <application>libpq</>'s behavior when <filename>/etc/passwd</> + Fix <application>libpq</application>'s behavior when <filename>/etc/passwd</filename> isn't readable (Tom Lane) </para> <para> - While doing <function>PQsetdbLogin()</>, <application>libpq</> + While doing <function>PQsetdbLogin()</function>, <application>libpq</application> attempts to ascertain the user's operating system name, which on most - Unix platforms involves reading <filename>/etc/passwd</>. As of 9.4, + Unix platforms involves reading <filename>/etc/passwd</filename>. As of 9.4, failure to do that was treated as a hard error. Restore the previous behavior, which was to fail only if the application does not provide a database role name to connect as. This supports operation in chroot - environments that lack an <filename>/etc/passwd</> file. + environments that lack an <filename>/etc/passwd</filename> file. </para> </listitem> @@ -8220,17 +8456,17 @@ Branch: REL9_0_STABLE [2600e4436] 2014-12-31 12:17:12 -0500 <listitem> <para> - Improve consistency of parsing of <application>psql</>'s special + Improve consistency of parsing of <application>psql</application>'s special variables (Tom Lane) </para> <para> - Allow variant spellings of <literal>on</> and <literal>off</> (such - as <literal>1</>/<literal>0</>) for <literal>ECHO_HIDDEN</> - and <literal>ON_ERROR_ROLLBACK</>. Report a warning for unrecognized - values for <literal>COMP_KEYWORD_CASE</>, <literal>ECHO</>, - <literal>ECHO_HIDDEN</>, <literal>HISTCONTROL</>, - <literal>ON_ERROR_ROLLBACK</>, and <literal>VERBOSITY</>. Recognize + Allow variant spellings of <literal>on</literal> and <literal>off</literal> (such + as <literal>1</literal>/<literal>0</literal>) for <literal>ECHO_HIDDEN</literal> + and <literal>ON_ERROR_ROLLBACK</literal>. Report a warning for unrecognized + values for <literal>COMP_KEYWORD_CASE</literal>, <literal>ECHO</literal>, + <literal>ECHO_HIDDEN</literal>, <literal>HISTCONTROL</literal>, + <literal>ON_ERROR_ROLLBACK</literal>, and <literal>VERBOSITY</literal>. Recognize all values for all these variables case-insensitively; previously there was a mishmash of case-sensitive and case-insensitive behaviors. </para> @@ -8245,7 +8481,7 @@ Branch: REL9_3_STABLE [bb1e2426b] 2015-01-05 19:27:09 -0500 <listitem> <para> - Fix <application>pg_dump</> to handle comments on event triggers + Fix <application>pg_dump</application> to handle comments on event triggers without failing (Tom Lane) </para> </listitem> @@ -8259,8 +8495,8 @@ Branch: REL9_3_STABLE [cc609c46f] 2015-01-30 09:01:36 -0600 <listitem> <para> - Allow parallel <application>pg_dump</> to - use <option>--serializable-deferrable</> (Kevin Grittner) + Allow parallel <application>pg_dump</application> to + use <option>--serializable-deferrable</option> (Kevin Grittner) </para> </listitem> @@ -8275,7 +8511,7 @@ Branch: REL9_1_STABLE [2a0bfa4d6] 2015-01-03 20:54:13 +0100 <listitem> <para> - Prevent WAL files created by <literal>pg_basebackup -x/-X</> from + Prevent WAL files created by <literal>pg_basebackup -x/-X</literal> from being archived again when the standby is promoted (Andres Freund) </para> </listitem> @@ -8293,12 +8529,12 @@ Branch: REL9_0_STABLE [dc9a506e6] 2015-01-29 20:18:46 -0500 <listitem> <para> Handle unexpected query results, especially NULLs, safely in - <filename>contrib/tablefunc</>'s <function>connectby()</> + <filename>contrib/tablefunc</filename>'s <function>connectby()</function> (Michael Paquier) </para> <para> - <function>connectby()</> previously crashed if it encountered a NULL + <function>connectby()</function> previously crashed if it encountered a NULL key value. It now prints that row but doesn't recurse further. </para> </listitem> @@ -8392,14 +8628,14 @@ Branch: REL9_4_STABLE [adb355106] 2015-01-14 11:08:17 -0500 <listitem> <para> - Allow <varname>CFLAGS</> from <application>configure</>'s environment - to override automatically-supplied <varname>CFLAGS</> (Tom Lane) + Allow <varname>CFLAGS</varname> from <application>configure</application>'s environment + to override automatically-supplied <varname>CFLAGS</varname> (Tom Lane) </para> <para> - Previously, <application>configure</> would add any switches that it + Previously, <application>configure</application> would add any switches that it chose of its own accord to the end of the - user-specified <varname>CFLAGS</> string. Since most compilers + user-specified <varname>CFLAGS</varname> string. Since most compilers process switches left-to-right, this meant that configure's choices would override the user-specified flags in case of conflicts. That should work the other way around, so adjust the logic to put the @@ -8419,13 +8655,13 @@ Branch: REL9_0_STABLE [338ff75fc] 2015-01-19 23:44:33 -0500 <listitem> <para> - Make <application>pg_regress</> remove any temporary installation it + Make <application>pg_regress</application> remove any temporary installation it created upon successful exit (Tom Lane) </para> <para> This results in a very substantial reduction in disk space usage - during <literal>make check-world</>, since that sequence involves + during <literal>make check-world</literal>, since that sequence involves creation of numerous temporary installations. </para> </listitem> @@ -8451,7 +8687,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Update time zone data files to <application>tzdata</> release 2015a + Update time zone data files to <application>tzdata</application> release 2015a for DST law changes in Chile and Mexico, plus historical changes in Iceland. </para> @@ -8474,7 +8710,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <title>Overview</title> <para> - Major enhancements in <productname>PostgreSQL</> 9.4 include: + Major enhancements in <productname>PostgreSQL</productname> 9.4 include: </para> <!-- This list duplicates items below, but without authors or details--> @@ -8483,35 +8719,35 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add <link linkend="datatype-json"><type>jsonb</></link>, a more - capable and efficient data type for storing <acronym>JSON</> data + Add <link linkend="datatype-json"><type>jsonb</type></link>, a more + capable and efficient data type for storing <acronym>JSON</acronym> data </para> </listitem> <listitem> <para> - Add new <acronym>SQL</> command <xref linkend="SQL-ALTERSYSTEM"> - for changing <filename>postgresql.conf</> configuration file entries + Add new <acronym>SQL</acronym> command <xref linkend="sql-altersystem"> + for changing <filename>postgresql.conf</filename> configuration file entries </para> </listitem> <listitem> <para> - Reduce lock strength for some <xref linkend="SQL-ALTERTABLE"> + Reduce lock strength for some <xref linkend="sql-altertable"> commands </para> </listitem> <listitem> <para> - Allow <link linkend="rules-materializedviews">materialized views</> + Allow <link linkend="rules-materializedviews">materialized views</link> to be refreshed without blocking concurrent reads </para> </listitem> <listitem> <para> - Add support for <link linkend="logicaldecoding">logical decoding</> + Add support for <link linkend="logicaldecoding">logical decoding</link> of WAL data, to allow database changes to be streamed out in a customizable format </para> @@ -8519,7 +8755,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Allow <link linkend="bgworker">background worker processes</> + Allow <link linkend="bgworker">background worker processes</link> to be dynamically registered, started and terminated </para> </listitem> @@ -8558,14 +8794,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> Previously, an input array string that started with a single-element sub-array could later contain multi-element sub-arrays, - e.g. <literal>'{{1}, {2,3}}'::int[]</> would be accepted. + e.g. <literal>'{{1}, {2,3}}'::int[]</literal> would be accepted. </para> </listitem> <listitem> <para> - When converting values of type <type>date</>, <type>timestamp</> - or <type>timestamptz</> + When converting values of type <type>date</type>, <type>timestamp</type> + or <type>timestamptz</type> to <link linkend="datatype-json"><type>JSON</type></link>, render the values in a format compliant with ISO 8601 (Andrew Dunstan) </para> @@ -8575,7 +8811,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <xref linkend="guc-datestyle"> setting; but many JSON processors require timestamps to be in ISO 8601 format. If necessary, the previous behavior can be obtained by explicitly casting the datetime - value to <type>text</> before passing it to the JSON conversion + value to <type>text</type> before passing it to the JSON conversion function. </para> </listitem> @@ -8583,15 +8819,15 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> The <link linkend="functions-json-op-table"><type>json</type> - <literal>#></> <type>text[]</></link> path extraction operator now + <literal>#></literal> <type>text[]</type></link> path extraction operator now returns its lefthand input, not NULL, if the array is empty (Tom Lane) </para> <para> This is consistent with the notion that this represents zero applications of the simple field/element extraction - operator <literal>-></>. Similarly, <type>json</type> - <literal>#>></> <type>text[]</> with an empty array merely + operator <literal>-></literal>. Similarly, <type>json</type> + <literal>#>></literal> <type>text[]</type> with an empty array merely coerces its lefthand input to text. </para> </listitem> @@ -8616,26 +8852,26 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Cause consecutive whitespace in <link - linkend="functions-formatting-table"><function>to_timestamp()</></link> - and <function>to_date()</> format strings to consume a corresponding + linkend="functions-formatting-table"><function>to_timestamp()</function></link> + and <function>to_date()</function> format strings to consume a corresponding number of characters in the input string (whitespace or not), then - conditionally consume adjacent whitespace, if not in <literal>FX</> + conditionally consume adjacent whitespace, if not in <literal>FX</literal> mode (Jeevan Chalke) </para> <para> - Previously, consecutive whitespace characters in a non-<literal>FX</> + Previously, consecutive whitespace characters in a non-<literal>FX</literal> format string behaved like a single whitespace character and consumed all adjacent whitespace in the input string. For example, previously a format string of three spaces would consume only the first space in - <literal>' 12'</>, but it will now consume all three characters. + <literal>' 12'</literal>, but it will now consume all three characters. </para> </listitem> <listitem> <para> Fix <link - linkend="textsearch-functions-table"><function>ts_rank_cd()</></link> + linkend="textsearch-functions-table"><function>ts_rank_cd()</function></link> to ignore stripped lexemes (Alex Hill) </para> @@ -8649,15 +8885,15 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> For functions declared to take <link linkend="xfunc-sql-variadic-functions"><literal>VARIADIC - "any"</></link>, an actual parameter marked as <literal>VARIADIC</> + "any"</literal></link>, an actual parameter marked as <literal>VARIADIC</literal> must be of a determinable array type (Pavel Stehule) </para> <para> Such parameters can no longer be written as an undecorated string - literal or <literal>NULL</>; a cast to an appropriate array data type + literal or <literal>NULL</literal>; a cast to an appropriate array data type will now be required. Note that this does not affect parameters not - marked <literal>VARIADIC</>. + marked <literal>VARIADIC</literal>. </para> </listitem> @@ -8669,8 +8905,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </para> <para> - Constructs like <literal>row_to_json(tab.*)</> now always emit column - names that match the column aliases visible for table <literal>tab</> + Constructs like <literal>row_to_json(tab.*)</literal> now always emit column + names that match the column aliases visible for table <literal>tab</literal> at the point of the call. In previous releases the emitted column names would sometimes be the table's actual column names regardless of any aliases assigned in the query. @@ -8686,8 +8922,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Rename <link linkend="SQL-EXPLAIN"><command>EXPLAIN - ANALYZE</></link>'s <quote>total runtime</quote> output + Rename <link linkend="sql-explain"><command>EXPLAIN + ANALYZE</command></link>'s <quote>total runtime</quote> output to <quote>execution time</quote> (Tom Lane) </para> @@ -8699,15 +8935,15 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - <link linkend="SQL-SHOW"><command>SHOW TIME ZONE</></link> now - outputs simple numeric UTC offsets in <acronym>POSIX</> timezone + <link linkend="sql-show"><command>SHOW TIME ZONE</command></link> now + outputs simple numeric UTC offsets in <acronym>POSIX</acronym> timezone format (Tom Lane) </para> <para> Previously, such timezone settings were displayed as <link - linkend="datatype-interval-output"><type>interval</></link> values. - The new output is properly interpreted by <command>SET TIME ZONE</> + linkend="datatype-interval-output"><type>interval</type></link> values. + The new output is properly interpreted by <command>SET TIME ZONE</command> when passed as a simple string, whereas the old output required special treatment to be re-parsed correctly. </para> @@ -8716,25 +8952,25 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Foreign data wrappers that support updating foreign tables must - consider the possible presence of <literal>AFTER ROW</> triggers + consider the possible presence of <literal>AFTER ROW</literal> triggers (Noah Misch) </para> <para> - When an <literal>AFTER ROW</> trigger is present, all columns of the + When an <literal>AFTER ROW</literal> trigger is present, all columns of the table must be returned by updating actions, since the trigger might inspect any or all of them. Previously, foreign tables never had triggers, so the FDW might optimize away fetching columns not mentioned - in the <literal>RETURNING</> clause (if any). + in the <literal>RETURNING</literal> clause (if any). </para> </listitem> <listitem> <para> Prevent <link - linkend="ddl-constraints-check-constraints"><literal>CHECK</></link> + linkend="ddl-constraints-check-constraints"><literal>CHECK</literal></link> constraints from referencing system columns, except - <structfield>tableoid</> (Amit Kapila) + <structfield>tableoid</structfield> (Amit Kapila) </para> <para> @@ -8752,7 +8988,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> Previously, there was an undocumented precedence order among - the <literal>recovery_target_<replaceable>xxx</></literal> parameters. + the <literal>recovery_target_<replaceable>xxx</replaceable></literal> parameters. </para> </listitem> @@ -8766,14 +9002,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 User commands that did their own quote preservation might need adjustment. This is likely to be an issue for commands used in <xref linkend="guc-archive-command">, <xref linkend="restore-command">, - and <link linkend="sql-copy"><command>COPY TO/FROM PROGRAM</></link>. + and <link linkend="sql-copy"><command>COPY TO/FROM PROGRAM</command></link>. </para> </listitem> <listitem> <para> Remove catalog column <link - linkend="catalog-pg-class"><structfield>pg_class.reltoastidxid</></link> + linkend="catalog-pg-class"><structfield>pg_class.reltoastidxid</structfield></link> (Michael Paquier) </para> </listitem> @@ -8781,33 +9017,33 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Remove catalog column <link - linkend="catalog-pg-rewrite"><structfield>pg_rewrite.ev_attr</></link> + linkend="catalog-pg-rewrite"><structfield>pg_rewrite.ev_attr</structfield></link> (Kevin Grittner) </para> <para> Per-column rules have not been supported since - <application>PostgreSQL</> 7.3. + <application>PostgreSQL</application> 7.3. </para> </listitem> <listitem> <para> - Remove native support for <application>Kerberos</> authentication - (<option>--with-krb5</>, etc) + Remove native support for <application>Kerberos</application> authentication + (<option>--with-krb5</option>, etc) (Magnus Hagander) </para> <para> - The supported way to use <application>Kerberos</> authentication is - with <acronym>GSSAPI</>. The native code has been deprecated since - <productname>PostgreSQL</> 8.3. + The supported way to use <application>Kerberos</application> authentication is + with <acronym>GSSAPI</acronym>. The native code has been deprecated since + <productname>PostgreSQL</productname> 8.3. </para> </listitem> <listitem> <para> - In <application>PL/Python</>, handle domains over arrays like the + In <application>PL/Python</application>, handle domains over arrays like the underlying array type (Rodolfo Campero) </para> @@ -8819,9 +9055,9 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Make libpq's <link - linkend="libpq-pqconnectdbparams"><function>PQconnectdbParams()</></link> + linkend="libpq-pqconnectdbparams"><function>PQconnectdbParams()</function></link> and <link - linkend="libpq-pqpingparams"><function>PQpingParams()</></link> + linkend="libpq-pqpingparams"><function>PQpingParams()</function></link> functions process zero-length strings as defaults (Adrian Vondendriesch) </para> @@ -8841,20 +9077,20 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> Previously, empty arrays were returned as zero-length one-dimensional arrays, whose text representation looked the same as zero-dimensional - arrays (<literal>{}</>), but they acted differently in array - operations. <application>intarray</>'s behavior in this area now + arrays (<literal>{}</literal>), but they acted differently in array + operations. <application>intarray</application>'s behavior in this area now matches the built-in array operators. </para> </listitem> <listitem> <para> - <xref linkend="pgupgrade"> now uses <option>-U</> - or <option>--username</> to specify the user name (Bruce Momjian) + <xref linkend="pgupgrade"> now uses <option>-U</option> + or <option>--username</option> to specify the user name (Bruce Momjian) </para> <para> - Previously this option was spelled <option>-u</> or <option>--user</>, + Previously this option was spelled <option>-u</option> or <option>--user</option>, but that was inconsistent with other tools. </para> </listitem> @@ -8884,7 +9120,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </para> <para> - The new <filename>worker_spi</> module shows an example of use + The new <filename>worker_spi</filename> module shows an example of use of this feature. </para> </listitem> @@ -8904,7 +9140,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> During crash recovery or immediate shutdown, send uncatchable - termination signals (<systemitem>SIGKILL</>) to child processes + termination signals (<systemitem>SIGKILL</systemitem>) to child processes that do not shut down promptly (MauMau, Álvaro Herrera) </para> @@ -8912,7 +9148,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 This reduces the likelihood of leaving orphaned child processes behind after <xref linkend="app-postmaster"> shutdown, as well as ensuring that crash recovery can proceed if some child processes - have become <quote>stuck</>. + have become <quote>stuck</quote>. </para> </listitem> @@ -8924,7 +9160,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Make <xref linkend="SQL-VACUUM"> properly report dead but + Make <xref linkend="sql-vacuum"> properly report dead but not-yet-removable rows to the statistics collector (Hari Babu) </para> @@ -8942,14 +9178,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Reduce <link linkend="GIN"><acronym>GIN</></link> index size + Reduce <link linkend="gin"><acronym>GIN</acronym></link> index size (Alexander Korotkov, Heikki Linnakangas) </para> <para> Indexes upgraded via <xref linkend="pgupgrade"> will work fine - but will still be in the old, larger <acronym>GIN</> format. - Use <xref linkend="SQL-REINDEX"> to recreate old GIN indexes in the + but will still be in the old, larger <acronym>GIN</acronym> format. + Use <xref linkend="sql-reindex"> to recreate old GIN indexes in the new format. </para> </listitem> @@ -8957,16 +9193,16 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Improve speed of multi-key <link - linkend="GIN"><acronym>GIN</></link> lookups (Alexander Korotkov, + linkend="gin"><acronym>GIN</acronym></link> lookups (Alexander Korotkov, Heikki Linnakangas) </para> </listitem> <listitem> <para> - Add <link linkend="GiST"><acronym>GiST</></link> index support - for <link linkend="datatype-inet"><type>inet</></link> and - <link linkend="datatype-cidr"><type>cidr</></link> data types + Add <link linkend="gist"><acronym>GiST</acronym></link> index support + for <link linkend="datatype-inet"><type>inet</type></link> and + <link linkend="datatype-cidr"><type>cidr</type></link> data types (Emre Hasegeli) </para> @@ -9002,7 +9238,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Allow multiple backends to insert - into <link linkend="wal"><acronym>WAL</></link> buffers + into <link linkend="wal"><acronym>WAL</acronym></link> buffers concurrently (Heikki Linnakangas) </para> @@ -9014,7 +9250,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Conditionally write only the modified portion of updated rows to - <link linkend="wal"><acronym>WAL</></link> (Amit Kapila) + <link linkend="wal"><acronym>WAL</acronym></link> (Amit Kapila) </para> </listitem> @@ -9029,7 +9265,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Improve speed of aggregates that - use <link linkend="datatype-numeric"><type>numeric</></link> state + use <link linkend="datatype-numeric"><type>numeric</type></link> state values (Hadi Moshayedi) </para> </listitem> @@ -9038,8 +9274,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> Attempt to <link linkend="vacuum-for-wraparound">freeze</link> tuples when tables are rewritten with <xref - linkend="SQL-CLUSTER"> or <link - linkend="SQL-VACUUM"><command>VACUUM FULL</></link> (Robert Haas, + linkend="sql-cluster"> or <link + linkend="sql-vacuum"><command>VACUUM FULL</command></link> (Robert Haas, Andres Freund) </para> @@ -9050,8 +9286,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Improve speed of <xref linkend="SQL-COPY"> with default <link - linkend="functions-sequence-table"><function>nextval()</></link> + Improve speed of <xref linkend="sql-copy"> with default <link + linkend="functions-sequence-table"><function>nextval()</function></link> columns (Simon Riggs) </para> </listitem> @@ -9059,7 +9295,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Improve speed of accessing many different <link - linkend="SQL-CREATESEQUENCE">sequences</link> in the same session + linkend="sql-createsequence">sequences</link> in the same session (David Rowley) </para> </listitem> @@ -9073,26 +9309,26 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Reduce memory allocated by <application>PL/pgSQL</> - <xref linkend="SQL-DO"> blocks (Tom Lane) + Reduce memory allocated by <application>PL/pgSQL</application> + <xref linkend="sql-do"> blocks (Tom Lane) </para> </listitem> <listitem> <para> Make the planner more aggressive about extracting restriction clauses - from mixed <literal>AND</>/<literal>OR</> clauses (Tom Lane) + from mixed <literal>AND</literal>/<literal>OR</literal> clauses (Tom Lane) </para> </listitem> <listitem> <para> - Disallow pushing volatile <literal>WHERE</> clauses down - into <literal>DISTINCT</> subqueries (Tom Lane) + Disallow pushing volatile <literal>WHERE</literal> clauses down + into <literal>DISTINCT</literal> subqueries (Tom Lane) </para> <para> - Pushing down a <literal>WHERE</> clause can produce a more + Pushing down a <literal>WHERE</literal> clause can produce a more efficient plan overall, but at the cost of evaluating the clause more often than is implied by the text of the query; so don't do it if the clause contains any volatile functions. @@ -9122,14 +9358,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Add <xref linkend="pg-stat-archiver-view"> system view to - report <link linkend="wal"><acronym>WAL</></link> archiver activity + report <link linkend="wal"><acronym>WAL</acronym></link> archiver activity (Gabriele Bartolini) </para> </listitem> <listitem> <para> - Add <structfield>n_mod_since_analyze</> columns to + Add <structfield>n_mod_since_analyze</structfield> columns to <xref linkend="pg-stat-all-tables-view"> and related system views (Mark Kirkwood) </para> @@ -9143,9 +9379,9 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add <structfield>backend_xid</> and <structfield>backend_xmin</> + Add <structfield>backend_xid</structfield> and <structfield>backend_xmin</structfield> columns to the system view <xref linkend="pg-stat-activity-view">, - and a <structfield>backend_xmin</> column to + and a <structfield>backend_xmin</structfield> column to <xref linkend="pg-stat-replication-view"> (Christian Kruse) </para> </listitem> @@ -9155,22 +9391,22 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </sect4> <sect4> - <title><acronym>SSL</></title> + <title><acronym>SSL</acronym></title> <itemizedlist> <listitem> <para> - Add support for <acronym>SSL</> <acronym>ECDH</> key exchange + Add support for <acronym>SSL</acronym> <acronym>ECDH</acronym> key exchange (Marko Kreen) </para> <para> This allows use of Elliptic Curve keys for server authentication. - Such keys are faster and have better security than <acronym>RSA</> + Such keys are faster and have better security than <acronym>RSA</acronym> keys. The new configuration parameter <xref linkend="guc-ssl-ecdh-curve"> - controls which curve is used for <acronym>ECDH</>. + controls which curve is used for <acronym>ECDH</acronym>. </para> </listitem> @@ -9184,14 +9420,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> By default, the server not the client now controls the preference - order of <acronym>SSL</> ciphers + order of <acronym>SSL</acronym> ciphers (Marko Kreen) </para> <para> Previously, the order specified by <xref linkend="guc-ssl-ciphers"> was usually ignored in favor of client-side defaults, which are not - configurable in most <productname>PostgreSQL</> clients. If + configurable in most <productname>PostgreSQL</productname> clients. If desired, the old behavior can be restored via the new configuration parameter <xref linkend="guc-ssl-prefer-server-ciphers">. </para> @@ -9199,14 +9435,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Make <xref linkend="guc-log-connections"> show <acronym>SSL</> + Make <xref linkend="guc-log-connections"> show <acronym>SSL</acronym> encryption information (Andreas Kunert) </para> </listitem> <listitem> <para> - Improve <acronym>SSL</> renegotiation handling (Álvaro + Improve <acronym>SSL</acronym> renegotiation handling (Álvaro Herrera) </para> </listitem> @@ -9222,14 +9458,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add new <acronym>SQL</> command <xref linkend="SQL-ALTERSYSTEM"> - for changing <filename>postgresql.conf</> configuration file entries + Add new <acronym>SQL</acronym> command <xref linkend="sql-altersystem"> + for changing <filename>postgresql.conf</filename> configuration file entries (Amit Kapila) </para> <para> Previously such settings could only be changed by manually - editing <filename>postgresql.conf</>. + editing <filename>postgresql.conf</filename>. </para> </listitem> @@ -9274,7 +9510,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> In contrast to <xref linkend="guc-local-preload-libraries">, this parameter can load any shared library, not just those in - the <filename>$libdir/plugins</> directory. + the <filename>$libdir/plugins</filename> directory. </para> </listitem> @@ -9287,7 +9523,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> Hint bit changes are not normally logged, except when checksums are enabled. This is useful for external tools - like <application>pg_rewind</>. + like <application>pg_rewind</application>. </para> </listitem> @@ -9320,14 +9556,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Allow terabyte units (<literal>TB</>) to be used when specifying + Allow terabyte units (<literal>TB</literal>) to be used when specifying configuration variable values (Simon Riggs) </para> </listitem> <listitem> <para> - Show <acronym>PID</>s of lock holders and waiters and improve + Show <acronym>PID</acronym>s of lock holders and waiters and improve information about relations in <xref linkend="guc-log-lock-waits"> log messages (Christian Kruse) </para> @@ -9340,14 +9576,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </para> <para> - The previous level was <literal>LOG</>, which was too verbose + The previous level was <literal>LOG</literal>, which was too verbose for libraries loaded per-session. </para> </listitem> <listitem> <para> - On Windows, make <literal>SQL_ASCII</>-encoded databases and server + On Windows, make <literal>SQL_ASCII</literal>-encoded databases and server processes (e.g., <xref linkend="app-postmaster">) emit messages in the character encoding of the server's Windows user locale (Alexander Law, Noah Misch) @@ -9355,7 +9591,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> Previously these messages were output in the Windows - <acronym>ANSI</> code page. + <acronym>ANSI</acronym> code page. </para> </listitem> @@ -9379,7 +9615,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> Replication slots allow preservation of resources like - <acronym>WAL</> files on the primary until they are no longer + <acronym>WAL</acronym> files on the primary until they are no longer needed by standby servers. </para> </listitem> @@ -9400,8 +9636,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Add <xref linkend="recovery-target"> - option <option>immediate</> to stop <link - linkend="wal"><acronym>WAL</></link> recovery as soon as a + option <option>immediate</option> to stop <link + linkend="wal"><acronym>WAL</acronym></link> recovery as soon as a consistent state is reached (MauMau, Heikki Linnakangas) </para> </listitem> @@ -9413,7 +9649,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> The timestamp reported - by <link linkend="functions-recovery-info-table"><function>pg_last_xact_replay_timestamp()</></link> + by <link linkend="functions-recovery-info-table"><function>pg_last_xact_replay_timestamp()</function></link> now reflects already-committed records, not transactions about to be committed. Recovering to a restore point now replays the restore point, rather than stopping just before the restore point. @@ -9423,34 +9659,34 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> <link - linkend="functions-admin-backup-table"><function>pg_switch_xlog()</></link> - now clears any unused trailing space in the old <acronym>WAL</> file + linkend="functions-admin-backup-table"><function>pg_switch_xlog()</function></link> + now clears any unused trailing space in the old <acronym>WAL</acronym> file (Heikki Linnakangas) </para> <para> - This improves the compression ratio for <acronym>WAL</> files. + This improves the compression ratio for <acronym>WAL</acronym> files. </para> </listitem> <listitem> <para> Report failure return codes from <link - linkend="archive-recovery-settings">external recovery commands</> + linkend="archive-recovery-settings">external recovery commands</link> (Peter Eisentraut) </para> </listitem> <listitem> <para> - Reduce spinlock contention during <acronym>WAL</> replay (Heikki + Reduce spinlock contention during <acronym>WAL</acronym> replay (Heikki Linnakangas) </para> </listitem> <listitem> <para> - Write <acronym>WAL</> records of running transactions more + Write <acronym>WAL</acronym> records of running transactions more frequently (Andres Freund) </para> @@ -9463,12 +9699,12 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </itemizedlist> <sect4> - <title><link linkend="logicaldecoding">Logical Decoding</></title> + <title><link linkend="logicaldecoding">Logical Decoding</link></title> <para> Logical decoding allows database changes to be streamed in a configurable format. The data is read from - the <link linkend="wal"><acronym>WAL</></link> and transformed into the + the <link linkend="wal"><acronym>WAL</acronym></link> and transformed into the desired target format. To implement this feature, the following changes were made: </para> @@ -9477,7 +9713,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add support for <link linkend="logicaldecoding">logical decoding</> + Add support for <link linkend="logicaldecoding">logical decoding</link> of WAL data, to allow database changes to be streamed out in a customizable format (Andres Freund) @@ -9486,8 +9722,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add new <xref linkend="guc-wal-level"> setting <option>logical</> - to enable logical change-set encoding in <acronym>WAL</> (Andres + Add new <xref linkend="guc-wal-level"> setting <option>logical</option> + to enable logical change-set encoding in <acronym>WAL</acronym> (Andres Freund) </para> </listitem> @@ -9495,7 +9731,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Add table-level parameter <link - linkend="catalog-pg-class"><literal>REPLICA IDENTITY</></link> + linkend="catalog-pg-class"><literal>REPLICA IDENTITY</literal></link> to control logical replication (Andres Freund) </para> </listitem> @@ -9503,7 +9739,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Add relation option <link - linkend="SQL-CREATETABLE-storage-parameters"><option>user_catalog_table</></link> + linkend="sql-createtable-storage-parameters"><option>user_catalog_table</option></link> to identify user-created tables involved in logical change-set encoding (Andres Freund) </para> @@ -9519,7 +9755,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Add <xref linkend="test-decoding"> module to illustrate logical - decoding at the <acronym>SQL</> level (Andres Freund) + decoding at the <acronym>SQL</acronym> level (Andres Freund) </para> </listitem> @@ -9537,28 +9773,28 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Add <link linkend="queries-tablefunctions"><literal>WITH - ORDINALITY</></link> syntax to number the rows returned from a - set-returning function in the <literal>FROM</> clause + ORDINALITY</literal></link> syntax to number the rows returned from a + set-returning function in the <literal>FROM</literal> clause (Andrew Gierth, David Fetter) </para> <para> This is particularly useful for functions like - <function>unnest()</>. + <function>unnest()</function>. </para> </listitem> <listitem> <para> Add <link linkend="queries-tablefunctions"><literal>ROWS - FROM()</></link> syntax to allow horizontal concatenation of - set-returning functions in the <literal>FROM</> clause (Andrew Gierth) + FROM()</literal></link> syntax to allow horizontal concatenation of + set-returning functions in the <literal>FROM</literal> clause (Andrew Gierth) </para> </listitem> <listitem> <para> - Allow <xref linkend="SQL-SELECT"> to have + Allow <xref linkend="sql-select"> to have an empty target list (Tom Lane) </para> @@ -9570,8 +9806,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Ensure that <link linkend="SQL-SELECT"><literal>SELECT ... FOR UPDATE - NOWAIT</></link> does not wait in corner cases involving + Ensure that <link linkend="sql-select"><literal>SELECT ... FOR UPDATE + NOWAIT</literal></link> does not wait in corner cases involving already-concurrently-updated tuples (Craig Ringer and Thomas Munro) </para> </listitem> @@ -9587,22 +9823,22 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add <link linkend="SQL-DISCARD"><command>DISCARD - SEQUENCES</></link> command to discard cached sequence-related state + Add <link linkend="sql-discard"><command>DISCARD + SEQUENCES</command></link> command to discard cached sequence-related state (Fabrízio de Royes Mello, Robert Haas) </para> <para> - <command>DISCARD ALL</> will now also discard such information. + <command>DISCARD ALL</command> will now also discard such information. </para> </listitem> <listitem> <para> - Add <literal>FORCE NULL</> option - to <link linkend="SQL-COPY"><command>COPY FROM</></link>, which + Add <literal>FORCE NULL</literal> option + to <link linkend="sql-copy"><command>COPY FROM</command></link>, which causes quoted strings matching the specified null string to be - converted to NULLs in <literal>CSV</> mode (Ian Barwick, Michael + converted to NULLs in <literal>CSV</literal> mode (Ian Barwick, Michael Paquier) </para> @@ -9620,35 +9856,35 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> New warnings are issued for <command>SET - LOCAL</>, <command>SET CONSTRAINTS</>, <command>SET TRANSACTION</> and - <command>ABORT</> when used outside a transaction block. + LOCAL</command>, <command>SET CONSTRAINTS</command>, <command>SET TRANSACTION</command> and + <command>ABORT</command> when used outside a transaction block. </para> </listitem> </itemizedlist> <sect4> - <title><xref linkend="SQL-EXPLAIN"></title> + <title><xref linkend="sql-explain"></title> <itemizedlist> <listitem> <para> - Make <command>EXPLAIN ANALYZE</> show planning time (Andreas + Make <command>EXPLAIN ANALYZE</command> show planning time (Andreas Karlsson) </para> </listitem> <listitem> <para> - Make <command>EXPLAIN</> show the grouping columns in Agg and + Make <command>EXPLAIN</command> show the grouping columns in Agg and Group nodes (Tom Lane) </para> </listitem> <listitem> <para> - Make <command>EXPLAIN ANALYZE</> show exact and lossy + Make <command>EXPLAIN ANALYZE</command> show exact and lossy block counts in bitmap heap scans (Etsuro Fujita) </para> </listitem> @@ -9664,22 +9900,22 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Allow a <link linkend="rules-materializedviews">materialized view</> + Allow a <link linkend="rules-materializedviews">materialized view</link> to be refreshed without blocking other sessions from reading the view meanwhile (Kevin Grittner) </para> <para> This is done with <link - linkend="SQL-REFRESHMATERIALIZEDVIEW"><command>REFRESH MATERIALIZED - VIEW CONCURRENTLY</></link>. + linkend="sql-refreshmaterializedview"><command>REFRESH MATERIALIZED + VIEW CONCURRENTLY</command></link>. </para> </listitem> <listitem> <para> Allow views to be <link - linkend="SQL-CREATEVIEW-updatable-views">automatically + linkend="sql-createview-updatable-views">automatically updated</link> even if they contain some non-updatable columns (Dean Rasheed) </para> @@ -9687,28 +9923,28 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> Previously the presence of non-updatable output columns such as expressions, literals, and function calls prevented automatic - updates. Now <command>INSERT</>s, <command>UPDATE</>s and - <command>DELETE</>s are supported, provided that they do not + updates. Now <command>INSERT</command>s, <command>UPDATE</command>s and + <command>DELETE</command>s are supported, provided that they do not attempt to assign new values to any of the non-updatable columns. </para> </listitem> <listitem> <para> - Allow control over whether <command>INSERT</>s and - <command>UPDATE</>s can add rows to an auto-updatable view that + Allow control over whether <command>INSERT</command>s and + <command>UPDATE</command>s can add rows to an auto-updatable view that would not appear in the view (Dean Rasheed) </para> <para> - This is controlled with the new <xref linkend="SQL-CREATEVIEW"> - clause <literal>WITH CHECK OPTION</>. + This is controlled with the new <xref linkend="sql-createview"> + clause <literal>WITH CHECK OPTION</literal>. </para> </listitem> <listitem> <para> - Allow <link linkend="rules-privileges">security barrier views</> + Allow <link linkend="rules-privileges">security barrier views</link> to be automatically updatable (Dean Rasheed) </para> </listitem> @@ -9726,60 +9962,60 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Support triggers on <link linkend="SQL-CREATEFOREIGNTABLE">foreign - tables</> (Ronan Dunklau) + Support triggers on <link linkend="sql-createforeigntable">foreign + tables</link> (Ronan Dunklau) </para> </listitem> <listitem> <para> Allow moving groups of objects from one tablespace to another - using the <literal>ALL IN TABLESPACE ... SET TABLESPACE</> form of - <xref linkend="SQL-ALTERTABLE">, <xref linkend="SQL-ALTERINDEX">, or - <xref linkend="SQL-ALTERMATERIALIZEDVIEW"> (Stephen Frost) + using the <literal>ALL IN TABLESPACE ... SET TABLESPACE</literal> form of + <xref linkend="sql-altertable">, <xref linkend="sql-alterindex">, or + <xref linkend="sql-altermaterializedview"> (Stephen Frost) </para> </listitem> <listitem> <para> Allow changing foreign key constraint deferrability - via <xref linkend="SQL-ALTERTABLE"> ... <literal>ALTER - CONSTRAINT</> (Simon Riggs) + via <xref linkend="sql-altertable"> ... <literal>ALTER + CONSTRAINT</literal> (Simon Riggs) </para> </listitem> <listitem> <para> - Reduce lock strength for some <xref linkend="SQL-ALTERTABLE"> + Reduce lock strength for some <xref linkend="sql-altertable"> commands (Simon Riggs, Noah Misch, Robert Haas) </para> <para> - Specifically, <literal>VALIDATE CONSTRAINT</>, <literal>CLUSTER - ON</>, <literal>SET WITHOUT CLUSTER</>, <literal>ALTER COLUMN - SET STATISTICS</>, <literal>ALTER COLUMN</> <literal>SET</> - <option>(attribute_option)</>, <literal>ALTER COLUMN RESET</> - <option>(attribute_option)</> no longer require <literal>ACCESS - EXCLUSIVE</> locks. + Specifically, <literal>VALIDATE CONSTRAINT</literal>, <literal>CLUSTER + ON</literal>, <literal>SET WITHOUT CLUSTER</literal>, <literal>ALTER COLUMN + SET STATISTICS</literal>, <literal>ALTER COLUMN</literal> <literal>SET</literal> + <option>(attribute_option)</option>, <literal>ALTER COLUMN RESET</literal> + <option>(attribute_option)</option> no longer require <literal>ACCESS + EXCLUSIVE</literal> locks. </para> </listitem> <listitem> <para> Allow tablespace options to be set - in <xref linkend="SQL-CREATETABLESPACE"> (Vik Fearing) + in <xref linkend="sql-createtablespace"> (Vik Fearing) </para> <para> Formerly these options could only be set - via <xref linkend="SQL-ALTERTABLESPACE">. + via <xref linkend="sql-altertablespace">. </para> </listitem> <listitem> <para> - Allow <xref linkend="SQL-CREATEAGGREGATE"> to define the estimated + Allow <xref linkend="sql-createaggregate"> to define the estimated size of the aggregate's transition state data (Hadi Moshayedi) </para> @@ -9791,7 +10027,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Fix <command>DROP IF EXISTS</> to avoid errors for non-existent + Fix <command>DROP IF EXISTS</command> to avoid errors for non-existent objects in more cases (Pavel Stehule, Dean Rasheed) </para> </listitem> @@ -9803,7 +10039,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </para> <para> - Previously, relations once moved into the <literal>pg_catalog</> + Previously, relations once moved into the <literal>pg_catalog</literal> schema could no longer be modified or dropped. </para> </listitem> @@ -9820,14 +10056,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Fully implement the <link - linkend="datatype-line"><type>line</></link> data type (Peter + linkend="datatype-line"><type>line</type></link> data type (Peter Eisentraut) </para> <para> - The line <emphasis>segment</> data type (<link - linkend="datatype-lseg"><type>lseg</></link>) has always been - fully supported. The previous <type>line</> data type (which was + The line <emphasis>segment</emphasis> data type (<link + linkend="datatype-lseg"><type>lseg</type></link>) has always been + fully supported. The previous <type>line</type> data type (which was enabled only via a compile-time option) is not binary or dump-compatible with the new implementation. </para> @@ -9835,17 +10071,17 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add <link linkend="datatype-pg-lsn"><type>pg_lsn</></link> - data type to represent a <acronym>WAL</> log sequence number - (<acronym>LSN</>) (Robert Haas, Michael Paquier) + Add <link linkend="datatype-pg-lsn"><type>pg_lsn</type></link> + data type to represent a <acronym>WAL</acronym> log sequence number + (<acronym>LSN</acronym>) (Robert Haas, Michael Paquier) </para> </listitem> <listitem> <para> Allow single-point <link - linkend="datatype-polygon"><type>polygon</></link>s to be converted - to <link linkend="datatype-circle"><type>circle</></link>s + linkend="datatype-polygon"><type>polygon</type></link>s to be converted + to <link linkend="datatype-circle"><type>circle</type></link>s (Bruce Momjian) </para> </listitem> @@ -9857,31 +10093,31 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </para> <para> - Previously, <productname>PostgreSQL</> assumed that the UTC offset - associated with a time zone abbreviation (such as <literal>EST</>) + Previously, <productname>PostgreSQL</productname> assumed that the UTC offset + associated with a time zone abbreviation (such as <literal>EST</literal>) never changes in the usage of any particular locale. However this assumption fails in the real world, so introduce the ability for a zone abbreviation to represent a UTC offset that sometimes changes. Update the zone abbreviation definition files to make use of this feature in timezone locales that have changed the UTC offset of their abbreviations since 1970 (according to the IANA timezone database). - In such timezones, <productname>PostgreSQL</> will now associate the + In such timezones, <productname>PostgreSQL</productname> will now associate the correct UTC offset with the abbreviation depending on the given date. </para> </listitem> <listitem> <para> - Allow 5+ digit years for non-<acronym>ISO</> <link - linkend="datatype-datetime"><type>timestamp</></link> and - <type>date</> strings, where appropriate (Bruce Momjian) + Allow 5+ digit years for non-<acronym>ISO</acronym> <link + linkend="datatype-datetime"><type>timestamp</type></link> and + <type>date</type> strings, where appropriate (Bruce Momjian) </para> </listitem> <listitem> <para> Add checks for overflow/underflow of <link - linkend="datatype-datetime"><type>interval</></link> values + linkend="datatype-datetime"><type>interval</type></link> values (Bruce Momjian) </para> </listitem> @@ -9889,14 +10125,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </itemizedlist> <sect4> - <title><link linkend="datatype-json"><acronym>JSON</></link></title> + <title><link linkend="datatype-json"><acronym>JSON</acronym></link></title> <itemizedlist> <listitem> <para> - Add <link linkend="datatype-json"><type>jsonb</></link>, a more - capable and efficient data type for storing <acronym>JSON</> data + Add <link linkend="datatype-json"><type>jsonb</type></link>, a more + capable and efficient data type for storing <acronym>JSON</acronym> data (Oleg Bartunov, Teodor Sigaev, Alexander Korotkov, Peter Geoghegan, Andrew Dunstan) </para> @@ -9904,9 +10140,9 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> This new type allows faster access to values within a JSON document, and faster and more useful indexing of JSON columns. - Scalar values in <type>jsonb</> documents are stored as appropriate + Scalar values in <type>jsonb</type> documents are stored as appropriate scalar SQL types, and the JSON document structure is pre-parsed - rather than being stored as text as in the original <type>json</> + rather than being stored as text as in the original <type>json</type> data type. </para> </listitem> @@ -9919,18 +10155,18 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> New functions include <link - linkend="functions-json-processing-table"><function>json_array_elements_text()</></link>, - <function>json_build_array()</>, <function>json_object()</>, - <function>json_object_agg()</>, <function>json_to_record()</>, - and <function>json_to_recordset()</>. + linkend="functions-json-processing-table"><function>json_array_elements_text()</function></link>, + <function>json_build_array()</function>, <function>json_object()</function>, + <function>json_object_agg()</function>, <function>json_to_record()</function>, + and <function>json_to_recordset()</function>. </para> </listitem> <listitem> <para> Add <link - linkend="functions-json-processing-table"><function>json_typeof()</></link> - to return the data type of a <type>json</> value (Andrew Tipton) + linkend="functions-json-processing-table"><function>json_typeof()</function></link> + to return the data type of a <type>json</type> value (Andrew Tipton) </para> </listitem> @@ -9948,13 +10184,13 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Add <link - linkend="functions-datetime-delay"><function>pg_sleep_for(interval)</></link> - and <function>pg_sleep_until(timestamp)</> to specify + linkend="functions-datetime-delay"><function>pg_sleep_for(interval)</function></link> + and <function>pg_sleep_until(timestamp)</function> to specify delays more flexibly (Vik Fearing, Julien Rouhaud) </para> <para> - The existing <function>pg_sleep()</> function only supports delays + The existing <function>pg_sleep()</function> function only supports delays specified in seconds. </para> </listitem> @@ -9962,7 +10198,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Add <link - linkend="array-functions-table"><function>cardinality()</></link> + linkend="array-functions-table"><function>cardinality()</function></link> function for arrays (Marko Tiikkaja) </para> @@ -9974,7 +10210,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add <acronym>SQL</> functions to allow <link linkend="lo-funcs">large + Add <acronym>SQL</acronym> functions to allow <link linkend="lo-funcs">large object reads/writes</link> at arbitrary offsets (Pavel Stehule) </para> </listitem> @@ -9982,7 +10218,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Allow <link - linkend="array-functions-table"><function>unnest()</></link> + linkend="array-functions-table"><function>unnest()</function></link> to take multiple arguments, which are individually unnested then horizontally concatenated (Andrew Gierth) </para> @@ -9990,36 +10226,36 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add functions to construct <type>time</>s, <type>date</>s, - <type>timestamp</>s, <type>timestamptz</>s, and <type>interval</>s + Add functions to construct <type>time</type>s, <type>date</type>s, + <type>timestamp</type>s, <type>timestamptz</type>s, and <type>interval</type>s from individual values, rather than strings (Pavel Stehule) </para> <para> - These functions' names are prefixed with <literal>make_</>, - e.g. <link linkend="functions-datetime-table"><function>make_date()</></link>. + These functions' names are prefixed with <literal>make_</literal>, + e.g. <link linkend="functions-datetime-table"><function>make_date()</function></link>. </para> </listitem> <listitem> <para> Make <link - linkend="functions-formatting-table"><function>to_char()</></link>'s - <literal>TZ</> format specifier return a useful value for simple + linkend="functions-formatting-table"><function>to_char()</function></link>'s + <literal>TZ</literal> format specifier return a useful value for simple numeric time zone offsets (Tom Lane) </para> <para> - Previously, <literal>to_char(CURRENT_TIMESTAMP, 'TZ')</> returned - an empty string if the <literal>timezone</> was set to a constant - like <literal>-4</>. + Previously, <literal>to_char(CURRENT_TIMESTAMP, 'TZ')</literal> returned + an empty string if the <literal>timezone</literal> was set to a constant + like <literal>-4</literal>. </para> </listitem> <listitem> <para> - Add timezone offset format specifier <literal>OF</> to <link - linkend="functions-formatting-table"><function>to_char()</></link> + Add timezone offset format specifier <literal>OF</literal> to <link + linkend="functions-formatting-table"><function>to_char()</function></link> (Bruce Momjian) </para> </listitem> @@ -10027,7 +10263,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Improve the random seed used for <link - linkend="functions-math-random-table"><function>random()</></link> + linkend="functions-math-random-table"><function>random()</function></link> (Honza Horak) </para> </listitem> @@ -10035,7 +10271,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Tighten validity checking for Unicode code points in <link - linkend="functions-string-other"><function>chr(int)</></link> + linkend="functions-string-other"><function>chr(int)</function></link> (Tom Lane) </para> @@ -10054,18 +10290,18 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add functions for looking up objects in <structname>pg_class</>, - <structname>pg_proc</>, <structname>pg_type</>, and - <structname>pg_operator</> that do not generate errors for + Add functions for looking up objects in <structname>pg_class</structname>, + <structname>pg_proc</structname>, <structname>pg_type</structname>, and + <structname>pg_operator</structname> that do not generate errors for non-existent objects (Yugo Nagata, Nozomi Anzai, Robert Haas) </para> <para> For example, <link - linkend="functions-info-catalog-table"><function>to_regclass()</></link> - does a lookup in <structname>pg_class</> similarly to - the <type>regclass</> input function, but it returns NULL for a + linkend="functions-info-catalog-table"><function>to_regclass()</function></link> + does a lookup in <structname>pg_class</structname> similarly to + the <type>regclass</type> input function, but it returns NULL for a non-existent object instead of failing. </para> </listitem> @@ -10073,7 +10309,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Add function <link - linkend="functions-admin-dblocation"><function>pg_filenode_relation()</></link> + linkend="functions-admin-dblocation"><function>pg_filenode_relation()</function></link> to allow for more efficient lookup of relation names from filenodes (Andres Freund) </para> @@ -10081,8 +10317,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add <structfield>parameter_default</> column to <link - linkend="infoschema-parameters"><structname>information_schema.parameters</></link> + Add <structfield>parameter_default</structfield> column to <link + linkend="infoschema-parameters"><structname>information_schema.parameters</structname></link> view (Peter Eisentraut) </para> </listitem> @@ -10090,7 +10326,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Make <link - linkend="infoschema-schemata"><structname>information_schema.schemata</></link> + linkend="infoschema-schemata"><structname>information_schema.schemata</structname></link> show all accessible schemas (Peter Eisentraut) </para> @@ -10112,7 +10348,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> Add control over which rows are passed into aggregate functions via the <link - linkend="syntax-aggregates"><literal>FILTER</></link> clause + linkend="syntax-aggregates"><literal>FILTER</literal></link> clause (David Fetter) </para> </listitem> @@ -10120,7 +10356,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Support ordered-set (<link - linkend="syntax-aggregates"><literal>WITHIN GROUP</></link>) + linkend="syntax-aggregates"><literal>WITHIN GROUP</literal></link>) aggregates (Atri Sharma, Andrew Gierth, Tom Lane) </para> </listitem> @@ -10128,11 +10364,11 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Add standard ordered-set aggregates <link - linkend="functions-orderedset-table"><function>percentile_cont()</></link>, - <function>percentile_disc()</>, <function>mode()</>, <link - linkend="functions-hypothetical-table"><function>rank()</></link>, - <function>dense_rank()</>, <function>percent_rank()</>, and - <function>cume_dist()</> + linkend="functions-orderedset-table"><function>percentile_cont()</function></link>, + <function>percentile_disc()</function>, <function>mode()</function>, <link + linkend="functions-hypothetical-table"><function>rank()</function></link>, + <function>dense_rank()</function>, <function>percent_rank()</function>, and + <function>cume_dist()</function> (Atri Sharma, Andrew Gierth) </para> </listitem> @@ -10140,7 +10376,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Support <link - linkend="xfunc-sql-variadic-functions"><literal>VARIADIC</></link> + linkend="xfunc-sql-variadic-functions"><literal>VARIADIC</literal></link> aggregate functions (Tom Lane) </para> </listitem> @@ -10152,7 +10388,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </para> <para> This allows proper declaration in SQL of aggregates like the built-in - aggregate <function>array_agg()</>. + aggregate <function>array_agg()</function>. </para> </listitem> @@ -10169,20 +10405,20 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add event trigger support to <link linkend="plperl">PL/Perl</> - and <link linkend="pltcl">PL/Tcl</> (Dimitri Fontaine) + Add event trigger support to <link linkend="plperl">PL/Perl</link> + and <link linkend="pltcl">PL/Tcl</link> (Dimitri Fontaine) </para> </listitem> <listitem> <para> - Convert <link linkend="datatype-numeric"><type>numeric</></link> - values to <type>decimal</> in <link linkend="plpython">PL/Python</link> + Convert <link linkend="datatype-numeric"><type>numeric</type></link> + values to <type>decimal</type> in <link linkend="plpython">PL/Python</link> (Szymon Guz, Ronan Dunklau) </para> <para> - Previously such values were converted to Python <type>float</> values, + Previously such values were converted to Python <type>float</type> values, risking loss of precision. </para> </listitem> @@ -10198,7 +10434,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <para> Add ability to retrieve the current PL/pgSQL call stack using <link linkend="plpgsql-call-stack"><command>GET - DIAGNOSTICS</></link> + DIAGNOSTICS</command></link> (Pavel Stehule, Stephen Frost) </para> </listitem> @@ -10206,17 +10442,17 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Add option <link - linkend="plpgsql-statements-sql-onerow"><option>print_strict_params</></link> + linkend="plpgsql-statements-sql-onerow"><option>print_strict_params</option></link> to display the parameters passed to a query that violated a - <literal>STRICT</> constraint (Marko Tiikkaja) + <literal>STRICT</literal> constraint (Marko Tiikkaja) </para> </listitem> <listitem> <para> Add variables <link - linkend="plpgsql-extra-checks"><varname>plpgsql.extra_warnings</></link> - and <varname>plpgsql.extra_errors</> to enable additional PL/pgSQL + linkend="plpgsql-extra-checks"><varname>plpgsql.extra_warnings</varname></link> + and <varname>plpgsql.extra_errors</varname> to enable additional PL/pgSQL warnings and errors (Marko Tiikkaja, Petr Jelinek) </para> @@ -10232,13 +10468,13 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </sect3> <sect3> - <title><link linkend="libpq"><application>libpq</></link></title> + <title><link linkend="libpq"><application>libpq</application></link></title> <itemizedlist> <listitem> <para> Make libpq's <link - linkend="libpq-pqconndefaults"><function>PQconndefaults()</></link> + linkend="libpq-pqconndefaults"><function>PQconndefaults()</function></link> function ignore invalid service files (Steve Singer, Bruce Momjian) </para> @@ -10250,7 +10486,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Accept <acronym>TLS</> protocol versions beyond <literal>TLSv1</> + Accept <acronym>TLS</acronym> protocol versions beyond <literal>TLSv1</literal> in libpq (Marko Kreen) </para> </listitem> @@ -10266,15 +10502,15 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add <xref linkend="APP-CREATEUSER"> option <option>-g</> + Add <xref linkend="app-createuser"> option <option>-g</option> to specify role membership (Christopher Browne) </para> </listitem> <listitem> <para> - Add <xref linkend="APP-VACUUMDB"> - option <option>--analyze-in-stages</> to analyze in stages of + Add <xref linkend="app-vacuumdb"> + option <option>--analyze-in-stages</option> to analyze in stages of increasing granularity (Peter Eisentraut) </para> @@ -10285,8 +10521,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Make <link linkend="app-pgresetwal"><application>pg_resetxlog</></> - with option <option>-n</> output current and potentially changed + Make <link linkend="app-pgresetwal"><application>pg_resetxlog</application></link> + with option <option>-n</option> output current and potentially changed values (Rajeev Rastogi) </para> </listitem> @@ -10301,19 +10537,19 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Make <xref linkend="app-pg-ctl"> return exit code <literal>4</> for + Make <xref linkend="app-pg-ctl"> return exit code <literal>4</literal> for an inaccessible data directory (Amit Kapila, Bruce Momjian) </para> <para> This behavior more closely matches the Linux Standard Base - (<acronym>LSB</>) Core Specification. + (<acronym>LSB</acronym>) Core Specification. </para> </listitem> <listitem> <para> - On Windows, ensure that a non-absolute <option>-D</> path + On Windows, ensure that a non-absolute <option>-D</option> path specification is interpreted relative to <xref linkend="app-pg-ctl">'s current directory (Kumar Rajeev Rastogi) @@ -10327,7 +10563,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Allow <function>sizeof()</> in <link linkend="ecpg">ECPG</link> + Allow <function>sizeof()</function> in <link linkend="ecpg">ECPG</link> C array definitions (Michael Meskes) </para> </listitem> @@ -10335,7 +10571,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Make <link linkend="ecpg">ECPG</link> properly handle nesting - of C-style comments in both C and <acronym>SQL</> text + of C-style comments in both C and <acronym>SQL</acronym> text (Michael Meskes) </para> </listitem> @@ -10343,21 +10579,21 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </itemizedlist> <sect4> - <title><xref linkend="APP-PSQL"></title> + <title><xref linkend="app-psql"></title> <itemizedlist> <listitem> <para> - Suppress <quote>No rows</quote> output in <application>psql</> <link - linkend="APP-PSQL-meta-commands"><option>expanded</></link> + Suppress <quote>No rows</quote> output in <application>psql</application> <link + linkend="app-psql-meta-commands"><option>expanded</option></link> mode when the footer is disabled (Bruce Momjian) </para> </listitem> <listitem> <para> - Allow Control-C to abort <application>psql</> when it's hung at + Allow Control-C to abort <application>psql</application> when it's hung at connection startup (Peter Eisentraut) </para> </listitem> @@ -10365,28 +10601,28 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </itemizedlist> <sect5> - <title><link linkend="APP-PSQL-meta-commands">Backslash Commands</link></title> + <title><link linkend="app-psql-meta-commands">Backslash Commands</link></title> <itemizedlist> <listitem> <para> - Make <application>psql</>'s <command>\db+</> show tablespace options + Make <application>psql</application>'s <command>\db+</command> show tablespace options (Magnus Hagander) </para> </listitem> <listitem> <para> - Make <command>\do+</> display the functions + Make <command>\do+</command> display the functions that implement the operators (Marko Tiikkaja) </para> </listitem> <listitem> <para> - Make <command>\d+</> output an - <literal>OID</> line only if an <literal>oid</literal> column + Make <command>\d+</command> output an + <literal>OID</literal> line only if an <literal>oid</literal> column exists in the table (Bruce Momjian) </para> @@ -10398,7 +10634,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Make <command>\d</> show disabled system triggers (Bruce + Make <command>\d</command> show disabled system triggers (Bruce Momjian) </para> @@ -10410,55 +10646,55 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Fix <command>\copy</> to no longer require - a space between <literal>stdin</> and a semicolon (Etsuro Fujita) + Fix <command>\copy</command> to no longer require + a space between <literal>stdin</literal> and a semicolon (Etsuro Fujita) </para> </listitem> <listitem> <para> - Output the row count at the end of <command>\copy</>, just - like <command>COPY</> already did (Kumar Rajeev Rastogi) + Output the row count at the end of <command>\copy</command>, just + like <command>COPY</command> already did (Kumar Rajeev Rastogi) </para> </listitem> <listitem> <para> - Fix <command>\conninfo</> to display the - server's <acronym>IP</> address for connections using - <literal>hostaddr</> (Fujii Masao) + Fix <command>\conninfo</command> to display the + server's <acronym>IP</acronym> address for connections using + <literal>hostaddr</literal> (Fujii Masao) </para> <para> - Previously <command>\conninfo</> could not display the server's - <acronym>IP</> address in such cases. + Previously <command>\conninfo</command> could not display the server's + <acronym>IP</acronym> address in such cases. </para> </listitem> <listitem> <para> - Show the <acronym>SSL</> protocol version in - <command>\conninfo</> (Marko Kreen) + Show the <acronym>SSL</acronym> protocol version in + <command>\conninfo</command> (Marko Kreen) </para> </listitem> <listitem> <para> - Add tab completion for <command>\pset</> + Add tab completion for <command>\pset</command> (Pavel Stehule) </para> </listitem> <listitem> <para> - Allow <command>\pset</> with no arguments + Allow <command>\pset</command> with no arguments to show all settings (Gilles Darold) </para> </listitem> <listitem> <para> - Make <command>\s</> display the name of the history file it wrote + Make <command>\s</command> display the name of the history file it wrote without converting it to an absolute path (Tom Lane) </para> @@ -10475,14 +10711,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </sect4> <sect4> - <title><xref linkend="APP-PGDUMP"></title> + <title><xref linkend="app-pgdump"></title> <itemizedlist> <listitem> <para> - Allow <xref linkend="APP-PGRESTORE"> options - <option>-I</>, <option>-P</>, <option>-T</> and <option>-n</> + Allow <xref linkend="app-pgrestore"> options + <option>-I</option>, <option>-P</option>, <option>-T</option> and <option>-n</option> to be specified multiple times (Heikki Linnakangas) </para> @@ -10493,17 +10729,17 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Optionally add <literal>IF EXISTS</> clauses to the <command>DROP</> + Optionally add <literal>IF EXISTS</literal> clauses to the <command>DROP</command> commands emitted when removing old objects during a restore (Pavel Stehule) </para> <para> This change prevents unnecessary errors when removing old objects. - The new <option>--if-exists</> option - for <xref linkend="APP-PGDUMP">, <xref linkend="APP-PG-DUMPALL">, - and <xref linkend="APP-PGRESTORE"> is only available - when <option>--clean</> is also specified. + The new <option>--if-exists</option> option + for <xref linkend="app-pgdump">, <xref linkend="app-pg-dumpall">, + and <xref linkend="app-pgrestore"> is only available + when <option>--clean</option> is also specified. </para> </listitem> @@ -10518,20 +10754,20 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add <application>pg_basebackup</> option <option>--xlogdir</> - to specify the <filename>pg_xlog</> directory location (Haribabu + Add <application>pg_basebackup</application> option <option>--xlogdir</option> + to specify the <filename>pg_xlog</filename> directory location (Haribabu Kommi) </para> </listitem> <listitem> <para> - Allow <application>pg_basebackup</> to relocate tablespaces in + Allow <application>pg_basebackup</application> to relocate tablespaces in the backup copy (Steeve Lennmark) </para> <para> - This is particularly useful for using <application>pg_basebackup</> + This is particularly useful for using <application>pg_basebackup</application> on the same machine as the primary. </para> </listitem> @@ -10542,8 +10778,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 </para> <para> - This can be controlled with the <application>pg_basebackup</> - <option>--max-rate</> parameter. + This can be controlled with the <application>pg_basebackup</application> + <option>--max-rate</option> parameter. </para> </listitem> @@ -10574,13 +10810,13 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> No longer require function prototypes for functions marked with the - <link linkend="xfunc-c"><function>PG_FUNCTION_INFO_V1</></link> + <link linkend="xfunc-c"><function>PG_FUNCTION_INFO_V1</function></link> macro (Peter Eisentraut) </para> <para> This change eliminates the need to write boilerplate prototypes. - Note that the <function>PG_FUNCTION_INFO_V1</> macro must appear + Note that the <function>PG_FUNCTION_INFO_V1</function> macro must appear before the corresponding function definition to avoid compiler warnings. </para> @@ -10588,41 +10824,41 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Remove <varname>SnapshotNow</> and - <function>HeapTupleSatisfiesNow()</> (Robert Haas) + Remove <varname>SnapshotNow</varname> and + <function>HeapTupleSatisfiesNow()</function> (Robert Haas) </para> <para> All existing uses have been switched to more appropriate snapshot - types. Catalog scans now use <acronym>MVCC</> snapshots. + types. Catalog scans now use <acronym>MVCC</acronym> snapshots. </para> </listitem> <listitem> <para> - Add an <acronym>API</> to allow memory allocations over one gigabyte + Add an <acronym>API</acronym> to allow memory allocations over one gigabyte (Noah Misch) </para> </listitem> <listitem> <para> - Add <function>psprintf()</> to simplify memory allocation during + Add <function>psprintf()</function> to simplify memory allocation during string composition (Peter Eisentraut, Tom Lane) </para> </listitem> <listitem> <para> - Support <function>printf()</> size modifier <literal>z</> to - print <type>size_t</> values (Andres Freund) + Support <function>printf()</function> size modifier <literal>z</literal> to + print <type>size_t</type> values (Andres Freund) </para> </listitem> <listitem> <para> - Change <acronym>API</> of <function>appendStringInfoVA()</> - to better use <function>vsnprintf()</> (David Rowley, Tom Lane) + Change <acronym>API</acronym> of <function>appendStringInfoVA()</function> + to better use <function>vsnprintf()</function> (David Rowley, Tom Lane) </para> </listitem> @@ -10642,7 +10878,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Improve spinlock speed on x86_64 <acronym>CPU</>s (Heikki + Improve spinlock speed on x86_64 <acronym>CPU</acronym>s (Heikki Linnakangas) </para> </listitem> @@ -10650,56 +10886,56 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Remove spinlock support for unsupported platforms - <productname>SINIX</>, <productname>Sun3</>, and - <productname>NS32K</> (Robert Haas) + <productname>SINIX</productname>, <productname>Sun3</productname>, and + <productname>NS32K</productname> (Robert Haas) </para> </listitem> <listitem> <para> - Remove <acronym>IRIX</> port (Robert Haas) + Remove <acronym>IRIX</acronym> port (Robert Haas) </para> </listitem> <listitem> <para> Reduce the number of semaphores required by - <option>--disable-spinlocks</> builds (Robert Haas) + <option>--disable-spinlocks</option> builds (Robert Haas) </para> </listitem> <listitem> <para> - Rewrite <application>duplicate_oids</> Unix shell script in - <application>Perl</> (Andrew Dunstan) + Rewrite <application>duplicate_oids</application> Unix shell script in + <application>Perl</application> (Andrew Dunstan) </para> </listitem> <listitem> <para> - Add Test Anything Protocol (<acronym>TAP</>) tests for client + Add Test Anything Protocol (<acronym>TAP</acronym>) tests for client programs (Peter Eisentraut) </para> <para> - Currently, these tests are run by <literal>make check-world</> - only if the <option>--enable-tap-tests</> option was given - to <application>configure</>. + Currently, these tests are run by <literal>make check-world</literal> + only if the <option>--enable-tap-tests</option> option was given + to <application>configure</application>. This might become the default behavior in some future release. </para> </listitem> <listitem> <para> - Add make targets <option>check-tests</> and - <option>installcheck-tests</>, which allow selection of individual + Add make targets <option>check-tests</option> and + <option>installcheck-tests</option>, which allow selection of individual tests to be run (Andrew Dunstan) </para> </listitem> <listitem> <para> - Remove <option>maintainer-check</> makefile rule (Peter Eisentraut) + Remove <option>maintainer-check</option> makefile rule (Peter Eisentraut) </para> <para> @@ -10709,7 +10945,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Improve support for <envar>VPATH</> builds of <acronym>PGXS</> + Improve support for <envar>VPATH</envar> builds of <acronym>PGXS</acronym> modules (Cédric Villemain, Andrew Dunstan, Peter Eisentraut) </para> </listitem> @@ -10722,8 +10958,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add a <application>configure</> flag that appends custom text to the - <envar>PG_VERSION</> string (Oskari Saarenmaa) + Add a <application>configure</application> flag that appends custom text to the + <envar>PG_VERSION</envar> string (Oskari Saarenmaa) </para> <para> @@ -10733,46 +10969,46 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Improve DocBook <acronym>XML</> validity (Peter Eisentraut) + Improve DocBook <acronym>XML</acronym> validity (Peter Eisentraut) </para> </listitem> <listitem> <para> Fix various minor security and sanity issues reported by the - <productname>Coverity</> scanner (Stephen Frost) + <productname>Coverity</productname> scanner (Stephen Frost) </para> </listitem> <listitem> <para> Improve detection of invalid memory usage when testing - <productname>PostgreSQL</> with <application>Valgrind</> + <productname>PostgreSQL</productname> with <application>Valgrind</application> (Noah Misch) </para> </listitem> <listitem> <para> - Improve sample <application>Emacs</> configuration file - <filename>emacs.samples</> (Peter Eisentraut) + Improve sample <application>Emacs</application> configuration file + <filename>emacs.samples</filename> (Peter Eisentraut) </para> <para> - Also add <filename>.dir-locals.el</> to the top of the source tree. + Also add <filename>.dir-locals.el</filename> to the top of the source tree. </para> </listitem> <listitem> <para> - Allow <application>pgindent</> to accept a command-line list + Allow <application>pgindent</application> to accept a command-line list of typedefs (Bruce Momjian) </para> </listitem> <listitem> <para> - Make <application>pgindent</> smarter about blank lines + Make <application>pgindent</application> smarter about blank lines around preprocessor conditionals (Bruce Momjian) </para> </listitem> @@ -10780,14 +11016,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Avoid most uses of <command>dlltool</command> - in <productname>Cygwin</> and - <productname>Mingw</> builds (Marco Atzeri, Hiroshi Inoue) + in <productname>Cygwin</productname> and + <productname>Mingw</productname> builds (Marco Atzeri, Hiroshi Inoue) </para> </listitem> <listitem> <para> - Support client-only installs in <acronym>MSVC</> (Windows) builds + Support client-only installs in <acronym>MSVC</acronym> (Windows) builds (MauMau) </para> </listitem> @@ -10814,13 +11050,13 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add <acronym>UUID</> random number generator - <function>gen_random_uuid()</> to <xref linkend="pgcrypto"> + Add <acronym>UUID</acronym> random number generator + <function>gen_random_uuid()</function> to <xref linkend="pgcrypto"> (Oskari Saarenmaa) </para> <para> - This allows creation of version 4 <acronym>UUID</>s without + This allows creation of version 4 <acronym>UUID</acronym>s without requiring installation of <xref linkend="uuid-ossp">. </para> </listitem> @@ -10828,12 +11064,12 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> Allow <xref linkend="uuid-ossp"> to work with - the <systemitem>BSD</> or <systemitem>e2fsprogs</> UUID libraries, - not only the <systemitem>OSSP</> UUID library (Matteo Beccati) + the <systemitem>BSD</systemitem> or <systemitem>e2fsprogs</systemitem> UUID libraries, + not only the <systemitem>OSSP</systemitem> UUID library (Matteo Beccati) </para> <para> - This improves the <application>uuid-ossp</> module's portability + This improves the <application>uuid-ossp</application> module's portability since it no longer has to have the increasingly-obsolete OSSP library. The module's name is now rather a misnomer, but we won't change it. @@ -10887,8 +11123,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Allow <link linkend="pgwaldump"><application>pg_xlogdump</></> - to report a live log stream with <option>--follow</> + Allow <link linkend="pgwaldump"><application>pg_xlogdump</application></link> + to report a live log stream with <option>--follow</option> (Heikki Linnakangas) </para> </listitem> @@ -10920,7 +11156,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Pass <xref linkend="pgupgrade">'s user name (<option>-U</>) option to + Pass <xref linkend="pgupgrade">'s user name (<option>-U</option>) option to generated analyze scripts (Bruce Momjian) </para> </listitem> @@ -10934,31 +11170,31 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Remove line length limit for <application>pgbench</> scripts (Sawada + Remove line length limit for <application>pgbench</application> scripts (Sawada Masahiko) </para> <para> - The previous line limit was <envar>BUFSIZ</>. + The previous line limit was <envar>BUFSIZ</envar>. </para> </listitem> <listitem> <para> - Add long option names to <application>pgbench</> (Fabien Coelho) + Add long option names to <application>pgbench</application> (Fabien Coelho) </para> </listitem> <listitem> <para> - Add <application>pgbench</> option <option>--rate</> to control + Add <application>pgbench</application> option <option>--rate</option> to control the transaction rate (Fabien Coelho) </para> </listitem> <listitem> <para> - Add <application>pgbench</> option <option>--progress</> to + Add <application>pgbench</application> option <option>--progress</option> to print periodic progress reports (Fabien Coelho) </para> @@ -10975,7 +11211,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Make <application>pg_stat_statements</> use a file, rather than + Make <application>pg_stat_statements</application> use a file, rather than shared memory, for query text storage (Peter Geoghegan) </para> @@ -10987,7 +11223,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Allow reporting of <application>pg_stat_statements</>'s internal + Allow reporting of <application>pg_stat_statements</application>'s internal query hash identifier (Daniel Farina, Sameer Thakur, Peter Geoghegan) </para> @@ -10995,7 +11231,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Add the ability to retrieve all <application>pg_stat_statements</> + Add the ability to retrieve all <application>pg_stat_statements</application> information except the query text (Peter Geoghegan) </para> @@ -11008,20 +11244,20 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500 <listitem> <para> - Make <application>pg_stat_statements</> ignore <command>DEALLOCATE</> + Make <application>pg_stat_statements</application> ignore <command>DEALLOCATE</command> commands (Fabien Coelho) </para> <para> - It already ignored <command>PREPARE</>, as well as planning time in + It already ignored <command>PREPARE</command>, as well as planning time in general, so this seems more consistent. </para> </listitem> <listitem> <para> - Save the statistics file into <filename>$PGDATA/pg_stat</> at server - shutdown, rather than <filename>$PGDATA/global</> (Fujii Masao) + Save the statistics file into <filename>$PGDATA/pg_stat</filename> at server + shutdown, rather than <filename>$PGDATA/global</filename> (Fujii Masao) </para> </listitem> |