<!-- doc/src/sgml/release-9.2.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-2-24">
+ <title>Release 9.2.24</title>
+
+ <formalpara>
+ <title>Release date:</title>
+ <para>2017-11-09</para>
+ </formalpara>
+
+ <para>
+ This release contains a variety of fixes from 9.2.23.
+ For information about new features in the 9.2 major release, see
+ <xref linkend="release-9-2">.
+ </para>
+
+ <para>
+ This is expected to be the last <productname>PostgreSQL</productname>
+ release in the 9.2.X series. Users are encouraged to update to a newer
+ release branch soon.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 9.2.24</title>
+
+ <para>
+ A dump/restore is not required for those running 9.2.X.
+ </para>
+
+ <para>
+ However, if you are upgrading from a version earlier than 9.2.22,
+ see <xref linkend="release-9-2-22">.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <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>
+ Prevent low-probability crash in processing of nested trigger firings
+ (Tom Lane)
+ </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 <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>
+ 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-2-23">
<title>Release 9.2.23</title>
</para>
<para>
- The <productname>PostgreSQL</> community will stop releasing updates
+ The <productname>PostgreSQL</productname> community will stop releasing updates
for the 9.2.X release series in September 2017.
Users are encouraged to update to a newer release branch soon.
</para>
<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
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>
</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,
<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>
<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>
</para>
<para>
- The <productname>PostgreSQL</> community will stop releasing updates
+ The <productname>PostgreSQL</productname> community will stop releasing updates
for the 9.2.X release series in September 2017.
Users are encouraged to update to a newer release branch soon.
</para>
<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>
<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>
<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;
<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>
<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>
</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>
<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 <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>
<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>
<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>
<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>
<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>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>
<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>
<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>
<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>
<listitem>
<para>
- Fix <application>pg_basebackup</> output to stdout on Windows
+ Fix <application>pg_basebackup</application> output to stdout on Windows
(Haribabu Kommi)
</para>
<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>
<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>
<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>
</para>
<para>
- The <productname>PostgreSQL</> community will stop releasing updates
+ The <productname>PostgreSQL</productname> community will stop releasing updates
for the 9.2.X release series in September 2017.
Users are encouraged to update to a newer release branch soon.
</para>
<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.
<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,
<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>
<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>
<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>
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>
<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>
<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>
- Improve performance of <structname>pg_timezone_names</> view
+ Improve performance of <structname>pg_timezone_names</structname> view
(Tom Lane, David Rowley)
</para>
</listitem>
<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>
<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>
<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>
<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>
- 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
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>
<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.
<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.
<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>
</para>
<para>
- In corner cases, a spurious <quote>out-of-sequence TLI</> error
+ In corner cases, a spurious <quote>out-of-sequence TLI</quote> error
could be reported during recovery.
</para>
</listitem>
<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>
</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>
<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>
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>
<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>
<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>
<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>
<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 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>
<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>
<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>
<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>
- 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.
<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>
<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>
<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>
<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>
- 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>
<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>
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,
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>
<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)
</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
<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.
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>
<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.
<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>
<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>
<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.
<listitem>
<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>
<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>
<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>
<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>
<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>
- 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>
<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>
<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>
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.
<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>
<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>
<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>
<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>
- 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>
<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>
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>
<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>
<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>
<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>
- 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>
<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>
<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>
<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>
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
<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>
<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>
<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>
<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>
<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>
<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)
<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>
<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>
<listitem>
<para>
- Fix possible internal overflow in <type>numeric</> division
+ Fix possible internal overflow in <type>numeric</type> division
(Dean Rasheed)
</para>
</listitem>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
- 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>
- Accept <application>flex</> versions later than 2.5.x
+ Accept <application>flex</application> versions later than 2.5.x
(Tom Lane, Michael Paquier)
</para>
<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>
<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.
<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>
<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>
<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
<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>
</para>
<para>
- This substantially improves performance when <application>pg_dump</>
+ This substantially improves performance when <application>pg_dump</application>
tries to dump a large number of tables.
</para>
</listitem>
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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
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>
<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>
<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>
<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>
</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>
<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>
<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>
<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>
<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>
<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>
<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>
<listitem>
<para>
- Fix <filename>contrib/sepgsql</>'s handling of <command>SELECT INTO</>
+ Fix <filename>contrib/sepgsql</filename>'s handling of <command>SELECT INTO</command>
statements (Kohei KaiGai)
</para>
</listitem>
<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>
<listitem>
<para>
Fix memory leaks and missing out-of-memory checks
- in <application>ecpg</> (Michael Paquier)
+ in <application>ecpg</application> (Michael Paquier)
</para>
</listitem>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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.
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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
<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>
<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.
<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>
<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>
<listitem>
<para>
- Allow <application>libpq</> to use TLS protocol versions beyond v1
+ Allow <application>libpq</application> to use TLS protocol versions beyond v1
(Noah Misch)
</para>
<para>
- For a long time, <application>libpq</> was coded so that the only SSL
+ For a long time, <application>libpq</application> was coded so that the only SSL
protocol it would allow was TLS v1. Now that newer TLS versions are
becoming popular, allow it to negotiate the highest commonly-supported
- TLS version with the server. (<productname>PostgreSQL</> servers were
+ TLS version with the server. (<productname>PostgreSQL</productname> servers were
already capable of such negotiation, so no change is needed on the
server side.) This is a back-patch of a change already released in
9.4.0.
</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>
</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
</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.
<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)
<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>
<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>
<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>
<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>
<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>
<listitem>
<para>
- Avoid <quote>cannot GetMultiXactIdMembers() during recovery</> error
+ Avoid <quote>cannot GetMultiXactIdMembers() during recovery</quote> error
(Álvaro Herrera)
</para>
</listitem>
<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>
<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>
<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>
</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>
<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>
<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>
<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>
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>
<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>
<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>
<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>
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>
<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>
<listitem>
<para>
- Fix array handling in <application>ecpg</> (Michael Meskes)
+ Fix array handling in <application>ecpg</application> (Michael Meskes)
</para>
</listitem>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<listitem>
<para>
- Fix failure in <application>pg_receivexlog</> (Andres Freund)
+ Fix failure in <application>pg_receivexlog</application> (Andres Freund)
</para>
<para>
A patch merge mistake in 9.2.10 led to <quote>could not create archive
- status file</> errors.
+ status file</quote> errors.
</para>
</listitem>
<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>
<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).
<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</> 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> 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>
<para>
<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.
<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>
<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
<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.
<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>
</listitem>
<listitem>
<para>
Avoid possible data corruption if <command>ALTER DATABASE SET
- TABLESPACE</> is used to move a database to a new tablespace and then
+ TABLESPACE</command> is used to move a database to a new tablespace and then
shortly later move it back to its original tablespace (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Avoid corrupting tables when <command>ANALYZE</> inside a transaction
+ Avoid corrupting tables when <command>ANALYZE</command> inside a transaction
is rolled back (Andres Freund, Tom Lane, Michael Paquier)
</para>
<para>
If the failing transaction had earlier removed the last index, rule, or
trigger from the table, the table would be left in a corrupted state
- with the relevant <structname>pg_class</> flags not set though they
+ with the relevant <structname>pg_class</structname> flags not set though they
should be.
</para>
</listitem>
<listitem>
<para>
Ensure that unlogged tables are copied correctly
- during <command>CREATE DATABASE</> or <command>ALTER DATABASE SET
- TABLESPACE</> (Pavan Deolasee, Andres Freund)
+ during <command>CREATE DATABASE</command> or <command>ALTER DATABASE SET
+ TABLESPACE</command> (Pavan Deolasee, Andres Freund)
</para>
</listitem>
<listitem>
<para>
- Fix <command>DROP</>'s dependency searching to correctly handle the
+ Fix <command>DROP</command>'s dependency searching to correctly handle the
case where a table column is recursively visited before its table
(Petr Jelinek, Tom Lane)
</para>
<para>
This case is only known to arise when an extension creates both a
datatype and a table using that datatype. The faulty code might
- refuse a <command>DROP EXTENSION</> unless <literal>CASCADE</> is
+ refuse a <command>DROP EXTENSION</command> unless <literal>CASCADE</literal> is
specified, which should not be required.
</para>
</listitem>
</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>
<listitem>
<para>
- Fix planning of <command>SELECT FOR UPDATE</> when using a partial
+ Fix planning of <command>SELECT FOR UPDATE</command> when using a partial
index on a child table (Kyotaro Horiguchi)
</para>
<para>
- In <literal>READ COMMITTED</> mode, <command>SELECT FOR UPDATE</> must
- also recheck the partial index's <literal>WHERE</> condition when
+ In <literal>READ COMMITTED</literal> mode, <command>SELECT FOR UPDATE</command> must
+ also recheck the partial index's <literal>WHERE</literal> condition when
rechecking a recently-updated row to see if it still satisfies the
- query's <literal>WHERE</> condition. This requirement was missed if the
+ query's <literal>WHERE</literal> condition. This requirement was missed if the
index belonged to an inheritance child table, so that it was possible
to incorrectly return rows that no longer satisfy the query condition.
</para>
<listitem>
<para>
- Fix corner case wherein <command>SELECT FOR UPDATE</> could return a row
+ Fix corner case wherein <command>SELECT FOR UPDATE</command> could return a row
twice, and possibly miss returning other rows (Tom Lane)
</para>
<para>
- In <literal>READ COMMITTED</> mode, a <command>SELECT FOR UPDATE</>
+ In <literal>READ COMMITTED</literal> mode, a <command>SELECT FOR UPDATE</command>
that is scanning an inheritance tree could incorrectly return a row
from a prior child table instead of the one it should return from a
later child table.
<listitem>
<para>
Reject duplicate column names in the referenced-columns list of
- a <literal>FOREIGN KEY</> declaration (David Rowley)
+ a <literal>FOREIGN KEY</literal> declaration (David Rowley)
</para>
<para>
<listitem>
<para>
- Fix bugs in raising a <type>numeric</> value to a large integral power
+ Fix bugs in raising a <type>numeric</type> value to a large integral power
(Tom Lane)
</para>
<listitem>
<para>
- In <function>numeric_recv()</>, truncate away any fractional digits
- that would be hidden according to the value's <literal>dscale</> field
+ In <function>numeric_recv()</function>, truncate away any fractional digits
+ that would be hidden according to the value's <literal>dscale</literal> field
(Tom Lane)
</para>
<para>
- A <type>numeric</> value's display scale (<literal>dscale</>) should
+ A <type>numeric</type> value's display scale (<literal>dscale</literal>) should
never be less than the number of nonzero fractional digits; but
apparently there's at least one broken client application that
- transmits binary <type>numeric</> values in which that's true.
+ transmits binary <type>numeric</type> values in which that's true.
This leads to strange behavior since the extra digits are taken into
account by arithmetic operations even though they aren't printed.
- The least risky fix seems to be to truncate away such <quote>hidden</>
+ The least risky fix seems to be to truncate away such <quote>hidden</quote>
digits on receipt, so that the value is indeed what it prints as.
</para>
</listitem>
<para>
Matching would often fail when the number of allowed iterations is
- limited by a <literal>?</> quantifier or a bound expression.
+ limited by a <literal>?</literal> quantifier or a bound expression.
</para>
</listitem>
<listitem>
<para>
- Fix bugs in <type>tsquery</> <literal>@></> <type>tsquery</>
+ Fix bugs in <type>tsquery</type> <literal>@></literal> <type>tsquery</type>
operator (Heikki Linnakangas)
</para>
<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>
</para>
<para>
- In some contexts, constructs like <literal>row_to_json(tab.*)</> may
+ In some contexts, constructs like <literal>row_to_json(tab.*)</literal> may
not produce the expected column names. This is fixed properly as of
9.4; in older branches, just ensure that we produce some nonempty
name. (In some cases this will be the underlying table's column name
<listitem>
<para>
Fix mishandling of system columns,
- particularly <structfield>tableoid</>, in FDW queries (Etsuro Fujita)
+ particularly <structfield>tableoid</structfield>, in FDW queries (Etsuro Fujita)
</para>
</listitem>
<listitem>
<para>
- Avoid doing <literal><replaceable>indexed_column</> = ANY
- (<replaceable>array</>)</literal> as an index qualifier if that leads
+ Avoid doing <literal><replaceable>indexed_column</replaceable> = ANY
+ (<replaceable>array</replaceable>)</literal> as an index qualifier if that leads
to an inferior plan (Andrew Gierth)
</para>
<para>
- In some cases, <literal>= ANY</> conditions applied to non-first index
+ In some cases, <literal>= ANY</literal> conditions applied to non-first index
columns would be done as index conditions even though it would be
better to use them as simple filter conditions.
</para>
<listitem>
<para>
Fix planner problems with nested append relations, such as inherited
- tables within <literal>UNION ALL</> subqueries (Tom Lane)
+ tables within <literal>UNION ALL</literal> subqueries (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Exempt tables that have per-table <varname>cost_limit</>
- and/or <varname>cost_delay</> settings from autovacuum's global cost
+ Exempt tables that have per-table <varname>cost_limit</varname>
+ and/or <varname>cost_delay</varname> settings from autovacuum's global cost
balancing rules (Álvaro Herrera)
</para>
the target database, if they met the usual thresholds for
autovacuuming. This is at best pretty unexpected; at worst it delays
response to the wraparound threat. Fix it so that if autovacuum is
- turned off, workers <emphasis>only</> do anti-wraparound vacuums and
+ turned off, workers <emphasis>only</emphasis> do anti-wraparound vacuums and
not any other work.
</para>
</listitem>
<listitem>
<para>
Fix several cases where recovery logic improperly ignored WAL records
- for <literal>COMMIT/ABORT PREPARED</> (Heikki Linnakangas)
+ for <literal>COMMIT/ABORT PREPARED</literal> (Heikki Linnakangas)
</para>
<para>
The most notable oversight was
- that <varname>recovery_target_xid</> could not be used to stop at
+ that <varname>recovery_target_xid</varname> could not be used to stop at
a two-phase commit.
</para>
</listitem>
<listitem>
<para>
- Avoid creating unnecessary <filename>.ready</> marker files for
+ Avoid creating unnecessary <filename>.ready</filename> marker files for
timeline history files (Fujii Masao)
</para>
</listitem>
<listitem>
<para>
Fix possible null pointer dereference when an empty prepared statement
- is used and the <varname>log_statement</> setting is <literal>mod</>
- or <literal>ddl</> (Fujii Masao)
+ is used and the <varname>log_statement</varname> setting is <literal>mod</literal>
+ or <literal>ddl</literal> (Fujii Masao)
</para>
</listitem>
<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>
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>
<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>
<listitem>
<para>
- Fix processing of repeated <literal>dbname</> parameters
- in <function>PQconnectdbParams()</> (Alex Shulgin)
+ Fix processing of repeated <literal>dbname</literal> parameters
+ in <function>PQconnectdbParams()</function> (Alex Shulgin)
</para>
<para>
Unexpected behavior ensued if the first occurrence
- of <literal>dbname</> contained a connection string or URI to be
+ of <literal>dbname</literal> contained a connection string or URI to be
expanded.
</para>
</listitem>
<listitem>
<para>
- Ensure that <application>libpq</> reports a suitable error message on
+ Ensure that <application>libpq</application> reports a suitable error message on
unexpected socket EOF (Marko Tiikkaja, Tom Lane)
</para>
<para>
- Depending on kernel behavior, <application>libpq</> might return an
+ Depending on kernel behavior, <application>libpq</application> might return an
empty error string rather than something useful when the server
unexpectedly closed the socket.
</para>
<listitem>
<para>
- Clear any old error message during <function>PQreset()</>
+ Clear any old error message during <function>PQreset()</function>
(Heikki Linnakangas)
</para>
<para>
- If <function>PQreset()</> is called repeatedly, and the connection
+ If <function>PQreset()</function> is called repeatedly, and the connection
cannot be re-established, error messages from the failed connection
- attempts kept accumulating in the <structname>PGconn</>'s error
+ attempts kept accumulating in the <structname>PGconn</structname>'s error
string.
</para>
</listitem>
<listitem>
<para>
Properly handle out-of-memory conditions while parsing connection
- options in <application>libpq</> (Alex Shulgin, Heikki Linnakangas)
+ options in <application>libpq</application> (Alex Shulgin, Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Fix array overrun in <application>ecpg</>'s version
- of <function>ParseDateTime()</> (Michael Paquier)
+ Fix array overrun in <application>ecpg</application>'s version
+ of <function>ParseDateTime()</function> (Michael Paquier)
</para>
</listitem>
<listitem>
<para>
- In <application>initdb</>, give a clearer error message if a password
+ In <application>initdb</application>, give a clearer error message if a password
file is specified but is empty (Mats Erik Andersson)
</para>
</listitem>
<listitem>
<para>
- Fix <application>psql</>'s <command>\s</> command to work nicely with
+ Fix <application>psql</application>'s <command>\s</command> command to work nicely with
libedit, and add pager support (Stepan Rutz, Tom Lane)
</para>
<para>
- When using libedit rather than readline, <command>\s</> printed the
+ When using libedit rather than readline, <command>\s</command> printed the
command history in a fairly unreadable encoded format, and on recent
libedit versions might fail altogether. Fix that by printing the
history ourselves rather than having the library do it. A pleasant
<para>
This patch also fixes a bug that caused newline encoding to be applied
inconsistently when saving the command history with libedit.
- Multiline history entries written by older <application>psql</>
+ Multiline history entries written by older <application>psql</application>
versions will be read cleanly with this patch, but perhaps not
vice versa, depending on the exact libedit versions involved.
</para>
<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>
<listitem>
<para>
- Fix <application>psql</>'s expanded-mode display to work
- consistently when using <literal>border</> = 3
- and <literal>linestyle</> = <literal>ascii</> or <literal>unicode</>
+ Fix <application>psql</application>'s expanded-mode display to work
+ consistently when using <literal>border</literal> = 3
+ and <literal>linestyle</literal> = <literal>ascii</literal> or <literal>unicode</literal>
(Stephen Frost)
</para>
</listitem>
<listitem>
<para>
- Improve performance of <application>pg_dump</> when the database
+ Improve performance of <application>pg_dump</application> when the database
contains many instances of multiple dependency paths between the same
two objects (Tom Lane)
</para>
<listitem>
<para>
- Fix <application>pg_dumpall</> to restore its ability to dump from
+ Fix <application>pg_dumpall</application> to restore its ability to dump from
pre-8.1 servers (Gilles Darold)
</para>
</listitem>
<listitem>
<para>
- Fix core dump in <literal>pg_dump --binary-upgrade</> on zero-column
+ Fix core dump in <literal>pg_dump --binary-upgrade</literal> on zero-column
composite type (Rushabh Lathia)
</para>
</listitem>
<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>
<listitem>
<para>
- Fix failure of <filename>contrib/auto_explain</> to print per-node
- timing information when doing <command>EXPLAIN ANALYZE</> (Tom Lane)
+ Fix failure of <filename>contrib/auto_explain</filename> to print per-node
+ timing information when doing <command>EXPLAIN ANALYZE</command> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix upgrade-from-unpackaged script for <filename>contrib/citext</>
+ Fix upgrade-from-unpackaged script for <filename>contrib/citext</filename>
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix block number checking
- in <filename>contrib/pageinspect</>'s <function>get_raw_page()</>
+ in <filename>contrib/pageinspect</filename>'s <function>get_raw_page()</function>
(Tom Lane)
</para>
<listitem>
<para>
- Fix <filename>contrib/pgcrypto</>'s <function>pgp_sym_decrypt()</>
+ Fix <filename>contrib/pgcrypto</filename>'s <function>pgp_sym_decrypt()</function>
to not fail on messages whose length is 6 less than a power of 2
(Marko Tiikkaja)
</para>
<listitem>
<para>
- Fix file descriptor leak in <filename>contrib/pg_test_fsync</>
+ Fix file descriptor leak in <filename>contrib/pg_test_fsync</filename>
(Jeff Janes)
</para>
<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>
<listitem>
<para>
- Avoid a possible crash in <filename>contrib/xml2</>'s
- <function>xslt_process()</> (Mark Simonetti)
+ Avoid a possible crash in <filename>contrib/xml2</filename>'s
+ <function>xslt_process()</function> (Mark Simonetti)
</para>
<para>
- <application>libxslt</> seems to have an undocumented dependency on
+ <application>libxslt</application> seems to have an undocumented dependency on
the order in which resources are freed; reorder our calls to avoid a
crash.
</para>
<listitem>
<para>
- Mark some <filename>contrib</> I/O functions with correct volatility
+ Mark some <filename>contrib</filename> I/O functions with correct volatility
properties (Tom Lane)
</para>
<para>
With OpenLDAP versions 2.4.24 through 2.4.31,
- inclusive, <productname>PostgreSQL</> backends can crash at exit.
- Raise a warning during <application>configure</> based on the
+ inclusive, <productname>PostgreSQL</productname> backends can crash at exit.
+ Raise a warning during <application>configure</application> based on the
compile-time OpenLDAP version number, and test the crashing scenario
- in the <filename>contrib/dblink</> regression test.
+ in the <filename>contrib/dblink</filename> regression test.
</para>
</listitem>
<listitem>
<para>
- In non-MSVC Windows builds, ensure <filename>libpq.dll</> is installed
+ In non-MSVC Windows builds, ensure <filename>libpq.dll</filename> is installed
with execute permissions (Noah Misch)
</para>
</listitem>
<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>
</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>
<para>
Add CST (China Standard Time) to our lists.
- Remove references to ADT as <quote>Arabia Daylight Time</>, an
+ Remove references to ADT as <quote>Arabia Daylight Time</quote>, an
abbreviation that's been out of use since 2007; therefore, claiming
- there is a conflict with <quote>Atlantic Daylight Time</> doesn't seem
+ there is a conflict with <quote>Atlantic Daylight Time</quote> doesn't seem
especially helpful.
Fix entirely incorrect GMT offsets for CKT (Cook Islands), FJT, and FJST
(Fiji); we didn't even have them on the proper side of the date line.
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2015a.
+ Update time zone data files to <application>tzdata</application> release 2015a.
</para>
<para>
The IANA timezone database has adopted abbreviations of the form
- <literal>A<replaceable>x</>ST</literal>/<literal>A<replaceable>x</>DT</literal>
+ <literal>A<replaceable>x</replaceable>ST</literal>/<literal>A<replaceable>x</replaceable>DT</literal>
for all Australian time zones, reflecting what they believe to be
current majority practice Down Under. These names do not conflict
with usage elsewhere (other than ACST for Acre Summer Time, which has
been in disuse since 1994). Accordingly, adopt these names into
- our <quote>Default</> timezone abbreviation set.
- The <quote>Australia</> abbreviation set now contains only CST, EAST,
+ our <quote>Default</quote> timezone abbreviation set.
+ The <quote>Australia</quote> abbreviation set now contains only CST, EAST,
EST, SAST, SAT, and WST, all of which are thought to be mostly
historical usage. Note that SAST has also been changed to be South
- Africa Standard Time in the <quote>Default</> abbreviation set.
+ Africa Standard Time in the <quote>Default</quote> abbreviation set.
</para>
<para>
<listitem>
<para>
- Correctly initialize padding bytes in <filename>contrib/btree_gist</>
- indexes on <type>bit</> columns (Heikki Linnakangas)
+ Correctly initialize padding bytes in <filename>contrib/btree_gist</filename>
+ indexes on <type>bit</type> columns (Heikki Linnakangas)
</para>
<para>
This error could result in incorrect query results due to values that
should compare equal not being seen as equal.
- Users with GiST indexes on <type>bit</> or <type>bit varying</>
- columns should <command>REINDEX</> those indexes after installing this
+ Users with GiST indexes on <type>bit</type> or <type>bit varying</type>
+ columns should <command>REINDEX</command> those indexes after installing this
update.
</para>
</listitem>
<listitem>
<para>
Fix possibly-incorrect cache invalidation during nested calls
- to <function>ReceiveSharedInvalidMessages</> (Andres Freund)
+ to <function>ReceiveSharedInvalidMessages</function> (Andres Freund)
</para>
</listitem>
<para>
This oversight could result in <quote>variable not found in subplan
- target lists</> errors, or in silently wrong query results.
+ target lists</quote> errors, or in silently wrong query results.
</para>
</listitem>
<listitem>
<para>
- Fix <quote>could not find pathkey item to sort</> planner failures
- with <literal>UNION ALL</> over subqueries reading from tables with
+ Fix <quote>could not find pathkey item to sort</quote> planner failures
+ with <literal>UNION ALL</literal> over subqueries reading from tables with
inheritance children (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Improve planner to drop constant-NULL inputs
- of <literal>AND</>/<literal>OR</> when possible (Tom Lane)
+ of <literal>AND</literal>/<literal>OR</literal> when possible (Tom Lane)
</para>
<para>
<listitem>
<para>
- Fix identification of input type category in <function>to_json()</>
+ Fix identification of input type category in <function>to_json()</function>
and friends (Tom Lane)
</para>
<para>
- This is known to have led to inadequate quoting of <type>money</>
- fields in the <type>JSON</> result, and there may have been wrong
+ This is known to have led to inadequate quoting of <type>money</type>
+ fields in the <type>JSON</type> result, and there may have been wrong
results for other data types as well.
</para>
</listitem>
This corrects cases where TOAST pointers could be copied into other
tables without being dereferenced. If the original data is later
deleted, it would lead to errors like <quote>missing chunk number 0
- for toast value ...</> when the now-dangling pointer is used.
+ for toast value ...</quote> when the now-dangling pointer is used.
</para>
</listitem>
<listitem>
<para>
- Fix <quote>record type has not been registered</> failures with
+ Fix <quote>record type has not been registered</quote> failures with
whole-row references to the output of Append plan nodes (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix query-lifespan memory leak while evaluating the arguments for a
- function in <literal>FROM</> (Tom Lane)
+ function in <literal>FROM</literal> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix data encoding error in <filename>hungarian.stop</> (Tom Lane)
+ Fix data encoding error in <filename>hungarian.stop</filename> (Tom Lane)
</para>
</listitem>
<para>
This could cause problems (at least spurious warnings, and at worst an
- infinite loop) if <command>CREATE INDEX</> or <command>CLUSTER</> were
+ infinite loop) if <command>CREATE INDEX</command> or <command>CLUSTER</command> were
done later in the same transaction.
</para>
</listitem>
<listitem>
<para>
- Clear <structname>pg_stat_activity</>.<structfield>xact_start</>
- during <command>PREPARE TRANSACTION</> (Andres Freund)
+ Clear <structname>pg_stat_activity</structname>.<structfield>xact_start</structfield>
+ during <command>PREPARE TRANSACTION</command> (Andres Freund)
</para>
<para>
- After the <command>PREPARE</>, the originating session is no longer in
+ After the <command>PREPARE</command>, the originating session is no longer in
a transaction, so it should not continue to display a transaction
start time.
</para>
<listitem>
<para>
- Fix <command>REASSIGN OWNED</> to not fail for text search objects
+ Fix <command>REASSIGN OWNED</command> to not fail for text search objects
(Álvaro Herrera)
</para>
</listitem>
<para>
This ensures that the postmaster will properly clean up after itself
- if, for example, it receives <systemitem>SIGINT</> while still
+ if, for example, it receives <systemitem>SIGINT</systemitem> while still
starting up.
</para>
</listitem>
<listitem>
<para>
- Fix client host name lookup when processing <filename>pg_hba.conf</>
+ Fix client host name lookup when processing <filename>pg_hba.conf</filename>
entries that specify host names instead of IP addresses (Tom Lane)
</para>
<listitem>
<para>
- Allow the root user to use <literal>postgres -C variable</> and
- <literal>postgres --describe-config</> (MauMau)
+ Allow the root user to use <literal>postgres -C variable</literal> and
+ <literal>postgres --describe-config</literal> (MauMau)
</para>
<para>
The prohibition on starting the server as root does not need to extend
to these operations, and relaxing it prevents failure
- of <application>pg_ctl</> in some scenarios.
+ of <application>pg_ctl</application> in some scenarios.
</para>
</listitem>
<listitem>
<para>
Secure Unix-domain sockets of temporary postmasters started during
- <literal>make check</> (Noah Misch)
+ <literal>make check</literal> (Noah Misch)
</para>
<para>
the operating-system user running the test, as we previously noted in
CVE-2014-0067. This change defends against that risk by placing the
server's socket in a temporary, mode 0700 subdirectory
- of <filename>/tmp</>. The hazard remains however on platforms where
+ of <filename>/tmp</filename>. The hazard remains however on platforms where
Unix sockets are not supported, notably Windows, because then the
temporary postmaster must accept local TCP connections.
</para>
<para>
A useful side effect of this change is to simplify
- <literal>make check</> testing in builds that
- override <literal>DEFAULT_PGSOCKET_DIR</>. Popular non-default values
- like <filename>/var/run/postgresql</> are often not writable by the
+ <literal>make check</literal> testing in builds that
+ override <literal>DEFAULT_PGSOCKET_DIR</literal>. Popular non-default values
+ like <filename>/var/run/postgresql</filename> are often not writable by the
build user, requiring workarounds that will no longer be necessary.
</para>
</listitem>
</para>
<para>
- This oversight could cause <application>initdb</>
- and <application>pg_upgrade</> to fail on Windows, if the installation
- path contained both spaces and <literal>@</> signs.
+ This oversight could cause <application>initdb</application>
+ and <application>pg_upgrade</application> to fail on Windows, if the installation
+ path contained both spaces and <literal>@</literal> signs.
</para>
</listitem>
<listitem>
<para>
- Fix linking of <application>libpython</> on macOS (Tom Lane)
+ Fix linking of <application>libpython</application> on macOS (Tom Lane)
</para>
<para>
<listitem>
<para>
- Avoid buffer bloat in <application>libpq</> when the server
+ Avoid buffer bloat in <application>libpq</application> when the server
consistently sends data faster than the client can absorb it
(Shin-ichi Morita, Tom Lane)
</para>
<para>
- <application>libpq</> could be coerced into enlarging its input buffer
+ <application>libpq</application> could be coerced into enlarging its input buffer
until it runs out of memory (which would be reported misleadingly
- as <quote>lost synchronization with server</>). Under ordinary
+ as <quote>lost synchronization with server</quote>). Under ordinary
circumstances it's quite far-fetched that data could be continuously
- transmitted more quickly than the <function>recv()</> loop can
+ transmitted more quickly than the <function>recv()</function> loop can
absorb it, but this has been observed when the client is artificially
slowed by scheduler constraints.
</para>
<listitem>
<para>
- Ensure that LDAP lookup attempts in <application>libpq</> time out as
+ Ensure that LDAP lookup attempts in <application>libpq</application> time out as
intended (Laurenz Albe)
</para>
</listitem>
<listitem>
<para>
- Fix <application>ecpg</> to do the right thing when an array
- of <type>char *</> is the target for a FETCH statement returning more
+ Fix <application>ecpg</application> to do the right thing when an array
+ of <type>char *</type> is the target for a FETCH statement returning more
than one row, as well as some other array-handling fixes
(Ashutosh Bapat)
</para>
<listitem>
<para>
- Fix <application>pg_restore</>'s processing of old-style large object
+ Fix <application>pg_restore</application>'s processing of old-style large object
comments (Tom Lane)
</para>
<para>
A direct-to-database restore from an archive file generated by a
- pre-9.0 version of <application>pg_dump</> would usually fail if the
+ pre-9.0 version of <application>pg_dump</application> would usually fail if the
archive contained more than a few comments for large objects.
</para>
</listitem>
<listitem>
<para>
- Fix <application>pg_upgrade</> for cases where the new server creates
+ Fix <application>pg_upgrade</application> for cases where the new server creates
a TOAST table but the old version did not (Bruce Momjian)
</para>
<para>
- This rare situation would manifest as <quote>relation OID mismatch</>
+ This rare situation would manifest as <quote>relation OID mismatch</quote>
errors.
</para>
</listitem>
<listitem>
<para>
- Prevent <filename>contrib/auto_explain</> from changing the output of
- a user's <command>EXPLAIN</> (Tom Lane)
+ Prevent <filename>contrib/auto_explain</filename> from changing the output of
+ a user's <command>EXPLAIN</command> (Tom Lane)
</para>
<para>
- If <filename>auto_explain</> is active, it could cause
- an <literal>EXPLAIN (ANALYZE, TIMING OFF)</> command to nonetheless
+ If <filename>auto_explain</filename> is active, it could cause
+ an <literal>EXPLAIN (ANALYZE, TIMING OFF)</literal> command to nonetheless
print timing information.
</para>
</listitem>
<listitem>
<para>
- Fix query-lifespan memory leak in <filename>contrib/dblink</>
+ Fix query-lifespan memory leak in <filename>contrib/dblink</filename>
(MauMau, Joe Conway)
</para>
</listitem>
<listitem>
<para>
- In <filename>contrib/pgcrypto</> functions, ensure sensitive
+ In <filename>contrib/pgcrypto</filename> functions, ensure sensitive
information is cleared from stack variables before returning
(Marko Kreen)
</para>
<listitem>
<para>
Prevent use of already-freed memory in
- <filename>contrib/pgstattuple</>'s <function>pgstat_heap()</>
+ <filename>contrib/pgstattuple</filename>'s <function>pgstat_heap()</function>
(Noah Misch)
</para>
</listitem>
<listitem>
<para>
- In <filename>contrib/uuid-ossp</>, cache the state of the OSSP UUID
+ In <filename>contrib/uuid-ossp</filename>, cache the state of the OSSP UUID
library across calls (Tom Lane)
</para>
<para>
This improves the efficiency of UUID generation and reduces the amount
- of entropy drawn from <filename>/dev/urandom</>, on platforms that
+ of entropy drawn from <filename>/dev/urandom</filename>, on platforms that
have that.
</para>
</listitem>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2014e
+ Update time zone data files to <application>tzdata</application> release 2014e
for DST law changes in Crimea, Egypt, and Morocco.
</para>
</listitem>
<listitem>
<para>
Avoid race condition in checking transaction commit status during
- receipt of a <command>NOTIFY</> message (Marko Tiikkaja)
+ receipt of a <command>NOTIFY</command> message (Marko Tiikkaja)
</para>
<para>
<listitem>
<para>
- Remove incorrect code that tried to allow <literal>OVERLAPS</> with
+ Remove incorrect code that tried to allow <literal>OVERLAPS</literal> with
single-element row arguments (Joshua Yanovski)
</para>
<listitem>
<para>
- Avoid getting more than <literal>AccessShareLock</> when de-parsing a
+ Avoid getting more than <literal>AccessShareLock</literal> when de-parsing a
rule or view (Dean Rasheed)
</para>
<para>
- This oversight resulted in <application>pg_dump</> unexpectedly
- acquiring <literal>RowExclusiveLock</> locks on tables mentioned as
- the targets of <literal>INSERT</>/<literal>UPDATE</>/<literal>DELETE</>
+ This oversight resulted in <application>pg_dump</application> unexpectedly
+ acquiring <literal>RowExclusiveLock</literal> locks on tables mentioned as
+ the targets of <literal>INSERT</literal>/<literal>UPDATE</literal>/<literal>DELETE</literal>
commands in rules. While usually harmless, that could interfere with
concurrent transactions that tried to acquire, for example,
- <literal>ShareLock</> on those tables.
+ <literal>ShareLock</literal> on those tables.
</para>
</listitem>
<listitem>
<para>
- Fix <application>walsender</>'s failure to shut down cleanly when client
- is <application>pg_receivexlog</> (Fujii Masao)
+ Fix <application>walsender</application>'s failure to shut down cleanly when client
+ is <application>pg_receivexlog</application> (Fujii Masao)
</para>
</listitem>
<listitem>
<para>
- Prevent interrupts while reporting non-<literal>ERROR</> messages
+ Prevent interrupts while reporting non-<literal>ERROR</literal> messages
(Tom Lane)
</para>
<para>
This guards against rare server-process freezeups due to recursive
- entry to <function>syslog()</>, and perhaps other related problems.
+ entry to <function>syslog()</function>, and perhaps other related problems.
</para>
</listitem>
<listitem>
<para>
- Fix tracking of <application>psql</> script line numbers
- during <literal>\copy</> from out-of-line data
+ Fix tracking of <application>psql</application> script line numbers
+ during <literal>\copy</literal> from out-of-line data
(Kumar Rajeev Rastogi, Amit Khandekar)
</para>
<para>
- <literal>\copy ... from</> incremented the script file line number
+ <literal>\copy ... from</literal> incremented the script file line number
for each data line, even if the data was not coming from the script
file. This mistake resulted in wrong line numbers being reported for
any errors occurring later in the same script file.
<listitem>
<para>
- Prevent intermittent <quote>could not reserve shared memory region</>
+ Prevent intermittent <quote>could not reserve shared memory region</quote>
failures on recent Windows versions (MauMau)
</para>
</listitem>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2014a
+ Update time zone data files to <application>tzdata</application> release 2014a
for DST law changes in Fiji and Turkey, plus historical changes in
Israel and Ukraine.
</para>
<listitem>
<para>
- Shore up <literal>GRANT ... WITH ADMIN OPTION</> restrictions
+ Shore up <literal>GRANT ... WITH ADMIN OPTION</literal> restrictions
(Noah Misch)
</para>
<para>
- Granting a role without <literal>ADMIN OPTION</> is supposed to
+ Granting a role without <literal>ADMIN OPTION</literal> is supposed to
prevent the grantee from adding or removing members from the granted
role, but this restriction was easily bypassed by doing <literal>SET
- ROLE</> first. The security impact is mostly that a role member can
+ ROLE</literal> first. The security impact is mostly that a role member can
revoke the access of others, contrary to the wishes of his grantor.
Unapproved role member additions are a lesser concern, since an
uncooperative role member could provide most of his rights to others
- anyway by creating views or <literal>SECURITY DEFINER</> functions.
+ anyway by creating views or <literal>SECURITY DEFINER</literal> functions.
(CVE-2014-0060)
</para>
</listitem>
<para>
The primary role of PL validator functions is to be called implicitly
- during <command>CREATE FUNCTION</>, but they are also normal SQL
+ during <command>CREATE FUNCTION</command>, but they are also normal SQL
functions that a user can call explicitly. Calling a validator on
a function actually written in some other language was not checked
for and could be exploited for privilege-escalation purposes.
<para>
If the name lookups come to different conclusions due to concurrent
activity, we might perform some parts of the DDL on a different table
- than other parts. At least in the case of <command>CREATE INDEX</>,
+ than other parts. At least in the case of <command>CREATE INDEX</command>,
this can be used to cause the permissions checks to be performed
against a different table than the index creation, allowing for a
privilege escalation attack.
</para>
<para>
- The <literal>MAXDATELEN</> constant was too small for the longest
- possible value of type <type>interval</>, allowing a buffer overrun
- in <function>interval_out()</>. Although the datetime input
+ The <literal>MAXDATELEN</literal> constant was too small for the longest
+ possible value of type <type>interval</type>, allowing a buffer overrun
+ in <function>interval_out()</function>. Although the datetime input
functions were more careful about avoiding buffer overrun, the limit
was short enough to cause them to reject some valid inputs, such as
- input containing a very long timezone name. The <application>ecpg</>
+ input containing a very long timezone name. The <application>ecpg</application>
library contained these vulnerabilities along with some of its own.
(CVE-2014-0063)
</para>
</para>
<para>
- Use <function>strlcpy()</> and related functions to provide a clear
+ Use <function>strlcpy()</function> and related functions to provide a clear
guarantee that fixed-size buffers are not overrun. Unlike the
preceding items, it is unclear whether these cases really represent
live issues, since in most cases there appear to be previous
<listitem>
<para>
- Avoid crashing if <function>crypt()</> returns NULL (Honza Horak,
+ Avoid crashing if <function>crypt()</function> returns NULL (Honza Horak,
Bruce Momjian)
</para>
<para>
- There are relatively few scenarios in which <function>crypt()</>
- could return NULL, but <filename>contrib/chkpass</> would crash
+ There are relatively few scenarios in which <function>crypt()</function>
+ could return NULL, but <filename>contrib/chkpass</filename> would crash
if it did. One practical case in which this could be an issue is
- if <application>libc</> is configured to refuse to execute unapproved
- hashing algorithms (e.g., <quote>FIPS mode</>).
+ if <application>libc</application> is configured to refuse to execute unapproved
+ hashing algorithms (e.g., <quote>FIPS mode</quote>).
(CVE-2014-0066)
</para>
</listitem>
<listitem>
<para>
- Document risks of <literal>make check</> in the regression testing
+ Document risks of <literal>make check</literal> in the regression testing
instructions (Noah Misch, Tom Lane)
</para>
<para>
- Since the temporary server started by <literal>make check</>
- uses <quote>trust</> authentication, another user on the same machine
+ Since the temporary server started by <literal>make check</literal>
+ uses <quote>trust</quote> authentication, another user on the same machine
could connect to it as database superuser, and then potentially
exploit the privileges of the operating-system user who started the
tests. A future release will probably incorporate changes in the
testing procedure to prevent this risk, but some public discussion is
needed first. So for the moment, just warn people against using
- <literal>make check</> when there are untrusted users on the
+ <literal>make check</literal> when there are untrusted users on the
same machine.
(CVE-2014-0067)
</para>
<para>
The WAL update could be applied to the wrong page, potentially many
pages past where it should have been. Aside from corrupting data,
- this error has been observed to result in significant <quote>bloat</>
+ this error has been observed to result in significant <quote>bloat</quote>
of standby servers compared to their masters, due to updates being
applied far beyond where the end-of-file should have been. This
failure mode does not appear to be a significant risk during crash
was already consistent at the start of replay, thus possibly allowing
hot-standby queries before the database was really consistent. Other
symptoms such as <quote>PANIC: WAL contains references to invalid
- pages</> were also possible.
+ pages</quote> were also possible.
</para>
</listitem>
<listitem>
<para>
Fix improper locking of btree index pages while replaying
- a <literal>VACUUM</> operation in hot-standby mode (Andres Freund,
+ a <literal>VACUUM</literal> operation in hot-standby mode (Andres Freund,
Heikki Linnakangas, Tom Lane)
</para>
<para>
This error could result in <quote>PANIC: WAL contains references to
- invalid pages</> failures.
+ invalid pages</quote> failures.
</para>
</listitem>
<listitem>
<para>
- When <literal>pause_at_recovery_target</>
- and <literal>recovery_target_inclusive</> are both set, ensure the
+ When <literal>pause_at_recovery_target</literal>
+ and <literal>recovery_target_inclusive</literal> are both set, ensure the
target record is applied before pausing, not after (Heikki
Linnakangas)
</para>
<para>
Ensure that signal handlers don't attempt to use the
- process's <varname>MyProc</> pointer after it's no longer valid.
+ process's <varname>MyProc</varname> pointer after it's no longer valid.
</para>
</listitem>
<listitem>
<para>
- Fix unsafe references to <varname>errno</> within error reporting
+ Fix unsafe references to <varname>errno</varname> within error reporting
logic (Christian Kruse)
</para>
<para>
This would typically lead to odd behaviors such as missing or
- inappropriate <literal>HINT</> fields.
+ inappropriate <literal>HINT</literal> fields.
</para>
</listitem>
<listitem>
<para>
- Fix possible crashes from using <function>ereport()</> too early
+ Fix possible crashes from using <function>ereport()</function> too early
during server startup (Tom Lane)
</para>
<listitem>
<para>
- Fix length checking for Unicode identifiers (<literal>U&"..."</>
+ Fix length checking for Unicode identifiers (<literal>U&"..."</literal>
syntax) containing escapes (Tom Lane)
</para>
<para>
A previous patch allowed such keywords to be used without quoting
in places such as role identifiers; but it missed cases where a
- list of role identifiers was permitted, such as <literal>DROP ROLE</>.
+ list of role identifiers was permitted, such as <literal>DROP ROLE</literal>.
</para>
</listitem>
<listitem>
<para>
Fix possible crash due to invalid plan for nested sub-selects, such
- as <literal>WHERE (... x IN (SELECT ...) ...) IN (SELECT ...)</>
+ as <literal>WHERE (... x IN (SELECT ...) ...) IN (SELECT ...)</literal>
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix <literal>UPDATE/DELETE</> of an inherited target table
- that has <literal>UNION ALL</> subqueries (Tom Lane)
+ Fix <literal>UPDATE/DELETE</literal> of an inherited target table
+ that has <literal>UNION ALL</literal> subqueries (Tom Lane)
</para>
<para>
- Without this fix, <literal>UNION ALL</> subqueries aren't correctly
+ Without this fix, <literal>UNION ALL</literal> subqueries aren't correctly
inserted into the update plans for inheritance child tables after the
first one, typically resulting in no update happening for those child
table(s).
<listitem>
<para>
- Ensure that <command>ANALYZE</> creates statistics for a table column
- even when all the values in it are <quote>too wide</> (Tom Lane)
+ Ensure that <command>ANALYZE</command> creates statistics for a table column
+ even when all the values in it are <quote>too wide</quote> (Tom Lane)
</para>
<para>
- <command>ANALYZE</> intentionally omits very wide values from its
+ <command>ANALYZE</command> intentionally omits very wide values from its
histogram and most-common-values calculations, but it neglected to do
something sane in the case that all the sampled entries are too wide.
</para>
<listitem>
<para>
- In <literal>ALTER TABLE ... SET TABLESPACE</>, allow the database's
+ In <literal>ALTER TABLE ... SET TABLESPACE</literal>, allow the database's
default tablespace to be used without a permissions check
(Stephen Frost)
</para>
<para>
- <literal>CREATE TABLE</> has always allowed such usage,
- but <literal>ALTER TABLE</> didn't get the memo.
+ <literal>CREATE TABLE</literal> has always allowed such usage,
+ but <literal>ALTER TABLE</literal> didn't get the memo.
</para>
</listitem>
<listitem>
<para>
- Fix <quote>cannot accept a set</> error when some arms of
- a <literal>CASE</> return a set and others don't (Tom Lane)
+ Fix <quote>cannot accept a set</quote> error when some arms of
+ a <literal>CASE</literal> return a set and others don't (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix possible misbehavior in <function>plainto_tsquery()</>
+ Fix possible misbehavior in <function>plainto_tsquery()</function>
(Heikki Linnakangas)
</para>
<para>
- Use <function>memmove()</> not <function>memcpy()</> for copying
+ Use <function>memmove()</function> not <function>memcpy()</function> for copying
overlapping memory regions. There have been no field reports of
this actually causing trouble, but it's certainly risky.
</para>
<listitem>
<para>
- Fix placement of permissions checks in <function>pg_start_backup()</>
- and <function>pg_stop_backup()</> (Andres Freund, Magnus Hagander)
+ Fix placement of permissions checks in <function>pg_start_backup()</function>
+ and <function>pg_stop_backup()</function> (Andres Freund, Magnus Hagander)
</para>
<para>
<listitem>
<para>
- Accept <literal>SHIFT_JIS</> as an encoding name for locale checking
+ Accept <literal>SHIFT_JIS</literal> as an encoding name for locale checking
purposes (Tatsuo Ishii)
</para>
</listitem>
<listitem>
<para>
- Fix <literal>*</>-qualification of named parameters in SQL-language
+ Fix <literal>*</literal>-qualification of named parameters in SQL-language
functions (Tom Lane)
</para>
<para>
Given a composite-type parameter
- named <literal>foo</>, <literal>$1.*</> worked fine,
- but <literal>foo.*</> not so much.
+ named <literal>foo</literal>, <literal>$1.*</literal> worked fine,
+ but <literal>foo.*</literal> not so much.
</para>
</listitem>
<listitem>
<para>
- Fix misbehavior of <function>PQhost()</> on Windows (Fujii Masao)
+ Fix misbehavior of <function>PQhost()</function> on Windows (Fujii Masao)
</para>
<para>
- It should return <literal>localhost</> if no host has been specified.
+ It should return <literal>localhost</literal> if no host has been specified.
</para>
</listitem>
<listitem>
<para>
- Improve error handling in <application>libpq</> and <application>psql</>
- for failures during <literal>COPY TO STDOUT/FROM STDIN</> (Tom Lane)
+ Improve error handling in <application>libpq</application> and <application>psql</application>
+ for failures during <literal>COPY TO STDOUT/FROM STDIN</literal> (Tom Lane)
</para>
<para>
In particular this fixes an infinite loop that could occur in 9.2 and
up if the server connection was lost during <literal>COPY FROM
- STDIN</>. Variants of that scenario might be possible in older
+ STDIN</literal>. Variants of that scenario might be possible in older
versions, or with other client applications.
</para>
</listitem>
<listitem>
<para>
Fix incorrect translation handling in
- some <application>psql</> <literal>\d</> commands
+ some <application>psql</application> <literal>\d</literal> commands
(Peter Eisentraut, Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Ensure <application>pg_basebackup</>'s background process is killed
+ Ensure <application>pg_basebackup</application>'s background process is killed
when exiting its foreground process (Magnus Hagander)
</para>
</listitem>
<listitem>
<para>
Fix possible incorrect printing of filenames
- in <application>pg_basebackup</>'s verbose mode (Magnus Hagander)
+ in <application>pg_basebackup</application>'s verbose mode (Magnus Hagander)
</para>
</listitem>
<listitem>
<para>
- Fix misaligned descriptors in <application>ecpg</> (MauMau)
+ Fix misaligned descriptors in <application>ecpg</application> (MauMau)
</para>
</listitem>
<listitem>
<para>
- In <application>ecpg</>, handle lack of a hostname in the connection
+ In <application>ecpg</application>, handle lack of a hostname in the connection
parameters properly (Michael Meskes)
</para>
</listitem>
<listitem>
<para>
- Fix performance regression in <filename>contrib/dblink</> connection
+ Fix performance regression in <filename>contrib/dblink</filename> connection
startup (Joe Conway)
</para>
<listitem>
<para>
- In <filename>contrib/isn</>, fix incorrect calculation of the check
+ In <filename>contrib/isn</filename>, fix incorrect calculation of the check
digit for ISMN values (Fabien Coelho)
</para>
</listitem>
<listitem>
<para>
- Fix <filename>contrib/pg_stat_statement</>'s handling
- of <literal>CURRENT_DATE</> and related constructs (Kyotaro
+ Fix <filename>contrib/pg_stat_statement</filename>'s handling
+ of <literal>CURRENT_DATE</literal> and related constructs (Kyotaro
Horiguchi)
</para>
</listitem>
<listitem>
<para>
- In Mingw and Cygwin builds, install the <application>libpq</> DLL
- in the <filename>bin</> directory (Andrew Dunstan)
+ In Mingw and Cygwin builds, install the <application>libpq</application> DLL
+ in the <filename>bin</filename> directory (Andrew Dunstan)
</para>
<para>
This duplicates what the MSVC build has long done. It should fix
- problems with programs like <application>psql</> failing to start
+ problems with programs like <application>psql</application> failing to start
because they can't find the DLL.
</para>
</listitem>
<listitem>
<para>
- Avoid using the deprecated <literal>dllwrap</> tool in Cygwin builds
+ Avoid using the deprecated <literal>dllwrap</literal> tool in Cygwin builds
(Marco Atzeri)
</para>
</listitem>
<listitem>
<para>
- Don't generate plain-text <filename>HISTORY</>
- and <filename>src/test/regress/README</> files anymore (Tom Lane)
+ Don't generate plain-text <filename>HISTORY</filename>
+ and <filename>src/test/regress/README</filename> files anymore (Tom Lane)
</para>
<para>
the likely audience for plain-text format. Distribution tarballs
will still contain files by these names, but they'll just be stubs
directing the reader to consult the main documentation.
- The plain-text <filename>INSTALL</> file will still be maintained, as
+ The plain-text <filename>INSTALL</filename> file will still be maintained, as
there is arguably a use-case for that.
</para>
</listitem>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2013i
+ Update time zone data files to <application>tzdata</application> release 2013i
for DST law changes in Jordan and historical changes in Cuba.
</para>
<para>
- In addition, the zones <literal>Asia/Riyadh87</>,
- <literal>Asia/Riyadh88</>, and <literal>Asia/Riyadh89</> have been
+ In addition, the zones <literal>Asia/Riyadh87</literal>,
+ <literal>Asia/Riyadh88</literal>, and <literal>Asia/Riyadh89</literal> have been
removed, as they are no longer maintained by IANA, and never
represented actual civil timekeeping practice.
</para>
<listitem>
<para>
- Fix <command>VACUUM</>'s tests to see whether it can
- update <structfield>relfrozenxid</> (Andres Freund)
+ Fix <command>VACUUM</command>'s tests to see whether it can
+ update <structfield>relfrozenxid</structfield> (Andres Freund)
</para>
<para>
- In some cases <command>VACUUM</> (either manual or autovacuum) could
- incorrectly advance a table's <structfield>relfrozenxid</> value,
+ In some cases <command>VACUUM</command> (either manual or autovacuum) could
+ incorrectly advance a table's <structfield>relfrozenxid</structfield> value,
allowing tuples to escape freezing, causing those rows to become
invisible once 2^31 transactions have elapsed. The probability of
data loss is fairly low since multiple incorrect advancements would
need to happen before actual loss occurs, but it's not zero. In 9.2.0
and later, the probability of loss is higher, and it's also possible
- to get <quote>could not access status of transaction</> errors as a
+ to get <quote>could not access status of transaction</quote> errors as a
consequence of this bug. Users upgrading from releases 9.0.4 or 8.4.8
or earlier are not affected, but all later versions contain the bug.
</para>
<para>
The issue can be ameliorated by, after upgrading, vacuuming all tables
in all databases while having <link
- linkend="guc-vacuum-freeze-table-age"><varname>vacuum_freeze_table_age</></link>
+ linkend="guc-vacuum-freeze-table-age"><varname>vacuum_freeze_table_age</varname></link>
set to zero. This will fix any latent corruption but will not be able
to fix all pre-existing data errors. However, an installation can be
presumed safe after performing this vacuuming if it has executed fewer
than 2^31 update transactions in its lifetime (check this with
- <literal>SELECT txid_current() < 2^31</>).
+ <literal>SELECT txid_current() < 2^31</literal>).
</para>
</listitem>
<listitem>
<para>
- Fix initialization of <filename>pg_clog</> and <filename>pg_subtrans</>
+ Fix initialization of <filename>pg_clog</filename> and <filename>pg_subtrans</filename>
during hot standby startup (Andres Freund, Heikki Linnakangas)
</para>
<para>
This could lead to corruption of the lock data structures in shared
- memory, causing <quote>lock already held</> and other odd errors.
+ memory, causing <quote>lock already held</quote> and other odd errors.
</para>
</listitem>
<listitem>
<para>
- Truncate <filename>pg_multixact</> contents during WAL replay
+ Truncate <filename>pg_multixact</filename> contents during WAL replay
(Andres Freund)
</para>
<listitem>
<para>
- Ensure an anti-wraparound <command>VACUUM</> counts a page as scanned
+ Ensure an anti-wraparound <command>VACUUM</command> counts a page as scanned
when it's only verified that no tuples need freezing (Sergey
Burladyan, Jeff Janes)
</para>
<para>
This bug could result in failing to
- advance <structfield>relfrozenxid</>, so that the table would still be
+ advance <structfield>relfrozenxid</structfield>, so that the table would still be
thought to need another anti-wraparound vacuum. In the worst case the
database might even shut down to prevent wraparound.
</para>
<listitem>
<para>
- Fix <quote>unexpected spgdoinsert() failure</> error during SP-GiST
+ Fix <quote>unexpected spgdoinsert() failure</quote> error during SP-GiST
index creation (Teodor Sigaev)
</para>
</listitem>
<listitem>
<para>
- Avoid flattening a subquery whose <literal>SELECT</> list contains a
- volatile function wrapped inside a sub-<literal>SELECT</> (Tom Lane)
+ Avoid flattening a subquery whose <literal>SELECT</literal> list contains a
+ volatile function wrapped inside a sub-<literal>SELECT</literal> (Tom Lane)
</para>
<para>
<para>
This error could lead to incorrect plans for queries involving
- multiple levels of subqueries within <literal>JOIN</> syntax.
+ multiple levels of subqueries within <literal>JOIN</literal> syntax.
</para>
</listitem>
<listitem>
<para>
Fix incorrect planning in cases where the same non-strict expression
- appears in multiple <literal>WHERE</> and outer <literal>JOIN</>
+ appears in multiple <literal>WHERE</literal> and outer <literal>JOIN</literal>
equality clauses (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix array slicing of <type>int2vector</> and <type>oidvector</> values
+ Fix array slicing of <type>int2vector</type> and <type>oidvector</type> values
(Tom Lane)
</para>
<para>
Expressions of this kind are now implicitly promoted to
- regular <type>int2</> or <type>oid</> arrays.
+ regular <type>int2</type> or <type>oid</type> arrays.
</para>
</listitem>
In some cases, the system would use the simple GMT offset value when
it should have used the regular timezone setting that had prevailed
before the simple offset was selected. This change also causes
- the <function>timeofday</> function to honor the simple GMT offset
+ the <function>timeofday</function> function to honor the simple GMT offset
zone.
</para>
</listitem>
<listitem>
<para>
- Properly quote generated command lines in <application>pg_ctl</>
+ Properly quote generated command lines in <application>pg_ctl</application>
(Naoya Anzai and Tom Lane)
</para>
<listitem>
<para>
- Fix <application>pg_dumpall</> to work when a source database
+ Fix <application>pg_dumpall</application> to work when a source database
sets <link
- linkend="guc-default-transaction-read-only"><varname>default_transaction_read_only</></link>
- via <command>ALTER DATABASE SET</> (Kevin Grittner)
+ linkend="guc-default-transaction-read-only"><varname>default_transaction_read_only</varname></link>
+ via <command>ALTER DATABASE SET</command> (Kevin Grittner)
</para>
<para>
<listitem>
<para>
- Make <application>ecpg</> search for quoted cursor names
+ Make <application>ecpg</application> search for quoted cursor names
case-sensitively (Zoltán Böszörményi)
</para>
</listitem>
<listitem>
<para>
- Fix <application>ecpg</>'s processing of lists of variables
- declared <type>varchar</> (Zoltán Böszörményi)
+ Fix <application>ecpg</application>'s processing of lists of variables
+ declared <type>varchar</type> (Zoltán Böszörményi)
</para>
</listitem>
<listitem>
<para>
- Make <filename>contrib/lo</> defend against incorrect trigger definitions
+ Make <filename>contrib/lo</filename> defend against incorrect trigger definitions
(Marc Cousin)
</para>
</listitem>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2013h
+ Update time zone data files to <application>tzdata</application> release 2013h
for DST law changes in Argentina, Brazil, Jordan, Libya,
Liechtenstein, Morocco, and Palestine. Also, new timezone
abbreviations WIB, WIT, WITA for Indonesia.
</para>
<para>
- <productname>PostgreSQL</> case-folds non-ASCII characters only
+ <productname>PostgreSQL</productname> case-folds non-ASCII characters only
when using a single-byte server encoding.
</para>
</listitem>
<listitem>
<para>
Fix checkpoint memory leak in background writer when <literal>wal_level =
- hot_standby</> (Naoya Anzai)
+ hot_standby</literal> (Naoya Anzai)
</para>
</listitem>
<listitem>
<para>
- Fix memory overcommit bug when <varname>work_mem</> is using more
+ Fix memory overcommit bug when <varname>work_mem</varname> is using more
than 24GB of memory (Stephen Frost)
</para>
</listitem>
</para>
<para>
- Previously tests like <literal>col IS NOT TRUE</> and <literal>col IS
- NOT FALSE</> did not properly factor in NULL values when estimating
+ Previously tests like <literal>col IS NOT TRUE</literal> and <literal>col IS
+ NOT FALSE</literal> did not properly factor in NULL values when estimating
plan costs.
</para>
</listitem>
<listitem>
<para>
- Fix accounting for qualifier evaluation costs in <literal>UNION ALL</>
+ Fix accounting for qualifier evaluation costs in <literal>UNION ALL</literal>
and inheritance queries (Tom Lane)
</para>
<para>
This fixes cases where suboptimal query plans could be chosen if
- some <literal>WHERE</> clauses are expensive to calculate.
+ some <literal>WHERE</literal> clauses are expensive to calculate.
</para>
</listitem>
<listitem>
<para>
- Prevent pushing down <literal>WHERE</> clauses into unsafe
- <literal>UNION/INTERSECT</> subqueries (Tom Lane)
+ Prevent pushing down <literal>WHERE</literal> clauses into unsafe
+ <literal>UNION/INTERSECT</literal> subqueries (Tom Lane)
</para>
<para>
- Subqueries of a <literal>UNION</> or <literal>INTERSECT</> that
+ Subqueries of a <literal>UNION</literal> or <literal>INTERSECT</literal> that
contain set-returning functions or volatile functions in their
- <literal>SELECT</> lists could be improperly optimized, leading to
+ <literal>SELECT</literal> lists could be improperly optimized, leading to
run-time errors or incorrect query results.
</para>
</listitem>
<listitem>
<para>
- Fix rare case of <quote>failed to locate grouping columns</>
+ Fix rare case of <quote>failed to locate grouping columns</quote>
planner failure (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix <application>pg_dump</> of foreign tables with dropped columns (Andrew Dunstan)
+ Fix <application>pg_dump</application> of foreign tables with dropped columns (Andrew Dunstan)
</para>
<para>
- Previously such cases could cause a <application>pg_upgrade</> error.
+ Previously such cases could cause a <application>pg_upgrade</application> error.
</para>
</listitem>
<listitem>
<para>
- Reorder <application>pg_dump</> processing of extension-related
+ Reorder <application>pg_dump</application> processing of extension-related
rules and event triggers (Joe Conway)
</para>
</listitem>
<listitem>
<para>
Force dumping of extension tables if specified by <command>pg_dump
- -t</> or <literal>-n</> (Joe Conway)
+ -t</command> or <literal>-n</literal> (Joe Conway)
</para>
</listitem>
<listitem>
<para>
- Fix <command>pg_restore -l</> with the directory archive to display
+ Fix <command>pg_restore -l</command> with the directory archive to display
the correct format name (Fujii Masao)
</para>
</listitem>
<listitem>
<para>
- Properly record index comments created using <literal>UNIQUE</>
- and <literal>PRIMARY KEY</> syntax (Andres Freund)
+ Properly record index comments created using <literal>UNIQUE</literal>
+ and <literal>PRIMARY KEY</literal> syntax (Andres Freund)
</para>
<para>
- This fixes a parallel <application>pg_restore</> failure.
+ This fixes a parallel <application>pg_restore</application> failure.
</para>
</listitem>
<listitem>
<para>
- Cause <command>pg_basebackup -x</> with an empty xlog directory
+ Cause <command>pg_basebackup -x</command> with an empty xlog directory
to throw an error rather than crashing (Magnus Hagander, Haruka
Takatsuka)
</para>
<listitem>
<para>
- Fix <command>REINDEX TABLE</> and <command>REINDEX DATABASE</>
+ Fix <command>REINDEX TABLE</command> and <command>REINDEX DATABASE</command>
to properly revalidate constraints and mark invalidated indexes as
valid (Noah Misch)
</para>
<para>
- <command>REINDEX INDEX</> has always worked properly.
+ <command>REINDEX INDEX</command> has always worked properly.
</para>
</listitem>
<listitem>
<para>
Fix possible deadlock during concurrent <command>CREATE INDEX
- CONCURRENTLY</> operations (Tom Lane)
+ CONCURRENTLY</command> operations (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix <function>regexp_matches()</> handling of zero-length matches
+ Fix <function>regexp_matches()</function> handling of zero-length matches
(Jeevan Chalke)
</para>
<listitem>
<para>
- Prevent <command>CREATE FUNCTION</> from checking <command>SET</>
+ Prevent <command>CREATE FUNCTION</command> from checking <command>SET</command>
variables unless function body checking is enabled (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Allow <command>ALTER DEFAULT PRIVILEGES</> to operate on schemas
+ Allow <command>ALTER DEFAULT PRIVILEGES</command> to operate on schemas
without requiring CREATE permission (Tom Lane)
</para>
</listitem>
<para>
Specifically, lessen keyword restrictions for role names, language
- names, <command>EXPLAIN</> and <command>COPY</> options, and
- <command>SET</> values. This allows <literal>COPY ... (FORMAT
- BINARY)</> to work as expected; previously <literal>BINARY</> needed
+ names, <command>EXPLAIN</command> and <command>COPY</command> options, and
+ <command>SET</command> values. This allows <literal>COPY ... (FORMAT
+ BINARY)</literal> to work as expected; previously <literal>BINARY</literal> needed
to be quoted.
</para>
</listitem>
<listitem>
<para>
- Print proper line number during <command>COPY</> failure (Heikki
+ Print proper line number during <command>COPY</command> failure (Heikki
Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Fix <function>pgp_pub_decrypt()</> so it works for secret keys with
+ Fix <function>pgp_pub_decrypt()</function> so it works for secret keys with
passwords (Marko Kreen)
</para>
</listitem>
<listitem>
<para>
- Make <application>pg_upgrade</> use <literal>pg_dump
- --quote-all-identifiers</> to avoid problems with keyword changes
+ Make <application>pg_upgrade</application> use <literal>pg_dump
+ --quote-all-identifiers</literal> to avoid problems with keyword changes
between releases (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Ensure that <command>VACUUM ANALYZE</> still runs the ANALYZE phase
+ Ensure that <command>VACUUM ANALYZE</command> still runs the ANALYZE phase
if its attempt to truncate the file is cancelled due to lock conflicts
(Kevin Grittner)
</para>
<listitem>
<para>
Avoid possible failure when performing transaction control commands (e.g
- <command>ROLLBACK</>) in prepared queries (Tom Lane)
+ <command>ROLLBACK</command>) in prepared queries (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Ensure that floating-point data input accepts standard spellings
- of <quote>infinity</> on all platforms (Tom Lane)
+ of <quote>infinity</quote> on all platforms (Tom Lane)
</para>
<para>
- The C99 standard says that allowable spellings are <literal>inf</>,
- <literal>+inf</>, <literal>-inf</>, <literal>infinity</>,
- <literal>+infinity</>, and <literal>-infinity</>. Make sure we
- recognize these even if the platform's <function>strtod</> function
+ The C99 standard says that allowable spellings are <literal>inf</literal>,
+ <literal>+inf</literal>, <literal>-inf</literal>, <literal>infinity</literal>,
+ <literal>+infinity</literal>, and <literal>-infinity</literal>. Make sure we
+ recognize these even if the platform's <function>strtod</function> function
doesn't.
</para>
</listitem>
<listitem>
<para>
- Avoid unnecessary reporting when <varname>track_activities</> is off
+ Avoid unnecessary reporting when <varname>track_activities</varname> is off
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Prevent crash when <application>psql</>'s <envar>PSQLRC</> variable
+ Prevent crash when <application>psql</application>'s <envar>PSQLRC</envar> variable
contains a tilde (Bruce Momjian)
</para>
</listitem>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2013d
+ Update time zone data files to <application>tzdata</application> release 2013d
for DST law changes in Israel, Morocco, Palestine, and Paraguay.
Also, historical zone data corrections for Macquarie Island.
</para>
<para>
However, this release corrects several errors in management of GiST
indexes. After installing this update, it is advisable to
- <command>REINDEX</> any GiST indexes that meet one or more of the
+ <command>REINDEX</command> any GiST indexes that meet one or more of the
conditions described below.
</para>
<para>
A connection request containing a database name that begins with
- <quote><literal>-</></quote> could be crafted to damage or destroy
+ <quote><literal>-</literal></quote> could be crafted to damage or destroy
files within the server's data directory, even if the request is
eventually rejected. (CVE-2013-1899)
</para>
<para>
This avoids a scenario wherein random numbers generated by
- <filename>contrib/pgcrypto</> functions might be relatively easy for
+ <filename>contrib/pgcrypto</filename> functions might be relatively easy for
another database user to guess. The risk is only significant when
- the postmaster is configured with <varname>ssl</> = <literal>on</>
+ the postmaster is configured with <varname>ssl</varname> = <literal>on</literal>
but most connections don't use SSL encryption. (CVE-2013-1900)
</para>
</listitem>
<para>
An unprivileged database user could exploit this mistake to call
- <function>pg_start_backup()</> or <function>pg_stop_backup()</>,
+ <function>pg_start_backup()</function> or <function>pg_stop_backup()</function>,
thus possibly interfering with creation of routine backups.
(CVE-2013-1901)
</para>
<listitem>
<para>
- Fix GiST indexes to not use <quote>fuzzy</> geometric comparisons when
+ Fix GiST indexes to not use <quote>fuzzy</quote> geometric comparisons when
it's not appropriate to do so (Alexander Korotkov)
</para>
<para>
- The core geometric types perform comparisons using <quote>fuzzy</>
- equality, but <function>gist_box_same</> must do exact comparisons,
+ The core geometric types perform comparisons using <quote>fuzzy</quote>
+ equality, but <function>gist_box_same</function> must do exact comparisons,
else GiST indexes using it might become inconsistent. After installing
- this update, users should <command>REINDEX</> any GiST indexes on
- <type>box</>, <type>polygon</>, <type>circle</>, or <type>point</>
- columns, since all of these use <function>gist_box_same</>.
+ this update, users should <command>REINDEX</command> any GiST indexes on
+ <type>box</type>, <type>polygon</type>, <type>circle</type>, or <type>point</type>
+ columns, since all of these use <function>gist_box_same</function>.
</para>
</listitem>
<listitem>
<para>
Fix erroneous range-union and penalty logic in GiST indexes that use
- <filename>contrib/btree_gist</> for variable-width data types, that is
- <type>text</>, <type>bytea</>, <type>bit</>, and <type>numeric</>
+ <filename>contrib/btree_gist</filename> for variable-width data types, that is
+ <type>text</type>, <type>bytea</type>, <type>bit</type>, and <type>numeric</type>
columns (Tom Lane)
</para>
<para>
These errors could result in inconsistent indexes in which some keys
that are present would not be found by searches, and also in useless
- index bloat. Users are advised to <command>REINDEX</> such indexes
+ index bloat. Users are advised to <command>REINDEX</command> such indexes
after installing this update.
</para>
</listitem>
These errors could result in inconsistent indexes in which some keys
that are present would not be found by searches, and also in indexes
that are unnecessarily inefficient to search. Users are advised to
- <command>REINDEX</> multi-column GiST indexes after installing this
+ <command>REINDEX</command> multi-column GiST indexes after installing this
update.
</para>
</listitem>
<listitem>
<para>
- Fix <function>gist_point_consistent</>
+ Fix <function>gist_point_consistent</function>
to handle fuzziness consistently (Alexander Korotkov)
</para>
<para>
- Index scans on GiST indexes on <type>point</> columns would sometimes
+ Index scans on GiST indexes on <type>point</type> columns would sometimes
yield results different from a sequential scan, because
- <function>gist_point_consistent</> disagreed with the underlying
+ <function>gist_point_consistent</function> disagreed with the underlying
operator code about whether to do comparisons exactly or fuzzily.
</para>
</listitem>
</para>
<para>
- This bug could result in <quote>incorrect local pin count</> errors
+ This bug could result in <quote>incorrect local pin count</quote> errors
during replay, making recovery impossible.
</para>
</listitem>
<listitem>
<para>
Ensure we do crash recovery before entering archive recovery, if the
- database was not stopped cleanly and a <filename>recovery.conf</> file
+ database was not stopped cleanly and a <filename>recovery.conf</filename> file
is present (Heikki Linnakangas, Kyotaro Horiguchi, Mitsumasa Kondo)
</para>
<listitem>
<para>
- Fix race condition in <command>DELETE RETURNING</> (Tom Lane)
+ Fix race condition in <command>DELETE RETURNING</command> (Tom Lane)
</para>
<para>
- Under the right circumstances, <command>DELETE RETURNING</> could
+ Under the right circumstances, <command>DELETE RETURNING</command> could
attempt to fetch data from a shared buffer that the current process
no longer has any pin on. If some other process changed the buffer
- meanwhile, this would lead to garbage <literal>RETURNING</> output, or
+ meanwhile, this would lead to garbage <literal>RETURNING</literal> output, or
even a crash.
</para>
</listitem>
<listitem>
<para>
- Fix <function>to_char()</> to use ASCII-only case-folding rules where
+ Fix <function>to_char()</function> to use ASCII-only case-folding rules where
appropriate (Tom Lane)
</para>
<para>
This fixes misbehavior of some template patterns that should be
- locale-independent, but mishandled <quote><literal>I</></quote> and
- <quote><literal>i</></quote> in Turkish locales.
+ locale-independent, but mishandled <quote><literal>I</literal></quote> and
+ <quote><literal>i</literal></quote> in Turkish locales.
</para>
</listitem>
<listitem>
<para>
- Fix unwanted rejection of timestamp <literal>1999-12-31 24:00:00</>
+ Fix unwanted rejection of timestamp <literal>1999-12-31 24:00:00</literal>
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix logic error when a single transaction does <command>UNLISTEN</>
- then <command>LISTEN</> (Tom Lane)
+ Fix logic error when a single transaction does <command>UNLISTEN</command>
+ then <command>LISTEN</command> (Tom Lane)
</para>
<para>
<listitem>
<para>
- Fix performance issue in <literal>EXPLAIN (ANALYZE, TIMING OFF)</>
+ Fix performance issue in <literal>EXPLAIN (ANALYZE, TIMING OFF)</literal>
(Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
- Remove useless <quote>picksplit doesn't support secondary split</> log
+ Remove useless <quote>picksplit doesn't support secondary split</quote> log
messages (Josh Hansen, Tom Lane)
</para>
<listitem>
<para>
Remove vestigial secondary-split support in
- <function>gist_box_picksplit()</> (Tom Lane)
+ <function>gist_box_picksplit()</function> (Tom Lane)
</para>
<para>
<listitem>
<para>
- Eliminate memory leaks in PL/Perl's <function>spi_prepare()</> function
+ Eliminate memory leaks in PL/Perl's <function>spi_prepare()</function> function
(Alex Hunsaker, Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix <application>pg_dumpall</> to handle database names containing
- <quote><literal>=</></quote> correctly (Heikki Linnakangas)
+ Fix <application>pg_dumpall</application> to handle database names containing
+ <quote><literal>=</literal></quote> correctly (Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Avoid crash in <application>pg_dump</> when an incorrect connection
+ Avoid crash in <application>pg_dump</application> when an incorrect connection
string is given (Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Ignore invalid indexes in <application>pg_dump</> and
- <application>pg_upgrade</> (Michael Paquier, Bruce Momjian)
+ Ignore invalid indexes in <application>pg_dump</application> and
+ <application>pg_upgrade</application> (Michael Paquier, Bruce Momjian)
</para>
<para>
a uniqueness condition not satisfied by the table's data. Also, if the
index creation is in fact still in progress, it seems reasonable to
consider it to be an uncommitted DDL change, which
- <application>pg_dump</> wouldn't be expected to dump anyway.
- <application>pg_upgrade</> now also skips invalid indexes rather than
+ <application>pg_dump</application> wouldn't be expected to dump anyway.
+ <application>pg_upgrade</application> now also skips invalid indexes rather than
failing.
</para>
</listitem>
<listitem>
<para>
- In <application>pg_basebackup</>, include only the current server
+ In <application>pg_basebackup</application>, include only the current server
version's subdirectory when backing up a tablespace (Heikki
Linnakangas)
</para>
<listitem>
<para>
- Add a server version check in <application>pg_basebackup</> and
- <application>pg_receivexlog</>, so they fail cleanly with version
+ Add a server version check in <application>pg_basebackup</application> and
+ <application>pg_receivexlog</application>, so they fail cleanly with version
combinations that won't work (Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Fix <filename>contrib/dblink</> to handle inconsistent settings of
- <varname>DateStyle</> or <varname>IntervalStyle</> safely (Daniel
+ Fix <filename>contrib/dblink</filename> to handle inconsistent settings of
+ <varname>DateStyle</varname> or <varname>IntervalStyle</varname> safely (Daniel
Farina, Tom Lane)
</para>
Previously, if the remote server had different settings of these
parameters, ambiguous dates might be read incorrectly. This fix
ensures that datetime and interval columns fetched by a
- <filename>dblink</> query will be interpreted correctly. Note however
+ <filename>dblink</filename> query will be interpreted correctly. Note however
that inconsistent settings are still risky, since literal values
appearing in SQL commands sent to the remote server might be
interpreted differently than they would be locally.
<listitem>
<para>
- Fix <filename>contrib/pg_trgm</>'s <function>similarity()</> function
+ Fix <filename>contrib/pg_trgm</filename>'s <function>similarity()</function> function
to return zero for trigram-less strings (Tom Lane)
</para>
<para>
- Previously it returned <literal>NaN</> due to internal division by zero.
+ Previously it returned <literal>NaN</literal> due to internal division by zero.
</para>
</listitem>
<listitem>
<para>
- Enable building <productname>PostgreSQL</> with Microsoft Visual
+ Enable building <productname>PostgreSQL</productname> with Microsoft Visual
Studio 2012 (Brar Piening, Noah Misch)
</para>
</listitem>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2013b
+ Update time zone data files to <application>tzdata</application> release 2013b
for DST law changes in Chile, Haiti, Morocco, Paraguay, and some
Russian areas. Also, historical zone data corrections for numerous
places.
<para>
Also, update the time zone abbreviation files for recent changes in
- Russia and elsewhere: <literal>CHOT</>, <literal>GET</>,
- <literal>IRKT</>, <literal>KGT</>, <literal>KRAT</>, <literal>MAGT</>,
- <literal>MAWT</>, <literal>MSK</>, <literal>NOVT</>, <literal>OMST</>,
- <literal>TKT</>, <literal>VLAT</>, <literal>WST</>, <literal>YAKT</>,
- <literal>YEKT</> now follow their current meanings, and
- <literal>VOLT</> (Europe/Volgograd) and <literal>MIST</>
+ Russia and elsewhere: <literal>CHOT</literal>, <literal>GET</literal>,
+ <literal>IRKT</literal>, <literal>KGT</literal>, <literal>KRAT</literal>, <literal>MAGT</literal>,
+ <literal>MAWT</literal>, <literal>MSK</literal>, <literal>NOVT</literal>, <literal>OMST</literal>,
+ <literal>TKT</literal>, <literal>VLAT</literal>, <literal>WST</literal>, <literal>YAKT</literal>,
+ <literal>YEKT</literal> now follow their current meanings, and
+ <literal>VOLT</literal> (Europe/Volgograd) and <literal>MIST</literal>
(Antarctica/Macquarie) are added to the default abbreviations list.
</para>
</listitem>
<listitem>
<para>
- Prevent execution of <function>enum_recv</> from SQL (Tom Lane)
+ Prevent execution of <function>enum_recv</function> from SQL (Tom Lane)
</para>
<para>
<para>
This mistake could result in incorrect <quote>WAL ends before end of
- online backup</> errors.
+ online backup</quote> errors.
</para>
</listitem>
<listitem>
<para>
- Improve performance of <function>SPI_execute</> and related
- functions, thereby improving PL/pgSQL's <literal>EXECUTE</>
+ Improve performance of <function>SPI_execute</function> and related
+ functions, thereby improving PL/pgSQL's <literal>EXECUTE</literal>
(Heikki Linnakangas, Tom Lane)
</para>
<listitem>
<para>
- Fix intermittent crash in <literal>DROP INDEX CONCURRENTLY</> (Tom Lane)
+ Fix intermittent crash in <literal>DROP INDEX CONCURRENTLY</literal> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix potential corruption of shared-memory lock table during
- <command>CREATE/DROP INDEX CONCURRENTLY</> (Tom Lane)
+ <command>CREATE/DROP INDEX CONCURRENTLY</command> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix <command>COPY</>'s multiple-tuple-insertion code for the case of
+ Fix <command>COPY</command>'s multiple-tuple-insertion code for the case of
a tuple larger than page size minus fillfactor (Heikki Linnakangas)
</para>
<listitem>
<para>
Protect against race conditions when scanning
- <structname>pg_tablespace</> (Stephen Frost, Tom Lane)
+ <structname>pg_tablespace</structname> (Stephen Frost, Tom Lane)
</para>
<para>
- <command>CREATE DATABASE</> and <command>DROP DATABASE</> could
+ <command>CREATE DATABASE</command> and <command>DROP DATABASE</command> could
misbehave if there were concurrent updates of
- <structname>pg_tablespace</> entries.
+ <structname>pg_tablespace</structname> entries.
</para>
</listitem>
<listitem>
<para>
- Prevent <command>DROP OWNED</> from trying to drop whole databases or
+ Prevent <command>DROP OWNED</command> from trying to drop whole databases or
tablespaces (Álvaro Herrera)
</para>
<listitem>
<para>
Fix error in <link
- linkend="guc-vacuum-freeze-table-age"><varname>vacuum_freeze_table_age</></link>
+ linkend="guc-vacuum-freeze-table-age"><varname>vacuum_freeze_table_age</varname></link>
implementation (Andres Freund)
</para>
<para>
In installations that have existed for more than <link
- linkend="guc-vacuum-freeze-min-age"><varname>vacuum_freeze_min_age</></link>
+ linkend="guc-vacuum-freeze-min-age"><varname>vacuum_freeze_min_age</varname></link>
transactions, this mistake prevented autovacuum from using partial-table
scans, so that a full-table scan would always happen instead.
</para>
<listitem>
<para>
- Prevent misbehavior when a <symbol>RowExpr</> or <symbol>XmlExpr</>
+ Prevent misbehavior when a <symbol>RowExpr</symbol> or <symbol>XmlExpr</symbol>
is parse-analyzed twice (Andres Freund, Tom Lane)
</para>
<para>
This mistake could be user-visible in contexts such as
- <literal>CREATE TABLE LIKE INCLUDING INDEXES</>.
+ <literal>CREATE TABLE LIKE INCLUDING INDEXES</literal>.
</para>
</listitem>
<para>
There were some issues with default privileges for types, and
- <application>pg_dump</> failed to dump such privileges at all.
+ <application>pg_dump</application> failed to dump such privileges at all.
</para>
</listitem>
<listitem>
<para>
- Reject out-of-range dates in <function>to_date()</> (Hitoshi Harada)
+ Reject out-of-range dates in <function>to_date()</function> (Hitoshi Harada)
</para>
</listitem>
<listitem>
<para>
- Fix <function>pg_extension_config_dump()</> to handle
+ Fix <function>pg_extension_config_dump()</function> to handle
extension-update cases properly (Tom Lane)
</para>
<para>
The previous coding resulted in sometimes omitting the first line in
- the <literal>CONTEXT</> traceback for the error.
+ the <literal>CONTEXT</literal> traceback for the error.
</para>
</listitem>
</para>
<para>
- This bug affected <application>psql</> and some other client programs.
+ This bug affected <application>psql</application> and some other client programs.
</para>
</listitem>
<listitem>
<para>
- Fix possible crash in <application>psql</>'s <command>\?</> command
+ Fix possible crash in <application>psql</application>'s <command>\?</command> command
when not connected to a database (Meng Qingzhong)
</para>
</listitem>
<listitem>
<para>
Fix possible error if a relation file is removed while
- <application>pg_basebackup</> is running (Heikki Linnakangas)
+ <application>pg_basebackup</application> is running (Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Tolerate timeline switches while <literal>pg_basebackup -X fetch</>
+ Tolerate timeline switches while <literal>pg_basebackup -X fetch</literal>
is backing up a standby server (Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Make <application>pg_dump</> exclude data of unlogged tables when
+ Make <application>pg_dump</application> exclude data of unlogged tables when
running on a hot-standby server (Magnus Hagander)
</para>
<para>
This would fail anyway because the data is not available on the standby
server, so it seems most convenient to assume
- <option>--no-unlogged-table-data</> automatically.
+ <option>--no-unlogged-table-data</option> automatically.
</para>
</listitem>
<listitem>
<para>
- Fix <application>pg_upgrade</> to deal with invalid indexes safely
+ Fix <application>pg_upgrade</application> to deal with invalid indexes safely
(Bruce Momjian)
</para>
</listitem>
<listitem>
<para>
- Fix <application>pg_upgrade</>'s -O/-o options (Marti Raudsepp)
+ Fix <application>pg_upgrade</application>'s -O/-o options (Marti Raudsepp)
</para>
</listitem>
<listitem>
<para>
- Fix one-byte buffer overrun in <application>libpq</>'s
- <function>PQprintTuples</> (Xi Wang)
+ Fix one-byte buffer overrun in <application>libpq</application>'s
+ <function>PQprintTuples</function> (Xi Wang)
</para>
<para>
This ancient function is not used anywhere by
- <productname>PostgreSQL</> itself, but it might still be used by some
+ <productname>PostgreSQL</productname> itself, but it might still be used by some
client code.
</para>
</listitem>
<listitem>
<para>
- Make <application>ecpglib</> use translated messages properly
+ Make <application>ecpglib</application> use translated messages properly
(Chen Huajun)
</para>
</listitem>
<listitem>
<para>
- Properly install <application>ecpg_compat</> and
- <application>pgtypes</> libraries on MSVC (Jiang Guiqing)
+ Properly install <application>ecpg_compat</application> and
+ <application>pgtypes</application> libraries on MSVC (Jiang Guiqing)
</para>
</listitem>
<listitem>
<para>
- Include our version of <function>isinf()</> in
- <application>libecpg</> if it's not provided by the system
+ Include our version of <function>isinf()</function> in
+ <application>libecpg</application> if it's not provided by the system
(Jiang Guiqing)
</para>
</listitem>
<listitem>
<para>
- Make <application>pgxs</> build executables with the right
- <literal>.exe</> suffix when cross-compiling for Windows
+ Make <application>pgxs</application> build executables with the right
+ <literal>.exe</literal> suffix when cross-compiling for Windows
(Zoltan Boszormenyi)
</para>
</listitem>
<listitem>
<para>
- Add new timezone abbreviation <literal>FET</> (Tom Lane)
+ Add new timezone abbreviation <literal>FET</literal> (Tom Lane)
</para>
<para>
</para>
<para>
- However, you may need to perform <command>REINDEX</> operations to
+ However, you may need to perform <command>REINDEX</command> operations to
correct problems in concurrently-built indexes, as described in the first
changelog item below.
</para>
<listitem>
<para>
Fix multiple bugs associated with <command>CREATE/DROP INDEX
- CONCURRENTLY</> (Andres Freund, Tom Lane, Simon Riggs, Pavan Deolasee)
+ CONCURRENTLY</command> (Andres Freund, Tom Lane, Simon Riggs, Pavan Deolasee)
</para>
<para>
- An error introduced while adding <command>DROP INDEX CONCURRENTLY</>
+ An error introduced while adding <command>DROP INDEX CONCURRENTLY</command>
allowed incorrect indexing decisions to be made during the initial
- phase of <command>CREATE INDEX CONCURRENTLY</>; so that indexes built
+ phase of <command>CREATE INDEX CONCURRENTLY</command>; so that indexes built
by that command could be corrupt. It is recommended that indexes
- built in 9.2.X with <command>CREATE INDEX CONCURRENTLY</> be rebuilt
+ built in 9.2.X with <command>CREATE INDEX CONCURRENTLY</command> be rebuilt
after applying this update.
</para>
<para>
- In addition, fix <command>CREATE/DROP INDEX CONCURRENTLY</> to use
+ In addition, fix <command>CREATE/DROP INDEX CONCURRENTLY</command> to use
in-place updates when changing the state of an index's
- <structname>pg_index</> row. This prevents race conditions that could
+ <structname>pg_index</structname> row. This prevents race conditions that could
cause concurrent sessions to miss updating the target index, thus
again resulting in corrupt concurrently-created indexes.
</para>
<para>
Also, fix various other operations to ensure that they ignore
invalid indexes resulting from a failed <command>CREATE INDEX
- CONCURRENTLY</> command. The most important of these is
- <command>VACUUM</>, because an auto-vacuum could easily be launched
+ CONCURRENTLY</command> command. The most important of these is
+ <command>VACUUM</command>, because an auto-vacuum could easily be launched
on the table before corrective action can be taken to fix or remove
the invalid index.
</para>
<para>
- Also fix <command>DROP INDEX CONCURRENTLY</> to not disable
+ Also fix <command>DROP INDEX CONCURRENTLY</command> to not disable
insertions into the target index until all queries using it are done.
</para>
<para>
- Also fix misbehavior if <command>DROP INDEX CONCURRENTLY</> is
+ Also fix misbehavior if <command>DROP INDEX CONCURRENTLY</command> is
canceled: the previous coding could leave an un-droppable index behind.
</para>
</listitem>
<listitem>
<para>
- Correct predicate locking for <command>DROP INDEX CONCURRENTLY</>
+ Correct predicate locking for <command>DROP INDEX CONCURRENTLY</command>
(Kevin Grittner)
</para>
<para>
Previously, SSI predicate locks were processed at the wrong time,
possibly leading to incorrect behavior of serializable transactions
- executing in parallel with the <command>DROP</>.
+ executing in parallel with the <command>DROP</command>.
</para>
</listitem>
<para>
This oversight could prevent subsequent execution of certain
- operations such as <command>CREATE INDEX CONCURRENTLY</>.
+ operations such as <command>CREATE INDEX CONCURRENTLY</command>.
</para>
</listitem>
<listitem>
<para>
- Avoid bogus <quote>out-of-sequence timeline ID</> errors in standby
+ Avoid bogus <quote>out-of-sequence timeline ID</quote> errors in standby
mode (Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
Fix the syslogger process to not fail when
- <varname>log_rotation_age</> exceeds 2^31 milliseconds (about 25 days)
+ <varname>log_rotation_age</varname> exceeds 2^31 milliseconds (about 25 days)
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix <function>WaitLatch()</> to return promptly when the requested
+ Fix <function>WaitLatch()</function> to return promptly when the requested
timeout expires (Jeff Janes, Tom Lane)
</para>
<para>
With the previous coding, a steady stream of non-wait-terminating
- interrupts could delay return from <function>WaitLatch()</>
+ interrupts could delay return from <function>WaitLatch()</function>
indefinitely. This has been shown to be a problem for the autovacuum
launcher process, and might cause trouble elsewhere as well.
</para>
<para>
The planner could derive incorrect constraints from a clause equating
a non-strict construct to something else, for example
- <literal>WHERE COALESCE(foo, 0) = 0</>
- when <literal>foo</> is coming from the nullable side of an outer join.
+ <literal>WHERE COALESCE(foo, 0) = 0</literal>
+ when <literal>foo</literal> is coming from the nullable side of an outer join.
9.2 showed this type of error in more cases than previous releases,
but the basic bug has been there for a long time.
</para>
<listitem>
<para>
- Fix <command>SELECT DISTINCT</> with index-optimized
- <function>MIN</>/<function>MAX</> on an inheritance tree (Tom Lane)
+ Fix <command>SELECT DISTINCT</command> with index-optimized
+ <function>MIN</function>/<function>MAX</function> on an inheritance tree (Tom Lane)
</para>
<para>
The planner would fail with <quote>failed to re-find MinMaxAggInfo
- record</> given this combination of factors.
+ record</quote> given this combination of factors.
</para>
</listitem>
<para>
A strict join clause can be sufficient to establish an
- <replaceable>x</> <literal>IS NOT NULL</> predicate, for example.
+ <replaceable>x</replaceable> <literal>IS NOT NULL</literal> predicate, for example.
This fixes a planner regression in 9.2, since previous versions could
make comparable deductions.
</para>
</para>
<para>
- This affects multicolumn <literal>NOT IN</> subplans, such as
- <literal>WHERE (a, b) NOT IN (SELECT x, y FROM ...)</>
- when for instance <literal>b</> and <literal>y</> are <type>int4</>
- and <type>int8</> respectively. This mistake led to wrong answers
+ This affects multicolumn <literal>NOT IN</literal> subplans, such as
+ <literal>WHERE (a, b) NOT IN (SELECT x, y FROM ...)</literal>
+ when for instance <literal>b</literal> and <literal>y</literal> are <type>int4</type>
+ and <type>int8</type> respectively. This mistake led to wrong answers
or crashes depending on the specific datatypes involved.
</para>
</listitem>
<para>
This oversight could result in wrong answers from merge joins whose
inner side is an index scan using an
- <literal><replaceable>indexed_column</> =
- ANY(<replaceable>array</>)</literal> condition.
+ <literal><replaceable>indexed_column</replaceable> =
+ ANY(<replaceable>array</replaceable>)</literal> condition.
</para>
</listitem>
<listitem>
<para>
Acquire buffer lock when re-fetching the old tuple for an
- <literal>AFTER ROW UPDATE/DELETE</> trigger (Andres Freund)
+ <literal>AFTER ROW UPDATE/DELETE</literal> trigger (Andres Freund)
</para>
<para>
In very unusual circumstances, this oversight could result in passing
- incorrect data to a trigger <literal>WHEN</> condition, or to the
+ incorrect data to a trigger <literal>WHEN</literal> condition, or to the
precheck logic for a foreign-key enforcement trigger. That could
result in a crash, or in an incorrect decision about whether to
fire the trigger.
<listitem>
<para>
- Fix <command>ALTER COLUMN TYPE</> to handle inherited check
+ Fix <command>ALTER COLUMN TYPE</command> to handle inherited check
constraints properly (Pavan Deolasee)
</para>
<listitem>
<para>
- Fix <command>ALTER EXTENSION SET SCHEMA</>'s failure to move some
+ Fix <command>ALTER EXTENSION SET SCHEMA</command>'s failure to move some
subsidiary objects into the new schema (Álvaro Herrera, Dimitri
Fontaine)
</para>
<listitem>
<para>
- Handle <command>CREATE TABLE AS EXECUTE</> correctly in extended query
+ Handle <command>CREATE TABLE AS EXECUTE</command> correctly in extended query
protocol (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Don't modify the input parse tree in <command>DROP RULE IF NOT
- EXISTS</> and <command>DROP TRIGGER IF NOT EXISTS</> (Tom Lane)
+ EXISTS</command> and <command>DROP TRIGGER IF NOT EXISTS</command> (Tom Lane)
</para>
<para>
<listitem>
<para>
- Fix <command>REASSIGN OWNED</> to handle grants on tablespaces
+ Fix <command>REASSIGN OWNED</command> to handle grants on tablespaces
(Álvaro Herrera)
</para>
</listitem>
<listitem>
<para>
- Ignore incorrect <structname>pg_attribute</> entries for system
+ Ignore incorrect <structname>pg_attribute</structname> entries for system
columns for views (Tom Lane)
</para>
<listitem>
<para>
- Fix rule printing to dump <literal>INSERT INTO <replaceable>table</>
+ Fix rule printing to dump <literal>INSERT INTO <replaceable>table</replaceable>
DEFAULT VALUES</literal> correctly (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Guard against stack overflow when there are too many
- <literal>UNION</>/<literal>INTERSECT</>/<literal>EXCEPT</> clauses
+ <literal>UNION</literal>/<literal>INTERSECT</literal>/<literal>EXCEPT</literal> clauses
in a query (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix failure to advance XID epoch if XID wraparound happens during a
- checkpoint and <varname>wal_level</> is <literal>hot_standby</>
+ checkpoint and <varname>wal_level</varname> is <literal>hot_standby</literal>
(Tom Lane, Andres Freund)
</para>
<para>
While this mistake had no particular impact on
<productname>PostgreSQL</productname> itself, it was bad for
- applications that rely on <function>txid_current()</> and related
+ applications that rely on <function>txid_current()</function> and related
functions: the TXID value would appear to go backwards.
</para>
</listitem>
<listitem>
<para>
- Fix <function>pg_terminate_backend()</> and
- <function>pg_cancel_backend()</> to not throw error for a non-existent
+ Fix <function>pg_terminate_backend()</function> and
+ <function>pg_cancel_backend()</function> to not throw error for a non-existent
target process (Josh Kupershmidt)
</para>
<listitem>
<para>
Fix display of
- <structname>pg_stat_replication</>.<structfield>sync_state</> at a
+ <structname>pg_stat_replication</structname>.<structfield>sync_state</structfield> at a
page boundary (Kyotaro Horiguchi)
</para>
</listitem>
<para>
Formerly, this would result in something quite unhelpful, such as
- <quote>Non-recoverable failure in name resolution</>.
+ <quote>Non-recoverable failure in name resolution</quote>.
</para>
</listitem>
<listitem>
<para>
- Make <application>pg_ctl</> more robust about reading the
- <filename>postmaster.pid</> file (Heikki Linnakangas)
+ Make <application>pg_ctl</application> more robust about reading the
+ <filename>postmaster.pid</filename> file (Heikki Linnakangas)
</para>
<para>
<listitem>
<para>
- Fix possible crash in <application>psql</> if incorrectly-encoded data
- is presented and the <varname>client_encoding</> setting is a
+ Fix possible crash in <application>psql</application> if incorrectly-encoded data
+ is presented and the <varname>client_encoding</varname> setting is a
client-only encoding, such as SJIS (Jiang Guiqing)
</para>
</listitem>
<listitem>
<para>
- Make <application>pg_dump</> dump <literal>SEQUENCE SET</> items in
+ Make <application>pg_dump</application> dump <literal>SEQUENCE SET</literal> items in
the data not pre-data section of the archive (Tom Lane)
</para>
<para>
This fixes an undesirable inconsistency between the meanings of
- <option>--data-only</> and <option>--section=data</>, and also fixes
+ <option>--data-only</option> and <option>--section=data</option>, and also fixes
dumping of sequences that are marked as extension configuration tables.
</para>
</listitem>
<listitem>
<para>
- Fix <application>pg_dump</>'s handling of <command>DROP DATABASE</>
- commands in <option>--clean</> mode (Guillaume Lelarge)
+ Fix <application>pg_dump</application>'s handling of <command>DROP DATABASE</command>
+ commands in <option>--clean</option> mode (Guillaume Lelarge)
</para>
<para>
- Beginning in 9.2.0, <literal>pg_dump --clean</> would issue a
- <command>DROP DATABASE</> command, which was either useless or
+ Beginning in 9.2.0, <literal>pg_dump --clean</literal> would issue a
+ <command>DROP DATABASE</command> command, which was either useless or
dangerous depending on the usage scenario. It no longer does that.
- This change also fixes the combination of <option>--clean</> and
- <option>--create</> to work sensibly, i.e., emit <command>DROP
- DATABASE</> then <command>CREATE DATABASE</> before reconnecting to the
+ This change also fixes the combination of <option>--clean</option> and
+ <option>--create</option> to work sensibly, i.e., emit <command>DROP
+ DATABASE</command> then <command>CREATE DATABASE</command> before reconnecting to the
target database.
</para>
</listitem>
<listitem>
<para>
- Fix <application>pg_dump</> for views with circular dependencies and
+ Fix <application>pg_dump</application> for views with circular dependencies and
no relation options (Tom Lane)
</para>
The previous fix to dump relation options when a view is
involved in a circular dependency didn't work right for the case
that the view has no options; it emitted <literal>ALTER VIEW foo
- SET ()</> which is invalid syntax.
+ SET ()</literal> which is invalid syntax.
</para>
</listitem>
<listitem>
<para>
- Fix bugs in the <filename>restore.sql</> script emitted by
- <application>pg_dump</> in <literal>tar</> output format (Tom Lane)
+ Fix bugs in the <filename>restore.sql</filename> script emitted by
+ <application>pg_dump</application> in <literal>tar</literal> output format (Tom Lane)
</para>
<para>
The script would fail outright on tables whose names include
upper-case characters. Also, make the script capable of restoring
- data in <option>--inserts</> mode as well as the regular COPY mode.
+ data in <option>--inserts</option> mode as well as the regular COPY mode.
</para>
</listitem>
<listitem>
<para>
- Fix <application>pg_restore</> to accept POSIX-conformant
- <literal>tar</> files (Brian Weaver, Tom Lane)
+ Fix <application>pg_restore</application> to accept POSIX-conformant
+ <literal>tar</literal> files (Brian Weaver, Tom Lane)
</para>
<para>
- The original coding of <application>pg_dump</>'s <literal>tar</>
+ The original coding of <application>pg_dump</application>'s <literal>tar</literal>
output mode produced files that are not fully conformant with the
POSIX standard. This has been corrected for version 9.3. This
patch updates previous branches so that they will accept both the
<listitem>
<para>
- Fix <literal>tar</> files emitted by <application>pg_basebackup</> to
+ Fix <literal>tar</literal> files emitted by <application>pg_basebackup</application> to
be POSIX conformant (Brian Weaver, Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix <application>pg_resetxlog</> to locate <filename>postmaster.pid</>
+ Fix <application>pg_resetxlog</application> to locate <filename>postmaster.pid</filename>
correctly when given a relative path to the data directory (Tom Lane)
</para>
<para>
- This mistake could lead to <application>pg_resetxlog</> not noticing
+ This mistake could lead to <application>pg_resetxlog</application> not noticing
that there is an active postmaster using the data directory.
</para>
</listitem>
<listitem>
<para>
- Fix <application>libpq</>'s <function>lo_import()</> and
- <function>lo_export()</> functions to report file I/O errors properly
+ Fix <application>libpq</application>'s <function>lo_import()</function> and
+ <function>lo_export()</function> functions to report file I/O errors properly
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix <application>ecpg</>'s processing of nested structure pointer
+ Fix <application>ecpg</application>'s processing of nested structure pointer
variables (Muhammad Usama)
</para>
</listitem>
<listitem>
<para>
- Fix <application>ecpg</>'s <function>ecpg_get_data</> function to
+ Fix <application>ecpg</application>'s <function>ecpg_get_data</function> function to
handle arrays properly (Michael Meskes)
</para>
</listitem>
<listitem>
<para>
- Prevent <application>pg_upgrade</> from trying to process TOAST tables
+ Prevent <application>pg_upgrade</application> from trying to process TOAST tables
for system catalogs (Bruce Momjian)
</para>
<para>
- This fixes an error seen when the <literal>information_schema</> has
+ This fixes an error seen when the <literal>information_schema</literal> has
been dropped and recreated. Other failures were also possible.
</para>
</listitem>
<listitem>
<para>
- Improve <application>pg_upgrade</> performance by setting
- <varname>synchronous_commit</> to <literal>off</> in the new cluster
+ Improve <application>pg_upgrade</application> performance by setting
+ <varname>synchronous_commit</varname> to <literal>off</literal> in the new cluster
(Bruce Momjian)
</para>
</listitem>
<listitem>
<para>
- Make <filename>contrib/pageinspect</>'s btree page inspection
+ Make <filename>contrib/pageinspect</filename>'s btree page inspection
functions take buffer locks while examining pages (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Work around unportable behavior of <literal>malloc(0)</> and
- <literal>realloc(NULL, 0)</> (Tom Lane)
+ Work around unportable behavior of <literal>malloc(0)</literal> and
+ <literal>realloc(NULL, 0)</literal> (Tom Lane)
</para>
<para>
- On platforms where these calls return <literal>NULL</>, some code
+ On platforms where these calls return <literal>NULL</literal>, some code
mistakenly thought that meant out-of-memory.
- This is known to have broken <application>pg_dump</> for databases
+ This is known to have broken <application>pg_dump</application> for databases
containing no user-defined aggregates. There might be other cases
as well.
</para>
<listitem>
<para>
- Ensure that <literal>make install</> for an extension creates the
- <filename>extension</> installation directory (Cédric Villemain)
+ Ensure that <literal>make install</literal> for an extension creates the
+ <filename>extension</filename> installation directory (Cédric Villemain)
</para>
<para>
- Previously, this step was missed if <varname>MODULEDIR</> was set in
+ Previously, this step was missed if <varname>MODULEDIR</varname> was set in
the extension's Makefile.
</para>
</listitem>
<listitem>
<para>
- Fix <application>pgxs</> support for building loadable modules on AIX
+ Fix <application>pgxs</application> support for building loadable modules on AIX
(Tom Lane)
</para>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2012j
+ Update time zone data files to <application>tzdata</application> release 2012j
for DST law changes in Cuba, Israel, Jordan, Libya, Palestine, Western
Samoa, and portions of Brazil.
</para>
</para>
<para>
- However, you may need to perform <command>REINDEX</> and/or
- <command>VACUUM</> operations to recover from the effects of the data
+ However, you may need to perform <command>REINDEX</command> and/or
+ <command>VACUUM</command> operations to recover from the effects of the data
corruption bug described in the first changelog item below.
</para>
likely to occur on standby slave servers since those perform much
more WAL replay. There is a low probability of corruption of btree
and GIN indexes. There is a much higher probability of corruption
- of table <quote>visibility maps</>, which might lead to wrong answers
+ of table <quote>visibility maps</quote>, which might lead to wrong answers
from index-only scans. Table data proper cannot be corrupted by this
bug.
</para>
<para>
While no index corruption due to this bug is known to have occurred
in the field, as a precautionary measure it is recommended that
- production installations <command>REINDEX</> all btree and GIN
+ production installations <command>REINDEX</command> all btree and GIN
indexes at a convenient time after upgrading to 9.2.1.
</para>
<para>
- Also, it is recommended to perform a <command>VACUUM</> of all tables
+ Also, it is recommended to perform a <command>VACUUM</command> of all tables
while having <link
- linkend="guc-vacuum-freeze-table-age"><varname>vacuum_freeze_table_age</></link>
+ linkend="guc-vacuum-freeze-table-age"><varname>vacuum_freeze_table_age</varname></link>
set to zero. This will fix any incorrect visibility map data. <link
- linkend="guc-vacuum-cost-delay"><varname>vacuum_cost_delay</></link>
+ linkend="guc-vacuum-cost-delay"><varname>vacuum_cost_delay</varname></link>
can be adjusted to reduce the performance impact of vacuuming, while
causing it to take longer to finish.
</para>
<listitem>
<para>
Fix possible incorrect sorting of output from queries involving
- <literal>WHERE <replaceable>indexed_column</> IN
- (<replaceable>list_of_values</>)</literal> (Tom Lane)
+ <literal>WHERE <replaceable>indexed_column</replaceable> IN
+ (<replaceable>list_of_values</replaceable>)</literal> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix planner failure for queries involving <literal>GROUP BY</>
+ Fix planner failure for queries involving <literal>GROUP BY</literal>
expressions along with window functions and aggregates (Tom Lane)
</para>
</listitem>
<para>
This error could result in wrong answers from queries that scan the
- same <literal>WITH</> subquery multiple times.
+ same <literal>WITH</literal> subquery multiple times.
</para>
</listitem>
<listitem>
<para>
Improve selectivity estimation for text search queries involving
- prefixes, i.e. <replaceable>word</><literal>:*</> patterns (Tom Lane)
+ prefixes, i.e. <replaceable>word</replaceable><literal>:*</literal> patterns (Tom Lane)
</para>
</listitem>
<para>
A command that needed no locks other than ones its transaction already
- had might fail to notice a concurrent <command>GRANT</> or
- <command>REVOKE</> that committed since the start of its transaction.
+ had might fail to notice a concurrent <command>GRANT</command> or
+ <command>REVOKE</command> that committed since the start of its transaction.
</para>
</listitem>
<listitem>
<para>
- Fix <command>ANALYZE</> to not fail when a column is a domain over an
+ Fix <command>ANALYZE</command> to not fail when a column is a domain over an
array type (Tom Lane)
</para>
</listitem>
<para>
Some Linux distributions contain an incorrect version of
- <filename>pthread.h</> that results in incorrect compiled code in
+ <filename>pthread.h</filename> that results in incorrect compiled code in
PL/Perl, leading to crashes if a PL/Perl function calls another one
that throws an error.
</para>
<listitem>
<para>
- Remove unnecessary dependency on <application>pg_config</> from
- <application>pg_upgrade</> (Peter Eisentraut)
+ Remove unnecessary dependency on <application>pg_config</application> from
+ <application>pg_upgrade</application> (Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2012f
+ Update time zone data files to <application>tzdata</application> release 2012f
for DST law changes in Fiji
</para>
</listitem>
<listitem>
<para>
Allow queries to retrieve data only from indexes, avoiding heap
- access (<firstterm>index-only scans</>)
+ access (<firstterm>index-only scans</firstterm>)
</para>
</listitem>
<para>
Allow streaming replication slaves to forward data to other slaves
(<link linkend="cascading-replication"><firstterm>cascading
- replication</></link>)
+ replication</firstterm></link>)
</para>
</listitem>
<listitem>
<para>
Allow <link
- linkend="app-pgbasebackup"><application>pg_basebackup</></link>
+ linkend="app-pgbasebackup"><application>pg_basebackup</application></link>
to make base backups from standby servers
</para>
</listitem>
<listitem>
<para>
Add a <link
- linkend="app-pgreceivewal"><application>pg_receivexlog</></link>
+ linkend="app-pgreceivewal"><application>pg_receivexlog</application></link>
tool to archive WAL file changes as they are written
</para>
</listitem>
<listitem>
<para>
- Add the <link linkend="SPGiST">SP-GiST</link> (Space-Partitioned
+ Add the <link linkend="spgist">SP-GiST</link> (Space-Partitioned
GiST) index access method
</para>
</listitem>
<listitem>
<para>
Add a <link
- linkend="SQL-CREATEVIEW"><literal>security_barrier</></link>
+ linkend="sql-createview"><literal>security_barrier</literal></link>
option for views
</para>
</listitem>
<listitem>
<para>
- Allow <application>libpq</> connection strings to have the format of a
+ Allow <application>libpq</application> connection strings to have the format of a
<link linkend="libpq-connstring"><acronym>URI</acronym></link>
</para>
</listitem>
<listitem>
<para>
Add a <link linkend="libpq-single-row-mode">single-row processing
- mode</link> to <application>libpq</> for better handling of large
+ mode</link> to <application>libpq</application> for better handling of large
result sets
</para>
</listitem>
<listitem>
<para>
- Remove the <structfield>spclocation</> field from <link
- linkend="catalog-pg-tablespace"><structname>pg_tablespace</></link>
+ Remove the <structfield>spclocation</structfield> field from <link
+ linkend="catalog-pg-tablespace"><structname>pg_tablespace</structname></link>
(Magnus Hagander)
</para>
a tablespace. This change allows tablespace directories to be moved
while the server is down, by manually adjusting the symbolic links.
To replace this field, we have added <link
- linkend="functions-info-catalog-table"><function>pg_tablespace_location()</></link>
+ linkend="functions-info-catalog-table"><function>pg_tablespace_location()</function></link>
to allow querying of the symbolic links.
</para>
</listitem>
<listitem>
<para>
- Move <type>tsvector</> most-common-element statistics to new
- <link linkend="view-pg-stats"><structname>pg_stats</></link> columns
+ Move <type>tsvector</type> most-common-element statistics to new
+ <link linkend="view-pg-stats"><structname>pg_stats</structname></link> columns
(Alexander Korotkov)
</para>
<para>
- Consult <structfield>most_common_elems</>
- and <structfield>most_common_elem_freqs</> for the data formerly
- available in <structfield>most_common_vals</>
- and <structfield>most_common_freqs</> for a <type>tsvector</> column.
+ Consult <structfield>most_common_elems</structfield>
+ and <structfield>most_common_elem_freqs</structfield> for the data formerly
+ available in <structfield>most_common_vals</structfield>
+ and <structfield>most_common_freqs</structfield> for a <type>tsvector</type> column.
</para>
</listitem>
<listitem>
<para>
- Remove <link linkend="hstore">hstore</link>'s <literal>=></>
+ Remove <link linkend="hstore">hstore</link>'s <literal>=></literal>
operator (Robert Haas)
</para>
<para>
- Users should now use <function>hstore(text, text)</>. Since
+ Users should now use <function>hstore(text, text)</function>. Since
<productname>PostgreSQL</productname> 9.0, a warning message has been
- emitted when an operator named <literal>=></> is created because
+ emitted when an operator named <literal>=></literal> is created because
the <acronym>SQL</acronym> standard reserves that token for
another use.
</para>
<listitem>
<para>
Ensure that <link
- linkend="functions-xml-processing"><function>xpath()</></link>
+ linkend="functions-xml-processing"><function>xpath()</function></link>
escapes special characters in string values (Florian Pflug)
</para>
<listitem>
<para>
Make <link
- linkend="functions-admin-dbobject"><function>pg_relation_size()</></link>
+ linkend="functions-admin-dbobject"><function>pg_relation_size()</function></link>
and friends return NULL if the object does not exist (Phil Sorber)
</para>
<para>
This prevents queries that call these functions from returning
- errors immediately after a concurrent <command>DROP</>.
+ errors immediately after a concurrent <command>DROP</command>.
</para>
</listitem>
<para>
Make <link
linkend="functions-datetime-extract"><function>EXTRACT(EPOCH FROM
- <replaceable>timestamp without time zone</>)</function></link>
+ <replaceable>timestamp without time zone</replaceable>)</function></link>
measure the epoch from local midnight, not <acronym>UTC</acronym>
midnight (Tom Lane)
</para>
This change reverts an ill-considered change made in release 7.3.
Measuring from <acronym>UTC</acronym> midnight was inconsistent
because it made the result dependent on the <link
- linkend="guc-timezone"><varname>timezone</></link> setting, which
- computations for <type>timestamp without time zone</> should not be.
+ linkend="guc-timezone"><varname>timezone</varname></link> setting, which
+ computations for <type>timestamp without time zone</type> should not be.
The previous behavior remains available by casting the input value
- to <type>timestamp with time zone</>.
+ to <type>timestamp with time zone</type>.
</para>
</listitem>
<listitem>
<para>
- Properly parse time strings with trailing <literal>yesterday</>,
- <literal>today</>, and <literal>tomorrow</> (Dean Rasheed)
+ Properly parse time strings with trailing <literal>yesterday</literal>,
+ <literal>today</literal>, and <literal>tomorrow</literal> (Dean Rasheed)
</para>
<para>
<listitem>
<para>
Fix <link
- linkend="functions-formatting"><function>to_date()</></link> and
- <function>to_timestamp()</> to wrap incomplete dates toward 2020
+ linkend="functions-formatting"><function>to_date()</function></link> and
+ <function>to_timestamp()</function> to wrap incomplete dates toward 2020
(Bruce Momjian)
</para>
<listitem>
<para>
- Prevent <link linkend="SQL-ALTERDOMAIN"><command>ALTER
+ Prevent <link linkend="sql-alterdomain"><command>ALTER
DOMAIN</command></link> from working on non-domain types (Peter
Eisentraut)
</para>
<listitem>
<para>
No longer forcibly lowercase procedural language names in <link
- linkend="SQL-CREATEFUNCTION"><command>CREATE FUNCTION</></link>
+ linkend="sql-createfunction"><command>CREATE FUNCTION</command></link>
(Robert Haas)
</para>
<para>
While unquoted language identifiers are still lowercased, strings
and quoted identifiers are no longer forcibly down-cased.
- Thus for example <literal>CREATE FUNCTION ... LANGUAGE 'C'</>
- will no longer work; it must be spelled <literal>'c'</>, or better
+ Thus for example <literal>CREATE FUNCTION ... LANGUAGE 'C'</literal>
+ will no longer work; it must be spelled <literal>'c'</literal>, or better
omit the quotes.
</para>
</listitem>
<para>
Provide consistent backquote, variable
expansion, and quoted substring behavior in <link
- linkend="APP-PSQL"><application>psql</></link> meta-command
+ linkend="app-psql"><application>psql</application></link> meta-command
arguments (Tom Lane)
</para>
<para>
Previously, such references were treated oddly when not separated by
- whitespace from adjacent text. For example <literal>'FOO'BAR</> was
- output as <literal>FOO BAR</> (unexpected insertion of a space) and
- <literal>FOO'BAR'BAZ</> was output unchanged (not removing the quotes
+ whitespace from adjacent text. For example <literal>'FOO'BAR</literal> was
+ output as <literal>FOO BAR</literal> (unexpected insertion of a space) and
+ <literal>FOO'BAR'BAZ</literal> was output unchanged (not removing the quotes
as most would expect).
</para>
</listitem>
<listitem>
<para>
No longer treat <link
- linkend="APP-CLUSTERDB"><application>clusterdb</></link>
+ linkend="app-clusterdb"><application>clusterdb</application></link>
table names as double-quoted; no longer treat <link
- linkend="APP-REINDEXDB"><application>reindexdb</></link> table
+ linkend="app-reindexdb"><application>reindexdb</application></link> table
and index names as double-quoted (Bruce Momjian)
</para>
<listitem>
<para>
- <link linkend="APP-CREATEUSER"><application>createuser</></link>
+ <link linkend="app-createuser"><application>createuser</application></link>
no longer prompts for option settings by default (Peter Eisentraut)
</para>
<para>
- Use <option>--interactive</> to obtain the old behavior.
+ Use <option>--interactive</option> to obtain the old behavior.
</para>
</listitem>
<listitem>
<para>
Disable prompting for the user name in <link
- linkend="APP-DROPUSER"><application>dropuser</></link> unless
- <option>--interactive</> is specified (Peter Eisentraut)
+ linkend="app-dropuser"><application>dropuser</application></link> unless
+ <option>--interactive</option> is specified (Peter Eisentraut)
</para>
</listitem>
<para>
This allows changing the names and locations of the files that were
- previously hard-coded as <filename>server.crt</>,
- <filename>server.key</>, <filename>root.crt</>, and
- <filename>root.crl</> in the data directory.
- <emphasis>The server will no longer examine <filename>root.crt</> or
- <filename>root.crl</> by default</emphasis>; to load these files, the
+ previously hard-coded as <filename>server.crt</filename>,
+ <filename>server.key</filename>, <filename>root.crt</filename>, and
+ <filename>root.crl</filename> in the data directory.
+ <emphasis>The server will no longer examine <filename>root.crt</filename> or
+ <filename>root.crl</filename> by default</emphasis>; to load these files, the
associated parameters must be set to non-default values.
</para>
</listitem>
<listitem>
<para>
- Remove the <varname>silent_mode</> parameter (Heikki Linnakangas)
+ Remove the <varname>silent_mode</varname> parameter (Heikki Linnakangas)
</para>
<para>
Similar behavior can be obtained with <command>pg_ctl start
- -l postmaster.log</>.
+ -l postmaster.log</command>.
</para>
</listitem>
<listitem>
<para>
- Remove the <varname>wal_sender_delay</> parameter,
+ Remove the <varname>wal_sender_delay</varname> parameter,
as it is no longer needed (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Remove the <varname>custom_variable_classes</> parameter (Tom Lane)
+ Remove the <varname>custom_variable_classes</varname> parameter (Tom Lane)
</para>
<para>
<listitem>
<para>
Rename <link
- linkend="monitoring-stats-views-table"><structname>pg_stat_activity</></link><structfield>.procpid</>
- to <structfield>pid</>, to match other system tables (Magnus Hagander)
+ linkend="monitoring-stats-views-table"><structname>pg_stat_activity</structname></link><structfield>.procpid</structfield>
+ to <structfield>pid</structfield>, to match other system tables (Magnus Hagander)
</para>
</listitem>
<listitem>
<para>
- Create a separate <structfield>pg_stat_activity</> column to
+ Create a separate <structfield>pg_stat_activity</structfield> column to
report process state (Scott Mead, Magnus Hagander)
</para>
<para>
- The previous <structfield>query</> and <structfield>query_start</>
+ The previous <structfield>query</structfield> and <structfield>query_start</structfield>
values now remain available for an idle session, allowing enhanced
analysis.
</para>
<listitem>
<para>
- Rename <structname>pg_stat_activity</>.<structfield>current_query</> to
- <structfield>query</> because it is not cleared when the query
+ Rename <structname>pg_stat_activity</structname>.<structfield>current_query</structfield> to
+ <structfield>query</structfield> because it is not cleared when the query
completes (Magnus Hagander)
</para>
</listitem>
<listitem>
<para>
Change all <acronym>SQL</acronym>-level statistics timing values
- to be <type>float8</> columns measured in milliseconds (Tom Lane)
+ to be <type>float8</type> columns measured in milliseconds (Tom Lane)
</para>
<para>
This change eliminates the designed-in assumption that the values
- are accurate to microseconds and no more (since the <type>float8</>
+ are accurate to microseconds and no more (since the <type>float8</type>
values can be fractional).
The columns affected are
- <structname>pg_stat_user_functions</>.<structfield>total_time</>,
- <structname>pg_stat_user_functions</>.<structfield>self_time</>,
- <structname>pg_stat_xact_user_functions</>.<structfield>total_time</>,
+ <structname>pg_stat_user_functions</structname>.<structfield>total_time</structfield>,
+ <structname>pg_stat_user_functions</structname>.<structfield>self_time</structfield>,
+ <structname>pg_stat_xact_user_functions</structname>.<structfield>total_time</structfield>,
and
- <structname>pg_stat_xact_user_functions</>.<structfield>self_time</>.
+ <structname>pg_stat_xact_user_functions</structname>.<structfield>self_time</structfield>.
The statistics functions underlying these columns now also return
- <type>float8</> milliseconds, rather than <type>bigint</>
+ <type>float8</type> milliseconds, rather than <type>bigint</type>
microseconds.
- <filename>contrib/pg_stat_statements</>'
- <structfield>total_time</> column is now also measured in
+ <filename>contrib/pg_stat_statements</filename>'
+ <structfield>total_time</structfield> column is now also measured in
milliseconds.
</para>
</listitem>
</para>
<para>
- This feature is often called <firstterm>index-only scans</>.
+ This feature is often called <firstterm>index-only scans</firstterm>.
Heap access can be skipped for heap pages containing only tuples that
are visible to all sessions, as reported by the visibility map; so
the benefit applies mainly to mostly-static data. The visibility map
<listitem>
<para>
- Add the <link linkend="SPGiST">SP-GiST</link> (Space-Partitioned
+ Add the <link linkend="spgist">SP-GiST</link> (Space-Partitioned
GiST) index access method (Teodor Sigaev, Oleg Bartunov, Tom
Lane)
</para>
<listitem>
<para>
- Move the frequently accessed members of the <structname>PGPROC</>
+ Move the frequently accessed members of the <structname>PGPROC</structname>
shared memory array to a separate array (Pavan
Deolasee, Heikki Linnakangas, Robert Haas)
</para>
<listitem>
<para>
Make the number of CLOG buffers scale based on <link
- linkend="guc-shared-buffers"><varname>shared_buffers</></link>
+ linkend="guc-shared-buffers"><varname>shared_buffers</varname></link>
(Robert Haas, Simon Riggs, Tom Lane)
</para>
</listitem>
<para>
Previously, only <link
- linkend="guc-wal-writer-delay"><varname>wal_writer_delay</></link>
+ linkend="guc-wal-writer-delay"><varname>wal_writer_delay</varname></link>
triggered <acronym>WAL</acronym> flushing to disk; now filling a
<acronym>WAL</acronym> buffer also triggers <acronym>WAL</acronym>
writes.
<para>
In the past, a prepared statement always had a single
- <quote>generic</> plan that was used for all parameter values, which
+ <quote>generic</quote> plan that was used for all parameter values, which
was frequently much inferior to the plans used for non-prepared
statements containing explicit constant values. Now, the planner
attempts to generate custom plans for specific parameter values.
</para>
<para>
- The new <quote>parameterized path</> mechanism allows inner
+ The new <quote>parameterized path</quote> mechanism allows inner
index scans to use values from relations that are more than one join
level up from the scan. This can greatly improve performance in
situations where semantic restrictions (such as outer joins) limit
</para>
<para>
- Wrappers can now provide multiple access <quote>paths</> for their
+ Wrappers can now provide multiple access <quote>paths</quote> for their
tables, allowing more flexibility in join planning.
</para>
</listitem>
<para>
This check is only performed when <link
- linkend="guc-constraint-exclusion"><varname>constraint_exclusion</></link>
+ linkend="guc-constraint-exclusion"><varname>constraint_exclusion</varname></link>
is <literal>on</literal>.
</para>
</listitem>
<listitem>
<para>
- Allow <literal>indexed_col op ANY(ARRAY[...])</> conditions to be
+ Allow <literal>indexed_col op ANY(ARRAY[...])</literal> conditions to be
used in plain index scans and index-only scans (Tom Lane)
</para>
<listitem>
<para>
- Support <function>MIN</>/<function>MAX</> index optimizations on
+ Support <function>MIN</function>/<function>MAX</function> index optimizations on
<type>boolean</type> columns (Marti Raudsepp)
</para>
</listitem>
<listitem>
<para>
- Account for set-returning functions in <command>SELECT</> target
+ Account for set-returning functions in <command>SELECT</command> target
lists when setting row count estimates (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Improve statistical estimates for subqueries using
- <literal>DISTINCT</> (Tom Lane)
+ <literal>DISTINCT</literal> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Do not treat role names and <literal>samerole</> specified in <link
+ Do not treat role names and <literal>samerole</literal> specified in <link
linkend="auth-pg-hba-conf"><filename>pg_hba.conf</filename></link>
as automatically including superusers (Andrew Dunstan)
</para>
<para>
- This makes it easier to use <literal>reject</> lines with group roles.
+ This makes it easier to use <literal>reject</literal> lines with group roles.
</para>
</listitem>
<para>
This logging is triggered by <link
- linkend="guc-log-autovacuum-min-duration"><varname>log_autovacuum_min_duration</></link>.
+ linkend="guc-log-autovacuum-min-duration"><varname>log_autovacuum_min_duration</varname></link>.
</para>
</listitem>
<listitem>
<para>
Add <link
- linkend="functions-admin-backup"><function>pg_xlog_location_diff()</></link>
+ linkend="functions-admin-backup"><function>pg_xlog_location_diff()</function></link>
to simplify WAL location comparisons (Euler Taveira de Oliveira)
</para>
<para>
This allows different instances to use the event log
with different identifiers, by setting the <link
- linkend="guc-event-source"><varname>event_source</></link>
+ linkend="guc-event-source"><varname>event_source</varname></link>
server parameter, which is similar to how <link
- linkend="guc-syslog-ident"><varname>syslog_ident</></link> works.
+ linkend="guc-syslog-ident"><varname>syslog_ident</varname></link> works.
</para>
</listitem>
<listitem>
<para>
- Change <quote>unexpected EOF</> messages to <literal>DEBUG1</> level,
+ Change <quote>unexpected EOF</quote> messages to <literal>DEBUG1</literal> level,
except when there is an open transaction (Magnus Hagander)
</para>
<listitem>
<para>
Track temporary file sizes and file counts in the <link
- linkend="pg-stat-database-view"><structname>pg_stat_database</></link>
+ linkend="pg-stat-database-view"><structname>pg_stat_database</structname></link>
system view (Tomas Vondra)
</para>
</listitem>
<listitem>
<para>
- Add a deadlock counter to the <structname>pg_stat_database</>
+ Add a deadlock counter to the <structname>pg_stat_database</structname>
system view (Magnus Hagander)
</para>
</listitem>
<listitem>
<para>
Add a server parameter <link
- linkend="guc-track-io-timing"><varname>track_io_timing</></link>
+ linkend="guc-track-io-timing"><varname>track_io_timing</varname></link>
to track I/O timings (Ants Aasma, Robert Haas)
</para>
</listitem>
<listitem>
<para>
Report checkpoint timing information in <link
- linkend="pg-stat-bgwriter-view"><structname>pg_stat_bgwriter</></link>
+ linkend="pg-stat-bgwriter-view"><structname>pg_stat_bgwriter</structname></link>
(Greg Smith, Peter Geoghegan)
</para>
</listitem>
<listitem>
<para>
Silently ignore nonexistent schemas specified in <link
- linkend="guc-search-path"><varname>search_path</></link> (Tom Lane)
+ linkend="guc-search-path"><varname>search_path</varname></link> (Tom Lane)
</para>
<para>
<listitem>
<para>
Allow superusers to set <link
- linkend="guc-deadlock-timeout"><varname>deadlock_timeout</></link>
+ linkend="guc-deadlock-timeout"><varname>deadlock_timeout</varname></link>
per-session, not just per-cluster (Noah Misch)
</para>
<para>
- This allows <varname>deadlock_timeout</> to be reduced for
+ This allows <varname>deadlock_timeout</varname> to be reduced for
transactions that are likely to be involved in a deadlock, thus
detecting the failure more quickly. Alternatively, increasing the
value can be used to reduce the chances of a session being chosen for
<listitem>
<para>
Add a server parameter <link
- linkend="guc-temp-file-limit"><varname>temp_file_limit</></link>
+ linkend="guc-temp-file-limit"><varname>temp_file_limit</varname></link>
to constrain temporary file space usage per session (Mark Kirkwood)
</para>
</listitem>
<listitem>
<para>
- Add <link linkend="app-postmaster">postmaster</link> <option>-C</>
+ Add <link linkend="app-postmaster">postmaster</link> <option>-C</option>
option to query configuration parameters (Bruce Momjian)
</para>
<para>
- This allows <application>pg_ctl</> to better handle cases where
- <envar>PGDATA</> or <option>-D</> points to a configuration-only
+ This allows <application>pg_ctl</application> to better handle cases where
+ <envar>PGDATA</envar> or <option>-D</option> points to a configuration-only
directory.
</para>
</listitem>
<listitem>
<para>
Replace an empty locale name with the implied value in
- <command>CREATE DATABASE</>
+ <command>CREATE DATABASE</command>
(Tom Lane)
</para>
<para>
This prevents cases where
- <structname>pg_database</>.<structfield>datcollate</> or
- <structfield>datctype</> could be interpreted differently after a
+ <structname>pg_database</structname>.<structfield>datcollate</structfield> or
+ <structfield>datctype</structfield> could be interpreted differently after a
server restart.
</para>
</listitem>
<listitem>
<para>
- Add an <literal>include_if_exists</> facility for configuration
+ Add an <literal>include_if_exists</literal> facility for configuration
files (Greg Smith)
</para>
<para>
- This works the same as <literal>include</>, except that an error
+ This works the same as <literal>include</literal>, except that an error
is not thrown if the file is missing.
</para>
</listitem>
<listitem>
<para>
- Identify the server time zone during <application>initdb</>, and set
+ Identify the server time zone during <application>initdb</application>, and set
<filename>postgresql.conf</filename> entries
- <link linkend="guc-timezone"><varname>timezone</></link> and
- <link linkend="guc-log-timezone"><varname>log_timezone</></link>
+ <link linkend="guc-timezone"><varname>timezone</varname></link> and
+ <link linkend="guc-log-timezone"><varname>log_timezone</varname></link>
accordingly (Tom Lane)
</para>
<listitem>
<para>
Fix <link
- linkend="view-pg-settings"><structname>pg_settings</></link> to
+ linkend="view-pg-settings"><structname>pg_settings</structname></link> to
report <filename>postgresql.conf</filename> line numbers on Windows
(Tom Lane)
</para>
<para>
Allow streaming replication slaves to forward data to other slaves
(<link linkend="cascading-replication"><firstterm>cascading
- replication</></link>) (Fujii Masao)
+ replication</firstterm></link>) (Fujii Masao)
</para>
<para>
<listitem>
<para>
Add new <link
- linkend="guc-synchronous-commit"><varname>synchronous_commit</></link>
- mode <literal>remote_write</> (Fujii Masao, Simon Riggs)
+ linkend="guc-synchronous-commit"><varname>synchronous_commit</varname></link>
+ mode <literal>remote_write</literal> (Fujii Masao, Simon Riggs)
</para>
<para>
<listitem>
<para>
Add a <link
- linkend="app-pgreceivewal"><application>pg_receivexlog</></link>
+ linkend="app-pgreceivewal"><application>pg_receivexlog</application></link>
tool to archive WAL file changes as they are written, rather
than waiting for completed WAL files (Magnus Hagander)
</para>
<listitem>
<para>
Allow <link
- linkend="app-pgbasebackup"><application>pg_basebackup</></link>
+ linkend="app-pgbasebackup"><application>pg_basebackup</application></link>
to make base backups from standby servers (Jun Ishizuka, Fujii Masao)
</para>
<listitem>
<para>
- Allow streaming of WAL files while <application>pg_basebackup</>
+ Allow streaming of WAL files while <application>pg_basebackup</application>
is performing a backup (Magnus Hagander)
</para>
<para>
This change allows better results when a row value is converted to
- <type>hstore</> or <type>json</> type: the fields of the resulting
+ <type>hstore</type> or <type>json</type> type: the fields of the resulting
value will now have the expected names.
</para>
</listitem>
<listitem>
<para>
- Improve column labels used for sub-<command>SELECT</> results
+ Improve column labels used for sub-<command>SELECT</command> results
(Marti Raudsepp)
</para>
<para>
- Previously, the generic label <literal>?column?</> was used.
+ Previously, the generic label <literal>?column?</literal> was used.
</para>
</listitem>
<listitem>
<para>
- When a row fails a <literal>CHECK</> or <literal>NOT NULL</>
+ When a row fails a <literal>CHECK</literal> or <literal>NOT NULL</literal>
constraint, show the row's contents as error detail (Jan
Kundrát)
</para>
<para>
This change adds locking that should eliminate <quote>cache lookup
- failed</> errors in many scenarios. Also, it is no longer possible
+ failed</quote> errors in many scenarios. Also, it is no longer possible
to add relations to a schema that is being concurrently dropped, a
scenario that formerly led to inconsistent system catalog contents.
</para>
<listitem>
<para>
- Add <literal>CONCURRENTLY</> option to <link
- linkend="SQL-DROPINDEX"><command>DROP INDEX</command></link>
+ Add <literal>CONCURRENTLY</literal> option to <link
+ linkend="sql-dropindex"><command>DROP INDEX</command></link>
(Simon Riggs)
</para>
<listitem>
<para>
- Allow <link linkend="ddl-constraints"><literal>CHECK</></link>
- constraints to be declared <literal>NOT VALID</> (Álvaro
+ Allow <link linkend="ddl-constraints"><literal>CHECK</literal></link>
+ constraints to be declared <literal>NOT VALID</literal> (Álvaro
Herrera)
</para>
<para>
- Adding a <literal>NOT VALID</> constraint does not cause the table to
+ Adding a <literal>NOT VALID</literal> constraint does not cause the table to
be scanned to verify that existing rows meet the constraint.
Subsequently, newly added or updated rows are checked.
Such constraints are ignored by the planner when considering
- <varname>constraint_exclusion</>, since it is not certain that all
+ <varname>constraint_exclusion</varname>, since it is not certain that all
rows meet the constraint.
</para>
<para>
- The new <command>ALTER TABLE VALIDATE</> command allows <literal>NOT
- VALID</> constraints to be checked for existing rows, after which
+ The new <command>ALTER TABLE VALIDATE</command> command allows <literal>NOT
+ VALID</literal> constraints to be checked for existing rows, after which
they are converted into ordinary constraints.
</para>
</listitem>
<listitem>
<para>
- Allow <literal>CHECK</> constraints to be declared <literal>NO
- INHERIT</> (Nikhil Sontakke, Alex Hunsaker, Álvaro Herrera)
+ Allow <literal>CHECK</literal> constraints to be declared <literal>NO
+ INHERIT</literal> (Nikhil Sontakke, Alex Hunsaker, Álvaro Herrera)
</para>
<para>
<listitem>
<para>
- Add the ability to <link linkend="SQL-ALTERTABLE">rename</link>
+ Add the ability to <link linkend="sql-altertable">rename</link>
constraints (Peter Eisentraut)
</para>
</listitem>
</sect4>
<sect4>
- <title><command>ALTER</></title>
+ <title><command>ALTER</command></title>
<itemizedlist>
<listitem>
<para>
Reduce need to rebuild tables and indexes for certain <link
- linkend="SQL-ALTERTABLE"><command>ALTER TABLE</command></link>
- ... <literal>ALTER COLUMN TYPE</> operations (Noah Misch)
+ linkend="sql-altertable"><command>ALTER TABLE</command></link>
+ ... <literal>ALTER COLUMN TYPE</literal> operations (Noah Misch)
</para>
<para>
- Increasing the length limit for a <type>varchar</> or <type>varbit</>
+ Increasing the length limit for a <type>varchar</type> or <type>varbit</type>
column, or removing the limit altogether, no longer requires a table
rewrite. Similarly, increasing the allowable precision of a
- <type>numeric</> column, or changing a column from constrained
- <type>numeric</> to unconstrained <type>numeric</>, no longer
+ <type>numeric</type> column, or changing a column from constrained
+ <type>numeric</type> to unconstrained <type>numeric</type>, no longer
requires a table rewrite. Table rewrites are also avoided in similar
- cases involving the <type>interval</>, <type>timestamp</>, and
- <type>timestamptz</> types.
+ cases involving the <type>interval</type>, <type>timestamp</type>, and
+ <type>timestamptz</type> types.
</para>
</listitem>
<listitem>
<para>
- Avoid having <link linkend="SQL-ALTERTABLE"><command>ALTER
+ Avoid having <link linkend="sql-altertable"><command>ALTER
TABLE</command></link> revalidate foreign key constraints in some
cases where it is not necessary (Noah Misch)
</para>
<listitem>
<para>
- Add <literal>IF EXISTS</> options to some <command>ALTER</command>
+ Add <literal>IF EXISTS</literal> options to some <command>ALTER</command>
commands (Pavel Stehule)
</para>
<listitem>
<para>
- Add <link linkend="SQL-ALTERFOREIGNDATAWRAPPER"><command>ALTER
- FOREIGN DATA WRAPPER</command></link> ... <literal>RENAME</>
- and <link linkend="SQL-ALTERSERVER"><command>ALTER
- SERVER</command></link> ... <literal>RENAME</> (Peter Eisentraut)
+ Add <link linkend="sql-alterforeigndatawrapper"><command>ALTER
+ FOREIGN DATA WRAPPER</command></link> ... <literal>RENAME</literal>
+ and <link linkend="sql-alterserver"><command>ALTER
+ SERVER</command></link> ... <literal>RENAME</literal> (Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
- Add <link linkend="SQL-ALTERDOMAIN"><command>ALTER
- DOMAIN</command></link> ... <literal>RENAME</> (Peter Eisentraut)
+ Add <link linkend="sql-alterdomain"><command>ALTER
+ DOMAIN</command></link> ... <literal>RENAME</literal> (Peter Eisentraut)
</para>
<para>
<listitem>
<para>
Throw an error for <command>ALTER DOMAIN</command> ... <literal>DROP
- CONSTRAINT</> on a nonexistent constraint (Peter Eisentraut)
+ CONSTRAINT</literal> on a nonexistent constraint (Peter Eisentraut)
</para>
<para>
- An <literal>IF EXISTS</> option has been added to provide the
+ An <literal>IF EXISTS</literal> option has been added to provide the
previous behavior.
</para>
</listitem>
</sect4>
<sect4>
- <title><link linkend="SQL-CREATETABLE"><command>CREATE TABLE</></link></title>
+ <title><link linkend="sql-createtable"><command>CREATE TABLE</command></link></title>
<itemizedlist>
<listitem>
<para>
- Fix <command>CREATE TABLE</command> ... <literal>AS EXECUTE</>
- to handle <literal>WITH NO DATA</> and column name specifications
+ Fix <command>CREATE TABLE</command> ... <literal>AS EXECUTE</literal>
+ to handle <literal>WITH NO DATA</literal> and column name specifications
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
Add a <link
- linkend="SQL-CREATEVIEW"><literal>security_barrier</></link>
+ linkend="sql-createview"><literal>security_barrier</literal></link>
option for views (KaiGai Kohei, Robert Haas)
</para>
<para>
This option prevents optimizations that might allow view-protected
data to be exposed to users, for example pushing a clause involving
- an insecure function into the <literal>WHERE</> clause of the view.
+ an insecure function into the <literal>WHERE</literal> clause of the view.
Such views can be expected to perform more poorly than ordinary
views.
</para>
<listitem>
<para>
Add a new <link
- linkend="SQL-CREATEFUNCTION"><literal>LEAKPROOF</></link> function
+ linkend="sql-createfunction"><literal>LEAKPROOF</literal></link> function
attribute to mark functions that can safely be pushed down
- into <literal>security_barrier</> views (KaiGai Kohei)
+ into <literal>security_barrier</literal> views (KaiGai Kohei)
</para>
</listitem>
</para>
<para>
- This adds support for the <acronym>SQL</>-conforming
- <literal>USAGE</> privilege on types and domains. The intent is
+ This adds support for the <acronym>SQL</acronym>-conforming
+ <literal>USAGE</literal> privilege on types and domains. The intent is
to be able to restrict which users can create dependencies on types,
since such dependencies limit the owner's ability to alter the type.
</para>
Because the object is being created by <command>SELECT INTO</command>
or <command>CREATE TABLE AS</command>, the creator would ordinarily
have insert permissions; but there are corner cases where this is not
- true, such as when <literal>ALTER DEFAULT PRIVILEGES</> has removed
+ true, such as when <literal>ALTER DEFAULT PRIVILEGES</literal> has removed
such permissions.
</para>
</listitem>
<listitem>
<para>
- Allow <link linkend="SQL-VACUUM"><command>VACUUM</></link> to more
+ Allow <link linkend="sql-vacuum"><command>VACUUM</command></link> to more
easily skip pages that cannot be locked (Simon Riggs, Robert Haas)
</para>
<para>
- This change should greatly reduce the incidence of <command>VACUUM</>
- getting <quote>stuck</> waiting for other sessions.
+ This change should greatly reduce the incidence of <command>VACUUM</command>
+ getting <quote>stuck</quote> waiting for other sessions.
</para>
</listitem>
<listitem>
<para>
- Make <link linkend="SQL-EXPLAIN"><command>EXPLAIN</></link>
- <literal>(BUFFERS)</> count blocks dirtied and written (Robert Haas)
+ Make <link linkend="sql-explain"><command>EXPLAIN</command></link>
+ <literal>(BUFFERS)</literal> count blocks dirtied and written (Robert Haas)
</para>
</listitem>
</para>
<para>
- This is accomplished by setting the new <literal>TIMING</> option to
- <literal>FALSE</>.
+ This is accomplished by setting the new <literal>TIMING</literal> option to
+ <literal>FALSE</literal>.
</para>
</listitem>
<listitem>
<para>
Add <link
- linkend="functions-json"><function>array_to_json()</></link>
- and <function>row_to_json()</> (Andrew Dunstan)
+ linkend="functions-json"><function>array_to_json()</function></link>
+ and <function>row_to_json()</function> (Andrew Dunstan)
</para>
</listitem>
<listitem>
<para>
- Add a <link linkend="datatype-serial"><type>SMALLSERIAL</></link>
+ Add a <link linkend="datatype-serial"><type>SMALLSERIAL</type></link>
data type (Mike Pultz)
</para>
<para>
- This is like <type>SERIAL</>, except it stores the sequence in
- a two-byte integer column (<type>int2</>).
+ This is like <type>SERIAL</type>, except it stores the sequence in
+ a two-byte integer column (<type>int2</type>).
</para>
</listitem>
<listitem>
<para>
- Allow <link linkend="SQL-CREATEDOMAIN">domains</link> to be
- declared <literal>NOT VALID</> (Álvaro Herrera)
+ Allow <link linkend="sql-createdomain">domains</link> to be
+ declared <literal>NOT VALID</literal> (Álvaro Herrera)
</para>
<para>
This option can be set at domain creation time, or via <command>ALTER
- DOMAIN</command> ... <literal>ADD CONSTRAINT</> ... <literal>NOT
- VALID</>. <command>ALTER DOMAIN</command> ... <literal>VALIDATE
- CONSTRAINT</> fully validates the constraint.
+ DOMAIN</command> ... <literal>ADD CONSTRAINT</literal> ... <literal>NOT
+ VALID</literal>. <command>ALTER DOMAIN</command> ... <literal>VALIDATE
+ CONSTRAINT</literal> fully validates the constraint.
</para>
</listitem>
<listitem>
<para>
Support more locale-specific formatting options for the <link
- linkend="datatype-money"><type>money</></link> data type (Tom Lane)
+ linkend="datatype-money"><type>money</type></link> data type (Tom Lane)
</para>
<para>
<listitem>
<para>
- Add bitwise <quote>and</>, <quote>or</>, and <quote>not</>
- operators for the <type>macaddr</> data type (Brendan Jurd)
+ Add bitwise <quote>and</quote>, <quote>or</quote>, and <quote>not</quote>
+ operators for the <type>macaddr</type> data type (Brendan Jurd)
</para>
</listitem>
<listitem>
<para>
Allow <link
- linkend="functions-xml-processing"><function>xpath()</></link> to
+ linkend="functions-xml-processing"><function>xpath()</function></link> to
return a single-element <acronym>XML</acronym> array when supplied a
scalar value (Florian Pflug)
</para>
<para>
Previously, it returned an empty array. This change will also
- cause <function>xpath_exists()</> to return true, not false,
+ cause <function>xpath_exists()</function> to return true, not false,
for such expressions.
</para>
</listitem>
<listitem>
<para>
Allow non-superusers to use <link
- linkend="functions-admin-signal"><function>pg_cancel_backend()</></link>
+ linkend="functions-admin-signal"><function>pg_cancel_backend()</function></link>
and <link
- linkend="functions-admin-signal"><function>pg_terminate_backend()</></link>
+ linkend="functions-admin-signal"><function>pg_terminate_backend()</function></link>
on other sessions belonging to the same user
(Magnus Hagander, Josh Kupershmidt, Dan Farina)
</para>
This allows multiple transactions to share identical views of the
database state.
Snapshots are exported via <link
- linkend="functions-snapshot-synchronization"><function>pg_export_snapshot()</></link>
- and imported via <link linkend="SQL-SET-TRANSACTION"><command>SET
+ linkend="functions-snapshot-synchronization"><function>pg_export_snapshot()</function></link>
+ and imported via <link linkend="sql-set-transaction"><command>SET
TRANSACTION SNAPSHOT</command></link>. Only snapshots from
currently-running transactions can be imported.
</para>
<para>
Support <link
linkend="functions-info-catalog-table"><literal>COLLATION
- FOR</></link> on expressions (Peter Eisentraut)
+ FOR</literal></link> on expressions (Peter Eisentraut)
</para>
<para>
<listitem>
<para>
Add <link
- linkend="functions-info-schema-table"><function>pg_opfamily_is_visible()</></link>
+ linkend="functions-info-schema-table"><function>pg_opfamily_is_visible()</function></link>
(Josh Kupershmidt)
</para>
</listitem>
<listitem>
<para>
- Add a <type>numeric</> variant of <link
- linkend="functions-admin-dbsize"><function>pg_size_pretty()</></link>
- for use with <function>pg_xlog_location_diff()</> (Fujii Masao)
+ Add a <type>numeric</type> variant of <link
+ linkend="functions-admin-dbsize"><function>pg_size_pretty()</function></link>
+ for use with <function>pg_xlog_location_diff()</function> (Fujii Masao)
</para>
</listitem>
<listitem>
<para>
Add a <link
- linkend="functions-info-session-table"><function>pg_trigger_depth()</></link>
+ linkend="functions-info-session-table"><function>pg_trigger_depth()</function></link>
function (Kevin Grittner)
</para>
<listitem>
<para>
Allow <link
- linkend="functions-aggregate-table"><function>string_agg()</></link>
- to process <type>bytea</> values (Pavel Stehule)
+ linkend="functions-aggregate-table"><function>string_agg()</function></link>
+ to process <type>bytea</type> values (Pavel Stehule)
</para>
</listitem>
</para>
<para>
- For example, <literal>^(\w+)( \1)+$</>. Previous releases did not
+ For example, <literal>^(\w+)( \1)+$</literal>. Previous releases did not
check that the back-reference actually matched the first occurrence.
</para>
</listitem>
<listitem>
<para>
Add information schema views
- <structname>role_udt_grants</>, <structname>udt_privileges</>,
- and <structname>user_defined_types</> (Peter Eisentraut)
+ <structname>role_udt_grants</structname>, <structname>udt_privileges</structname>,
+ and <structname>user_defined_types</structname> (Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
Add composite-type attributes to the
- information schema <structname>element_types</> view
+ information schema <structname>element_types</structname> view
(Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
- Implement <structfield>interval_type</> columns in the information
+ Implement <structfield>interval_type</structfield> columns in the information
schema (Peter Eisentraut)
</para>
<listitem>
<para>
Implement collation-related columns in the information schema
- <structname>attributes</>, <structname>columns</>,
- <structname>domains</>, and <structname>element_types</>
+ <structname>attributes</structname>, <structname>columns</structname>,
+ <structname>domains</structname>, and <structname>element_types</structname>
views (Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
- Implement the <structfield>with_hierarchy</> column in the
- information schema <structname>table_privileges</> view (Peter
+ Implement the <structfield>with_hierarchy</structfield> column in the
+ information schema <structname>table_privileges</structname> view (Peter
Eisentraut)
</para>
</listitem>
<listitem>
<para>
- Add display of sequence <literal>USAGE</> privileges to information
+ Add display of sequence <literal>USAGE</literal> privileges to information
schema (Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
- Allow the PL/pgSQL <command>OPEN</> cursor command to supply
+ Allow the PL/pgSQL <command>OPEN</command> cursor command to supply
parameters by name (Yeb Havinga)
</para>
</listitem>
<listitem>
<para>
Improve performance and memory consumption for long chains of
- <literal>ELSIF</> clauses (Tom Lane)
+ <literal>ELSIF</literal> clauses (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Add <link linkend="APP-INITDB"><application>initdb</></link>
- options <option>--auth-local</> and <option>--auth-host</>
+ Add <link linkend="app-initdb"><application>initdb</application></link>
+ options <option>--auth-local</option> and <option>--auth-host</option>
(Peter Eisentraut)
</para>
<para>
- This allows separate control of <literal>local</> and
- <literal>host</> <filename>pg_hba.conf</filename> authentication
- settings. <option>--auth</> still controls both.
+ This allows separate control of <literal>local</literal> and
+ <literal>host</literal> <filename>pg_hba.conf</filename> authentication
+ settings. <option>--auth</option> still controls both.
</para>
</listitem>
<listitem>
<para>
- Add <option>--replication</>/<option>--no-replication</> flags to
- <link linkend="APP-CREATEUSER"><application>createuser</></link>
+ Add <option>--replication</option>/<option>--no-replication</option> flags to
+ <link linkend="app-createuser"><application>createuser</application></link>
to control replication permission (Fujii Masao)
</para>
</listitem>
<listitem>
<para>
- Add the <option>--if-exists</> option to <link
- linkend="APP-DROPDB"><application>dropdb</></link> and <link
- linkend="APP-DROPUSER"><application>dropuser</></link> (Josh
+ Add the <option>--if-exists</option> option to <link
+ linkend="app-dropdb"><application>dropdb</application></link> and <link
+ linkend="app-dropuser"><application>dropuser</application></link> (Josh
Kupershmidt)
</para>
</listitem>
<listitem>
<para>
Give command-line tools the ability to specify the name of the
- database to connect to, and fall back to <literal>template1</>
- if a <literal>postgres</> database connection fails (Robert Haas)
+ database to connect to, and fall back to <literal>template1</literal>
+ if a <literal>postgres</literal> database connection fails (Robert Haas)
</para>
</listitem>
</itemizedlist>
<sect4>
- <title><link linkend="APP-PSQL"><application>psql</></link></title>
+ <title><link linkend="app-psql"><application>psql</application></link></title>
<itemizedlist>
</para>
<para>
- This adds the <literal>auto</> option to the <command>\x</>
+ This adds the <literal>auto</literal> option to the <command>\x</command>
command, which switches to the expanded mode when the normal
output would be wider than the screen.
</para>
</para>
<para>
- This is done with a new command <command>\ir</>.
+ This is done with a new command <command>\ir</command>.
</para>
</listitem>
<listitem>
<para>
Add support for non-<acronym>ASCII</acronym> characters in
- <application>psql</> variable names (Tom Lane)
+ <application>psql</application> variable names (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Add support for major-version-specific <filename>.psqlrc</> files
+ Add support for major-version-specific <filename>.psqlrc</filename> files
(Bruce Momjian)
</para>
<para>
- <application>psql</> already supported minor-version-specific
- <filename>.psqlrc</> files.
+ <application>psql</application> already supported minor-version-specific
+ <filename>.psqlrc</filename> files.
</para>
</listitem>
<listitem>
<para>
- Provide environment variable overrides for <application>psql</>
+ Provide environment variable overrides for <application>psql</application>
history and startup file locations (Andrew Dunstan)
</para>
<listitem>
<para>
- Add a <command>\setenv</> command to modify
+ Add a <command>\setenv</command> command to modify
the environment variables passed to child processes (Andrew Dunstan)
</para>
</listitem>
<listitem>
<para>
- Name <application>psql</>'s temporary editor files with a
- <filename>.sql</> extension (Peter Eisentraut)
+ Name <application>psql</application>'s temporary editor files with a
+ <filename>.sql</filename> extension (Peter Eisentraut)
</para>
<para>
<listitem>
<para>
- Allow <application>psql</> to use zero-byte field and record
+ Allow <application>psql</application> to use zero-byte field and record
separators (Peter Eisentraut)
</para>
<para>
Various shell tools use zero-byte (NUL) separators,
- e.g. <application>find</>.
+ e.g. <application>find</application>.
</para>
</listitem>
<listitem>
<para>
- Make the <command>\timing</> option report times for
+ Make the <command>\timing</command> option report times for
failed queries (Magnus Hagander)
</para>
<listitem>
<para>
- Unify and tighten <application>psql</>'s treatment of <command>\copy</>
- and SQL <command>COPY</> (Noah Misch)
+ Unify and tighten <application>psql</application>'s treatment of <command>\copy</command>
+ and SQL <command>COPY</command> (Noah Misch)
</para>
<para>
This fix makes failure behavior more predictable and honors
- <command>\set ON_ERROR_ROLLBACK</>.
+ <command>\set ON_ERROR_ROLLBACK</command>.
</para>
</listitem>
<itemizedlist>
<listitem>
<para>
- Make <command>\d</> on a sequence show the
+ Make <command>\d</command> on a sequence show the
table/column name owning it (Magnus Hagander)
</para>
</listitem>
<listitem>
<para>
- Show statistics target for columns in <command>\d+</> (Magnus
+ Show statistics target for columns in <command>\d+</command> (Magnus
Hagander)
</para>
</listitem>
<listitem>
<para>
- Show role password expiration dates in <command>\du</>
+ Show role password expiration dates in <command>\du</command>
(Fabrízio de Royes Mello)
</para>
</listitem>
</para>
<para>
- These are included in the output of <command>\dC+</>,
- <command>\dc+</>, <command>\dD+</>, and <command>\dL</> respectively.
+ These are included in the output of <command>\dC+</command>,
+ <command>\dc+</command>, <command>\dD+</command>, and <command>\dL</command> respectively.
</para>
</listitem>
</para>
<para>
- These are included in the output of <command>\des+</>,
- <command>\det+</>, and <command>\dew+</> for foreign servers, foreign
+ These are included in the output of <command>\des+</command>,
+ <command>\det+</command>, and <command>\dew+</command> for foreign servers, foreign
tables, and foreign data wrappers respectively.
</para>
</listitem>
<listitem>
<para>
- Change <command>\dd</> to display comments only for object types
+ Change <command>\dd</command> to display comments only for object types
without their own backslash command (Josh Kupershmidt)
</para>
</listitem>
<listitem>
<para>
- In <application>psql</> tab completion, complete <acronym>SQL</>
+ In <application>psql</application> tab completion, complete <acronym>SQL</acronym>
keywords in either upper or lower case according to the new <link
- linkend="APP-PSQL-variables"><literal>COMP_KEYWORD_CASE</></link>
+ linkend="app-psql-variables"><literal>COMP_KEYWORD_CASE</literal></link>
setting (Peter Eisentraut)
</para>
</listitem>
</sect4>
<sect4>
- <title><link linkend="APP-PGDUMP"><application>pg_dump</></link></title>
+ <title><link linkend="app-pgdump"><application>pg_dump</application></link></title>
<itemizedlist>
<listitem>
<para>
- Add an <option>--exclude-table-data</> option to
- <application>pg_dump</> (Andrew Dunstan)
+ Add an <option>--exclude-table-data</option> option to
+ <application>pg_dump</application> (Andrew Dunstan)
</para>
<para>
<listitem>
<para>
- Add a <option>--section</> option to <application>pg_dump</>
- and <application>pg_restore</> (Andrew Dunstan)
+ Add a <option>--section</option> option to <application>pg_dump</application>
+ and <application>pg_restore</application> (Andrew Dunstan)
</para>
<para>
- Valid values are <literal>pre-data</>, <literal>data</>,
- and <literal>post-data</>. The option can be
+ Valid values are <literal>pre-data</literal>, <literal>data</literal>,
+ and <literal>post-data</literal>. The option can be
given more than once to select two or more sections.
</para>
</listitem>
<listitem>
<para>
Make <link
- linkend="APP-PG-DUMPALL"><application>pg_dumpall</></link> dump all
+ linkend="app-pg-dumpall"><application>pg_dumpall</application></link> dump all
roles first, then all configuration settings on roles (Phil Sorber)
</para>
<listitem>
<para>
- Allow <application>pg_dumpall</> to avoid errors if the
- <literal>postgres</> database is missing in the new cluster
+ Allow <application>pg_dumpall</application> to avoid errors if the
+ <literal>postgres</literal> database is missing in the new cluster
(Robert Haas)
</para>
</listitem>
<listitem>
<para>
Tighten rules for when extension configuration tables are dumped
- by <application>pg_dump</> (Tom Lane)
+ by <application>pg_dump</application> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Make <application>pg_dump</> emit more useful dependency
+ Make <application>pg_dump</application> emit more useful dependency
information (Tom Lane)
</para>
<listitem>
<para>
- Improve <application>pg_dump</>'s performance when dumping many
+ Improve <application>pg_dump</application>'s performance when dumping many
database objects (Tom Lane)
</para>
</listitem>
</sect3>
<sect3>
- <title><link linkend="libpq"><application>libpq</></link></title>
+ <title><link linkend="libpq"><application>libpq</application></link></title>
<itemizedlist>
<listitem>
<para>
- Allow <application>libpq</> connection strings to have the format of a
+ Allow <application>libpq</application> connection strings to have the format of a
<link linkend="libpq-connstring"><acronym>URI</acronym></link>
(Alexander Shulgin)
</para>
<para>
- The syntax begins with <literal>postgres://</>. This can allow
+ The syntax begins with <literal>postgres://</literal>. This can allow
applications to avoid implementing their own parser for URIs
representing database connections.
</para>
</para>
<para>
- Previously, <application>libpq</> always collected the entire query
+ Previously, <application>libpq</application> always collected the entire query
result in memory before passing it back to the application.
</para>
</listitem>
<listitem>
<para>
- Add <literal>const</> qualifiers to the declarations of the functions
- <function>PQconnectdbParams</>, <function>PQconnectStartParams</>,
- and <function>PQpingParams</> (Lionel Elie Mamane)
+ Add <literal>const</literal> qualifiers to the declarations of the functions
+ <function>PQconnectdbParams</function>, <function>PQconnectStartParams</function>,
+ and <function>PQpingParams</function> (Lionel Elie Mamane)
</para>
</listitem>
<listitem>
<para>
- Allow the <filename>.pgpass</> file to include escaped characters
+ Allow the <filename>.pgpass</filename> file to include escaped characters
in the password field (Robert Haas)
</para>
</listitem>
<listitem>
<para>
- Make library functions use <function>abort()</> instead of
- <function>exit()</> when it is necessary to terminate the process
+ Make library functions use <function>abort()</function> instead of
+ <function>exit()</function> when it is necessary to terminate the process
(Peter Eisentraut)
</para>
<listitem>
<para>
- Install <filename>plpgsql.h</> into <filename>include/server</> during installation
+ Install <filename>plpgsql.h</filename> into <filename>include/server</filename> during installation
(Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
Improve the concurrent transaction regression tests
- (<application>isolationtester</>) (Noah Misch)
+ (<application>isolationtester</application>) (Noah Misch)
</para>
</listitem>
<listitem>
<para>
- Modify <application>thread_test</> to create its test files in
- the current directory, rather than <filename>/tmp</> (Bruce Momjian)
+ Modify <application>thread_test</application> to create its test files in
+ the current directory, rather than <filename>/tmp</filename> (Bruce Momjian)
</para>
</listitem>
<listitem>
<para>
- Add a <application>pg_upgrade</> test suite (Peter Eisentraut)
+ Add a <application>pg_upgrade</application> test suite (Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
- Add options to <application>git_changelog</> for use in major
+ Add options to <application>git_changelog</application> for use in major
release note creation (Bruce Momjian)
</para>
</listitem>
<listitem>
<para>
- Support Linux's <filename>/proc/self/oom_score_adj</> API (Tom Lane)
+ Support Linux's <filename>/proc/self/oom_score_adj</filename> API (Tom Lane)
</para>
</listitem>
<para>
This improvement does not apply to
- <function>dblink_send_query()</>/<function>dblink_get_result()</>.
+ <function>dblink_send_query()</function>/<function>dblink_get_result()</function>.
</para>
</listitem>
<listitem>
<para>
- Support <literal>force_not_null</> option in <link
+ Support <literal>force_not_null</literal> option in <link
linkend="file-fdw">file_fdw</link> (Shigeru Hanada)
</para>
</listitem>
<listitem>
<para>
Implement dry-run mode for <link
- linkend="pgarchivecleanup"><application>pg_archivecleanup</></link>
+ linkend="pgarchivecleanup"><application>pg_archivecleanup</application></link>
(Gabriele Bartolini)
</para>
<listitem>
<para>
Add new <link linkend="pgbench">pgbench</link> switches
- <option>--unlogged-tables</>, <option>--tablespace</>, and
- <option>--index-tablespace</> (Robert Haas)
+ <option>--unlogged-tables</option>, <option>--tablespace</option>, and
+ <option>--index-tablespace</option> (Robert Haas)
</para>
</listitem>
<listitem>
<para>
Change <link
- linkend="pgtestfsync"><application>pg_test_fsync</></link> to test
+ linkend="pgtestfsync"><application>pg_test_fsync</application></link> to test
for a fixed amount of time, rather than a fixed number of cycles
(Bruce Momjian)
</para>
<para>
- The <option>-o</>/cycles option was removed, and
- <option>-s</>/seconds added.
+ The <option>-o</option>/cycles option was removed, and
+ <option>-s</option>/seconds added.
</para>
</listitem>
<listitem>
<para>
Add a <link
- linkend="pgtesttiming"><application>pg_test_timing</></link>
+ linkend="pgtesttiming"><application>pg_test_timing</application></link>
utility to measure clock monotonicity and timing overhead (Ants
Aasma, Greg Smith)
</para>
</itemizedlist>
<sect4>
- <title><link linkend="pgupgrade"><application>pg_upgrade</></link></title>
+ <title><link linkend="pgupgrade"><application>pg_upgrade</application></link></title>
<itemizedlist>
<listitem>
<para>
- Adjust <application>pg_upgrade</> environment variables (Bruce
+ Adjust <application>pg_upgrade</application> environment variables (Bruce
Momjian)
</para>
<para>
Rename data, bin, and port environment
- variables to begin with <literal>PG</>, and support
+ variables to begin with <literal>PG</literal>, and support
<envar>PGPORTOLD</envar>/<envar>PGPORTNEW</envar>, to replace
<envar>PGPORT</envar>.
</para>
<listitem>
<para>
- Overhaul <application>pg_upgrade</> logging and failure reporting
+ Overhaul <application>pg_upgrade</application> logging and failure reporting
(Bruce Momjian)
</para>
<para>
Create four append-only log files, and delete them on success.
- Add <option>-r</>/<option>--retain</> option to unconditionally
- retain these files. Also remove <application>pg_upgrade</> options
- <option>-g</>/<option>-G</>/<option>-l</> options as unnecessary,
+ Add <option>-r</option>/<option>--retain</option> option to unconditionally
+ retain these files. Also remove <application>pg_upgrade</application> options
+ <option>-g</option>/<option>-G</option>/<option>-l</option> options as unnecessary,
and tighten log file permissions.
</para>
</listitem>
<listitem>
<para>
- Make <application>pg_upgrade</> create a script to incrementally
+ Make <application>pg_upgrade</application> create a script to incrementally
generate more accurate optimizer statistics (Bruce Momjian)
</para>
<listitem>
<para>
- Allow <application>pg_upgrade</> to upgrade an old cluster that
- does not have a <literal>postgres</> database (Bruce Momjian)
+ Allow <application>pg_upgrade</application> to upgrade an old cluster that
+ does not have a <literal>postgres</literal> database (Bruce Momjian)
</para>
</listitem>
<listitem>
<para>
- Allow <application>pg_upgrade</> to handle cases where some
+ Allow <application>pg_upgrade</application> to handle cases where some
old or new databases are missing, as long as they are empty
(Bruce Momjian)
</para>
<listitem>
<para>
- Allow <application>pg_upgrade</> to handle configuration-only
+ Allow <application>pg_upgrade</application> to handle configuration-only
directory installations (Bruce Momjian)
</para>
</listitem>
<listitem>
<para>
- In <application>pg_upgrade</>, add <option>-o</>/<option>-O</>
+ In <application>pg_upgrade</application>, add <option>-o</option>/<option>-O</option>
options to pass parameters to the servers (Bruce Momjian)
</para>
<listitem>
<para>
- Change <application>pg_upgrade</> to use port 50432 by default
+ Change <application>pg_upgrade</application> to use port 50432 by default
(Bruce Momjian)
</para>
<listitem>
<para>
- Reduce cluster locking in <application>pg_upgrade</> (Bruce
+ Reduce cluster locking in <application>pg_upgrade</application> (Bruce
Momjian)
</para>
</sect4>
<sect4>
- <title><link linkend="pgstatstatements"><application>pg_stat_statements</></link></title>
+ <title><link linkend="pgstatstatements"><application>pg_stat_statements</application></link></title>
<itemizedlist>
<listitem>
<para>
- Allow <application>pg_stat_statements</> to aggregate similar
+ Allow <application>pg_stat_statements</application> to aggregate similar
queries via SQL text normalization (Peter Geoghegan, Tom Lane)
</para>
<listitem>
<para>
Add dirtied and written block counts and read/write times to
- <application>pg_stat_statements</> (Robert Haas, Ants Aasma)
+ <application>pg_stat_statements</application> (Robert Haas, Ants Aasma)
</para>
</listitem>
<listitem>
<para>
- Prevent <application>pg_stat_statements</> from double-counting
+ Prevent <application>pg_stat_statements</application> from double-counting
<command>PREPARE</command> and <command>EXECUTE</command> commands
(Tom Lane)
</para>
<itemizedlist>
<listitem>
<para>
- Support <literal>SECURITY LABEL</> on global objects (KaiGai
+ Support <literal>SECURITY LABEL</literal> on global objects (KaiGai
Kohei, Robert Haas)
</para>
<listitem>
<para>
- Add <function>sepgsql_setcon()</> and related functions to control
+ Add <function>sepgsql_setcon()</function> and related functions to control
the sepgsql security domain (KaiGai Kohei)
</para>
</listitem>
</para>
<para>
- Use <command>gmake STYLE=website draft</>.
+ Use <command>gmake STYLE=website draft</command>.
</para>
</listitem>
<listitem>
<para>
Document that user/database names are preserved with double-quoting
- by command-line tools like <application>vacuumdb</> (Bruce
+ by command-line tools like <application>vacuumdb</application> (Bruce
Momjian)
</para>
</listitem>
<listitem>
<para>
- Deprecate use of <literal>GLOBAL</> and <literal>LOCAL</> in
- <command>CREATE TEMP TABLE</> (Noah Misch)
+ Deprecate use of <literal>GLOBAL</literal> and <literal>LOCAL</literal> in
+ <command>CREATE TEMP TABLE</command> (Noah Misch)
</para>
<para>
- <productname>PostgreSQL</> has long treated these keyword as no-ops,
+ <productname>PostgreSQL</productname> has long treated these keyword as no-ops,
and continues to do so; but in future they might mean what the SQL
standard says they mean, so applications should avoid using them.
</para>
<!-- doc/src/sgml/release-9.3.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-3-20">
+ <title>Release 9.3.20</title>
+
+ <formalpara>
+ <title>Release date:</title>
+ <para>2017-11-09</para>
+ </formalpara>
+
+ <para>
+ This release contains a variety of fixes from 9.3.19.
+ For information about new features in the 9.3 major release, see
+ <xref linkend="release-9-3">.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 9.3.20</title>
+
+ <para>
+ A dump/restore is not required for those running 9.3.X.
+ </para>
+
+ <para>
+ However, if you are upgrading from a version earlier than 9.3.18,
+ see <xref linkend="release-9-3-18">.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <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>
+ Prevent low-probability crash in processing of nested trigger firings
+ (Tom Lane)
+ </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>
+ 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-3-19">
<title>Release 9.3.19</title>
<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
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>
</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,
<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>
<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>
<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>
<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>
<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>
<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;
<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>
<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>
</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>
<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 <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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<listitem>
<para>
- Fix <application>pg_basebackup</> output to stdout on Windows
+ Fix <application>pg_basebackup</application> output to stdout on Windows
(Haribabu Kommi)
</para>
<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>
<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>
<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>
<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>
<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>
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.
<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,
<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>
<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>
<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>
<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>
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>
<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>
<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>
- Improve performance of <structname>pg_timezone_names</> view
+ Improve performance of <structname>pg_timezone_names</structname> view
(Tom Lane, David Rowley)
</para>
</listitem>
<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>
<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>
<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>
<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>
<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>
<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
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>
<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.
<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.
<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>
<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>
</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>
<listitem>
<para>
Report correct object identity during <command>ALTER TEXT SEARCH
- CONFIGURATION</> (Artur Zakirov)
+ CONFIGURATION</command> (Artur Zakirov)
</para>
<para>
<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>
<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>
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>
<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>
<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>
<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>
<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 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>
<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>
<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>
<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>
<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.
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>
<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>
<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>
<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>
<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>
<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>
<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>
- 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>
<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>
<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>
<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>
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,
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>
<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)
</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
<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.
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>
<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.
<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>
<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>
<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>
<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.
<listitem>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
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.
<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>
<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>
<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>
<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>
- 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>
<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
<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>
<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>
<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>
<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>
- 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>
<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>
<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>
<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>
<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
<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>
<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>
<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>
<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>
<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>
<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)
<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>
<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>
<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>
<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>
<listitem>
<para>
- Fix possible internal overflow in <type>numeric</> division
+ Fix possible internal overflow in <type>numeric</type> division
(Dean Rasheed)
</para>
</listitem>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
- Accept <application>flex</> versions later than 2.5.x
+ Accept <application>flex</application> versions later than 2.5.x
(Tom Lane, Michael Paquier)
</para>
<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>
<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.
<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>
<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>
<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>
<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
<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>
</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>
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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
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>
<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>
<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>
<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>
</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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<listitem>
<para>
Fix memory leaks and missing out-of-memory checks
- in <application>ecpg</> (Michael Paquier)
+ in <application>ecpg</application> (Michael Paquier)
</para>
</listitem>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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.
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
</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 be
+ 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
in <xref linkend="runtime-config-resource-vacuum-cost"> to reduce
the performance consequences for concurrent sessions.) You must
- use <productname>PostgreSQL</> 9.3.5 or later to perform this step.
+ use <productname>PostgreSQL</productname> 9.3.5 or later to perform this step.
</para>
</listitem>
</orderedlist>
<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
<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>
<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.
</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>
<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>
<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>
<listitem>
<para>
- Allow <application>libpq</> to use TLS protocol versions beyond v1
+ Allow <application>libpq</application> to use TLS protocol versions beyond v1
(Noah Misch)
</para>
<para>
- For a long time, <application>libpq</> was coded so that the only SSL
+ For a long time, <application>libpq</application> was coded so that the only SSL
protocol it would allow was TLS v1. Now that newer TLS versions are
becoming popular, allow it to negotiate the highest commonly-supported
- TLS version with the server. (<productname>PostgreSQL</> servers were
+ TLS version with the server. (<productname>PostgreSQL</productname> servers were
already capable of such negotiation, so no change is needed on the
server side.) This is a back-patch of a change already released in
9.4.0.
</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>
</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
</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.
<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)
<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
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
</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>
<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>
<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>
<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>
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>
<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>
<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>
<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>
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>
<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>
<listitem>
<para>
- Fix array handling in <application>ecpg</> (Michael Meskes)
+ Fix array handling in <application>ecpg</application> (Michael Meskes)
</para>
</listitem>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<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).
<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</> 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> 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>
<para>
<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.
<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>
<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
<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.
<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>
</listitem>
<listitem>
<para>
Avoid possible data corruption if <command>ALTER DATABASE SET
- TABLESPACE</> is used to move a database to a new tablespace and then
+ TABLESPACE</command> is used to move a database to a new tablespace and then
shortly later move it back to its original tablespace (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Avoid corrupting tables when <command>ANALYZE</> inside a transaction
+ Avoid corrupting tables when <command>ANALYZE</command> inside a transaction
is rolled back (Andres Freund, Tom Lane, Michael Paquier)
</para>
<para>
If the failing transaction had earlier removed the last index, rule, or
trigger from the table, the table would be left in a corrupted state
- with the relevant <structname>pg_class</> flags not set though they
+ with the relevant <structname>pg_class</structname> flags not set though they
should be.
</para>
</listitem>
<listitem>
<para>
Ensure that unlogged tables are copied correctly
- during <command>CREATE DATABASE</> or <command>ALTER DATABASE SET
- TABLESPACE</> (Pavan Deolasee, Andres Freund)
+ during <command>CREATE DATABASE</command> or <command>ALTER DATABASE SET
+ TABLESPACE</command> (Pavan Deolasee, Andres Freund)
</para>
</listitem>
<listitem>
<para>
Fix incorrect processing
- of <structname>CreateEventTrigStmt</>.<structfield>eventname</> (Petr
+ of <structname>CreateEventTrigStmt</structname>.<structfield>eventname</structfield> (Petr
Jelinek)
</para>
<para>
- This could result in misbehavior if <command>CREATE EVENT TRIGGER</>
+ This could result in misbehavior if <command>CREATE EVENT TRIGGER</command>
were executed as a prepared query, or via extended query protocol.
</para>
</listitem>
<listitem>
<para>
- Fix <command>DROP</>'s dependency searching to correctly handle the
+ Fix <command>DROP</command>'s dependency searching to correctly handle the
case where a table column is recursively visited before its table
(Petr Jelinek, Tom Lane)
</para>
<para>
This case is only known to arise when an extension creates both a
datatype and a table using that datatype. The faulty code might
- refuse a <command>DROP EXTENSION</> unless <literal>CASCADE</> is
+ refuse a <command>DROP EXTENSION</command> unless <literal>CASCADE</literal> is
specified, which should not be required.
</para>
</listitem>
</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>
<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>
<listitem>
<para>
- Fix planning of <command>SELECT FOR UPDATE</> when using a partial
+ Fix planning of <command>SELECT FOR UPDATE</command> when using a partial
index on a child table (Kyotaro Horiguchi)
</para>
<para>
- In <literal>READ COMMITTED</> mode, <command>SELECT FOR UPDATE</> must
- also recheck the partial index's <literal>WHERE</> condition when
+ In <literal>READ COMMITTED</literal> mode, <command>SELECT FOR UPDATE</command> must
+ also recheck the partial index's <literal>WHERE</literal> condition when
rechecking a recently-updated row to see if it still satisfies the
- query's <literal>WHERE</> condition. This requirement was missed if the
+ query's <literal>WHERE</literal> condition. This requirement was missed if the
index belonged to an inheritance child table, so that it was possible
to incorrectly return rows that no longer satisfy the query condition.
</para>
<listitem>
<para>
- Fix corner case wherein <command>SELECT FOR UPDATE</> could return a row
+ Fix corner case wherein <command>SELECT FOR UPDATE</command> could return a row
twice, and possibly miss returning other rows (Tom Lane)
</para>
<para>
- In <literal>READ COMMITTED</> mode, a <command>SELECT FOR UPDATE</>
+ In <literal>READ COMMITTED</literal> mode, a <command>SELECT FOR UPDATE</command>
that is scanning an inheritance tree could incorrectly return a row
from a prior child table instead of the one it should return from a
later child table.
<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>
<listitem>
<para>
Reject duplicate column names in the referenced-columns list of
- a <literal>FOREIGN KEY</> declaration (David Rowley)
+ a <literal>FOREIGN KEY</literal> declaration (David Rowley)
</para>
<para>
<listitem>
<para>
- Re-enable error for <literal>SELECT ... OFFSET -1</> (Tom Lane)
+ Re-enable error for <literal>SELECT ... OFFSET -1</literal> (Tom Lane)
</para>
<para>
<listitem>
<para>
- Fix <function>json_agg()</> to not return extra trailing right
+ Fix <function>json_agg()</function> to not return extra trailing right
brackets in its result (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix bugs in raising a <type>numeric</> value to a large integral power
+ Fix bugs in raising a <type>numeric</type> value to a large integral power
(Tom Lane)
</para>
<listitem>
<para>
- In <function>numeric_recv()</>, truncate away any fractional digits
- that would be hidden according to the value's <literal>dscale</> field
+ In <function>numeric_recv()</function>, truncate away any fractional digits
+ that would be hidden according to the value's <literal>dscale</literal> field
(Tom Lane)
</para>
<para>
- A <type>numeric</> value's display scale (<literal>dscale</>) should
+ A <type>numeric</type> value's display scale (<literal>dscale</literal>) should
never be less than the number of nonzero fractional digits; but
apparently there's at least one broken client application that
- transmits binary <type>numeric</> values in which that's true.
+ transmits binary <type>numeric</type> values in which that's true.
This leads to strange behavior since the extra digits are taken into
account by arithmetic operations even though they aren't printed.
- The least risky fix seems to be to truncate away such <quote>hidden</>
+ The least risky fix seems to be to truncate away such <quote>hidden</quote>
digits on receipt, so that the value is indeed what it prints as.
</para>
</listitem>
<para>
Matching would often fail when the number of allowed iterations is
- limited by a <literal>?</> quantifier or a bound expression.
+ limited by a <literal>?</literal> quantifier or a bound expression.
</para>
</listitem>
<listitem>
<para>
- Fix bugs in <type>tsquery</> <literal>@></> <type>tsquery</>
+ Fix bugs in <type>tsquery</type> <literal>@></literal> <type>tsquery</type>
operator (Heikki Linnakangas)
</para>
<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>
</para>
<para>
- In some contexts, constructs like <literal>row_to_json(tab.*)</> may
+ In some contexts, constructs like <literal>row_to_json(tab.*)</literal> may
not produce the expected column names. This is fixed properly as of
9.4; in older branches, just ensure that we produce some nonempty
name. (In some cases this will be the underlying table's column name
<listitem>
<para>
Fix mishandling of system columns,
- particularly <structfield>tableoid</>, in FDW queries (Etsuro Fujita)
+ particularly <structfield>tableoid</structfield>, in FDW queries (Etsuro Fujita)
</para>
</listitem>
</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>
<listitem>
<para>
- Avoid doing <literal><replaceable>indexed_column</> = ANY
- (<replaceable>array</>)</literal> as an index qualifier if that leads
+ Avoid doing <literal><replaceable>indexed_column</replaceable> = ANY
+ (<replaceable>array</replaceable>)</literal> as an index qualifier if that leads
to an inferior plan (Andrew Gierth)
</para>
<para>
- In some cases, <literal>= ANY</> conditions applied to non-first index
+ In some cases, <literal>= ANY</literal> conditions applied to non-first index
columns would be done as index conditions even though it would be
better to use them as simple filter conditions.
</para>
<listitem>
<para>
- Fix <quote>variable not found in subplan target list</> planner
+ Fix <quote>variable not found in subplan target list</quote> planner
failure when an inline-able SQL function taking a composite argument
- is used in a <literal>LATERAL</> subselect and the composite argument
+ is used in a <literal>LATERAL</literal> subselect and the composite argument
is a lateral reference (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix planner problems with nested append relations, such as inherited
- tables within <literal>UNION ALL</> subqueries (Tom Lane)
+ tables within <literal>UNION ALL</literal> subqueries (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Exempt tables that have per-table <varname>cost_limit</>
- and/or <varname>cost_delay</> settings from autovacuum's global cost
+ Exempt tables that have per-table <varname>cost_limit</varname>
+ and/or <varname>cost_delay</varname> settings from autovacuum's global cost
balancing rules (Álvaro Herrera)
</para>
the target database, if they met the usual thresholds for
autovacuuming. This is at best pretty unexpected; at worst it delays
response to the wraparound threat. Fix it so that if autovacuum is
- turned off, workers <emphasis>only</> do anti-wraparound vacuums and
+ turned off, workers <emphasis>only</emphasis> do anti-wraparound vacuums and
not any other work.
</para>
</listitem>
<listitem>
<para>
Fix several cases where recovery logic improperly ignored WAL records
- for <literal>COMMIT/ABORT PREPARED</> (Heikki Linnakangas)
+ for <literal>COMMIT/ABORT PREPARED</literal> (Heikki Linnakangas)
</para>
<para>
The most notable oversight was
- that <varname>recovery_target_xid</> could not be used to stop at
+ that <varname>recovery_target_xid</varname> could not be used to stop at
a two-phase commit.
</para>
</listitem>
<listitem>
<para>
- Avoid creating unnecessary <filename>.ready</> marker files for
+ Avoid creating unnecessary <filename>.ready</filename> marker files for
timeline history files (Fujii Masao)
</para>
</listitem>
<listitem>
<para>
Fix possible null pointer dereference when an empty prepared statement
- is used and the <varname>log_statement</> setting is <literal>mod</>
- or <literal>ddl</> (Fujii Masao)
+ is used and the <varname>log_statement</varname> setting is <literal>mod</literal>
+ or <literal>ddl</literal> (Fujii Masao)
</para>
</listitem>
<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>
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>
<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>
<listitem>
<para>
- Fix processing of repeated <literal>dbname</> parameters
- in <function>PQconnectdbParams()</> (Alex Shulgin)
+ Fix processing of repeated <literal>dbname</literal> parameters
+ in <function>PQconnectdbParams()</function> (Alex Shulgin)
</para>
<para>
Unexpected behavior ensued if the first occurrence
- of <literal>dbname</> contained a connection string or URI to be
+ of <literal>dbname</literal> contained a connection string or URI to be
expanded.
</para>
</listitem>
<listitem>
<para>
- Ensure that <application>libpq</> reports a suitable error message on
+ Ensure that <application>libpq</application> reports a suitable error message on
unexpected socket EOF (Marko Tiikkaja, Tom Lane)
</para>
<para>
- Depending on kernel behavior, <application>libpq</> might return an
+ Depending on kernel behavior, <application>libpq</application> might return an
empty error string rather than something useful when the server
unexpectedly closed the socket.
</para>
<listitem>
<para>
- Clear any old error message during <function>PQreset()</>
+ Clear any old error message during <function>PQreset()</function>
(Heikki Linnakangas)
</para>
<para>
- If <function>PQreset()</> is called repeatedly, and the connection
+ If <function>PQreset()</function> is called repeatedly, and the connection
cannot be re-established, error messages from the failed connection
- attempts kept accumulating in the <structname>PGconn</>'s error
+ attempts kept accumulating in the <structname>PGconn</structname>'s error
string.
</para>
</listitem>
<listitem>
<para>
Properly handle out-of-memory conditions while parsing connection
- options in <application>libpq</> (Alex Shulgin, Heikki Linnakangas)
+ options in <application>libpq</application> (Alex Shulgin, Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Fix array overrun in <application>ecpg</>'s version
- of <function>ParseDateTime()</> (Michael Paquier)
+ Fix array overrun in <application>ecpg</application>'s version
+ of <function>ParseDateTime()</function> (Michael Paquier)
</para>
</listitem>
<listitem>
<para>
- In <application>initdb</>, give a clearer error message if a password
+ In <application>initdb</application>, give a clearer error message if a password
file is specified but is empty (Mats Erik Andersson)
</para>
</listitem>
<listitem>
<para>
- Fix <application>psql</>'s <command>\s</> command to work nicely with
+ Fix <application>psql</application>'s <command>\s</command> command to work nicely with
libedit, and add pager support (Stepan Rutz, Tom Lane)
</para>
<para>
- When using libedit rather than readline, <command>\s</> printed the
+ When using libedit rather than readline, <command>\s</command> printed the
command history in a fairly unreadable encoded format, and on recent
libedit versions might fail altogether. Fix that by printing the
history ourselves rather than having the library do it. A pleasant
<para>
This patch also fixes a bug that caused newline encoding to be applied
inconsistently when saving the command history with libedit.
- Multiline history entries written by older <application>psql</>
+ Multiline history entries written by older <application>psql</application>
versions will be read cleanly with this patch, but perhaps not
vice versa, depending on the exact libedit versions involved.
</para>
<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>
<listitem>
<para>
- Make <application>psql</>'s <command>\watch</> command display
- nulls as specified by <command>\pset null</> (Fujii Masao)
+ Make <application>psql</application>'s <command>\watch</command> command display
+ nulls as specified by <command>\pset null</command> (Fujii Masao)
</para>
</listitem>
<listitem>
<para>
- Fix <application>psql</>'s expanded-mode display to work
- consistently when using <literal>border</> = 3
- and <literal>linestyle</> = <literal>ascii</> or <literal>unicode</>
+ Fix <application>psql</application>'s expanded-mode display to work
+ consistently when using <literal>border</literal> = 3
+ and <literal>linestyle</literal> = <literal>ascii</literal> or <literal>unicode</literal>
(Stephen Frost)
</para>
</listitem>
<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>
<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>
<listitem>
<para>
- Improve performance of <application>pg_dump</> when the database
+ Improve performance of <application>pg_dump</application> when the database
contains many instances of multiple dependency paths between the same
two objects (Tom Lane)
</para>
<listitem>
<para>
- Fix <application>pg_dumpall</> to restore its ability to dump from
+ Fix <application>pg_dumpall</application> to restore its ability to dump from
pre-8.1 servers (Gilles Darold)
</para>
</listitem>
<listitem>
<para>
- Fix core dump in <literal>pg_dump --binary-upgrade</> on zero-column
+ Fix core dump in <literal>pg_dump --binary-upgrade</literal> on zero-column
composite type (Rushabh Lathia)
</para>
</listitem>
<listitem>
<para>
Fix failure to fsync tables in nondefault tablespaces
- during <application>pg_upgrade</> (Abhijit Menon-Sen, Andres Freund)
+ during <application>pg_upgrade</application> (Abhijit Menon-Sen, Andres Freund)
</para>
<para>
<listitem>
<para>
- In <application>pg_upgrade</>, cope with cases where the new cluster
+ In <application>pg_upgrade</application>, cope with cases where the new cluster
creates a TOAST table for a table that didn't previously have one
(Bruce Momjian)
</para>
<listitem>
<para>
- In <application>pg_upgrade</>, don't try to
- set <literal>autovacuum_multixact_freeze_max_age</> for the old cluster
+ In <application>pg_upgrade</application>, don't try to
+ set <literal>autovacuum_multixact_freeze_max_age</literal> for the old cluster
(Bruce Momjian)
</para>
<listitem>
<para>
- In <application>pg_upgrade</>, preserve the transaction ID epoch
+ In <application>pg_upgrade</application>, preserve the transaction ID epoch
(Bruce Momjian)
</para>
<para>
- This oversight did not bother <productname>PostgreSQL</> proper,
+ This oversight did not bother <productname>PostgreSQL</productname> proper,
but could confuse some external replication tools.
</para>
</listitem>
<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>
<listitem>
<para>
- Fix memory leak in <application>pg_receivexlog</> (Fujii Masao)
+ Fix memory leak in <application>pg_receivexlog</application> (Fujii Masao)
</para>
</listitem>
<listitem>
<para>
- Fix unintended suppression of <application>pg_receivexlog</> verbose
+ Fix unintended suppression of <application>pg_receivexlog</application> verbose
messages (Fujii Masao)
</para>
</listitem>
<listitem>
<para>
- Fix failure of <filename>contrib/auto_explain</> to print per-node
- timing information when doing <command>EXPLAIN ANALYZE</> (Tom Lane)
+ Fix failure of <filename>contrib/auto_explain</filename> to print per-node
+ timing information when doing <command>EXPLAIN ANALYZE</command> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix upgrade-from-unpackaged script for <filename>contrib/citext</>
+ Fix upgrade-from-unpackaged script for <filename>contrib/citext</filename>
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
Avoid integer overflow and buffer overrun
- in <filename>contrib/hstore</>'s <function>hstore_to_json()</>
+ in <filename>contrib/hstore</filename>'s <function>hstore_to_json()</function>
(Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Fix recognition of numbers in <function>hstore_to_json_loose()</>,
+ Fix recognition of numbers in <function>hstore_to_json_loose()</function>,
so that JSON numbers and strings are correctly distinguished
(Andrew Dunstan)
</para>
<listitem>
<para>
Fix block number checking
- in <filename>contrib/pageinspect</>'s <function>get_raw_page()</>
+ in <filename>contrib/pageinspect</filename>'s <function>get_raw_page()</function>
(Tom Lane)
</para>
<listitem>
<para>
- Fix <filename>contrib/pgcrypto</>'s <function>pgp_sym_decrypt()</>
+ Fix <filename>contrib/pgcrypto</filename>'s <function>pgp_sym_decrypt()</function>
to not fail on messages whose length is 6 less than a power of 2
(Marko Tiikkaja)
</para>
<listitem>
<para>
- Fix file descriptor leak in <filename>contrib/pg_test_fsync</>
+ Fix file descriptor leak in <filename>contrib/pg_test_fsync</filename>
(Jeff Janes)
</para>
<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>
<listitem>
<para>
- Avoid a possible crash in <filename>contrib/xml2</>'s
- <function>xslt_process()</> (Mark Simonetti)
+ Avoid a possible crash in <filename>contrib/xml2</filename>'s
+ <function>xslt_process()</function> (Mark Simonetti)
</para>
<para>
- <application>libxslt</> seems to have an undocumented dependency on
+ <application>libxslt</application> seems to have an undocumented dependency on
the order in which resources are freed; reorder our calls to avoid a
crash.
</para>
<listitem>
<para>
- Mark some <filename>contrib</> I/O functions with correct volatility
+ Mark some <filename>contrib</filename> I/O functions with correct volatility
properties (Tom Lane)
</para>
<para>
With OpenLDAP versions 2.4.24 through 2.4.31,
- inclusive, <productname>PostgreSQL</> backends can crash at exit.
- Raise a warning during <application>configure</> based on the
+ inclusive, <productname>PostgreSQL</productname> backends can crash at exit.
+ Raise a warning during <application>configure</application> based on the
compile-time OpenLDAP version number, and test the crashing scenario
- in the <filename>contrib/dblink</> regression test.
+ in the <filename>contrib/dblink</filename> regression test.
</para>
</listitem>
<listitem>
<para>
- In non-MSVC Windows builds, ensure <filename>libpq.dll</> is installed
+ In non-MSVC Windows builds, ensure <filename>libpq.dll</filename> is installed
with execute permissions (Noah Misch)
</para>
</listitem>
<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>
</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>
<para>
Add CST (China Standard Time) to our lists.
- Remove references to ADT as <quote>Arabia Daylight Time</>, an
+ Remove references to ADT as <quote>Arabia Daylight Time</quote>, an
abbreviation that's been out of use since 2007; therefore, claiming
- there is a conflict with <quote>Atlantic Daylight Time</> doesn't seem
+ there is a conflict with <quote>Atlantic Daylight Time</quote> doesn't seem
especially helpful.
Fix entirely incorrect GMT offsets for CKT (Cook Islands), FJT, and FJST
(Fiji); we didn't even have them on the proper side of the date line.
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2015a.
+ Update time zone data files to <application>tzdata</application> release 2015a.
</para>
<para>
The IANA timezone database has adopted abbreviations of the form
- <literal>A<replaceable>x</>ST</literal>/<literal>A<replaceable>x</>DT</literal>
+ <literal>A<replaceable>x</replaceable>ST</literal>/<literal>A<replaceable>x</replaceable>DT</literal>
for all Australian time zones, reflecting what they believe to be
current majority practice Down Under. These names do not conflict
with usage elsewhere (other than ACST for Acre Summer Time, which has
been in disuse since 1994). Accordingly, adopt these names into
- our <quote>Default</> timezone abbreviation set.
- The <quote>Australia</> abbreviation set now contains only CST, EAST,
+ our <quote>Default</quote> timezone abbreviation set.
+ The <quote>Australia</quote> abbreviation set now contains only CST, EAST,
EST, SAST, SAT, and WST, all of which are thought to be mostly
historical usage. Note that SAST has also been changed to be South
- Africa Standard Time in the <quote>Default</> abbreviation set.
+ Africa Standard Time in the <quote>Default</quote> abbreviation set.
</para>
<para>
<para>
However, this release corrects a logic error
- in <application>pg_upgrade</>, as well as an index corruption problem in
+ in <application>pg_upgrade</application>, as well as an index corruption problem in
some GiST indexes. See the first two changelog entries below to find out
whether your installation has been affected and what steps you should take
if so.
<listitem>
<para>
- In <application>pg_upgrade</>, remove <filename>pg_multixact</> files
- left behind by <application>initdb</> (Bruce Momjian)
+ In <application>pg_upgrade</application>, remove <filename>pg_multixact</filename> files
+ left behind by <application>initdb</application> (Bruce Momjian)
</para>
<para>
- If you used a pre-9.3.5 version of <application>pg_upgrade</> to
+ If you used a pre-9.3.5 version of <application>pg_upgrade</application> to
upgrade a database cluster to 9.3, it might have left behind a file
- <filename>$PGDATA/pg_multixact/offsets/0000</> that should not be
- there and will eventually cause problems in <command>VACUUM</>.
+ <filename>$PGDATA/pg_multixact/offsets/0000</filename> that should not be
+ there and will eventually cause problems in <command>VACUUM</command>.
<emphasis>However, in common cases this file is actually valid and
must not be removed.</emphasis>
To determine whether your installation has this problem, run this
EXISTS (SELECT * FROM list WHERE file != '0000')
AS file_0000_removal_required;
</programlisting>
- If this query returns <literal>t</>, manually remove the file
- <filename>$PGDATA/pg_multixact/offsets/0000</>.
- Do nothing if the query returns <literal>f</>.
+ If this query returns <literal>t</literal>, manually remove the file
+ <filename>$PGDATA/pg_multixact/offsets/0000</filename>.
+ Do nothing if the query returns <literal>f</literal>.
</para>
</listitem>
<listitem>
<para>
- Correctly initialize padding bytes in <filename>contrib/btree_gist</>
- indexes on <type>bit</> columns (Heikki Linnakangas)
+ Correctly initialize padding bytes in <filename>contrib/btree_gist</filename>
+ indexes on <type>bit</type> columns (Heikki Linnakangas)
</para>
<para>
This error could result in incorrect query results due to values that
should compare equal not being seen as equal.
- Users with GiST indexes on <type>bit</> or <type>bit varying</>
- columns should <command>REINDEX</> those indexes after installing this
+ Users with GiST indexes on <type>bit</type> or <type>bit varying</type>
+ columns should <command>REINDEX</command> those indexes after installing this
update.
</para>
</listitem>
<listitem>
<para>
- Fix wraparound handling for <filename>pg_multixact/members</>
+ Fix wraparound handling for <filename>pg_multixact/members</filename>
(Álvaro Herrera)
</para>
</listitem>
<listitem>
<para>
- Truncate <structname>pg_multixact</> during checkpoints, not
- during <command>VACUUM</> (Álvaro Herrera)
+ Truncate <structname>pg_multixact</structname> during checkpoints, not
+ during <command>VACUUM</command> (Álvaro Herrera)
</para>
<para>
- This change ensures that <structname>pg_multixact</> segments can't be
+ This change ensures that <structname>pg_multixact</structname> segments can't be
removed if they'd still be needed during WAL replay after a crash.
</para>
</listitem>
<listitem>
<para>
Fix possibly-incorrect cache invalidation during nested calls
- to <function>ReceiveSharedInvalidMessages</> (Andres Freund)
+ to <function>ReceiveSharedInvalidMessages</function> (Andres Freund)
</para>
</listitem>
<listitem>
<para>
- Fix <quote>could not find pathkey item to sort</> planner failures
- with <literal>UNION ALL</> over subqueries reading from tables with
+ Fix <quote>could not find pathkey item to sort</quote> planner failures
+ with <literal>UNION ALL</literal> over subqueries reading from tables with
inheritance children (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Improve planner to drop constant-NULL inputs
- of <literal>AND</>/<literal>OR</> when possible (Tom Lane)
+ of <literal>AND</literal>/<literal>OR</literal> when possible (Tom Lane)
</para>
<para>
<listitem>
<para>
- Ensure that the planner sees equivalent <literal>VARIADIC</> and
- non-<literal>VARIADIC</> function calls as equivalent (Tom Lane)
+ Ensure that the planner sees equivalent <literal>VARIADIC</literal> and
+ non-<literal>VARIADIC</literal> function calls as equivalent (Tom Lane)
</para>
<para>
<listitem>
<para>
- Fix handling of nested <type>JSON</> objects
- in <function>json_populate_recordset()</> and friends
+ Fix handling of nested <type>JSON</type> objects
+ in <function>json_populate_recordset()</function> and friends
(Michael Paquier, Tom Lane)
</para>
<para>
- A nested <type>JSON</> object could result in previous fields of the
+ A nested <type>JSON</type> object could result in previous fields of the
parent object not being shown in the output.
</para>
</listitem>
<listitem>
<para>
- Fix identification of input type category in <function>to_json()</>
+ Fix identification of input type category in <function>to_json()</function>
and friends (Tom Lane)
</para>
<para>
- This is known to have led to inadequate quoting of <type>money</>
- fields in the <type>JSON</> result, and there may have been wrong
+ This is known to have led to inadequate quoting of <type>money</type>
+ fields in the <type>JSON</type> result, and there may have been wrong
results for other data types as well.
</para>
</listitem>
This corrects cases where TOAST pointers could be copied into other
tables without being dereferenced. If the original data is later
deleted, it would lead to errors like <quote>missing chunk number 0
- for toast value ...</> when the now-dangling pointer is used.
+ for toast value ...</quote> when the now-dangling pointer is used.
</para>
</listitem>
<listitem>
<para>
- Fix <quote>record type has not been registered</> failures with
+ Fix <quote>record type has not been registered</quote> failures with
whole-row references to the output of Append plan nodes (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix query-lifespan memory leak while evaluating the arguments for a
- function in <literal>FROM</> (Tom Lane)
+ function in <literal>FROM</literal> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix data encoding error in <filename>hungarian.stop</> (Tom Lane)
+ Fix data encoding error in <filename>hungarian.stop</filename> (Tom Lane)
</para>
</listitem>
<para>
This could cause problems (at least spurious warnings, and at worst an
- infinite loop) if <command>CREATE INDEX</> or <command>CLUSTER</> were
+ infinite loop) if <command>CREATE INDEX</command> or <command>CLUSTER</command> were
done later in the same transaction.
</para>
</listitem>
<listitem>
<para>
- Clear <structname>pg_stat_activity</>.<structfield>xact_start</>
- during <command>PREPARE TRANSACTION</> (Andres Freund)
+ Clear <structname>pg_stat_activity</structname>.<structfield>xact_start</structfield>
+ during <command>PREPARE TRANSACTION</command> (Andres Freund)
</para>
<para>
- After the <command>PREPARE</>, the originating session is no longer in
+ After the <command>PREPARE</command>, the originating session is no longer in
a transaction, so it should not continue to display a transaction
start time.
</para>
<listitem>
<para>
- Fix <command>REASSIGN OWNED</> to not fail for text search objects
+ Fix <command>REASSIGN OWNED</command> to not fail for text search objects
(Álvaro Herrera)
</para>
</listitem>
<listitem>
<para>
- Prevent <structname>pg_class</>.<structfield>relminmxid</> values from
- going backwards during <command>VACUUM FULL</> (Álvaro Herrera)
+ Prevent <structname>pg_class</structname>.<structfield>relminmxid</structfield> values from
+ going backwards during <command>VACUUM FULL</command> (Álvaro Herrera)
</para>
</listitem>
<listitem>
<para>
Fix dumping of rules/views when subsequent addition of a column has
- resulted in multiple input columns matching a <literal>USING</>
+ resulted in multiple input columns matching a <literal>USING</literal>
specification (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Repair view printing for some cases involving functions
- in <literal>FROM</> that return a composite type containing dropped
+ in <literal>FROM</literal> that return a composite type containing dropped
columns (Tom Lane)
</para>
</listitem>
<para>
This ensures that the postmaster will properly clean up after itself
- if, for example, it receives <systemitem>SIGINT</> while still
+ if, for example, it receives <systemitem>SIGINT</systemitem> while still
starting up.
</para>
</listitem>
<listitem>
<para>
- Fix client host name lookup when processing <filename>pg_hba.conf</>
+ Fix client host name lookup when processing <filename>pg_hba.conf</filename>
entries that specify host names instead of IP addresses (Tom Lane)
</para>
<listitem>
<para>
- Allow the root user to use <literal>postgres -C variable</> and
- <literal>postgres --describe-config</> (MauMau)
+ Allow the root user to use <literal>postgres -C variable</literal> and
+ <literal>postgres --describe-config</literal> (MauMau)
</para>
<para>
The prohibition on starting the server as root does not need to extend
to these operations, and relaxing it prevents failure
- of <application>pg_ctl</> in some scenarios.
+ of <application>pg_ctl</application> in some scenarios.
</para>
</listitem>
<listitem>
<para>
Secure Unix-domain sockets of temporary postmasters started during
- <literal>make check</> (Noah Misch)
+ <literal>make check</literal> (Noah Misch)
</para>
<para>
the operating-system user running the test, as we previously noted in
CVE-2014-0067. This change defends against that risk by placing the
server's socket in a temporary, mode 0700 subdirectory
- of <filename>/tmp</>. The hazard remains however on platforms where
+ of <filename>/tmp</filename>. The hazard remains however on platforms where
Unix sockets are not supported, notably Windows, because then the
temporary postmaster must accept local TCP connections.
</para>
<para>
A useful side effect of this change is to simplify
- <literal>make check</> testing in builds that
- override <literal>DEFAULT_PGSOCKET_DIR</>. Popular non-default values
- like <filename>/var/run/postgresql</> are often not writable by the
+ <literal>make check</literal> testing in builds that
+ override <literal>DEFAULT_PGSOCKET_DIR</literal>. Popular non-default values
+ like <filename>/var/run/postgresql</filename> are often not writable by the
build user, requiring workarounds that will no longer be necessary.
</para>
</listitem>
</para>
<para>
- This oversight could cause <application>initdb</>
- and <application>pg_upgrade</> to fail on Windows, if the installation
- path contained both spaces and <literal>@</> signs.
+ This oversight could cause <application>initdb</application>
+ and <application>pg_upgrade</application> to fail on Windows, if the installation
+ path contained both spaces and <literal>@</literal> signs.
</para>
</listitem>
<listitem>
<para>
- Fix linking of <application>libpython</> on macOS (Tom Lane)
+ Fix linking of <application>libpython</application> on macOS (Tom Lane)
</para>
<para>
<listitem>
<para>
- Avoid buffer bloat in <application>libpq</> when the server
+ Avoid buffer bloat in <application>libpq</application> when the server
consistently sends data faster than the client can absorb it
(Shin-ichi Morita, Tom Lane)
</para>
<para>
- <application>libpq</> could be coerced into enlarging its input buffer
+ <application>libpq</application> could be coerced into enlarging its input buffer
until it runs out of memory (which would be reported misleadingly
- as <quote>lost synchronization with server</>). Under ordinary
+ as <quote>lost synchronization with server</quote>). Under ordinary
circumstances it's quite far-fetched that data could be continuously
- transmitted more quickly than the <function>recv()</> loop can
+ transmitted more quickly than the <function>recv()</function> loop can
absorb it, but this has been observed when the client is artificially
slowed by scheduler constraints.
</para>
<listitem>
<para>
- Ensure that LDAP lookup attempts in <application>libpq</> time out as
+ Ensure that LDAP lookup attempts in <application>libpq</application> time out as
intended (Laurenz Albe)
</para>
</listitem>
<listitem>
<para>
- Fix <application>ecpg</> to do the right thing when an array
- of <type>char *</> is the target for a FETCH statement returning more
+ Fix <application>ecpg</application> to do the right thing when an array
+ of <type>char *</type> is the target for a FETCH statement returning more
than one row, as well as some other array-handling fixes
(Ashutosh Bapat)
</para>
<listitem>
<para>
- Fix <application>pg_dump</> to cope with a materialized view that
+ Fix <application>pg_dump</application> to cope with a materialized view that
depends on a table's primary key (Tom Lane)
</para>
<para>
This occurs if the view's query relies on functional dependency to
- abbreviate a <literal>GROUP BY</> list. <application>pg_dump</> got
+ abbreviate a <literal>GROUP BY</literal> list. <application>pg_dump</application> got
sufficiently confused that it dumped the materialized view as a
regular view.
</para>
<listitem>
<para>
- Fix parsing of <application>pg_dumpall</>'s <option>-i</> switch
+ Fix parsing of <application>pg_dumpall</application>'s <option>-i</option> switch
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix <application>pg_restore</>'s processing of old-style large object
+ Fix <application>pg_restore</application>'s processing of old-style large object
comments (Tom Lane)
</para>
<para>
A direct-to-database restore from an archive file generated by a
- pre-9.0 version of <application>pg_dump</> would usually fail if the
+ pre-9.0 version of <application>pg_dump</application> would usually fail if the
archive contained more than a few comments for large objects.
</para>
</listitem>
<listitem>
<para>
- Fix <application>pg_upgrade</> for cases where the new server creates
+ Fix <application>pg_upgrade</application> for cases where the new server creates
a TOAST table but the old version did not (Bruce Momjian)
</para>
<para>
- This rare situation would manifest as <quote>relation OID mismatch</>
+ This rare situation would manifest as <quote>relation OID mismatch</quote>
errors.
</para>
</listitem>
<listitem>
<para>
- In <application>pg_upgrade</>,
- preserve <structname>pg_database</>.<structfield>datminmxid</>
- and <structname>pg_class</>.<structfield>relminmxid</> values from the
+ In <application>pg_upgrade</application>,
+ preserve <structname>pg_database</structname>.<structfield>datminmxid</structfield>
+ and <structname>pg_class</structname>.<structfield>relminmxid</structfield> values from the
old cluster, or insert reasonable values when upgrading from pre-9.3;
also defend against unreasonable values in the core server
(Bruce Momjian, Álvaro Herrera, Tom Lane)
<listitem>
<para>
- Prevent <filename>contrib/auto_explain</> from changing the output of
- a user's <command>EXPLAIN</> (Tom Lane)
+ Prevent <filename>contrib/auto_explain</filename> from changing the output of
+ a user's <command>EXPLAIN</command> (Tom Lane)
</para>
<para>
- If <filename>auto_explain</> is active, it could cause
- an <literal>EXPLAIN (ANALYZE, TIMING OFF)</> command to nonetheless
+ If <filename>auto_explain</filename> is active, it could cause
+ an <literal>EXPLAIN (ANALYZE, TIMING OFF)</literal> command to nonetheless
print timing information.
</para>
</listitem>
<listitem>
<para>
- Fix query-lifespan memory leak in <filename>contrib/dblink</>
+ Fix query-lifespan memory leak in <filename>contrib/dblink</filename>
(MauMau, Joe Conway)
</para>
</listitem>
<listitem>
<para>
- In <filename>contrib/pgcrypto</> functions, ensure sensitive
+ In <filename>contrib/pgcrypto</filename> functions, ensure sensitive
information is cleared from stack variables before returning
(Marko Kreen)
</para>
<listitem>
<para>
Prevent use of already-freed memory in
- <filename>contrib/pgstattuple</>'s <function>pgstat_heap()</>
+ <filename>contrib/pgstattuple</filename>'s <function>pgstat_heap()</function>
(Noah Misch)
</para>
</listitem>
<listitem>
<para>
- In <filename>contrib/uuid-ossp</>, cache the state of the OSSP UUID
+ In <filename>contrib/uuid-ossp</filename>, cache the state of the OSSP UUID
library across calls (Tom Lane)
</para>
<para>
This improves the efficiency of UUID generation and reduces the amount
- of entropy drawn from <filename>/dev/urandom</>, on platforms that
+ of entropy drawn from <filename>/dev/urandom</filename>, on platforms that
have that.
</para>
</listitem>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2014e
+ Update time zone data files to <application>tzdata</application> release 2014e
for DST law changes in Crimea, Egypt, and Morocco.
</para>
</listitem>
<listitem>
<para>
Avoid race condition in checking transaction commit status during
- receipt of a <command>NOTIFY</> message (Marko Tiikkaja)
+ receipt of a <command>NOTIFY</command> message (Marko Tiikkaja)
</para>
<para>
<listitem>
<para>
- Allow materialized views to be referenced in <command>UPDATE</>
- and <command>DELETE</> commands (Michael Paquier)
+ Allow materialized views to be referenced in <command>UPDATE</command>
+ and <command>DELETE</command> commands (Michael Paquier)
</para>
<para>
<listitem>
<para>
- Remove incorrect code that tried to allow <literal>OVERLAPS</> with
+ Remove incorrect code that tried to allow <literal>OVERLAPS</literal> with
single-element row arguments (Joshua Yanovski)
</para>
<listitem>
<para>
- Avoid getting more than <literal>AccessShareLock</> when de-parsing a
+ Avoid getting more than <literal>AccessShareLock</literal> when de-parsing a
rule or view (Dean Rasheed)
</para>
<para>
- This oversight resulted in <application>pg_dump</> unexpectedly
- acquiring <literal>RowExclusiveLock</> locks on tables mentioned as
- the targets of <literal>INSERT</>/<literal>UPDATE</>/<literal>DELETE</>
+ This oversight resulted in <application>pg_dump</application> unexpectedly
+ acquiring <literal>RowExclusiveLock</literal> locks on tables mentioned as
+ the targets of <literal>INSERT</literal>/<literal>UPDATE</literal>/<literal>DELETE</literal>
commands in rules. While usually harmless, that could interfere with
concurrent transactions that tried to acquire, for example,
- <literal>ShareLock</> on those tables.
+ <literal>ShareLock</literal> on those tables.
</para>
</listitem>
<listitem>
<para>
Use non-default selectivity estimates for
- <literal><replaceable>value</> IN (<replaceable>list</>)</literal> and
- <literal><replaceable>value</> <replaceable>operator</> ANY
- (<replaceable>array</>)</literal>
+ <literal><replaceable>value</replaceable> IN (<replaceable>list</replaceable>)</literal> and
+ <literal><replaceable>value</replaceable> <replaceable>operator</replaceable> ANY
+ (<replaceable>array</replaceable>)</literal>
expressions when the righthand side is a stable expression (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Remove the correct per-database statistics file during <command>DROP
- DATABASE</> (Tomas Vondra)
+ DATABASE</command> (Tomas Vondra)
</para>
<para>
This fix prevents a permanent leak of statistics file space.
- Users who have done many <command>DROP DATABASE</> commands since
- upgrading to <productname>PostgreSQL</> 9.3 may wish to check their
+ Users who have done many <command>DROP DATABASE</command> commands since
+ upgrading to <productname>PostgreSQL</productname> 9.3 may wish to check their
statistics directory and delete statistics files that do not
correspond to any existing database. Please note
- that <filename>db_0.stat</> should not be removed.
+ that <filename>db_0.stat</filename> should not be removed.
</para>
</listitem>
<listitem>
<para>
- Fix <application>walsender</> ping logic to avoid inappropriate
+ Fix <application>walsender</application> ping logic to avoid inappropriate
disconnects under continuous load (Andres Freund, Heikki Linnakangas)
</para>
<para>
- <application>walsender</> failed to send ping messages to the client
+ <application>walsender</application> failed to send ping messages to the client
if it was constantly busy sending WAL data; but it expected to see
ping responses despite that, and would therefore disconnect
once <xref linkend="guc-wal-sender-timeout"> elapsed.
<listitem>
<para>
- Fix <application>walsender</>'s failure to shut down cleanly when client
- is <application>pg_receivexlog</> (Fujii Masao)
+ Fix <application>walsender</application>'s failure to shut down cleanly when client
+ is <application>pg_receivexlog</application> (Fujii Masao)
</para>
</listitem>
<listitem>
<para>
- Prevent interrupts while reporting non-<literal>ERROR</> messages
+ Prevent interrupts while reporting non-<literal>ERROR</literal> messages
(Tom Lane)
</para>
<para>
This guards against rare server-process freezeups due to recursive
- entry to <function>syslog()</>, and perhaps other related problems.
+ entry to <function>syslog()</function>, and perhaps other related problems.
</para>
</listitem>
<listitem>
<para>
- Fix tracking of <application>psql</> script line numbers
- during <literal>\copy</> from out-of-line data
+ Fix tracking of <application>psql</application> script line numbers
+ during <literal>\copy</literal> from out-of-line data
(Kumar Rajeev Rastogi, Amit Khandekar)
</para>
<para>
- <literal>\copy ... from</> incremented the script file line number
+ <literal>\copy ... from</literal> incremented the script file line number
for each data line, even if the data was not coming from the script
file. This mistake resulted in wrong line numbers being reported for
any errors occurring later in the same script file.
<listitem>
<para>
- Fix <application>contrib/postgres_fdw</> to handle multiple join
+ Fix <application>contrib/postgres_fdw</application> to handle multiple join
conditions properly (Tom Lane)
</para>
<para>
- This oversight could result in sending <literal>WHERE</> clauses to
+ This oversight could result in sending <literal>WHERE</literal> clauses to
the remote server for execution even though the clauses are not known
to have the same semantics on the remote server (for example, clauses
that use non-built-in operators). The query might succeed anyway,
<listitem>
<para>
- Prevent intermittent <quote>could not reserve shared memory region</>
+ Prevent intermittent <quote>could not reserve shared memory region</quote>
failures on recent Windows versions (MauMau)
</para>
</listitem>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2014a
+ Update time zone data files to <application>tzdata</application> release 2014a
for DST law changes in Fiji and Turkey, plus historical changes in
Israel and Ukraine.
</para>
<listitem>
<para>
- Shore up <literal>GRANT ... WITH ADMIN OPTION</> restrictions
+ Shore up <literal>GRANT ... WITH ADMIN OPTION</literal> restrictions
(Noah Misch)
</para>
<para>
- Granting a role without <literal>ADMIN OPTION</> is supposed to
+ Granting a role without <literal>ADMIN OPTION</literal> is supposed to
prevent the grantee from adding or removing members from the granted
role, but this restriction was easily bypassed by doing <literal>SET
- ROLE</> first. The security impact is mostly that a role member can
+ ROLE</literal> first. The security impact is mostly that a role member can
revoke the access of others, contrary to the wishes of his grantor.
Unapproved role member additions are a lesser concern, since an
uncooperative role member could provide most of his rights to others
- anyway by creating views or <literal>SECURITY DEFINER</> functions.
+ anyway by creating views or <literal>SECURITY DEFINER</literal> functions.
(CVE-2014-0060)
</para>
</listitem>
<para>
The primary role of PL validator functions is to be called implicitly
- during <command>CREATE FUNCTION</>, but they are also normal SQL
+ during <command>CREATE FUNCTION</command>, but they are also normal SQL
functions that a user can call explicitly. Calling a validator on
a function actually written in some other language was not checked
for and could be exploited for privilege-escalation purposes.
<para>
If the name lookups come to different conclusions due to concurrent
activity, we might perform some parts of the DDL on a different table
- than other parts. At least in the case of <command>CREATE INDEX</>,
+ than other parts. At least in the case of <command>CREATE INDEX</command>,
this can be used to cause the permissions checks to be performed
against a different table than the index creation, allowing for a
privilege escalation attack.
</para>
<para>
- The <literal>MAXDATELEN</> constant was too small for the longest
- possible value of type <type>interval</>, allowing a buffer overrun
- in <function>interval_out()</>. Although the datetime input
+ The <literal>MAXDATELEN</literal> constant was too small for the longest
+ possible value of type <type>interval</type>, allowing a buffer overrun
+ in <function>interval_out()</function>. Although the datetime input
functions were more careful about avoiding buffer overrun, the limit
was short enough to cause them to reject some valid inputs, such as
- input containing a very long timezone name. The <application>ecpg</>
+ input containing a very long timezone name. The <application>ecpg</application>
library contained these vulnerabilities along with some of its own.
(CVE-2014-0063)
</para>
</para>
<para>
- Use <function>strlcpy()</> and related functions to provide a clear
+ Use <function>strlcpy()</function> and related functions to provide a clear
guarantee that fixed-size buffers are not overrun. Unlike the
preceding items, it is unclear whether these cases really represent
live issues, since in most cases there appear to be previous
<listitem>
<para>
- Avoid crashing if <function>crypt()</> returns NULL (Honza Horak,
+ Avoid crashing if <function>crypt()</function> returns NULL (Honza Horak,
Bruce Momjian)
</para>
<para>
- There are relatively few scenarios in which <function>crypt()</>
- could return NULL, but <filename>contrib/chkpass</> would crash
+ There are relatively few scenarios in which <function>crypt()</function>
+ could return NULL, but <filename>contrib/chkpass</filename> would crash
if it did. One practical case in which this could be an issue is
- if <application>libc</> is configured to refuse to execute unapproved
- hashing algorithms (e.g., <quote>FIPS mode</>).
+ if <application>libc</application> is configured to refuse to execute unapproved
+ hashing algorithms (e.g., <quote>FIPS mode</quote>).
(CVE-2014-0066)
</para>
</listitem>
<listitem>
<para>
- Document risks of <literal>make check</> in the regression testing
+ Document risks of <literal>make check</literal> in the regression testing
instructions (Noah Misch, Tom Lane)
</para>
<para>
- Since the temporary server started by <literal>make check</>
- uses <quote>trust</> authentication, another user on the same machine
+ Since the temporary server started by <literal>make check</literal>
+ uses <quote>trust</quote> authentication, another user on the same machine
could connect to it as database superuser, and then potentially
exploit the privileges of the operating-system user who started the
tests. A future release will probably incorporate changes in the
testing procedure to prevent this risk, but some public discussion is
needed first. So for the moment, just warn people against using
- <literal>make check</> when there are untrusted users on the
+ <literal>make check</literal> when there are untrusted users on the
same machine.
(CVE-2014-0067)
</para>
<para>
The logic for tuple freezing was unable to handle some cases involving
freezing of
- <link linkend="vacuum-for-multixact-wraparound"><firstterm>multixact</>
+ <link linkend="vacuum-for-multixact-wraparound"><firstterm>multixact</firstterm>
IDs</link>, with the practical effect that shared row-level locks
might be forgotten once old enough.
</para>
Fixing this required changing the WAL record format for tuple
freezing. While this is no issue for standalone servers, when using
replication it means that <emphasis>standby servers must be upgraded
- to 9.3.3 or later before their masters are</>. An older standby will
+ to 9.3.3 or later before their masters are</emphasis>. An older standby will
be unable to interpret freeze records generated by a newer master, and
will fail with a PANIC message. (In such a case, upgrading the
standby should be sufficient to let it resume execution.)
<para>
This oversight could allow referential integrity checks to give false
positives (for instance, allow deletes that should have been rejected).
- Applications using the new commands <literal>SELECT FOR KEY SHARE</>
- and <literal>SELECT FOR NO KEY UPDATE</> might also have suffered
+ Applications using the new commands <literal>SELECT FOR KEY SHARE</literal>
+ and <literal>SELECT FOR NO KEY UPDATE</literal> might also have suffered
locking failures of this kind.
</para>
</listitem>
<listitem>
<para>
- Prevent <quote>forgetting</> valid row locks when one of several
+ Prevent <quote>forgetting</quote> valid row locks when one of several
holders of a row lock aborts (Álvaro Herrera)
</para>
<para>
This mistake could result in spurious <quote>could not serialize access
- due to concurrent update</> errors in <literal>REPEATABLE READ</>
- and <literal>SERIALIZABLE</> transaction isolation modes.
+ due to concurrent update</quote> errors in <literal>REPEATABLE READ</literal>
+ and <literal>SERIALIZABLE</literal> transaction isolation modes.
</para>
</listitem>
<listitem>
<para>
Handle wraparound correctly during extension or truncation
- of <filename>pg_multixact/members</>
+ of <filename>pg_multixact/members</filename>
(Andres Freund, Álvaro Herrera)
</para>
</listitem>
<listitem>
<para>
- Fix handling of 5-digit filenames in <filename>pg_multixact/members</>
+ Fix handling of 5-digit filenames in <filename>pg_multixact/members</filename>
(Álvaro Herrera)
</para>
<para>
This fixes a performance regression from pre-9.3 versions when doing
- <literal>SELECT FOR UPDATE</> followed by <literal>UPDATE/DELETE</>.
+ <literal>SELECT FOR UPDATE</literal> followed by <literal>UPDATE/DELETE</literal>.
</para>
</listitem>
<para>
During archive recovery, prefer highest timeline number when WAL
segments with the same ID are present in both the archive
- and <filename>pg_xlog/</> (Kyotaro Horiguchi)
+ and <filename>pg_xlog/</filename> (Kyotaro Horiguchi)
</para>
<para>
<para>
The WAL update could be applied to the wrong page, potentially many
pages past where it should have been. Aside from corrupting data,
- this error has been observed to result in significant <quote>bloat</>
+ this error has been observed to result in significant <quote>bloat</quote>
of standby servers compared to their masters, due to updates being
applied far beyond where the end-of-file should have been. This
failure mode does not appear to be a significant risk during crash
was already consistent at the start of replay, thus possibly allowing
hot-standby queries before the database was really consistent. Other
symptoms such as <quote>PANIC: WAL contains references to invalid
- pages</> were also possible.
+ pages</quote> were also possible.
</para>
</listitem>
<listitem>
<para>
Fix improper locking of btree index pages while replaying
- a <literal>VACUUM</> operation in hot-standby mode (Andres Freund,
+ a <literal>VACUUM</literal> operation in hot-standby mode (Andres Freund,
Heikki Linnakangas, Tom Lane)
</para>
<para>
This error could result in <quote>PANIC: WAL contains references to
- invalid pages</> failures.
+ invalid pages</quote> failures.
</para>
</listitem>
<listitem>
<para>
- When <literal>pause_at_recovery_target</>
- and <literal>recovery_target_inclusive</> are both set, ensure the
+ When <literal>pause_at_recovery_target</literal>
+ and <literal>recovery_target_inclusive</literal> are both set, ensure the
target record is applied before pausing, not after (Heikki
Linnakangas)
</para>
<listitem>
<para>
Prevent timeout interrupts from taking control away from mainline
- code unless <varname>ImmediateInterruptOK</> is set
+ code unless <varname>ImmediateInterruptOK</varname> is set
(Andres Freund, Tom Lane)
</para>
<para>
This is a serious issue for any application making use of statement
timeouts, as it could cause all manner of strange failures after a
- timeout occurred. We have seen reports of <quote>stuck</> spinlocks,
+ timeout occurred. We have seen reports of <quote>stuck</quote> spinlocks,
ERRORs being unexpectedly promoted to PANICs, unkillable backends,
and other misbehaviors.
</para>
<para>
Ensure that signal handlers don't attempt to use the
- process's <varname>MyProc</> pointer after it's no longer valid.
+ process's <varname>MyProc</varname> pointer after it's no longer valid.
</para>
</listitem>
<listitem>
<para>
- Fix unsafe references to <varname>errno</> within error reporting
+ Fix unsafe references to <varname>errno</varname> within error reporting
logic (Christian Kruse)
</para>
<para>
This would typically lead to odd behaviors such as missing or
- inappropriate <literal>HINT</> fields.
+ inappropriate <literal>HINT</literal> fields.
</para>
</listitem>
<listitem>
<para>
- Fix possible crashes from using <function>ereport()</> too early
+ Fix possible crashes from using <function>ereport()</function> too early
during server startup (Tom Lane)
</para>
<listitem>
<para>
- Fix length checking for Unicode identifiers (<literal>U&"..."</>
+ Fix length checking for Unicode identifiers (<literal>U&"..."</literal>
syntax) containing escapes (Tom Lane)
</para>
<para>
A previous patch allowed such keywords to be used without quoting
in places such as role identifiers; but it missed cases where a
- list of role identifiers was permitted, such as <literal>DROP ROLE</>.
+ list of role identifiers was permitted, such as <literal>DROP ROLE</literal>.
</para>
</listitem>
<listitem>
<para>
Fix possible crash due to invalid plan for nested sub-selects, such
- as <literal>WHERE (... x IN (SELECT ...) ...) IN (SELECT ...)</>
+ as <literal>WHERE (... x IN (SELECT ...) ...) IN (SELECT ...)</literal>
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix mishandling of <literal>WHERE</> conditions pulled up from
- a <literal>LATERAL</> subquery (Tom Lane)
+ Fix mishandling of <literal>WHERE</literal> conditions pulled up from
+ a <literal>LATERAL</literal> subquery (Tom Lane)
</para>
<para>
The typical symptom of this bug was a <quote>JOIN qualification
- cannot refer to other relations</> error, though subtle logic
+ cannot refer to other relations</quote> error, though subtle logic
errors in created plans seem possible as well.
</para>
</listitem>
<listitem>
<para>
- Disallow <literal>LATERAL</> references to the target table of
- an <literal>UPDATE/DELETE</> (Tom Lane)
+ Disallow <literal>LATERAL</literal> references to the target table of
+ an <literal>UPDATE/DELETE</literal> (Tom Lane)
</para>
<para>
<listitem>
<para>
- Fix <literal>UPDATE/DELETE</> of an inherited target table
- that has <literal>UNION ALL</> subqueries (Tom Lane)
+ Fix <literal>UPDATE/DELETE</literal> of an inherited target table
+ that has <literal>UNION ALL</literal> subqueries (Tom Lane)
</para>
<para>
- Without this fix, <literal>UNION ALL</> subqueries aren't correctly
+ Without this fix, <literal>UNION ALL</literal> subqueries aren't correctly
inserted into the update plans for inheritance child tables after the
first one, typically resulting in no update happening for those child
table(s).
<listitem>
<para>
- Fix <command>ANALYZE</> to not fail on a column that's a domain over
+ Fix <command>ANALYZE</command> to not fail on a column that's a domain over
a range type (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Ensure that <command>ANALYZE</> creates statistics for a table column
- even when all the values in it are <quote>too wide</> (Tom Lane)
+ Ensure that <command>ANALYZE</command> creates statistics for a table column
+ even when all the values in it are <quote>too wide</quote> (Tom Lane)
</para>
<para>
- <command>ANALYZE</> intentionally omits very wide values from its
+ <command>ANALYZE</command> intentionally omits very wide values from its
histogram and most-common-values calculations, but it neglected to do
something sane in the case that all the sampled entries are too wide.
</para>
<listitem>
<para>
- In <literal>ALTER TABLE ... SET TABLESPACE</>, allow the database's
+ In <literal>ALTER TABLE ... SET TABLESPACE</literal>, allow the database's
default tablespace to be used without a permissions check
(Stephen Frost)
</para>
<para>
- <literal>CREATE TABLE</> has always allowed such usage,
- but <literal>ALTER TABLE</> didn't get the memo.
+ <literal>CREATE TABLE</literal> has always allowed such usage,
+ but <literal>ALTER TABLE</literal> didn't get the memo.
</para>
</listitem>
<listitem>
<para>
- Fix <quote>cannot accept a set</> error when some arms of
- a <literal>CASE</> return a set and others don't (Tom Lane)
+ Fix <quote>cannot accept a set</quote> error when some arms of
+ a <literal>CASE</literal> return a set and others don't (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix possible misbehavior in <function>plainto_tsquery()</>
+ Fix possible misbehavior in <function>plainto_tsquery()</function>
(Heikki Linnakangas)
</para>
<para>
- Use <function>memmove()</> not <function>memcpy()</> for copying
+ Use <function>memmove()</function> not <function>memcpy()</function> for copying
overlapping memory regions. There have been no field reports of
this actually causing trouble, but it's certainly risky.
</para>
<listitem>
<para>
- Fix placement of permissions checks in <function>pg_start_backup()</>
- and <function>pg_stop_backup()</> (Andres Freund, Magnus Hagander)
+ Fix placement of permissions checks in <function>pg_start_backup()</function>
+ and <function>pg_stop_backup()</function> (Andres Freund, Magnus Hagander)
</para>
<para>
<listitem>
<para>
- Accept <literal>SHIFT_JIS</> as an encoding name for locale checking
+ Accept <literal>SHIFT_JIS</literal> as an encoding name for locale checking
purposes (Tatsuo Ishii)
</para>
</listitem>
<listitem>
<para>
- Fix <literal>*</>-qualification of named parameters in SQL-language
+ Fix <literal>*</literal>-qualification of named parameters in SQL-language
functions (Tom Lane)
</para>
<para>
Given a composite-type parameter
- named <literal>foo</>, <literal>$1.*</> worked fine,
- but <literal>foo.*</> not so much.
+ named <literal>foo</literal>, <literal>$1.*</literal> worked fine,
+ but <literal>foo.*</literal> not so much.
</para>
</listitem>
<listitem>
<para>
- Fix misbehavior of <function>PQhost()</> on Windows (Fujii Masao)
+ Fix misbehavior of <function>PQhost()</function> on Windows (Fujii Masao)
</para>
<para>
- It should return <literal>localhost</> if no host has been specified.
+ It should return <literal>localhost</literal> if no host has been specified.
</para>
</listitem>
<listitem>
<para>
- Improve error handling in <application>libpq</> and <application>psql</>
- for failures during <literal>COPY TO STDOUT/FROM STDIN</> (Tom Lane)
+ Improve error handling in <application>libpq</application> and <application>psql</application>
+ for failures during <literal>COPY TO STDOUT/FROM STDIN</literal> (Tom Lane)
</para>
<para>
In particular this fixes an infinite loop that could occur in 9.2 and
up if the server connection was lost during <literal>COPY FROM
- STDIN</>. Variants of that scenario might be possible in older
+ STDIN</literal>. Variants of that scenario might be possible in older
versions, or with other client applications.
</para>
</listitem>
<listitem>
<para>
Fix incorrect translation handling in
- some <application>psql</> <literal>\d</> commands
+ some <application>psql</application> <literal>\d</literal> commands
(Peter Eisentraut, Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Ensure <application>pg_basebackup</>'s background process is killed
+ Ensure <application>pg_basebackup</application>'s background process is killed
when exiting its foreground process (Magnus Hagander)
</para>
</listitem>
<listitem>
<para>
Fix possible incorrect printing of filenames
- in <application>pg_basebackup</>'s verbose mode (Magnus Hagander)
+ in <application>pg_basebackup</application>'s verbose mode (Magnus Hagander)
</para>
</listitem>
<listitem>
<para>
- Fix misaligned descriptors in <application>ecpg</> (MauMau)
+ Fix misaligned descriptors in <application>ecpg</application> (MauMau)
</para>
</listitem>
<listitem>
<para>
- In <application>ecpg</>, handle lack of a hostname in the connection
+ In <application>ecpg</application>, handle lack of a hostname in the connection
parameters properly (Michael Meskes)
</para>
</listitem>
<listitem>
<para>
- Fix performance regression in <filename>contrib/dblink</> connection
+ Fix performance regression in <filename>contrib/dblink</filename> connection
startup (Joe Conway)
</para>
<listitem>
<para>
- In <filename>contrib/isn</>, fix incorrect calculation of the check
+ In <filename>contrib/isn</filename>, fix incorrect calculation of the check
digit for ISMN values (Fabien Coelho)
</para>
</listitem>
<listitem>
<para>
- Fix <filename>contrib/pgbench</>'s progress logging to avoid overflow
+ Fix <filename>contrib/pgbench</filename>'s progress logging to avoid overflow
when the scale factor is large (Tatsuo Ishii)
</para>
</listitem>
<listitem>
<para>
- Fix <filename>contrib/pg_stat_statement</>'s handling
- of <literal>CURRENT_DATE</> and related constructs (Kyotaro
+ Fix <filename>contrib/pg_stat_statement</filename>'s handling
+ of <literal>CURRENT_DATE</literal> and related constructs (Kyotaro
Horiguchi)
</para>
</listitem>
<listitem>
<para>
Improve lost-connection error handling
- in <filename>contrib/postgres_fdw</> (Tom Lane)
+ in <filename>contrib/postgres_fdw</filename> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- In Mingw and Cygwin builds, install the <application>libpq</> DLL
- in the <filename>bin</> directory (Andrew Dunstan)
+ In Mingw and Cygwin builds, install the <application>libpq</application> DLL
+ in the <filename>bin</filename> directory (Andrew Dunstan)
</para>
<para>
This duplicates what the MSVC build has long done. It should fix
- problems with programs like <application>psql</> failing to start
+ problems with programs like <application>psql</application> failing to start
because they can't find the DLL.
</para>
</listitem>
<listitem>
<para>
- Avoid using the deprecated <literal>dllwrap</> tool in Cygwin builds
+ Avoid using the deprecated <literal>dllwrap</literal> tool in Cygwin builds
(Marco Atzeri)
</para>
</listitem>
<listitem>
<para>
- Don't generate plain-text <filename>HISTORY</>
- and <filename>src/test/regress/README</> files anymore (Tom Lane)
+ Don't generate plain-text <filename>HISTORY</filename>
+ and <filename>src/test/regress/README</filename> files anymore (Tom Lane)
</para>
<para>
the likely audience for plain-text format. Distribution tarballs
will still contain files by these names, but they'll just be stubs
directing the reader to consult the main documentation.
- The plain-text <filename>INSTALL</> file will still be maintained, as
+ The plain-text <filename>INSTALL</filename> file will still be maintained, as
there is arguably a use-case for that.
</para>
</listitem>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2013i
+ Update time zone data files to <application>tzdata</application> release 2013i
for DST law changes in Jordan and historical changes in Cuba.
</para>
<para>
- In addition, the zones <literal>Asia/Riyadh87</>,
- <literal>Asia/Riyadh88</>, and <literal>Asia/Riyadh89</> have been
+ In addition, the zones <literal>Asia/Riyadh87</literal>,
+ <literal>Asia/Riyadh88</literal>, and <literal>Asia/Riyadh89</literal> have been
removed, as they are no longer maintained by IANA, and never
represented actual civil timekeeping practice.
</para>
<listitem>
<para>
- Fix <command>VACUUM</>'s tests to see whether it can
- update <structfield>relfrozenxid</> (Andres Freund)
+ Fix <command>VACUUM</command>'s tests to see whether it can
+ update <structfield>relfrozenxid</structfield> (Andres Freund)
</para>
<para>
- In some cases <command>VACUUM</> (either manual or autovacuum) could
- incorrectly advance a table's <structfield>relfrozenxid</> value,
+ In some cases <command>VACUUM</command> (either manual or autovacuum) could
+ incorrectly advance a table's <structfield>relfrozenxid</structfield> value,
allowing tuples to escape freezing, causing those rows to become
invisible once 2^31 transactions have elapsed. The probability of
data loss is fairly low since multiple incorrect advancements would
need to happen before actual loss occurs, but it's not zero. In 9.2.0
and later, the probability of loss is higher, and it's also possible
- to get <quote>could not access status of transaction</> errors as a
+ to get <quote>could not access status of transaction</quote> errors as a
consequence of this bug. Users upgrading from releases 9.0.4 or 8.4.8
or earlier are not affected, but all later versions contain the bug.
</para>
<para>
The issue can be ameliorated by, after upgrading, vacuuming all tables
in all databases while having <link
- linkend="guc-vacuum-freeze-table-age"><varname>vacuum_freeze_table_age</></link>
+ linkend="guc-vacuum-freeze-table-age"><varname>vacuum_freeze_table_age</varname></link>
set to zero. This will fix any latent corruption but will not be able
to fix all pre-existing data errors. However, an installation can be
presumed safe after performing this vacuuming if it has executed fewer
than 2^31 update transactions in its lifetime (check this with
- <literal>SELECT txid_current() < 2^31</>).
+ <literal>SELECT txid_current() < 2^31</literal>).
</para>
</listitem>
<para>
These bugs could lead to <quote>could not access status of
- transaction</> errors, or to duplicate or vanishing rows.
+ transaction</quote> errors, or to duplicate or vanishing rows.
Users upgrading from releases prior to 9.3.0 are not affected.
</para>
<para>
The issue can be ameliorated by, after upgrading, vacuuming all tables
in all databases while having <link
- linkend="guc-vacuum-freeze-table-age"><varname>vacuum_freeze_table_age</></link>
+ linkend="guc-vacuum-freeze-table-age"><varname>vacuum_freeze_table_age</varname></link>
set to zero. This will fix latent corruption but will not be able to
fix all pre-existing data errors.
</para>
<listitem>
<para>
- Fix initialization of <filename>pg_clog</> and <filename>pg_subtrans</>
+ Fix initialization of <filename>pg_clog</filename> and <filename>pg_subtrans</filename>
during hot standby startup (Andres Freund, Heikki Linnakangas)
</para>
<para>
These bugs could result in incorrect behavior, such as locking or even
updating the wrong row, in the presence of concurrent updates.
- Spurious <quote>unable to fetch updated version of tuple</> errors
+ Spurious <quote>unable to fetch updated version of tuple</quote> errors
were also possible.
</para>
</listitem>
<para>
This could lead to corruption of the lock data structures in shared
- memory, causing <quote>lock already held</> and other odd errors.
+ memory, causing <quote>lock already held</quote> and other odd errors.
</para>
</listitem>
<listitem>
<para>
- Truncate <filename>pg_multixact</> contents during WAL replay
+ Truncate <filename>pg_multixact</filename> contents during WAL replay
(Andres Freund)
</para>
<listitem>
<para>
- Ensure an anti-wraparound <command>VACUUM</> counts a page as scanned
+ Ensure an anti-wraparound <command>VACUUM</command> counts a page as scanned
when it's only verified that no tuples need freezing (Sergey
Burladyan, Jeff Janes)
</para>
<para>
This bug could result in failing to
- advance <structfield>relfrozenxid</>, so that the table would still be
+ advance <structfield>relfrozenxid</structfield>, so that the table would still be
thought to need another anti-wraparound vacuum. In the worst case the
database might even shut down to prevent wraparound.
</para>
<listitem>
<para>
- Fix <quote>unexpected spgdoinsert() failure</> error during SP-GiST
+ Fix <quote>unexpected spgdoinsert() failure</quote> error during SP-GiST
index creation (Teodor Sigaev)
</para>
</listitem>
</para>
<para>
- Historically <productname>PostgreSQL</> has accepted queries like
+ Historically <productname>PostgreSQL</productname> has accepted queries like
<programlisting>
SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
</programlisting>
although a strict reading of the SQL standard would forbid the
- duplicate usage of table alias <literal>x</>. A misguided change in
+ duplicate usage of table alias <literal>x</literal>. A misguided change in
9.3.0 caused it to reject some such cases that were formerly accepted.
Restore the previous behavior.
</para>
<listitem>
<para>
- Avoid flattening a subquery whose <literal>SELECT</> list contains a
- volatile function wrapped inside a sub-<literal>SELECT</> (Tom Lane)
+ Avoid flattening a subquery whose <literal>SELECT</literal> list contains a
+ volatile function wrapped inside a sub-<literal>SELECT</literal> (Tom Lane)
</para>
<para>
<para>
This error could lead to incorrect plans for queries involving
- multiple levels of subqueries within <literal>JOIN</> syntax.
+ multiple levels of subqueries within <literal>JOIN</literal> syntax.
</para>
</listitem>
<listitem>
<para>
Fix incorrect planning in cases where the same non-strict expression
- appears in multiple <literal>WHERE</> and outer <literal>JOIN</>
+ appears in multiple <literal>WHERE</literal> and outer <literal>JOIN</literal>
equality clauses (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Fix array slicing of <type>int2vector</> and <type>oidvector</> values
+ Fix array slicing of <type>int2vector</type> and <type>oidvector</type> values
(Tom Lane)
</para>
<para>
Expressions of this kind are now implicitly promoted to
- regular <type>int2</> or <type>oid</> arrays.
+ regular <type>int2</type> or <type>oid</type> arrays.
</para>
</listitem>
<listitem>
<para>
- Return a valid JSON value when converting an empty <type>hstore</> value
- to <type>json</>
+ Return a valid JSON value when converting an empty <type>hstore</type> value
+ to <type>json</type>
(Oskari Saarenmaa)
</para>
</listitem>
In some cases, the system would use the simple GMT offset value when
it should have used the regular timezone setting that had prevailed
before the simple offset was selected. This change also causes
- the <function>timeofday</> function to honor the simple GMT offset
+ the <function>timeofday</function> function to honor the simple GMT offset
zone.
</para>
</listitem>
<listitem>
<para>
- Properly quote generated command lines in <application>pg_ctl</>
+ Properly quote generated command lines in <application>pg_ctl</application>
(Naoya Anzai and Tom Lane)
</para>
<listitem>
<para>
- Fix <application>pg_dumpall</> to work when a source database
+ Fix <application>pg_dumpall</application> to work when a source database
sets <link
- linkend="guc-default-transaction-read-only"><varname>default_transaction_read_only</></link>
- via <command>ALTER DATABASE SET</> (Kevin Grittner)
+ linkend="guc-default-transaction-read-only"><varname>default_transaction_read_only</varname></link>
+ via <command>ALTER DATABASE SET</command> (Kevin Grittner)
</para>
<para>
<listitem>
<para>
- Fix <application>pg_isready</> to handle its <option>-d</> option
+ Fix <application>pg_isready</application> to handle its <option>-d</option> option
properly (Fabrízio de Royes Mello and Fujii Masao)
</para>
</listitem>
<listitem>
<para>
- Fix parsing of WAL file names in <application>pg_receivexlog</>
+ Fix parsing of WAL file names in <application>pg_receivexlog</application>
(Heikki Linnakangas)
</para>
<para>
- This error made <application>pg_receivexlog</> unable to restart
+ This error made <application>pg_receivexlog</application> unable to restart
streaming after stopping, once at least 4 GB of WAL had been written.
</para>
</listitem>
<listitem>
<para>
Report out-of-disk-space failures properly
- in <application>pg_upgrade</> (Peter Eisentraut)
+ in <application>pg_upgrade</application> (Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
- Make <application>ecpg</> search for quoted cursor names
+ Make <application>ecpg</application> search for quoted cursor names
case-sensitively (Zoltán Böszörményi)
</para>
</listitem>
<listitem>
<para>
- Fix <application>ecpg</>'s processing of lists of variables
- declared <type>varchar</> (Zoltán Böszörményi)
+ Fix <application>ecpg</application>'s processing of lists of variables
+ declared <type>varchar</type> (Zoltán Böszörményi)
</para>
</listitem>
<listitem>
<para>
- Make <filename>contrib/lo</> defend against incorrect trigger definitions
+ Make <filename>contrib/lo</filename> defend against incorrect trigger definitions
(Marc Cousin)
</para>
</listitem>
<listitem>
<para>
- Update time zone data files to <application>tzdata</> release 2013h
+ Update time zone data files to <application>tzdata</application> release 2013h
for DST law changes in Argentina, Brazil, Jordan, Libya,
Liechtenstein, Morocco, and Palestine. Also, new timezone
abbreviations WIB, WIT, WITA for Indonesia.
</para>
<para>
- However, if you use the <literal>hstore</> extension, see the
+ However, if you use the <literal>hstore</literal> extension, see the
first changelog entry.
</para>
<listitem>
<para>
- Ensure new-in-9.3 JSON functionality is added to the <literal>hstore</>
+ Ensure new-in-9.3 JSON functionality is added to the <literal>hstore</literal>
extension during an update (Andrew Dunstan)
</para>
<para>
- Users who upgraded a pre-9.3 database containing <literal>hstore</>
+ Users who upgraded a pre-9.3 database containing <literal>hstore</literal>
should execute
<programlisting>
ALTER EXTENSION hstore UPDATE;
</programlisting>
after installing 9.3.1, to add two new JSON functions and a cast.
- (If <literal>hstore</> is already up to date, this command does
+ (If <literal>hstore</literal> is already up to date, this command does
nothing.)
</para>
</listitem>
<listitem>
<para>
- Fix timeline handling bugs in <application>pg_receivexlog</>
+ Fix timeline handling bugs in <application>pg_receivexlog</application>
(Heikki Linnakangas, Andrew Gierth)
</para>
</listitem>
<listitem>
<para>
- Prevent <command>CREATE FUNCTION</> from checking <command>SET</>
+ Prevent <command>CREATE FUNCTION</command> from checking <command>SET</command>
variables unless function body checking is enabled (Tom Lane)
</para>
</listitem>
<title>Overview</title>
<para>
- Major enhancements in <productname>PostgreSQL</> 9.3 include:
+ Major enhancements in <productname>PostgreSQL</productname> 9.3 include:
</para>
<!-- This list duplicates items below, but without authors or details-->
<listitem>
<para>
- Add <link linkend="SQL-CREATEMATERIALIZEDVIEW">materialized
+ Add <link linkend="sql-creatematerializedview">materialized
views</link>
</para>
</listitem>
<listitem>
<para>
Make simple views <link
- linkend="SQL-CREATEVIEW-updatable-views">auto-updatable</link>
+ linkend="sql-createview-updatable-views">auto-updatable</link>
</para>
</listitem>
<listitem>
<para>
- Add many features for the <type>JSON</> data type,
+ Add many features for the <type>JSON</type> data type,
including <link linkend="functions-json">operators and functions</link>
- to extract elements from <type>JSON</> values
+ to extract elements from <type>JSON</type> values
</para>
</listitem>
<listitem>
<para>
- Implement <acronym>SQL</>-standard <link
- linkend="queries-lateral"><literal>LATERAL</></link> option for
- <literal>FROM</>-clause subqueries and function calls
+ Implement <acronym>SQL</acronym>-standard <link
+ linkend="queries-lateral"><literal>LATERAL</literal></link> option for
+ <literal>FROM</literal>-clause subqueries and function calls
</para>
</listitem>
<listitem>
<para>
- Allow <link linkend="SQL-CREATEFOREIGNDATAWRAPPER">foreign data
+ Allow <link linkend="sql-createforeigndatawrapper">foreign data
wrappers</link> to support writes (inserts/updates/deletes) on foreign
tables
</para>
<listitem>
<para>
- Add a <link linkend="postgres-fdw"><productname>Postgres</> foreign
+ Add a <link linkend="postgres-fdw"><productname>Postgres</productname> foreign
data wrapper</link> to allow access to
- other <productname>Postgres</> servers
+ other <productname>Postgres</productname> servers
</para>
</listitem>
<para>
A dump/restore using <link
- linkend="APP-PG-DUMPALL"><application>pg_dumpall</></link>, or use
- of <link linkend="pgupgrade"><application>pg_upgrade</></link>, is
+ linkend="app-pg-dumpall"><application>pg_dumpall</application></link>, or use
+ of <link linkend="pgupgrade"><application>pg_upgrade</application></link>, is
required for those wishing to migrate data from any previous release.
</para>
<listitem>
<para>
- Rename <varname>replication_timeout</> to <link
- linkend="guc-wal-sender-timeout"><varname>wal_sender_timeout</></link>
+ Rename <varname>replication_timeout</varname> to <link
+ linkend="guc-wal-sender-timeout"><varname>wal_sender_timeout</varname></link>
(Amit Kapila)
</para>
<para>
This setting controls the <link
- linkend="wal"><acronym>WAL</></link> sender timeout.
+ linkend="wal"><acronym>WAL</acronym></link> sender timeout.
</para>
</listitem>
<listitem>
<para>
Require superuser privileges to set <link
- linkend="guc-commit-delay"><varname>commit_delay</></link>
+ linkend="guc-commit-delay"><varname>commit_delay</varname></link>
because it can now potentially delay other sessions (Simon Riggs)
</para>
</listitem>
<para>
Users who have set <link
- linkend="guc-work-mem"><varname>work_mem</></link> based on the
+ linkend="guc-work-mem"><varname>work_mem</varname></link> based on the
previous behavior may need to revisit that setting.
</para>
</listitem>
<listitem>
<para>
Throw an error if a tuple to be updated or deleted has already been
- updated or deleted by a <literal>BEFORE</> trigger (Kevin Grittner)
+ updated or deleted by a <literal>BEFORE</literal> trigger (Kevin Grittner)
</para>
<para>
Now an error is thrown to prevent the inconsistent results from being
committed. If this change affects your application, the best solution
is usually to move the data-propagation actions to
- an <literal>AFTER</> trigger.
+ an <literal>AFTER</literal> trigger.
</para>
<para>
<listitem>
<para>
- Change multicolumn <link linkend="SQL-CREATETABLE"><literal>ON UPDATE
- SET NULL/SET DEFAULT</></link> foreign key actions to affect
+ Change multicolumn <link linkend="sql-createtable"><literal>ON UPDATE
+ SET NULL/SET DEFAULT</literal></link> foreign key actions to affect
all columns of the constraint, not just those changed in the
- <command>UPDATE</> (Tom Lane)
+ <command>UPDATE</command> (Tom Lane)
</para>
<para>
Previously, we would set only those referencing columns that
correspond to referenced columns that were changed by
- the <command>UPDATE</>. This was what was required by SQL-92,
+ the <command>UPDATE</command>. This was what was required by SQL-92,
but more recent editions of the SQL standard specify the new behavior.
</para>
</listitem>
<listitem>
<para>
Force cached plans to be replanned if the <link
- linkend="guc-search-path"><varname>search_path</></link> changes
+ linkend="guc-search-path"><varname>search_path</varname></link> changes
(Tom Lane)
</para>
<para>
Previously, cached plans already generated in the current session were
not redone if the query was re-executed with a
- new <varname>search_path</> setting, resulting in surprising behavior.
+ new <varname>search_path</varname> setting, resulting in surprising behavior.
</para>
</listitem>
<listitem>
<para>
Fix <link
- linkend="functions-formatting-table"><function>to_number()</></link>
+ linkend="functions-formatting-table"><function>to_number()</function></link>
to properly handle a period used as a thousands separator (Tom Lane)
</para>
<para>
Previously, a period was considered to be a decimal point even when
- the locale says it isn't and the <literal>D</> format code is used to
+ the locale says it isn't and the <literal>D</literal> format code is used to
specify use of the locale-specific decimal point. This resulted in
- wrong answers if <literal>FM</> format was also used.
+ wrong answers if <literal>FM</literal> format was also used.
</para>
</listitem>
<listitem>
<para>
- Fix <literal>STRICT</> non-set-returning functions that have
+ Fix <literal>STRICT</literal> non-set-returning functions that have
set-returning functions in their arguments to properly return null
rows (Tom Lane)
</para>
<listitem>
<para>
- Store <link linkend="wal"><acronym>WAL</></link> in a continuous
+ Store <link linkend="wal"><acronym>WAL</acronym></link> in a continuous
stream, rather than skipping the last 16MB segment every 4GB
(Heikki Linnakangas)
</para>
<para>
- Previously, <acronym>WAL</> files with names ending in <literal>FF</>
- were not used because of this skipping. If you have <acronym>WAL</>
+ Previously, <acronym>WAL</acronym> files with names ending in <literal>FF</literal>
+ were not used because of this skipping. If you have <acronym>WAL</acronym>
backup or restore scripts that took this behavior into account, they
will need to be adjusted.
</para>
<listitem>
<para>
In <link
- linkend="catalog-pg-constraint"><structname>pg_constraint.confmatchtype</></link>,
- store the default foreign key match type (non-<literal>FULL</>,
- non-<literal>PARTIAL</>) as <literal>s</> for <quote>simple</>
+ linkend="catalog-pg-constraint"><structname>pg_constraint.confmatchtype</structname></link>,
+ store the default foreign key match type (non-<literal>FULL</literal>,
+ non-<literal>PARTIAL</literal>) as <literal>s</literal> for <quote>simple</quote>
(Tom Lane)
</para>
<para>
- Previously this case was represented by <literal>u</>
- for <quote>unspecified</>.
+ Previously this case was represented by <literal>u</literal>
+ for <quote>unspecified</quote>.
</para>
</listitem>
<para>
This change improves concurrency and reduces the probability of
deadlocks when updating tables involved in a foreign-key constraint.
- <command>UPDATE</>s that do not change any columns referenced in a
- foreign key now take the new <literal>NO KEY UPDATE</> lock mode on
- the row, while foreign key checks use the new <literal>KEY SHARE</>
- lock mode, which does not conflict with <literal>NO KEY UPDATE</>.
+ <command>UPDATE</command>s that do not change any columns referenced in a
+ foreign key now take the new <literal>NO KEY UPDATE</literal> lock mode on
+ the row, while foreign key checks use the new <literal>KEY SHARE</literal>
+ lock mode, which does not conflict with <literal>NO KEY UPDATE</literal>.
So there is no blocking unless a foreign-key column is changed.
</para>
</listitem>
<listitem>
<para>
Add configuration variable <link
- linkend="guc-lock-timeout"><varname>lock_timeout</></link> to
+ linkend="guc-lock-timeout"><varname>lock_timeout</varname></link> to
allow limiting how long a session will wait to acquire any one lock
(Zoltán Böszörményi)
</para>
<listitem>
<para>
- Add <link linkend="rangetypes-indexing"><acronym>SP-GiST</></link>
+ Add <link linkend="rangetypes-indexing"><acronym>SP-GiST</acronym></link>
support for range data types (Alexander Korotkov)
</para>
</listitem>
<listitem>
<para>
- Allow <link linkend="GiST"><acronym>GiST</></link> indexes to be
+ Allow <link linkend="gist"><acronym>GiST</acronym></link> indexes to be
unlogged (Jeevan Chalke)
</para>
</listitem>
<listitem>
<para>
- Improve performance of <acronym>GiST</> index insertion by randomizing
+ Improve performance of <acronym>GiST</acronym> index insertion by randomizing
the choice of which page to descend to when there are multiple equally
good alternatives (Heikki Linnakangas)
</para>
<listitem>
<para>
Improve optimizer's hash table size estimate for
- doing <literal>DISTINCT</> via hash aggregation (Tom Lane)
+ doing <literal>DISTINCT</literal> via hash aggregation (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Add <link linkend="SQL-COPY"><command>COPY FREEZE</></link>
+ Add <link linkend="sql-copy"><command>COPY FREEZE</command></link>
option to avoid the overhead of marking tuples as frozen later
(Simon Riggs, Jeff Davis)
</para>
<listitem>
<para>
Improve performance of <link
- linkend="datatype-numeric"><type>NUMERIC</></link> calculations
+ linkend="datatype-numeric"><type>NUMERIC</type></link> calculations
(Kyotaro Horiguchi)
</para>
</listitem>
<listitem>
<para>
Improve synchronization of sessions waiting for <link
- linkend="guc-commit-delay"><varname>commit_delay</></link>
+ linkend="guc-commit-delay"><varname>commit_delay</varname></link>
(Peter Geoghegan)
</para>
<para>
- This greatly improves the usefulness of <varname>commit_delay</>.
+ This greatly improves the usefulness of <varname>commit_delay</varname>.
</para>
</listitem>
<listitem>
<para>
Improve performance of the <link
- linkend="SQL-CREATETABLE"><command>CREATE TEMPORARY TABLE ... ON
- COMMIT DELETE ROWS</></link> option by not truncating such temporary
+ linkend="sql-createtable"><command>CREATE TEMPORARY TABLE ... ON
+ COMMIT DELETE ROWS</command></link> option by not truncating such temporary
tables in transactions that haven't touched any temporary tables
(Heikki Linnakangas)
</para>
<para>
This speeds up lock bookkeeping at statement completion in
multi-statement transactions that hold many locks; it is particularly
- useful for <application>pg_dump</>.
+ useful for <application>pg_dump</application>.
</para>
</listitem>
<para>
This speeds up sessions that create many tables in successive
- small transactions, such as a <application>pg_restore</> run.
+ small transactions, such as a <application>pg_restore</application> run.
</para>
</listitem>
<para>
The checksum option can be set during <link
- linkend="APP-INITDB">initdb</link>.
+ linkend="app-initdb">initdb</link>.
</para>
</listitem>
<listitem>
<para>
When an authentication failure occurs, log the relevant
- <link linkend="auth-pg-hba-conf"><filename>pg_hba.conf</></link>
+ <link linkend="auth-pg-hba-conf"><filename>pg_hba.conf</filename></link>
line, to ease debugging of unintended failures
(Magnus Hagander)
</para>
<listitem>
<para>
- Improve <link linkend="auth-ldap"><acronym>LDAP</></link> error
+ Improve <link linkend="auth-ldap"><acronym>LDAP</acronym></link> error
reporting and documentation (Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
- Add support for specifying <acronym>LDAP</> authentication parameters
- in <acronym>URL</> format, per RFC 4516 (Peter Eisentraut)
+ Add support for specifying <acronym>LDAP</acronym> authentication parameters
+ in <acronym>URL</acronym> format, per RFC 4516 (Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
Change the <link
- linkend="guc-ssl-ciphers"><varname>ssl_ciphers</></link> parameter
- to start with <literal>DEFAULT</>, rather than <literal>ALL</>,
+ linkend="guc-ssl-ciphers"><varname>ssl_ciphers</varname></link> parameter
+ to start with <literal>DEFAULT</literal>, rather than <literal>ALL</literal>,
then remove insecure ciphers (Magnus Hagander)
</para>
<listitem>
<para>
Parse and load <link
- linkend="auth-username-maps"><filename>pg_ident.conf</></link>
+ linkend="auth-username-maps"><filename>pg_ident.conf</filename></link>
once, not during each connection (Amit Kapila)
</para>
<para>
- This is similar to how <filename>pg_hba.conf</> is processed.
+ This is similar to how <filename>pg_hba.conf</filename> is processed.
</para>
</listitem>
</para>
<para>
- On Unix-like systems, <function>mmap()</> is now used for most
- of <productname>PostgreSQL</>'s shared memory. For most users, this
+ On Unix-like systems, <function>mmap()</function> is now used for most
+ of <productname>PostgreSQL</productname>'s shared memory. For most users, this
will eliminate any need to adjust kernel parameters for shared memory.
</para>
</listitem>
<para>
The configuration parameter
- <varname>unix_socket_directory</> is replaced by <link
- linkend="guc-unix-socket-directories"><varname>unix_socket_directories</></link>,
+ <varname>unix_socket_directory</varname> is replaced by <link
+ linkend="guc-unix-socket-directories"><varname>unix_socket_directories</varname></link>,
which accepts a list of directories.
</para>
</listitem>
<para>
Such a directory is specified with <link
- linkend="config-includes"><varname>include_dir</></link> in the server
+ linkend="config-includes"><varname>include_dir</varname></link> in the server
configuration file.
</para>
</listitem>
<listitem>
<para>
Increase the maximum <link
- linkend="APP-INITDB">initdb</link>-configured value for <link
- linkend="guc-shared-buffers"><varname>shared_buffers</></link>
+ linkend="app-initdb">initdb</link>-configured value for <link
+ linkend="guc-shared-buffers"><varname>shared_buffers</varname></link>
to 128MB (Robert Haas)
</para>
<para>
This is the maximum value that initdb will attempt to set in <link
- linkend="config-setting-configuration-file"><filename>postgresql.conf</></link>;
+ linkend="config-setting-configuration-file"><filename>postgresql.conf</filename></link>;
the previous maximum was 32MB.
</para>
</listitem>
<listitem>
<para>
Remove the <link linkend="guc-external-pid-file">external
- <acronym>PID</> file</link>, if any, on postmaster exit
+ <acronym>PID</acronym> file</link>, if any, on postmaster exit
(Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
- Add <acronym>SQL</> functions <link
- linkend="functions-admin-backup"><function>pg_is_in_backup()</></link>
+ Add <acronym>SQL</acronym> functions <link
+ linkend="functions-admin-backup"><function>pg_is_in_backup()</function></link>
and <link
- linkend="functions-admin-backup"><function>pg_backup_start_time()</></link>
+ linkend="functions-admin-backup"><function>pg_backup_start_time()</function></link>
(Gilles Darold)
</para>
<listitem>
<para>
Improve performance of streaming log shipping with <link
- linkend="guc-synchronous-commit"><varname>synchronous_commit</></link>
+ linkend="guc-synchronous-commit"><varname>synchronous_commit</varname></link>
disabled (Andres Freund)
</para>
</listitem>
<listitem>
<para>
Add the last checkpoint's redo location to <link
- linkend="APP-PGCONTROLDATA"><application>pg_controldata</></link>'s
+ linkend="app-pgcontroldata"><application>pg_controldata</application></link>'s
output (Fujii Masao)
</para>
<para>
- This information is useful for determining which <acronym>WAL</>
+ This information is useful for determining which <acronym>WAL</acronym>
files are needed for restore.
</para>
</listitem>
<listitem>
<para>
Allow tools like <link
- linkend="app-pgreceivewal"><application>pg_receivexlog</></link>
+ linkend="app-pgreceivewal"><application>pg_receivexlog</application></link>
to run on computers with different architectures (Heikki
Linnakangas)
</para>
<listitem>
<para>
Make <link
- linkend="app-pgbasebackup"><application>pg_basebackup</></link>
- <option>--write-recovery-conf</> output a
- minimal <filename>recovery.conf</> file (Zoltán
+ linkend="app-pgbasebackup"><application>pg_basebackup</application></link>
+ <option>--write-recovery-conf</option> output a
+ minimal <filename>recovery.conf</filename> file (Zoltán
Böszörményi, Magnus Hagander)
</para>
<listitem>
<para>
Allow <link
- linkend="app-pgreceivewal"><application>pg_receivexlog</></link>
+ linkend="app-pgreceivewal"><application>pg_receivexlog</application></link>
and <link
- linkend="app-pgbasebackup"><application>pg_basebackup</></link>
- <option>--xlog-method</> to handle streaming timeline switches
+ linkend="app-pgbasebackup"><application>pg_basebackup</application></link>
+ <option>--xlog-method</option> to handle streaming timeline switches
(Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
Add <link
- linkend="guc-wal-receiver-timeout"><varname>wal_receiver_timeout</></link>
- parameter to control the <acronym>WAL</> receiver's timeout
+ linkend="guc-wal-receiver-timeout"><varname>wal_receiver_timeout</varname></link>
+ parameter to control the <acronym>WAL</acronym> receiver's timeout
(Amit Kapila)
</para>
<listitem>
<para>
- Change the <link linkend="wal"><acronym>WAL</></link> record format to
+ Change the <link linkend="wal"><acronym>WAL</acronym></link> record format to
allow splitting the record header across pages (Heikki Linnakangas)
</para>
<listitem>
<para>
- Implement <acronym>SQL</>-standard <link
- linkend="queries-lateral"><literal>LATERAL</></link> option for
- <literal>FROM</>-clause subqueries and function calls (Tom Lane)
+ Implement <acronym>SQL</acronym>-standard <link
+ linkend="queries-lateral"><literal>LATERAL</literal></link> option for
+ <literal>FROM</literal>-clause subqueries and function calls (Tom Lane)
</para>
<para>
- This feature allows subqueries and functions in <literal>FROM</> to
- reference columns from other tables in the <literal>FROM</>
- clause. The <literal>LATERAL</> keyword is optional for functions.
+ This feature allows subqueries and functions in <literal>FROM</literal> to
+ reference columns from other tables in the <literal>FROM</literal>
+ clause. The <literal>LATERAL</literal> keyword is optional for functions.
</para>
</listitem>
<listitem>
<para>
Add support for piping <link
- linkend="SQL-COPY"><command>COPY</></link> and <link
- linkend="APP-PSQL"><application>psql</></link> <command>\copy</>
+ linkend="sql-copy"><command>COPY</command></link> and <link
+ linkend="app-psql"><application>psql</application></link> <command>\copy</command>
data to/from an external program (Etsuro Fujita)
</para>
</listitem>
<listitem>
<para>
Allow a multirow <link
- linkend="SQL-VALUES"><literal>VALUES</></link> clause in a rule
- to reference <literal>OLD</>/<literal>NEW</> (Tom Lane)
+ linkend="sql-values"><literal>VALUES</literal></link> clause in a rule
+ to reference <literal>OLD</literal>/<literal>NEW</literal> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Allow <link linkend="SQL-CREATEFOREIGNDATAWRAPPER">foreign data
+ Allow <link linkend="sql-createforeigndatawrapper">foreign data
wrappers</link> to support writes (inserts/updates/deletes) on foreign
tables (KaiGai Kohei)
</para>
<listitem>
<para>
- Add <link linkend="SQL-CREATESCHEMA"><command>CREATE SCHEMA ... IF
- NOT EXISTS</></link> clause (Fabrízio de Royes Mello)
+ Add <link linkend="sql-createschema"><command>CREATE SCHEMA ... IF
+ NOT EXISTS</command></link> clause (Fabrízio de Royes Mello)
</para>
</listitem>
<listitem>
<para>
- Make <link linkend="SQL-REASSIGN-OWNED"><command>REASSIGN
- OWNED</></link> also change ownership of shared objects
+ Make <link linkend="sql-reassign-owned"><command>REASSIGN
+ OWNED</command></link> also change ownership of shared objects
(Álvaro Herrera)
</para>
</listitem>
<listitem>
<para>
Make <link linkend="sql-createaggregate"><command>CREATE
- AGGREGATE</></link> complain if the given initial value string is not
+ AGGREGATE</command></link> complain if the given initial value string is not
valid input for the transition datatype (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Suppress <link linkend="SQL-CREATETABLE"><command>CREATE
- TABLE</></link>'s messages about implicit index and sequence creation
+ Suppress <link linkend="sql-createtable"><command>CREATE
+ TABLE</command></link>'s messages about implicit index and sequence creation
(Robert Haas)
</para>
<para>
- These messages now appear at <literal>DEBUG1</> verbosity, so that
+ These messages now appear at <literal>DEBUG1</literal> verbosity, so that
they will not be shown by default.
</para>
</listitem>
<listitem>
<para>
- Allow <link linkend="SQL-DROPTABLE"><command>DROP TABLE IF
- EXISTS</></link> to succeed when a non-existent schema is specified
+ Allow <link linkend="sql-droptable"><command>DROP TABLE IF
+ EXISTS</command></link> to succeed when a non-existent schema is specified
in the table name (Bruce Momjian)
</para>
</itemizedlist>
<sect4>
- <title><command>ALTER</></title>
+ <title><command>ALTER</command></title>
<itemizedlist>
<listitem>
<para>
- Support <literal>IF NOT EXISTS</> option in <link
- linkend="SQL-ALTERTYPE"><command>ALTER TYPE ... ADD VALUE</></link>
+ Support <literal>IF NOT EXISTS</literal> option in <link
+ linkend="sql-altertype"><command>ALTER TYPE ... ADD VALUE</command></link>
(Andrew Dunstan)
</para>
<listitem>
<para>
- Add <link linkend="SQL-ALTERROLE"><command>ALTER ROLE ALL
- SET</></link> to establish settings for all users (Peter Eisentraut)
+ Add <link linkend="sql-alterrole"><command>ALTER ROLE ALL
+ SET</command></link> to establish settings for all users (Peter Eisentraut)
</para>
<para>
This allows settings to apply to all users in all databases. <link
- linkend="SQL-ALTERDATABASE"><command>ALTER DATABASE SET</></link>
+ linkend="sql-alterdatabase"><command>ALTER DATABASE SET</command></link>
already allowed addition of settings for all users in a single
- database. <filename>postgresql.conf</> has a similar effect.
+ database. <filename>postgresql.conf</filename> has a similar effect.
</para>
</listitem>
<listitem>
<para>
- Add support for <link linkend="SQL-ALTERRULE"><command>ALTER RULE
- ... RENAME</></link> (Ali Dar)
+ Add support for <link linkend="sql-alterrule"><command>ALTER RULE
+ ... RENAME</command></link> (Ali Dar)
</para>
</listitem>
</sect4>
<sect4>
- <title><link linkend="rules-views"><command>VIEWs</></link></title>
+ <title><link linkend="rules-views"><command>VIEWs</command></link></title>
<itemizedlist>
<listitem>
<para>
- Add <link linkend="SQL-CREATEMATERIALIZEDVIEW">materialized
+ Add <link linkend="sql-creatematerializedview">materialized
views</link> (Kevin Grittner)
</para>
<listitem>
<para>
Make simple views <link
- linkend="SQL-CREATEVIEW-updatable-views">auto-updatable</link>
+ linkend="sql-createview-updatable-views">auto-updatable</link>
(Dean Rasheed)
</para>
Simple views that reference some or all columns from a
single base table are now updatable by default. More
complex views can be made updatable using <link
- linkend="SQL-CREATETRIGGER"><literal>INSTEAD OF</></link> triggers
- or <link linkend="SQL-CREATERULE"><literal>INSTEAD</></link> rules.
+ linkend="sql-createtrigger"><literal>INSTEAD OF</literal></link> triggers
+ or <link linkend="sql-createrule"><literal>INSTEAD</literal></link> rules.
</para>
</listitem>
<listitem>
<para>
- Add <link linkend="SQL-CREATEVIEW"><command>CREATE RECURSIVE
- VIEW</></link> syntax (Peter Eisentraut)
+ Add <link linkend="sql-createview"><command>CREATE RECURSIVE
+ VIEW</command></link> syntax (Peter Eisentraut)
</para>
<para>
Internally this is translated into <command>CREATE VIEW ... WITH
- RECURSIVE ...</>.
+ RECURSIVE ...</command>.
</para>
</listitem>
<listitem>
<para>
- Increase the maximum size of <link linkend="largeObjects">large
+ Increase the maximum size of <link linkend="largeobjects">large
objects</link> from 2GB to 4TB (Nozomi Anzai, Yugo Nagata)
</para>
<listitem>
<para>
Allow text <link linkend="datatype-timezones">timezone
- designations</link>, e.g. <quote>America/Chicago</>, in the
- <quote>T</> field of <acronym>ISO</>-format <type>timestamptz</type>
+ designations</link>, e.g. <quote>America/Chicago</quote>, in the
+ <quote>T</quote> field of <acronym>ISO</acronym>-format <type>timestamptz</type>
input (Bruce Momjian)
</para>
</listitem>
</itemizedlist>
<sect4>
- <title><link linkend="datatype-json"><type>JSON</></link></title>
+ <title><link linkend="datatype-json"><type>JSON</type></link></title>
<itemizedlist>
<listitem>
<para>
Add <link linkend="functions-json">operators and functions</link>
- to extract elements from <type>JSON</> values (Andrew Dunstan)
+ to extract elements from <type>JSON</type> values (Andrew Dunstan)
</para>
</listitem>
<listitem>
<para>
- Allow <type>JSON</> values to be <link
+ Allow <type>JSON</type> values to be <link
linkend="functions-json">converted into records</link>
(Andrew Dunstan)
</para>
<listitem>
<para>
Add <link linkend="functions-json">functions</link> to convert
- scalars, records, and <type>hstore</> values to <type>JSON</> (Andrew
+ scalars, records, and <type>hstore</type> values to <type>JSON</type> (Andrew
Dunstan)
</para>
</listitem>
<listitem>
<para>
Add <link
- linkend="array-functions-table"><function>array_remove()</></link>
+ linkend="array-functions-table"><function>array_remove()</function></link>
and <link
- linkend="array-functions-table"><function>array_replace()</></link>
+ linkend="array-functions-table"><function>array_replace()</function></link>
functions (Marco Nenciarini, Gabriele Bartolini)
</para>
</listitem>
<listitem>
<para>
Allow <link
- linkend="functions-string-other"><function>concat()</></link>
+ linkend="functions-string-other"><function>concat()</function></link>
and <link
- linkend="functions-string-format"><function>format()</></link>
- to properly expand <literal>VARIADIC</>-labeled arguments
+ linkend="functions-string-format"><function>format()</function></link>
+ to properly expand <literal>VARIADIC</literal>-labeled arguments
(Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
Improve <link
- linkend="functions-string-format"><function>format()</></link>
+ linkend="functions-string-format"><function>format()</function></link>
to provide field width and left/right alignment options (Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
Make <link
- linkend="functions-formatting-table"><function>to_char()</></link>,
+ linkend="functions-formatting-table"><function>to_char()</function></link>,
<link
- linkend="functions-formatting-table"><function>to_date()</></link>,
+ linkend="functions-formatting-table"><function>to_date()</function></link>,
and <link
- linkend="functions-formatting-table"><function>to_timestamp()</></link>
+ linkend="functions-formatting-table"><function>to_timestamp()</function></link>
handle negative (BC) century values properly
(Bruce Momjian)
</para>
<para>
Previously the behavior was either wrong or inconsistent
- with positive/<acronym>AD</> handling, e.g. with the format mask
- <quote>IYYY-IW-DY</>.
+ with positive/<acronym>AD</acronym> handling, e.g. with the format mask
+ <quote>IYYY-IW-DY</quote>.
</para>
</listitem>
<listitem>
<para>
Make <link
- linkend="functions-formatting-table"><function>to_date()</></link>
+ linkend="functions-formatting-table"><function>to_date()</function></link>
and <link
- linkend="functions-formatting-table"><function>to_timestamp()</></link>
- return proper results when mixing <acronym>ISO</> and Gregorian
+ linkend="functions-formatting-table"><function>to_timestamp()</function></link>
+ return proper results when mixing <acronym>ISO</acronym> and Gregorian
week/day designations (Bruce Momjian)
</para>
</listitem>
<listitem>
<para>
Cause <link
- linkend="functions-info-catalog-table"><function>pg_get_viewdef()</></link>
- to start a new line by default after each <literal>SELECT</> target
- list entry and <literal>FROM</> entry (Marko Tiikkaja)
+ linkend="functions-info-catalog-table"><function>pg_get_viewdef()</function></link>
+ to start a new line by default after each <literal>SELECT</literal> target
+ list entry and <literal>FROM</literal> entry (Marko Tiikkaja)
</para>
<para>
This reduces line length in view printing, for instance in <link
- linkend="APP-PGDUMP"><application>pg_dump</></link> output.
+ linkend="app-pgdump"><application>pg_dump</application></link> output.
</para>
</listitem>
<listitem>
<para>
- Fix <function>map_sql_value_to_xml_value()</> to print values of
+ Fix <function>map_sql_value_to_xml_value()</function> to print values of
domain types the same way their base type would be printed
(Pavel Stehule)
</para>
<para>
There are special formatting rules for certain built-in types such as
- <type>boolean</>; these rules now also apply to domains over these
+ <type>boolean</type>; these rules now also apply to domains over these
types.
</para>
</listitem>
<listitem>
<para>
- Allow PL/pgSQL to use <literal>RETURN</> with a composite-type
+ Allow PL/pgSQL to use <literal>RETURN</literal> with a composite-type
expression (Asif Rehman)
</para>
<para>
Previously, in a function returning a composite type,
- <literal>RETURN</> could only reference a variable of that type.
+ <literal>RETURN</literal> could only reference a variable of that type.
</para>
</listitem>
<listitem>
<para>
Allow PL/pgSQL to access the number of rows processed by
- <link linkend="SQL-COPY"><command>COPY</></link> (Pavel Stehule)
+ <link linkend="sql-copy"><command>COPY</command></link> (Pavel Stehule)
</para>
<para>
- A <command>COPY</> executed in a PL/pgSQL function now updates the
+ A <command>COPY</command> executed in a PL/pgSQL function now updates the
value retrieved by <link
linkend="plpgsql-statements-diagnostics"><command>GET DIAGNOSTICS
- x = ROW_COUNT</></link>.
+ x = ROW_COUNT</command></link>.
</para>
</listitem>
<listitem>
<para>
- Handle <link linkend="spi"><acronym>SPI</></link> errors raised
- explicitly (with PL/Python's <literal>RAISE</>) the same as
- internal <acronym>SPI</> errors (Oskari Saarenmaa and Jan Urbanski)
+ Handle <link linkend="spi"><acronym>SPI</acronym></link> errors raised
+ explicitly (with PL/Python's <literal>RAISE</literal>) the same as
+ internal <acronym>SPI</acronym> errors (Oskari Saarenmaa and Jan Urbanski)
</para>
</listitem>
<listitem>
<para>
- Prevent leakage of <acronym>SPI</> tuple tables during subtransaction
+ Prevent leakage of <acronym>SPI</acronym> tuple tables during subtransaction
abort (Tom Lane)
</para>
of such tuple tables and release them manually in error-recovery code.
Failure to do so caused a number of transaction-lifespan memory leakage
issues in PL/pgSQL and perhaps other SPI clients. <link
- linkend="spi-spi-freetupletable"><function>SPI_freetuptable()</></link>
+ linkend="spi-spi-freetupletable"><function>SPI_freetuptable()</function></link>
now protects itself against multiple freeing requests, so any existing
code that did take care to clean up shouldn't be broken by this change.
</para>
<listitem>
<para>
- Allow <acronym>SPI</> functions to access the number of rows processed
- by <link linkend="SQL-COPY"><command>COPY</></link> (Pavel Stehule)
+ Allow <acronym>SPI</acronym> functions to access the number of rows processed
+ by <link linkend="sql-copy"><command>COPY</command></link> (Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
Add command-line utility <link
- linkend="app-pg-isready"><application>pg_isready</></link> to
+ linkend="app-pg-isready"><application>pg_isready</application></link> to
check if the server is ready to accept connections (Phil Sorber)
</para>
</listitem>
<listitem>
<para>
- Support multiple <option>--table</> arguments for <link
- linkend="APP-PGRESTORE"><application>pg_restore</></link>,
- <link linkend="APP-CLUSTERDB"><application>clusterdb</></link>,
- <link linkend="APP-REINDEXDB"><application>reindexdb</></link>,
- and <link linkend="APP-VACUUMDB"><application>vacuumdb</></link>
+ Support multiple <option>--table</option> arguments for <link
+ linkend="app-pgrestore"><application>pg_restore</application></link>,
+ <link linkend="app-clusterdb"><application>clusterdb</application></link>,
+ <link linkend="app-reindexdb"><application>reindexdb</application></link>,
+ and <link linkend="app-vacuumdb"><application>vacuumdb</application></link>
(Josh Kupershmidt)
</para>
<para>
This is similar to the way <link
- linkend="APP-PGDUMP"><application>pg_dump</></link>'s
- <option>--table</> option works.
+ linkend="app-pgdump"><application>pg_dump</application></link>'s
+ <option>--table</option> option works.
</para>
</listitem>
<listitem>
<para>
- Add <option>--dbname</> option to <link
- linkend="APP-PG-DUMPALL"><application>pg_dumpall</></link>, <link
- linkend="app-pgbasebackup"><application>pg_basebackup</></link>, and
+ Add <option>--dbname</option> option to <link
+ linkend="app-pg-dumpall"><application>pg_dumpall</application></link>, <link
+ linkend="app-pgbasebackup"><application>pg_basebackup</application></link>, and
<link
- linkend="app-pgreceivewal"><application>pg_receivexlog</></link>
+ linkend="app-pgreceivewal"><application>pg_receivexlog</application></link>
to allow specifying a connection string (Amit Kapila)
</para>
</listitem>
<listitem>
<para>
Add libpq function <link
- linkend="libpq-pqconninfo"><function>PQconninfo()</></link>
+ linkend="libpq-pqconninfo"><function>PQconninfo()</function></link>
to return connection information (Zoltán
Böszörményi, Magnus Hagander)
</para>
</itemizedlist>
<sect4>
- <title><link linkend="APP-PSQL"><application>psql</></link></title>
+ <title><link linkend="app-psql"><application>psql</application></link></title>
<itemizedlist>
<listitem>
<para>
- Adjust function cost settings so <application>psql</> tab
+ Adjust function cost settings so <application>psql</application> tab
completion and pattern searching are more efficient (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Improve <application>psql</>'s tab completion coverage (Jeff Janes,
+ Improve <application>psql</application>'s tab completion coverage (Jeff Janes,
Dean Rasheed, Peter Eisentraut, Magnus Hagander)
</para>
</listitem>
<listitem>
<para>
- Allow the <application>psql</> <option>--single-transaction</>
+ Allow the <application>psql</application> <option>--single-transaction</option>
mode to work when reading from standard input (Fabien Coelho,
Robert Haas)
</para>
<listitem>
<para>
- Remove <application>psql</> warning when connecting to an older
+ Remove <application>psql</application> warning when connecting to an older
server (Peter Eisentraut)
</para>
<para>
A warning is still issued when connecting to a server of a newer major
- version than <application>psql</>'s.
+ version than <application>psql</application>'s.
</para>
</listitem>
</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>
- Add <application>psql</> command <command>\watch</> to repeatedly
+ Add <application>psql</application> command <command>\watch</command> to repeatedly
execute a SQL command (Will Leinweber)
</para>
</listitem>
<listitem>
<para>
- Add <application>psql</> command <command>\gset</> to store query
- results in <application>psql</> variables (Pavel Stehule)
+ Add <application>psql</application> command <command>\gset</command> to store query
+ results in <application>psql</application> variables (Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
- Add <acronym>SSL</> information to <application>psql</>'s
- <command>\conninfo</> command (Alastair Turner)
+ Add <acronym>SSL</acronym> information to <application>psql</application>'s
+ <command>\conninfo</command> command (Alastair Turner)
</para>
</listitem>
<listitem>
<para>
- Add <quote>Security</> column to <application>psql</>'s
- <command>\df+</> output (Jon Erdman)
+ Add <quote>Security</quote> column to <application>psql</application>'s
+ <command>\df+</command> output (Jon Erdman)
</para>
</listitem>
<listitem>
<para>
- Allow <application>psql</> command <command>\l</> to accept a database
+ Allow <application>psql</application> command <command>\l</command> to accept a database
name pattern (Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
- In <application>psql</>, do not allow <command>\connect</> to
+ In <application>psql</application>, do not allow <command>\connect</command> to
use defaults if there is no active connection (Bruce Momjian)
</para>
<listitem>
<para>
Properly reset state after failure of a SQL command executed with
- <application>psql</>'s <literal>\g</> <replaceable>file</>
+ <application>psql</application>'s <literal>\g</literal> <replaceable>file</replaceable>
(Tom Lane)
</para>
<listitem>
<para>
- Add a <literal>latex-longtable</> output format to
- <application>psql</> (Bruce Momjian)
+ Add a <literal>latex-longtable</literal> output format to
+ <application>psql</application> (Bruce Momjian)
</para>
<para>
<listitem>
<para>
- Add a <literal>border=3</> output mode to the <application>psql</>
- <literal>latex</> format (Bruce Momjian)
+ Add a <literal>border=3</literal> output mode to the <application>psql</application>
+ <literal>latex</literal> format (Bruce Momjian)
</para>
</listitem>
<listitem>
<para>
- In <application>psql</>'s tuples-only and expanded output modes, no
- longer emit <quote>(No rows)</> for zero rows (Peter Eisentraut)
+ In <application>psql</application>'s tuples-only and expanded output modes, no
+ longer emit <quote>(No rows)</quote> for zero rows (Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
- In <application>psql</>'s unaligned, expanded output mode, no longer
+ In <application>psql</application>'s unaligned, expanded output mode, no longer
print an empty line for zero rows (Peter Eisentraut)
</para>
</listitem>
</sect4>
<sect4>
- <title><link linkend="APP-PGDUMP"><application>pg_dump</></link></title>
+ <title><link linkend="app-pgdump"><application>pg_dump</application></link></title>
<itemizedlist>
<listitem>
<para>
- Add <application>pg_dump</> <option>--jobs</> option to dump tables in
+ Add <application>pg_dump</application> <option>--jobs</option> option to dump tables in
parallel (Joachim Wieland)
</para>
</listitem>
<listitem>
<para>
- Make <application>pg_dump</> output functions in a more predictable
+ Make <application>pg_dump</application> output functions in a more predictable
order (Joel Jacobson)
</para>
</listitem>
<listitem>
<para>
- Fix tar files emitted by <application>pg_dump</>
- to be <acronym>POSIX</> conformant (Brian Weaver, Tom Lane)
+ Fix tar files emitted by <application>pg_dump</application>
+ to be <acronym>POSIX</acronym> conformant (Brian Weaver, Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Add <option>--dbname</> option to <application>pg_dump</>, for
+ Add <option>--dbname</option> option to <application>pg_dump</application>, for
consistency with other client commands (Heikki Linnakangas)
</para>
</sect4>
<sect4>
- <title><link linkend="APP-INITDB"><application>initdb</></link></title>
+ <title><link linkend="app-initdb"><application>initdb</application></link></title>
<itemizedlist>
projects / postgresql.git / commitdiff