diff --git a/doc/src/sgml/release-10.sgml b/doc/src/sgml/release-10.sgml
index 64c141256ae..6c07157d294 100644
--- a/doc/src/sgml/release-10.sgml
+++ b/doc/src/sgml/release-10.sgml
@@ -1,6 +1,642 @@
+
+ Release 10.1
+
+
+ Release date:
+ 2017-11-09
+
+
+
+ This release contains a variety of fixes from 10.0.
+ For information about new features in major release 10, see
+ .
+
+
+
+ Migration to Version 10.1
+
+
+ A dump/restore is not required for those running 10.X.
+
+
+
+ However, if you use BRIN indexes, see the first changelog entry below.
+
+
+
+
+ Changes
+
+
+
+
+
+
+ Fix BRIN index summarization to handle concurrent table extension
+ correctly (Álvaro Herrera)
+
+
+
+ Previously, a race condition allowed some table rows to be omitted from
+ the index. It may be necessary to reindex existing BRIN indexes to
+ recover from past occurrences of this problem.
+
+
+
+
+
+
+ Fix possible failures during concurrent updates of a BRIN index
+ (Tom Lane)
+
+
+
+ These race conditions could result in errors like invalid index
+ offnum or inconsistent range map.
+
+
+
+
+
+
+ Prevent logical replication from setting non-replicated columns to
+ nulls when replicating an UPDATE (Petr Jelinek)
+
+
+
+
+
+
+ Fix logical replication to fire BEFORE ROW DELETE
+ triggers when expected (Masahiko Sawada)
+
+
+
+ Previously, that failed to happen unless the table also had
+ a BEFORE ROW UPDATE trigger.
+
+
+
+
+
+
+ Fix crash when logical decoding is invoked from a SPI-using function,
+ in particular any function written in a PL language
+ (Tom Lane)
+
+
+
+
+
+
+ Ignore CTEs when looking up the target table for
+ INSERT/UPDATE/DELETE,
+ and prevent matching schema-qualified target table names to trigger
+ transition table names (Thomas Munro)
+
+
+
+ This restores the pre-v10 behavior for CTEs attached to DML commands.
+
+
+
+
+
+
+ Avoid evaluating an aggregate function's argument expression(s) at rows
+ where its FILTER test fails (Tom Lane)
+
+
+
+ This restores the pre-v10 (and SQL-standard) behavior.
+
+
+
+
+
+
+ Fix incorrect query results when multiple GROUPING
+ SETS columns contain the same simple variable (Tom Lane)
+
+
+
+
+
+
+ Fix query-lifespan memory leakage while evaluating a set-returning
+ function in a SELECT's target list (Tom Lane)
+
+
+
+
+
+
+ Allow parallel execution of prepared statements with generic plans
+ (Amit Kapila, Kuntal Ghosh)
+
+
+
+
+
+
+ Fix incorrect parallelization decisions for nested queries
+ (Amit Kapila, Kuntal Ghosh)
+
+
+
+
+
+
+ Fix parallel query handling to not fail when a recently-used role is
+ dropped (Amit Kapila)
+
+
+
+
+
+
+ Fix crash in parallel execution of a bitmap scan having a BitmapAnd
+ plan node below a BitmapOr node (Dilip Kumar)
+
+
+
+
+
+
+ Fix json_build_array(),
+ json_build_object(), and their jsonb
+ equivalents to handle explicit VARIADIC arguments
+ correctly (Michael Paquier)
+
+
+
+
+
+
+ Fix autovacuum's work item logic to prevent possible
+ crashes and silent loss of work items (Álvaro Herrera)
+
+
+
+
+
+
+ Fix corner-case crashes when columns have been added to the end of a
+ view (Tom Lane)
+
+
+
+
+
+
+ Record proper dependencies when a view or rule
+ contains FieldSelect
+ or FieldStore expression nodes (Tom Lane)
+
+
+
+ Lack of these dependencies could allow a column or data
+ type DROP 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.
+
+
+
+
+
+
+ Correctly detect hashability of range data types (Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+
+ Correctly ignore RelabelType expression nodes
+ when examining functional-dependency statistics (David Rowley)
+
+
+
+ This allows, e.g., extended statistics on varchar columns
+ to be used properly.
+
+
+
+
+
+
+ Prevent sharing transition states between ordered-set aggregates
+ (David Rowley)
+
+
+
+ This causes a crash with the built-in ordered-set aggregates, and
+ probably with user-written ones as well. v11 and later will include
+ provisions for dealing with such cases safely, but in released
+ branches, just disable the optimization.
+
+
+
+
+
+
+ Prevent idle_in_transaction_session_timeout from
+ being ignored when a statement_timeout occurred
+ earlier (Lukas Fittl)
+
+
+
+
+
+
+ Fix low-probability loss of NOTIFY messages due to
+ XID wraparound (Marko Tiikkaja, Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+
+ Reduce the frequency of data flush requests during bulk file copies to
+ avoid performance problems on macOS, particularly with its new APFS
+ file system (Tom Lane)
+
+
+
+
+
+
+ Allow COPY's FREEZE option to
+ work when the transaction isolation level is REPEATABLE
+ READ or higher (Noah Misch)
+
+
+
+ This case was unintentionally broken by a previous bug fix.
+
+
+
+
+
+
+ Fix AggGetAggref() to return the
+ correct Aggref nodes to aggregate final
+ functions whose transition calculations have been merged (Tom Lane)
+
+
+
+
+
+
+ Fix insufficient schema-qualification in some new queries
+ in pg_dump
+ and psql
+ (Vitaly Burovoy, Tom Lane, Noah Misch)
+
+
+
+
+
+
+ Avoid use of @> operator
+ in psql's queries for \d
+ (Tom Lane)
+
+
+
+ This prevents problems when the parray_gin
+ extension is installed, since that defines a conflicting operator.
+
+
+
+
+
+
+ Fix pg_basebackup's matching of tablespace
+ paths to canonicalize both paths before comparing (Michael Paquier)
+
+
+
+ This is particularly helpful on Windows.
+
+
+
+
+
+
+ Fix libpq to not require user's home
+ directory to exist (Tom Lane)
+
+
+
+ In v10, failure to find the home directory while trying to
+ read ~/.pgpass 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 ~/.pg_service.conf, though this was less
+ obvious since that file is not sought unless a service name is
+ specified.
+
+
+
+
+
+
+ In ecpglib, correctly handle backslashes in string literals depending
+ on whether standard_conforming_strings is set
+ (Tsunakawa Takayuki)
+
+
+
+
+
+
+ Make ecpglib's Informix-compatibility mode ignore fractional digits in
+ integer input strings, as expected (Gao Zengqi, Michael Meskes)
+
+
+
+
+
+
+ Update time zone data files to tzdata
+ 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.
+
+
+
+
+
+
+ In the documentation, restore HTML anchors to being upper-case strings
+ (Peter Eisentraut)
+
+
+
+ Due to a toolchain change, the 10.0 user manual had lower-case strings
+ for intrapage anchors, thus breaking some external links into our
+ website documentation. Return to our previous convention of using
+ upper-case strings.
+
+
+
+
+
+
+
+
Release 10
@@ -727,7 +1363,7 @@
- A new CREATE
+ A new CREATE
INDEX option enables auto-summarization of the
previous BRIN page range when a new page
range is created.
@@ -851,9 +1487,9 @@
New commands are CREATE STATISTICS,
- ALTER STATISTICS, and
- DROP STATISTICS.
+ linkend="sql-createstatistics">CREATE STATISTICS,
+ ALTER STATISTICS, and
+ DROP STATISTICS.
This feature is helpful in estimating query memory usage and when
combining the statistics from individual columns.
@@ -976,7 +1612,7 @@
-->
Allow explicit control
- over EXPLAIN's display
+ over EXPLAIN's display
of planning and execution time (Ashutosh Bapat)
@@ -1009,7 +1645,7 @@
-->
Properly update the statistics collector during REFRESH MATERIALIZED
+ linkend="sql-refreshmaterializedview">REFRESH MATERIALIZED
VIEW (Jim Mlodgenski)
@@ -1592,7 +2228,7 @@
2016-12-07 [f0e44751d] Implement table partitioning.
-->
- Add table partitioning
+ Add table partitioning
syntax that automatically creates partition constraints and
handles routing of tuple insertions and updates (Amit Langote)
@@ -1609,7 +2245,7 @@
2017-03-31 [597027163] Add transition table support to plpgsql.
-->
- Add AFTER trigger
+ Add AFTER trigger
transition tables to record changed rows (Kevin Grittner, Thomas
Munro)
@@ -1625,7 +2261,7 @@
2016-12-05 [093129c9d] Add support for restrictive RLS policies
-->
- Allow restrictive row-level
+ Allow restrictive row-level
security policies (Stephen Frost)
@@ -1661,7 +2297,7 @@
2017-03-28 [ab89e465c] Altering default privileges on schemas
-->
- Allow default
+ Allow default
permissions on schemas (Matheus Oliveira)
@@ -1675,7 +2311,7 @@
2017-02-10 [2ea5b06c7] Add CREATE SEQUENCE AS clause
-->
- Add CREATE SEQUENCE
+ Add CREATE SEQUENCE
AS command to create a sequence matching an integer data type
(Peter Eisentraut)
@@ -1711,7 +2347,7 @@
- For example, allow DROP
+ For example, allow DROP
FUNCTION on a function name without arguments if there
is only one function with that name. This behavior is required by the
SQL standard.
@@ -1735,9 +2371,9 @@
-->
Support IF NOT EXISTS
- in CREATE SERVER,
- CREATE USER MAPPING,
- and CREATE COLLATION
+ in CREATE SERVER,
+ CREATE USER MAPPING,
+ and CREATE COLLATION
(Anastasia Lubennikova, Peter Eisentraut)
@@ -1748,7 +2384,7 @@
2017-03-03 [9eb344faf] Allow vacuums to report oldestxmin
-->
- Make VACUUM VERBOSE report
+ Make VACUUM VERBOSE report
the number of skipped frozen pages and oldest xmin (Masahiko
Sawada, Simon Riggs)
@@ -1815,7 +2451,7 @@
2017-04-06 [321732705] Identity columns
-->
- Add identity columns for
+ Add identity columns for
assigning a numeric value to columns on insert (Peter Eisentraut)
@@ -1835,7 +2471,7 @@
- This uses the syntax ALTER
+ This uses the syntax ALTER
TYPE ... RENAME VALUE.
@@ -2197,7 +2833,7 @@
Client Applications
- <xref linkend="APP-PSQL">
+ <xref linkend="app-psql">
@@ -2420,7 +3056,7 @@
2016-10-19 [5d58c07a4] initdb pg_basebackup: Rename -\-noxxx options to -\-no-x
-->
- Rename initdb
+ Rename initdb
options and to be spelled
and (Vik Fearing,
Peter Eisentraut)
@@ -2434,9 +3070,9 @@
- <link linkend="APP-PGDUMP"><application>pg_dump</application></link>,
- <link linkend="APP-PG-DUMPALL"><application>pg_dumpall</application></link>,
- <link linkend="APP-PGRESTORE"><application>pg_restore</application></link>
+ <link linkend="app-pgdump"><application>pg_dump</application></link>,
+ <link linkend="app-pg-dumpall"><application>pg_dumpall</application></link>,
+ <link linkend="app-pgrestore"><application>pg_restore</application></link>
diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml
index c1c864b237d..2f5f054c4e9 100644
--- a/doc/src/sgml/release-9.2.sgml
+++ b/doc/src/sgml/release-9.2.sgml
@@ -1,6 +1,182 @@
+
+ Release 9.2.24
+
+
+ Release date:
+ 2017-11-09
+
+
+
+ This release contains a variety of fixes from 9.2.23.
+ For information about new features in the 9.2 major release, see
+ .
+
+
+
+ This is expected to be the last PostgreSQL
+ release in the 9.2.X series. Users are encouraged to update to a newer
+ release branch soon.
+
+
+
+ Migration to Version 9.2.24
+
+
+ A dump/restore is not required for those running 9.2.X.
+
+
+
+ However, if you are upgrading from a version earlier than 9.2.22,
+ see .
+
+
+
+
+
+ Changes
+
+
+
+
+
+ Properly reject attempts to convert infinite float values to
+ type numeric (Tom Lane, KaiGai Kohei)
+
+
+
+ Previously the behavior was platform-dependent.
+
+
+
+
+
+ Fix corner-case crashes when columns have been added to the end of a
+ view (Tom Lane)
+
+
+
+
+
+ Record proper dependencies when a view or rule
+ contains FieldSelect
+ or FieldStore expression nodes (Tom Lane)
+
+
+
+ Lack of these dependencies could allow a column or data
+ type DROP 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.
+
+
+
+
+
+ Correctly detect hashability of range data types (Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+ Fix low-probability loss of NOTIFY messages due to
+ XID wraparound (Marko Tiikkaja, Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+ Prevent low-probability crash in processing of nested trigger firings
+ (Tom Lane)
+
+
+
+
+
+ Correctly restore the umask setting when file creation fails
+ in COPY or lo_export()
+ (Peter Eisentraut)
+
+
+
+
+
+ Give a better error message for duplicate column names
+ in ANALYZE (Nathan Bossart)
+
+
+
+
+
+ Fix libpq to not require user's home
+ directory to exist (Tom Lane)
+
+
+
+ In v10, failure to find the home directory while trying to
+ read ~/.pgpass 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 ~/.pg_service.conf, though this was less
+ obvious since that file is not sought unless a service name is
+ specified.
+
+
+
+
+
+ Fix libpq to guard against integer
+ overflow in the row count of a PGresult
+ (Michael Paquier)
+
+
+
+
+
+ Sync our copy of the timezone library with IANA release tzcode2017c
+ (Tom Lane)
+
+
+
+ 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 posixrules file exists in the timezone data
+ directory, now match current US law rather than what it was a dozen
+ years ago.
+
+
+
+
+
+ Update time zone data files to tzdata
+ 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.
+
+
+
+
+
+
+
+
Release 9.2.23
@@ -16,7 +192,7 @@
- The PostgreSQL community will stop releasing updates
+ The PostgreSQL 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.
@@ -43,20 +219,20 @@
Show foreign tables
- in information_schema.table_privileges
+ in information_schema.table_privileges
view (Peter Eisentraut)
- All other relevant information_schema views include
+ All other relevant information_schema views include
foreign tables, but this one ignored them.
- Since this view definition is installed by initdb,
+ Since this view definition is installed by initdb,
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 psql:
+ in psql:
SET search_path TO information_schema;
CREATE OR REPLACE VIEW table_privileges AS
@@ -95,21 +271,21 @@ CREATE OR REPLACE VIEW table_privileges AS
OR grantee.rolname = 'PUBLIC');
This must be repeated in each database to be fixed,
- including template0.
+ including template0.
Clean up handling of a fatal exit (e.g., due to receipt
- of SIGTERM) that occurs while trying to execute
- a ROLLBACK of a failed transaction (Tom Lane)
+ of SIGTERM) that occurs while trying to execute
+ a ROLLBACK of a failed transaction (Tom Lane)
This situation could result in an assertion failure. In production
builds, the exit would still occur, but it would log an unexpected
- message about cannot drop active portal.
+ message about cannot drop active portal.
@@ -126,7 +302,7 @@ CREATE OR REPLACE VIEW table_privileges AS
- Certain ALTER commands that change the definition of a
+ Certain ALTER 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,
@@ -138,13 +314,13 @@ CREATE OR REPLACE VIEW table_privileges AS
- Change ecpg's parser to allow RETURNING
+ Change ecpg's parser to allow RETURNING
clauses without attached C variables (Michael Meskes)
- This allows ecpg programs to contain SQL constructs
- that use RETURNING internally (for example, inside a CTE)
+ This allows ecpg programs to contain SQL constructs
+ that use RETURNING internally (for example, inside a CTE)
rather than using it to define values to be returned to the client.
@@ -156,12 +332,12 @@ CREATE OR REPLACE VIEW table_privileges AS
This fix avoids possible crashes of PL/Perl due to inconsistent
- assumptions about the width of time_t values.
+ assumptions about the width of time_t values.
A side-effect that may be visible to extension developers is
- that _USE_32BIT_TIME_T is no longer defined globally
- in PostgreSQL Windows builds. This is not expected
- to cause problems, because type time_t is not used
- in any PostgreSQL API definitions.
+ that _USE_32BIT_TIME_T is no longer defined globally
+ in PostgreSQL Windows builds. This is not expected
+ to cause problems, because type time_t is not used
+ in any PostgreSQL API definitions.
@@ -185,7 +361,7 @@ CREATE OR REPLACE VIEW table_privileges AS
- The PostgreSQL community will stop releasing updates
+ The PostgreSQL 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.
@@ -217,7 +393,7 @@ CREATE OR REPLACE VIEW table_privileges AS
Further restrict visibility
- of pg_user_mappings.umoptions, to
+ of pg_user_mappings.umoptions, to
protect passwords stored as user mapping options
(Noah Misch)
@@ -225,11 +401,11 @@ CREATE OR REPLACE VIEW table_privileges AS
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 USAGE permission on the associated foreign server.
+ have USAGE 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 information_schema.user_mapping_options does not
- show the options in such cases, pg_user_mappings
+ Since information_schema.user_mapping_options does not
+ show the options in such cases, pg_user_mappings
should not either.
(CVE-2017-7547)
@@ -244,15 +420,15 @@ CREATE OR REPLACE VIEW table_privileges AS
Restart the postmaster after adding allow_system_table_mods
- = true to postgresql.conf. (In versions
- supporting ALTER SYSTEM, you can use that to make the
+ = true to postgresql.conf. (In versions
+ supporting ALTER SYSTEM, you can use that to make the
configuration change, but you'll still need a restart.)
- In each database of the cluster,
+ In each database of the cluster,
run the following commands as superuser:
SET search_path = pg_catalog;
@@ -283,15 +459,15 @@ CREATE OR REPLACE VIEW pg_user_mappings AS
- Do not forget to include the template0
- and template1 databases, or the vulnerability will still
- exist in databases you create later. To fix template0,
+ Do not forget to include the template0
+ and template1 databases, or the vulnerability will still
+ exist in databases you create later. To fix template0,
you'll need to temporarily make it accept connections.
- In PostgreSQL 9.5 and later, you can use
+ In PostgreSQL 9.5 and later, you can use
ALTER DATABASE template0 WITH ALLOW_CONNECTIONS true;
- and then after fixing template0, undo that with
+ and then after fixing template0, undo that with
ALTER DATABASE template0 WITH ALLOW_CONNECTIONS false;
@@ -305,7 +481,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Finally, remove the allow_system_table_mods configuration
+ Finally, remove the allow_system_table_mods configuration
setting, and again restart the postmaster.
@@ -319,16 +495,16 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- libpq ignores empty password specifications, and does
+ libpq 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 psql or other libpq-based
+ via psql or other libpq-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-libpq-based client,
+ However, with a modified or non-libpq-based client,
logging in could be possible, depending on which authentication
method is configured. In particular the most common
- method, md5, accepted empty passwords.
+ method, md5, accepted empty passwords.
Change the server to reject empty passwords in all cases.
(CVE-2017-7546)
@@ -406,28 +582,28 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Fix possible creation of an invalid WAL segment when a standby is
- promoted just after it processes an XLOG_SWITCH WAL
+ promoted just after it processes an XLOG_SWITCH WAL
record (Andres Freund)
- Fix SIGHUP and SIGUSR1 handling in
+ Fix SIGHUP and SIGUSR1 handling in
walsender processes (Petr Jelinek, Andres Freund)
- Fix unnecessarily slow restarts of walreceiver
+ Fix unnecessarily slow restarts of walreceiver
processes due to race condition in postmaster (Tom Lane)
- Fix cases where an INSERT or UPDATE assigns
+ Fix cases where an INSERT or UPDATE assigns
to more than one element of a column that is of domain-over-array
type (Tom Lane)
@@ -436,56 +612,56 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Move autogenerated array types out of the way during
- ALTER ... RENAME (Vik Fearing)
+ ALTER ... RENAME (Vik Fearing)
Previously, we would rename a conflicting autogenerated array type
- out of the way during CREATE; this fix extends that
+ out of the way during CREATE; this fix extends that
behavior to renaming operations.
- Ensure that ALTER USER ... SET accepts all the syntax
- variants that ALTER ROLE ... SET does (Peter Eisentraut)
+ Ensure that ALTER USER ... SET accepts all the syntax
+ variants that ALTER ROLE ... SET does (Peter Eisentraut)
Properly update dependency info when changing a datatype I/O
- function's argument or return type from opaque to the
+ function's argument or return type from opaque to the
correct type (Heikki Linnakangas)
- CREATE TYPE updates I/O functions declared in this
+ CREATE TYPE updates I/O functions declared in this
long-obsolete style, but it forgot to record a dependency on the
- type, allowing a subsequent DROP TYPE to leave broken
+ type, allowing a subsequent DROP TYPE to leave broken
function definitions behind.
- Reduce memory usage when ANALYZE processes
- a tsvector column (Heikki Linnakangas)
+ Reduce memory usage when ANALYZE processes
+ a tsvector column (Heikki Linnakangas)
Fix unnecessary precision loss and sloppy rounding when multiplying
- or dividing money values by integers or floats (Tom Lane)
+ or dividing money values by integers or floats (Tom Lane)
Tighten checks for whitespace in functions that parse identifiers,
- such as regprocedurein() (Tom Lane)
+ such as regprocedurein() (Tom Lane)
@@ -496,22 +672,22 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Use relevant #define symbols from Perl while
- compiling PL/Perl (Ashutosh Sharma, Tom Lane)
+ Use relevant #define symbols from Perl while
+ compiling PL/Perl (Ashutosh Sharma, Tom Lane)
This avoids portability problems, typically manifesting as
- a handshake mismatch during library load, when working with
+ a handshake mismatch during library load, when working with
recent Perl versions.
- In psql, fix failure when COPY FROM STDIN
+ In psql, fix failure when COPY FROM STDIN
is ended with a keyboard EOF signal and then another COPY
- FROM STDIN is attempted (Thomas Munro)
+ FROM STDIN is attempted (Thomas Munro)
@@ -522,14 +698,14 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_dump to not emit invalid SQL for an empty
+ Fix pg_dump to not emit invalid SQL for an empty
operator class (Daniel Gustafsson)
- Fix pg_dump output to stdout on Windows (Kuntal Ghosh)
+ Fix pg_dump output to stdout on Windows (Kuntal Ghosh)
@@ -540,21 +716,21 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_get_ruledef() to print correct output for
- the ON SELECT rule of a view whose columns have been
+ Fix pg_get_ruledef() to print correct output for
+ the ON SELECT rule of a view whose columns have been
renamed (Tom Lane)
- In some corner cases, pg_dump relies
- on pg_get_ruledef() to dump views, so that this error
+ In some corner cases, pg_dump relies
+ on pg_get_ruledef() to dump views, so that this error
could result in dump/reload failures.
- Fix dumping of function expressions in the FROM clause in
+ Fix dumping of function expressions in the FROM clause in
cases where the expression does not deparse into something that looks
like a function call (Tom Lane)
@@ -562,7 +738,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_basebackup output to stdout on Windows
+ Fix pg_basebackup output to stdout on Windows
(Haribabu Kommi)
@@ -574,8 +750,8 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_upgrade to ensure that the ending WAL record
- does not have = minimum
+ Fix pg_upgrade to ensure that the ending WAL record
+ does not have = minimum
(Bruce Momjian)
@@ -587,7 +763,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Always use , not , when building
shared libraries with gcc (Tom Lane)
@@ -607,27 +783,27 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- In MSVC builds, handle the case where the openssl
- library is not within a VC subdirectory (Andrew Dunstan)
+ In MSVC builds, handle the case where the openssl
+ library is not within a VC subdirectory (Andrew Dunstan)
- In MSVC builds, add proper include path for libxml2
+ In MSVC builds, add proper include path for libxml2
header files (Andrew Dunstan)
This fixes a former need to move things around in standard Windows
- installations of libxml2.
+ installations of libxml2.
In MSVC builds, recognize a Tcl library that is
- named tcl86.lib (Noah Misch)
+ named tcl86.lib (Noah Misch)
@@ -651,7 +827,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- The PostgreSQL community will stop releasing updates
+ The PostgreSQL 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.
@@ -683,18 +859,18 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Restrict visibility
- of pg_user_mappings.umoptions, to
+ of pg_user_mappings.umoptions, to
protect passwords stored as user mapping options
(Michael Paquier, Feike Steenbergen)
The previous coding allowed the owner of a foreign server object,
- or anyone he has granted server USAGE permission to,
+ or anyone he has granted server USAGE 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
- information_schema.user_mapping_options, namely that
+ information_schema.user_mapping_options, namely that
these options are visible to the user being mapped, or if the mapping
is for PUBLIC and the current user is the server
owner, or if the current user is a superuser.
@@ -718,7 +894,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Some selectivity estimation functions in the planner will apply
user-defined operators to values obtained
- from pg_statistic, such as most common values and
+ from pg_statistic, 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,
@@ -732,7 +908,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix possible corruption of init forks of unlogged indexes
+ Fix possible corruption of init forks of unlogged indexes
(Robert Haas, Michael Paquier)
@@ -745,7 +921,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix incorrect reconstruction of pg_subtrans entries
+ Fix incorrect reconstruction of pg_subtrans entries
when a standby server replays a prepared but uncommitted two-phase
transaction (Tom Lane)
@@ -753,7 +929,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
In most cases this turned out to have no visible ill effects, but in
corner cases it could result in circular references
- in pg_subtrans, potentially causing infinite loops
+ in pg_subtrans, potentially causing infinite loops
in queries that examine rows modified by the two-phase transaction.
@@ -768,19 +944,19 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
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 ALTER TABLE
- ... RENAME.
+ ... RENAME.
Skip tablespace privilege checks when ALTER TABLE ... ALTER
- COLUMN TYPE rebuilds an existing index (Noah Misch)
+ COLUMN TYPE rebuilds an existing index (Noah Misch)
The command failed if the calling user did not currently have
- CREATE privilege for the tablespace containing the index.
+ CREATE privilege for the tablespace containing the index.
That behavior seems unhelpful, so skip the check, allowing the
index to be rebuilt where it is.
@@ -788,27 +964,27 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse
- to child tables when the constraint is marked NO INHERIT
+ Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse
+ to child tables when the constraint is marked NO INHERIT
(Amit Langote)
- This fix prevents unwanted constraint does not exist failures
+ This fix prevents unwanted constraint does not exist failures
when no matching constraint is present in the child tables.
- Fix VACUUM to account properly for pages that could not
+ Fix VACUUM to account properly for pages that could not
be scanned due to conflicting page pins (Andrew Gierth)
This tended to lead to underestimation of the number of tuples in
the table. In the worst case of a small heavily-contended
- table, VACUUM could incorrectly report that the table
+ table, VACUUM could incorrectly report that the table
contained no tuples, leading to very bad planning choices.
@@ -822,33 +998,33 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix cursor_to_xml() to produce valid output
- with tableforest = false
+ Fix cursor_to_xml() to produce valid output
+ with tableforest = false
(Thomas Munro, Peter Eisentraut)
- Previously it failed to produce a wrapping <table>
+ Previously it failed to produce a wrapping <table>
element.
- Improve performance of pg_timezone_names view
+ Improve performance of pg_timezone_names view
(Tom Lane, David Rowley)
- Fix sloppy handling of corner-case errors from lseek()
- and close() (Tom Lane)
+ Fix sloppy handling of corner-case errors from lseek()
+ and close() (Tom Lane)
Neither of these system calls are likely to fail in typical situations,
- but if they did, fd.c could get quite confused.
+ but if they did, fd.c could get quite confused.
@@ -866,21 +1042,21 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix ecpg to support COMMIT PREPARED
- and ROLLBACK PREPARED (Masahiko Sawada)
+ Fix ecpg to support COMMIT PREPARED
+ and ROLLBACK PREPARED (Masahiko Sawada)
Fix a double-free error when processing dollar-quoted string literals
- in ecpg (Michael Meskes)
+ in ecpg (Michael Meskes)
- In pg_dump, fix incorrect schema and owner marking for
+ In pg_dump, fix incorrect schema and owner marking for
comments and security labels of some types of database objects
(Giuseppe Broccolo, Tom Lane)
@@ -895,20 +1071,20 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Avoid emitting an invalid list file in pg_restore -l
+ Avoid emitting an invalid list file in pg_restore -l
when SQL object names contain newlines (Tom Lane)
Replace newlines by spaces, which is sufficient to make the output
- valid for pg_restore -L's purposes.
+ valid for pg_restore -L's purposes.
- Fix pg_upgrade to transfer comments and security labels
- attached to large objects (blobs) (Stephen Frost)
+ Fix pg_upgrade to transfer comments and security labels
+ attached to large objects (blobs) (Stephen Frost)
@@ -920,19 +1096,19 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Improve error handling
- in contrib/adminpack's pg_file_write()
+ in contrib/adminpack's pg_file_write()
function (Noah Misch)
Notably, it failed to detect errors reported
- by fclose().
+ by fclose().
- In contrib/dblink, avoid leaking the previous unnamed
+ In contrib/dblink, avoid leaking the previous unnamed
connection when establishing a new unnamed connection (Joe Conway)
@@ -967,7 +1143,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Update time zone data files to tzdata release 2017b
+ Update time zone data files to tzdata 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
@@ -981,9 +1157,9 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
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, PostgreSQL
+ abbreviation. At least for the time being, PostgreSQL
will continue to accept such removed abbreviations for timestamp input.
- But they will not be shown in the pg_timezone_names
+ But they will not be shown in the pg_timezone_names
view nor used for output.
@@ -996,15 +1172,15 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
The Microsoft MSVC build scripts neglected to install
- the posixrules file in the timezone directory tree.
+ the posixrules 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 US/Eastern zone. If you don't want that, remove
- the posixrules file, or replace it with a copy of some
+ the US/Eastern zone. If you don't want that, remove
+ the posixrules file, or replace it with a copy of some
other zone file (see ). Note that
due to caching, you may need to restart the server to get such changes
to take effect.
@@ -1058,15 +1234,15 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Fix a race condition that could cause indexes built
- with CREATE INDEX CONCURRENTLY to be corrupt
+ with CREATE INDEX CONCURRENTLY to be corrupt
(Pavan Deolasee, Tom Lane)
- If CREATE INDEX CONCURRENTLY was used to build an index
+ If CREATE INDEX CONCURRENTLY was used to build an index
that depends on a column not previously indexed, then rows
updated by transactions that ran concurrently with
- the CREATE INDEX command could have received incorrect
+ the CREATE INDEX 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.
@@ -1075,13 +1251,13 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Unconditionally WAL-log creation of the init fork for an
+ Unconditionally WAL-log creation of the init fork for an
unlogged table (Michael Paquier)
Previously, this was skipped when
- = minimal, but actually it's necessary even in that case
+ = minimal, but actually it's necessary even in that case
to ensure that the unlogged table is properly reset to empty after a
crash.
@@ -1098,7 +1274,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- In corner cases, a spurious out-of-sequence TLI error
+ In corner cases, a spurious out-of-sequence TLI error
could be reported during recovery.
@@ -1144,7 +1320,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Make sure ALTER TABLE preserves index tablespace
+ Make sure ALTER TABLE preserves index tablespace
assignments when rebuilding indexes (Tom Lane, Michael Paquier)
@@ -1162,15 +1338,15 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- This avoids could not find trigger NNN
- or relation NNN has no triggers errors.
+ This avoids could not find trigger NNN
+ or relation NNN has no triggers errors.
Fix processing of OID column when a table with OIDs is associated to
- a parent with OIDs via ALTER TABLE ... INHERIT (Amit
+ a parent with OIDs via ALTER TABLE ... INHERIT (Amit
Langote)
@@ -1203,12 +1379,12 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Ensure that column typmods are determined accurately for
- multi-row VALUES constructs (Tom Lane)
+ multi-row VALUES constructs (Tom Lane)
This fixes problems occurring when the first value in a column has a
- determinable typmod (e.g., length for a varchar value) but
+ determinable typmod (e.g., length for a varchar value) but
later values don't share the same limit.
@@ -1223,15 +1399,15 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
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 (U&'...') or Unicode identifier
- (U&"...").
+ string literal (U&'...') or Unicode identifier
+ (U&"...").
Ensure that a purely negative text search query, such
- as !foo, matches empty tsvectors (Tom Dunstan)
+ as !foo, matches empty tsvectors (Tom Dunstan)
@@ -1242,33 +1418,33 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Prevent crash when ts_rewrite() replaces a non-top-level
+ Prevent crash when ts_rewrite() replaces a non-top-level
subtree with an empty query (Artur Zakirov)
- Fix performance problems in ts_rewrite() (Tom Lane)
+ Fix performance problems in ts_rewrite() (Tom Lane)
- Fix ts_rewrite()'s handling of nested NOT operators
+ Fix ts_rewrite()'s handling of nested NOT operators
(Tom Lane)
- Fix array_fill() to handle empty arrays properly (Tom Lane)
+ Fix array_fill() to handle empty arrays properly (Tom Lane)
- Fix one-byte buffer overrun in quote_literal_cstr()
+ Fix one-byte buffer overrun in quote_literal_cstr()
(Heikki Linnakangas)
@@ -1280,8 +1456,8 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Prevent multiple calls of pg_start_backup()
- and pg_stop_backup() from running concurrently (Michael
+ Prevent multiple calls of pg_start_backup()
+ and pg_stop_backup() from running concurrently (Michael
Paquier)
@@ -1293,28 +1469,28 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Avoid discarding interval-to-interval casts
+ Avoid discarding interval-to-interval casts
that aren't really no-ops (Tom Lane)
In some cases, a cast that should result in zeroing out
- low-order interval fields was mistakenly deemed to be a
+ low-order interval fields was mistakenly deemed to be a
no-op and discarded. An example is that casting from INTERVAL
- MONTH to INTERVAL YEAR failed to clear the months field.
+ MONTH to INTERVAL YEAR failed to clear the months field.
- Fix pg_dump to dump user-defined casts and transforms
+ Fix pg_dump to dump user-defined casts and transforms
that use built-in functions (Stephen Frost)
- Fix possible pg_basebackup failure on standby
+ Fix possible pg_basebackup failure on standby
server when including WAL files (Amit Kapila, Robert Haas)
@@ -1333,21 +1509,21 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix PL/Tcl to support triggers on tables that have .tupno
+ Fix PL/Tcl to support triggers on tables that have .tupno
as a column name (Tom Lane)
This matches the (previously undocumented) behavior of
- PL/Tcl's spi_exec and spi_execp commands,
- namely that a magic .tupno column is inserted only if
+ PL/Tcl's spi_exec and spi_execp commands,
+ namely that a magic .tupno column is inserted only if
there isn't a real column named that.
- Allow DOS-style line endings in ~/.pgpass files,
+ Allow DOS-style line endings in ~/.pgpass files,
even on Unix (Vik Fearing)
@@ -1359,23 +1535,23 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix one-byte buffer overrun if ecpg is given a file
+ Fix one-byte buffer overrun if ecpg is given a file
name that ends with a dot (Takayuki Tsunakawa)
- Fix psql's tab completion for ALTER DEFAULT
- PRIVILEGES (Gilles Darold, Stephen Frost)
+ Fix psql's tab completion for ALTER DEFAULT
+ PRIVILEGES (Gilles Darold, Stephen Frost)
- In psql, treat an empty or all-blank setting of
- the PAGER environment variable as meaning no
- pager (Tom Lane)
+ In psql, treat an empty or all-blank setting of
+ the PAGER environment variable as meaning no
+ pager (Tom Lane)
@@ -1386,8 +1562,8 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Improve contrib/dblink's reporting of
- low-level libpq errors, such as out-of-memory
+ Improve contrib/dblink's reporting of
+ low-level libpq errors, such as out-of-memory
(Joe Conway)
@@ -1414,7 +1590,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Update time zone data files to tzdata release 2016j
+ Update time zone data files to tzdata 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.
@@ -1489,71 +1665,71 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix EXPLAIN to emit valid XML when
+ Fix EXPLAIN to emit valid XML when
is on (Markus Winand)
Previously the XML output-format option produced syntactically invalid
- tags such as <I/O-Read-Time>. That is now
- rendered as <I-O-Read-Time>.
+ tags such as <I/O-Read-Time>. That is now
+ rendered as <I-O-Read-Time>.
Suppress printing of zeroes for unmeasured times
- in EXPLAIN (Maksim Milyutin)
+ in EXPLAIN (Maksim Milyutin)
Certain option combinations resulted in printing zero values for times
that actually aren't ever measured in that combination. Our general
- policy in EXPLAIN is not to print such fields at all, so
+ policy in EXPLAIN is not to print such fields at all, so
do that consistently in all cases.
- Fix timeout length when VACUUM is waiting for exclusive
+ Fix timeout length when VACUUM is waiting for exclusive
table lock so that it can truncate the table (Simon Riggs)
The timeout was meant to be 50 milliseconds, but it was actually only
- 50 microseconds, causing VACUUM to give up on truncation
+ 50 microseconds, causing VACUUM to give up on truncation
much more easily than intended. Set it to the intended value.
- Fix bugs in merging inherited CHECK constraints while
+ Fix bugs in merging inherited CHECK constraints while
creating or altering a table (Tom Lane, Amit Langote)
- Allow identical CHECK constraints to be added to a parent
+ Allow identical CHECK 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 NOT VALID
+ constraint from the parent table with a NOT VALID
constraint on the child. Likewise, prevent merging of a NO
- INHERIT child constraint with an inherited constraint.
+ INHERIT child constraint with an inherited constraint.
Remove artificial restrictions on the values accepted
- by numeric_in() and numeric_recv()
+ by numeric_in() and numeric_recv()
(Tom Lane)
We allow numeric values up to the limit of the storage format (more
- than 1e100000), so it seems fairly pointless
- that numeric_in() rejected scientific-notation exponents
- above 1000. Likewise, it was silly for numeric_recv() to
+ than 1e100000), so it seems fairly pointless
+ that numeric_in() rejected scientific-notation exponents
+ above 1000. Likewise, it was silly for numeric_recv() to
reject more than 1000 digits in an input value.
@@ -1575,7 +1751,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Disallow starting a standalone backend with standby_mode
+ Disallow starting a standalone backend with standby_mode
turned on (Michael Paquier)
@@ -1589,7 +1765,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Don't try to share SSL contexts across multiple connections
- in libpq (Heikki Linnakangas)
+ in libpq (Heikki Linnakangas)
@@ -1600,30 +1776,30 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Avoid corner-case memory leak in libpq (Tom Lane)
+ Avoid corner-case memory leak in libpq (Tom Lane)
The reported problem involved leaking an error report
- during PQreset(), but there might be related cases.
+ during PQreset(), but there might be related cases.
- Make ecpg's and
options work consistently with our other executables (Haribabu Kommi)
- In pg_dump, never dump range constructor functions
+ In pg_dump, never dump range constructor functions
(Tom Lane)
- This oversight led to pg_upgrade failures with
+ This oversight led to pg_upgrade failures with
extensions containing range types, due to duplicate creation of the
constructor functions.
@@ -1631,8 +1807,8 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix contrib/intarray/bench/bench.pl to print the results
- of the EXPLAIN it does when given the option
(Daniel Gustafsson)
@@ -1653,17 +1829,17 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
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 tzdata
+ their time zone database, as they did in tzdata
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 pg_timezone_abbrevs view to fail altogether.
+ the pg_timezone_abbrevs view to fail altogether.
- Update time zone data files to tzdata release 2016h
+ Update time zone data files to tzdata 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,
@@ -1676,15 +1852,15 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
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, PostgreSQL
+ abbreviation. At least for the time being, PostgreSQL
will continue to accept such removed abbreviations for timestamp input.
- But they will not be shown in the pg_timezone_names
+ But they will not be shown in the pg_timezone_names
view nor used for output.
- In this update, AMT is no longer shown as being in use to
- mean Armenia Time. Therefore, we have changed the Default
+ In this update, AMT is no longer shown as being in use to
+ mean Armenia Time. Therefore, we have changed the Default
abbreviation set to interpret it as Amazon Time, thus UTC-4 not UTC+4.
@@ -1730,17 +1906,17 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Fix possible mis-evaluation of
- nested CASE-WHEN expressions (Heikki
+ nested CASE-WHEN expressions (Heikki
Linnakangas, Michael Paquier, Tom Lane)
- A CASE expression appearing within the test value
- subexpression of another CASE could become confused about
+ A CASE expression appearing within the test value
+ subexpression of another CASE 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 CASE expression could result in passing the wrong test
- value to functions called within a CASE expression in the
+ a CASE expression could result in passing the wrong test
+ value to functions called within a CASE 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)
@@ -1754,7 +1930,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Numerous places in vacuumdb and other client programs
+ Numerous places in vacuumdb 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
@@ -1763,22 +1939,22 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Fix handling of paired double quotes
- in psql's \connect
- and \password commands to match the documentation.
+ in psql's \connect
+ and \password commands to match the documentation.
- Introduce a new
- pg_dumpall now refuses to deal with database and role
+ pg_dumpall 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.
@@ -1788,40 +1964,40 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
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 pg_dumpall or other routine maintenance
+ executes pg_dumpall or other routine maintenance
operations. (CVE-2016-5424)
- Fix corner-case misbehaviors for IS NULL/IS NOT
- NULL applied to nested composite values (Andrew Gierth, Tom Lane)
+ Fix corner-case misbehaviors for IS NULL/IS NOT
+ NULL applied to nested composite values (Andrew Gierth, Tom Lane)
- The SQL standard specifies that IS NULL should return
+ The SQL standard specifies that IS NULL should return
TRUE for a row of all null values (thus ROW(NULL,NULL) IS
- NULL yields TRUE), but this is not meant to apply recursively
- (thus ROW(NULL, ROW(NULL,NULL)) IS NULL yields FALSE).
+ NULL yields TRUE), but this is not meant to apply recursively
+ (thus ROW(NULL, ROW(NULL,NULL)) IS NULL yields FALSE).
The core executor got this right, but certain planner optimizations
treated the test as recursive (thus producing TRUE in both cases),
- and contrib/postgres_fdw could produce remote queries
+ and contrib/postgres_fdw could produce remote queries
that misbehaved similarly.
- Make the inet and cidr data types properly reject
+ Make the inet and cidr data types properly reject
IPv6 addresses with too many colon-separated fields (Tom Lane)
- Prevent crash in close_ps()
- (the point ## lseg operator)
+ Prevent crash in close_ps()
+ (the point##lseg operator)
for NaN input coordinates (Tom Lane)
@@ -1832,12 +2008,12 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix several one-byte buffer over-reads in to_number()
+ Fix several one-byte buffer over-reads in to_number()
(Peter Eisentraut)
- In several cases the to_number() function would read one
+ In several cases the to_number() 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.
@@ -1847,7 +2023,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Avoid unsafe intermediate state during expensive paths
- through heap_update() (Masahiko Sawada, Andres Freund)
+ through heap_update() (Masahiko Sawada, Andres Freund)
@@ -1860,19 +2036,19 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Avoid crash in postgres -C when the specified variable
+ Avoid crash in postgres -C when the specified variable
has a null string value (Michael Paquier)
- Avoid consuming a transaction ID during VACUUM
+ Avoid consuming a transaction ID during VACUUM
(Alexander Korotkov)
- Some cases in VACUUM unnecessarily caused an XID to be
+ Some cases in VACUUM 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.
@@ -1881,12 +2057,12 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Avoid canceling hot-standby queries during VACUUM FREEZE
+ Avoid canceling hot-standby queries during VACUUM FREEZE
(Simon Riggs, Álvaro Herrera)
- VACUUM FREEZE on an otherwise-idle master server could
+ VACUUM FREEZE on an otherwise-idle master server could
result in unnecessary cancellations of queries on its standby
servers.
@@ -1894,8 +2070,8 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- When a manual ANALYZE specifies a column list, don't
- reset the table's changes_since_analyze counter
+ When a manual ANALYZE specifies a column list, don't
+ reset the table's changes_since_analyze counter
(Tom Lane)
@@ -1907,7 +2083,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix ANALYZE's overestimation of n_distinct
+ Fix ANALYZE's overestimation of n_distinct
for a unique or nearly-unique column with many null entries (Tom
Lane)
@@ -1942,8 +2118,8 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix contrib/btree_gin to handle the smallest
- possible bigint value correctly (Peter Eisentraut)
+ Fix contrib/btree_gin to handle the smallest
+ possible bigint value correctly (Peter Eisentraut)
@@ -1956,29 +2132,29 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
It's planned to switch to two-part instead of three-part server
version numbers for releases after 9.6. Make sure
- that PQserverVersion() returns the correct value for
+ that PQserverVersion() returns the correct value for
such cases.
- Fix ecpg's code for unsigned long long
+ Fix ecpg's code for unsigned long long
array elements (Michael Meskes)
- In pg_dump with both
- Make pg_basebackup accept -Z 0 as
+ Make pg_basebackup accept -Z 0 as
specifying no compression (Fujii Masao)
@@ -2012,7 +2188,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Update our copy of the timezone code to match
- IANA's tzcode release 2016c (Tom Lane)
+ IANA's tzcode release 2016c (Tom Lane)
@@ -2024,7 +2200,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Update time zone data files to tzdata release 2016f
+ Update time zone data files to tzdata release 2016f
for DST law changes in Kemerovo and Novosibirsk, plus historical
corrections for Azerbaijan, Belarus, and Morocco.
@@ -2080,7 +2256,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
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 libpq concurrently with
+ uses SSL connections in libpq 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.
@@ -2089,7 +2265,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix failed to build any N-way joins
+ Fix failed to build any N-way joins
planner error with a full join enclosed in the right-hand side of a
left join (Tom Lane)
@@ -2103,10 +2279,10 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Given a three-or-more-way equivalence class of variables, such
- as X.X = Y.Y = Z.Z, it was possible for the planner to omit
+ as X.X = Y.Y = Z.Z, 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 WHERE clauses. For various reasons, erroneous plans
+ the WHERE clauses. For various reasons, erroneous plans
were seldom selected in practice, so that this bug has gone undetected
for a long time.
@@ -2114,8 +2290,8 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix possible misbehavior of TH, th,
- and Y,YYY format codes in to_timestamp()
+ Fix possible misbehavior of TH, th,
+ and Y,YYY format codes in to_timestamp()
(Tom Lane)
@@ -2127,28 +2303,28 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix dumping of rules and views in which the array
- argument of a value operator
- ANY (array) construct is a sub-SELECT
+ Fix dumping of rules and views in which the array
+ argument of a valueoperator
+ ANY (array) construct is a sub-SELECT
(Tom Lane)
- Make pg_regress use a startup timeout from the
- PGCTLTIMEOUT environment variable, if that's set (Tom Lane)
+ Make pg_regress use a startup timeout from the
+ PGCTLTIMEOUT environment variable, if that's set (Tom Lane)
This is for consistency with a behavior recently added
- to pg_ctl; it eases automated testing on slow machines.
+ to pg_ctl; it eases automated testing on slow machines.
- Fix pg_upgrade to correctly restore extension
+ Fix pg_upgrade to correctly restore extension
membership for operator families containing only one operator class
(Tom Lane)
@@ -2156,7 +2332,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
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 pg_dump
+ immediate ill effects, but would cause later pg_dump
runs to emit output that would cause (harmless) errors on restore.
@@ -2177,22 +2353,22 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Reduce the number of SysV semaphores used by a build configured with
- (Tom Lane)
- Rename internal function strtoi()
- to strtoint() to avoid conflict with a NetBSD library
+ Rename internal function strtoi()
+ to strtoint() to avoid conflict with a NetBSD library
function (Thomas Munro)
- Fix reporting of errors from bind()
- and listen() system calls on Windows (Tom Lane)
+ Fix reporting of errors from bind()
+ and listen() system calls on Windows (Tom Lane)
@@ -2205,12 +2381,12 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Avoid possibly-unsafe use of Windows' FormatMessage()
+ Avoid possibly-unsafe use of Windows' FormatMessage()
function (Christian Ullrich)
- Use the FORMAT_MESSAGE_IGNORE_INSERTS flag where
+ Use the FORMAT_MESSAGE_IGNORE_INSERTS flag where
appropriate. No live bug is known to exist here, but it seems like a
good idea to be careful.
@@ -2218,9 +2394,9 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Update time zone data files to tzdata release 2016d
+ Update time zone data files to tzdata release 2016d
for DST law changes in Russia and Venezuela. There are new zone
- names Europe/Kirov and Asia/Tomsk to reflect
+ names Europe/Kirov and Asia/Tomsk to reflect
the fact that these regions now have different time zone histories from
adjacent regions.
@@ -2267,56 +2443,56 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Fix incorrect handling of NULL index entries in
- indexed ROW() comparisons (Tom Lane)
+ indexed ROW() comparisons (Tom Lane)
An index search using a row comparison such as ROW(a, b) >
- ROW('x', 'y') would stop upon reaching a NULL entry in
- the b column, ignoring the fact that there might be
- non-NULL b values associated with later values
- of a.
+ ROW('x', 'y') would stop upon reaching a NULL entry in
+ the b column, ignoring the fact that there might be
+ non-NULL b values associated with later values
+ of a.
Avoid unlikely data-loss scenarios due to renaming files without
- adequate fsync() calls before and after (Michael Paquier,
+ adequate fsync() calls before and after (Michael Paquier,
Tomas Vondra, Andres Freund)
- Correctly handle cases where pg_subtrans is close to XID
+ Correctly handle cases where pg_subtrans is close to XID
wraparound during server startup (Jeff Janes)
- Fix corner-case crash due to trying to free localeconv()
+ Fix corner-case crash due to trying to free localeconv()
output strings more than once (Tom Lane)
- Fix parsing of affix files for ispell dictionaries
+ Fix parsing of affix files for ispell dictionaries
(Tom Lane)
The code could go wrong if the affix file contained any characters
whose byte length changes during case-folding, for
- example I in Turkish UTF8 locales.
+ example I in Turkish UTF8 locales.
- Avoid use of sscanf() to parse ispell
+ Avoid use of sscanf() to parse ispell
dictionary files (Artur Zakirov)
@@ -2342,27 +2518,27 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix psql's tab completion logic to handle multibyte
+ Fix psql's tab completion logic to handle multibyte
characters properly (Kyotaro Horiguchi, Robert Haas)
- Fix psql's tab completion for
- SECURITY LABEL (Tom Lane)
+ Fix psql's tab completion for
+ SECURITY LABEL (Tom Lane)
- Pressing TAB after SECURITY LABEL might cause a crash
+ Pressing TAB after SECURITY LABEL might cause a crash
or offering of inappropriate keywords.
- Make pg_ctl accept a wait timeout from the
- PGCTLTIMEOUT environment variable, if none is specified on
+ Make pg_ctl accept a wait timeout from the
+ PGCTLTIMEOUT environment variable, if none is specified on
the command line (Noah Misch)
@@ -2376,20 +2552,20 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Fix incorrect test for Windows service status
- in pg_ctl (Manuel Mathar)
+ in pg_ctl (Manuel Mathar)
The previous set of minor releases attempted to
- fix pg_ctl to properly determine whether to send log
+ fix pg_ctl to properly determine whether to send log
messages to Window's Event Log, but got the test backwards.
- Fix pgbench to correctly handle the combination
- of -C and -M prepared options (Tom Lane)
+ Fix pgbench to correctly handle the combination
+ of -C and -M prepared options (Tom Lane)
@@ -2410,21 +2586,21 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Fix multiple mistakes in the statistics returned
- by contrib/pgstattuple's pgstatindex()
+ by contrib/pgstattuple's pgstatindex()
function (Tom Lane)
- Remove dependency on psed in MSVC builds, since it's no
+ Remove dependency on psed in MSVC builds, since it's no
longer provided by core Perl (Michael Paquier, Andrew Dunstan)
- Update time zone data files to tzdata release 2016c
+ Update time zone data files to tzdata 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
@@ -2485,25 +2661,25 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Perform an immediate shutdown if the postmaster.pid file
+ Perform an immediate shutdown if the postmaster.pid file
is removed (Tom Lane)
The postmaster now checks every minute or so
- that postmaster.pid is still there and still contains its
+ that postmaster.pid is still there and still contains its
own PID. If not, it performs an immediate shutdown, as though it had
- received SIGQUIT. The main motivation for this change
+ received SIGQUIT. 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 postmaster.pid and then starts a new
+ DBA forcibly removes postmaster.pid and then starts a new
postmaster.
- In SERIALIZABLE transaction isolation mode, serialization
+ In SERIALIZABLE transaction isolation mode, serialization
anomalies could be missed due to race conditions during insertions
(Kevin Grittner, Thomas Munro)
@@ -2512,7 +2688,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Fix failure to emit appropriate WAL records when doing ALTER
- TABLE ... SET TABLESPACE for unlogged relations (Michael Paquier,
+ TABLE ... SET TABLESPACE for unlogged relations (Michael Paquier,
Andres Freund)
@@ -2531,21 +2707,21 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix ALTER COLUMN TYPE to reconstruct inherited check
+ Fix ALTER COLUMN TYPE to reconstruct inherited check
constraints properly (Tom Lane)
- Fix REASSIGN OWNED to change ownership of composite types
+ Fix REASSIGN OWNED to change ownership of composite types
properly (Álvaro Herrera)
- Fix REASSIGN OWNED and ALTER OWNER to correctly
+ Fix REASSIGN OWNED and ALTER OWNER to correctly
update granted-permissions lists when changing owners of data types,
foreign data wrappers, or foreign servers (Bruce Momjian,
Álvaro Herrera)
@@ -2554,7 +2730,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix REASSIGN OWNED to ignore foreign user mappings,
+ Fix REASSIGN OWNED to ignore foreign user mappings,
rather than fail (Álvaro Herrera)
@@ -2576,14 +2752,14 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix dumping of whole-row Vars in ROW()
- and VALUES() lists (Tom Lane)
+ Fix dumping of whole-row Vars in ROW()
+ and VALUES() lists (Tom Lane)
- Fix possible internal overflow in numeric division
+ Fix possible internal overflow in numeric division
(Dean Rasheed)
@@ -2635,7 +2811,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
This causes the code to emit regular expression is too
- complex errors in some cases that previously used unreasonable
+ complex errors in some cases that previously used unreasonable
amounts of time and memory.
@@ -2648,14 +2824,14 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Make %h and %r escapes
- in log_line_prefix work for messages emitted due
- to log_connections (Tom Lane)
+ Make %h and %r escapes
+ in log_line_prefix work for messages emitted due
+ to log_connections (Tom Lane)
- Previously, %h/%r started to work just after a
- new session had emitted the connection received log message;
+ Previously, %h/%r started to work just after a
+ new session had emitted the connection received log message;
now they work for that message too.
@@ -2668,7 +2844,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
This oversight resulted in failure to recover from crashes
- whenever logging_collector is turned on.
+ whenever logging_collector is turned on.
@@ -2694,13 +2870,13 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- In psql, ensure that libreadline's idea
+ In psql, ensure that libreadline's idea
of the screen size is updated when the terminal window size changes
(Merlin Moncure)
- Previously, libreadline did not notice if the window
+ Previously, libreadline did not notice if the window
was resized during query output, leading to strange behavior during
later input of multiline queries.
@@ -2708,15 +2884,15 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix psql's \det command to interpret its
- pattern argument the same way as other \d commands with
+ Fix psql's \det command to interpret its
+ pattern argument the same way as other \d commands with
potentially schema-qualified patterns do (Reece Hart)
- Avoid possible crash in psql's \c command
+ Avoid possible crash in psql's \c command
when previous connection was via Unix socket and command specifies a
new hostname and same username (Tom Lane)
@@ -2724,21 +2900,21 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- In pg_ctl start -w, test child process status directly
+ In pg_ctl start -w, test child process status directly
rather than relying on heuristics (Tom Lane, Michael Paquier)
- Previously, pg_ctl relied on an assumption that the new
- postmaster would always create postmaster.pid within five
+ Previously, pg_ctl relied on an assumption that the new
+ postmaster would always create postmaster.pid within five
seconds. But that can fail on heavily-loaded systems,
- causing pg_ctl to report incorrectly that the
+ causing pg_ctl to report incorrectly that the
postmaster failed to start.
Except on Windows, this change also means that a pg_ctl start
- -w done immediately after another such command will now reliably
+ -w 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.
@@ -2746,23 +2922,23 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- In pg_ctl start -w, don't attempt to use a wildcard listen
+ In pg_ctl start -w, don't attempt to use a wildcard listen
address to connect to the postmaster (Kondo Yuta)
- On Windows, pg_ctl would fail to detect postmaster
- startup if listen_addresses is set to 0.0.0.0
- or ::, because it would try to use that value verbatim as
+ On Windows, pg_ctl would fail to detect postmaster
+ startup if listen_addresses is set to 0.0.0.0
+ or ::, because it would try to use that value verbatim as
the address to connect to, which doesn't work. Instead assume
- that 127.0.0.1 or ::1, respectively, is the
+ that 127.0.0.1 or ::1, respectively, is the
right thing to use.
- In pg_ctl on Windows, check service status to decide
+ In pg_ctl on Windows, check service status to decide
where to send output, rather than checking if standard output is a
terminal (Michael Paquier)
@@ -2770,18 +2946,18 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- In pg_dump and pg_basebackup, adopt
+ In pg_dump and pg_basebackup, adopt
the GNU convention for handling tar-archive members exceeding 8GB
(Tom Lane)
- The POSIX standard for tar file format does not allow
+ The POSIX standard for tar file format does not allow
archive member files to exceed 8GB, but most modern implementations
- of tar support an extension that fixes that. Adopt
- this extension so that pg_dump with no
longer fails on tables with more than 8GB of data, and so
- that pg_basebackup can handle files larger than 8GB.
+ that pg_basebackup 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
@@ -2791,44 +2967,44 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix assorted corner-case bugs in pg_dump's processing
+ Fix assorted corner-case bugs in pg_dump's processing
of extension member objects (Tom Lane)
- Make pg_dump mark a view's triggers as needing to be
+ Make pg_dump mark a view's triggers as needing to be
processed after its rule, to prevent possible failure during
- parallel pg_restore (Tom Lane)
+ parallel pg_restore (Tom Lane)
Ensure that relation option values are properly quoted
- in pg_dump (Kouhei Sutou, Tom Lane)
+ in pg_dump (Kouhei Sutou, Tom Lane)
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 pg_dump. This is not an issue with any
- reloption currently supported by core PostgreSQL, but
+ issued by pg_dump. This is not an issue with any
+ reloption currently supported by core PostgreSQL, but
extensions could allow reloptions that cause the problem.
- Fix pg_upgrade's file-copying code to handle errors
+ Fix pg_upgrade's file-copying code to handle errors
properly on Windows (Bruce Momjian)
- Install guards in pgbench against corner-case overflow
+ Install guards in pgbench against corner-case overflow
conditions during evaluation of script-specified division or modulo
operators (Fabien Coelho, Michael Paquier)
@@ -2837,22 +3013,22 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Fix failure to localize messages emitted
- by pg_receivexlog and pg_recvlogical
+ by pg_receivexlog and pg_recvlogical
(Ioseph Kim)
- Avoid dump/reload problems when using both plpython2
- and plpython3 (Tom Lane)
+ Avoid dump/reload problems when using both plpython2
+ and plpython3 (Tom Lane)
- In principle, both versions of PL/Python can be used in
+ In principle, both versions of PL/Python can be used in
the same database, though not in the same session (because the two
- versions of libpython cannot safely be used concurrently).
- However, pg_restore and pg_upgrade both
+ versions of libpython cannot safely be used concurrently).
+ However, pg_restore and pg_upgrade both
do things that can fall foul of the same-session restriction. Work
around that by changing the timing of the check.
@@ -2860,29 +3036,29 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix PL/Python regression tests to pass with Python 3.5
+ Fix PL/Python regression tests to pass with Python 3.5
(Peter Eisentraut)
- Prevent certain PL/Java parameters from being set by
+ Prevent certain PL/Java parameters from being set by
non-superusers (Noah Misch)
- This change mitigates a PL/Java security bug
- (CVE-2016-0766), which was fixed in PL/Java by marking
+ This change mitigates a PL/Java security bug
+ (CVE-2016-0766), which was fixed in PL/Java by marking
these parameters as superuser-only. To fix the security hazard for
- sites that update PostgreSQL more frequently
- than PL/Java, make the core code aware of them also.
+ sites that update PostgreSQL more frequently
+ than PL/Java, make the core code aware of them also.
- Improve libpq's handling of out-of-memory situations
+ Improve libpq's handling of out-of-memory situations
(Michael Paquier, Amit Kapila, Heikki Linnakangas)
@@ -2890,42 +3066,42 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Fix order of arguments
- in ecpg-generated typedef statements
+ in ecpg-generated typedef statements
(Michael Meskes)
- Use %g not %f format
- in ecpg's PGTYPESnumeric_from_double()
+ Use %g not %f format
+ in ecpg's PGTYPESnumeric_from_double()
(Tom Lane)
- Fix ecpg-supplied header files to not contain comments
+ Fix ecpg-supplied header files to not contain comments
continued from a preprocessor directive line onto the next line
(Michael Meskes)
- Such a comment is rejected by ecpg. It's not yet clear
- whether ecpg itself should be changed.
+ Such a comment is rejected by ecpg. It's not yet clear
+ whether ecpg itself should be changed.
- Ensure that contrib/pgcrypto's crypt()
+ Ensure that contrib/pgcrypto's crypt()
function can be interrupted by query cancel (Andreas Karlsson)
- Accept flex versions later than 2.5.x
+ Accept flex versions later than 2.5.x
(Tom Lane, Michael Paquier)
@@ -2937,19 +3113,19 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Install our missing script where PGXS builds can find it
+ Install our missing script where PGXS builds can find it
(Jim Nasby)
This allows sane behavior in a PGXS build done on a machine where build
- tools such as bison are missing.
+ tools such as bison are missing.
- Ensure that dynloader.h is included in the installed
+ Ensure that dynloader.h is included in the installed
header files in MSVC builds (Bruce Momjian, Michael Paquier)
@@ -2957,11 +3133,11 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
Add variant regression test expected-output file to match behavior of
- current libxml2 (Tom Lane)
+ current libxml2 (Tom Lane)
- The fix for libxml2's CVE-2015-7499 causes it not to
+ The fix for libxml2'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.
@@ -2970,7 +3146,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Update time zone data files to tzdata release 2016a for
+ Update time zone data files to tzdata release 2016a for
DST law changes in Cayman Islands, Metlakatla, and Trans-Baikal
Territory (Zabaykalsky Krai), plus historical corrections for Pakistan.
@@ -3016,8 +3192,8 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix contrib/pgcrypto to detect and report
- too-short crypt() salts (Josh Kupershmidt)
+ Fix contrib/pgcrypto to detect and report
+ too-short crypt() salts (Josh Kupershmidt)
@@ -3043,13 +3219,13 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Fix insertion of relations into the relation cache init file
+ Fix insertion of relations into the relation cache init file
(Tom Lane)
An oversight in a patch in the most recent minor releases
- caused pg_trigger_tgrelid_tgname_index to be omitted
+ caused pg_trigger_tgrelid_tgname_index 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
@@ -3067,7 +3243,7 @@ Branch: REL9_2_STABLE [38bec1805] 2017-01-25 07:02:25 +0900
- Improve LISTEN startup time when there are many unread
+ Improve LISTEN startup time when there are many unread
notifications (Matt Newell)
@@ -3085,7 +3261,7 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
- This substantially improves performance when pg_dump
+ This substantially improves performance when pg_dump
tries to dump a large number of tables.
@@ -3100,13 +3276,13 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
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 ssl_renegotiation_limit to zero (disabled).
+ of ssl_renegotiation_limit to zero (disabled).
- Lower the minimum values of the *_freeze_max_age parameters
+ Lower the minimum values of the *_freeze_max_age parameters
(Andres Freund)
@@ -3118,14 +3294,14 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
- Limit the maximum value of wal_buffers to 2GB to avoid
+ Limit the maximum value of wal_buffers to 2GB to avoid
server crashes (Josh Berkus)
- Fix rare internal overflow in multiplication of numeric values
+ Fix rare internal overflow in multiplication of numeric values
(Dean Rasheed)
@@ -3133,21 +3309,21 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
Guard against hard-to-reach stack overflows involving record types,
- range types, json, jsonb, tsquery,
- ltxtquery and query_int (Noah Misch)
+ range types, json, jsonb, tsquery,
+ ltxtquery and query_int (Noah Misch)
- Fix handling of DOW and DOY in datetime input
+ Fix handling of DOW and DOY in datetime input
(Greg Stark)
These tokens aren't meant to be used in datetime values, but previously
they resulted in opaque internal error messages rather
- than invalid input syntax.
+ than invalid input syntax.
@@ -3160,7 +3336,7 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
Add recursion depth protections to regular expression, SIMILAR
- TO, and LIKE matching (Tom Lane)
+ TO, and LIKE matching (Tom Lane)
@@ -3212,22 +3388,22 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
- Fix unexpected out-of-memory situation during sort errors
- when using tuplestores with small work_mem settings (Tom
+ Fix unexpected out-of-memory situation during sort errors
+ when using tuplestores with small work_mem settings (Tom
Lane)
- Fix very-low-probability stack overrun in qsort (Tom Lane)
+ Fix very-low-probability stack overrun in qsort (Tom Lane)
- Fix invalid memory alloc request size failure in hash joins
- with large work_mem settings (Tomas Vondra, Tom Lane)
+ Fix invalid memory alloc request size failure in hash joins
+ with large work_mem settings (Tomas Vondra, Tom Lane)
@@ -3240,9 +3416,9 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
These mistakes could lead to incorrect query plans that would give wrong
answers, or to assertion failures in assert-enabled builds, or to odd
planner errors such as could not devise a query plan for the
- given query, could not find pathkey item to
- sort, plan should not reference subplan's variable,
- or failed to assign all NestLoopParams to plan nodes.
+ given query, could not find pathkey item to
+ sort, plan should not reference subplan's variable,
+ or failed to assign all NestLoopParams to plan nodes.
Thanks are due to Andreas Seltenreich and Piotr Stefaniak for fuzz
testing that exposed these problems.
@@ -3250,7 +3426,7 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
- Improve planner's performance for UPDATE/DELETE
+ Improve planner's performance for UPDATE/DELETE
on large inheritance sets (Tom Lane, Dean Rasheed)
@@ -3271,12 +3447,12 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
During postmaster shutdown, ensure that per-socket lock files are
removed and listen sockets are closed before we remove
- the postmaster.pid file (Tom Lane)
+ the postmaster.pid file (Tom Lane)
This avoids race-condition failures if an external script attempts to
- start a new postmaster as soon as pg_ctl stop returns.
+ start a new postmaster as soon as pg_ctl stop returns.
@@ -3296,7 +3472,7 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
- Do not print a WARNING when an autovacuum worker is already
+ Do not print a WARNING when an autovacuum worker is already
gone when we attempt to signal it, and reduce log verbosity for such
signals (Tom Lane)
@@ -3333,7 +3509,7 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
- VACUUM attempted to recycle such pages, but did so in a
+ VACUUM attempted to recycle such pages, but did so in a
way that wasn't crash-safe.
@@ -3341,44 +3517,44 @@ Branch: REL9_1_STABLE [9b1b9446f] 2015-08-27 12:22:10 -0400
Fix off-by-one error that led to otherwise-harmless warnings
- about apparent wraparound in subtrans/multixact truncation
+ about apparent wraparound in subtrans/multixact truncation
(Thomas Munro)
- Fix misreporting of CONTINUE and MOVE statement
- types in PL/pgSQL's error context messages
+ Fix misreporting of CONTINUE and MOVE statement
+ types in PL/pgSQL's error context messages
(Pavel Stehule, Tom Lane)
- Fix PL/Perl to handle non-ASCII error
+ Fix PL/Perl to handle non-ASCII error
message texts correctly (Alex Hunsaker)
- Fix PL/Python crash when returning the string
- representation of a record result (Tom Lane)
+ Fix PL/Python crash when returning the string
+ representation of a record result (Tom Lane)
- Fix some places in PL/Tcl that neglected to check for
- failure of malloc() calls (Michael Paquier, Álvaro
+ Fix some places in PL/Tcl that neglected to check for
+ failure of malloc() calls (Michael Paquier, Álvaro
Herrera)
- In contrib/isn, fix output of ISBN-13 numbers that begin
+ In contrib/isn, fix output of ISBN-13 numbers that begin
with 979 (Fabien Coelho)
@@ -3395,14 +3571,14 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
- Fix contrib/sepgsql's handling of SELECT INTO
+ Fix contrib/sepgsql's handling of SELECT INTO
statements (Kohei KaiGai)
- Improve libpq's handling of out-of-memory conditions
+ Improve libpq's handling of out-of-memory conditions
(Michael Paquier, Heikki Linnakangas)
@@ -3410,64 +3586,64 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
Fix memory leaks and missing out-of-memory checks
- in ecpg (Michael Paquier)
+ in ecpg (Michael Paquier)
- Fix psql's code for locale-aware formatting of numeric
+ Fix psql's code for locale-aware formatting of numeric
output (Tom Lane)
- The formatting code invoked by \pset numericlocale on
+ The formatting code invoked by \pset numericlocale on
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 money data type.
+ output from the money data type.
- Prevent crash in psql's \c command when
+ Prevent crash in psql's \c command when
there is no current connection (Noah Misch)
- Make pg_dump handle inherited NOT VALID
+ Make pg_dump handle inherited NOT VALID
check constraints correctly (Tom Lane)
- Fix selection of default zlib compression level
- in pg_dump's directory output format (Andrew Dunstan)
+ Fix selection of default zlib compression level
+ in pg_dump's directory output format (Andrew Dunstan)
- Ensure that temporary files created during a pg_dump
- run with tar-format output are not world-readable (Michael
+ Ensure that temporary files created during a pg_dump
+ run with tar-format output are not world-readable (Michael
Paquier)
- Fix pg_dump and pg_upgrade to support
- cases where the postgres or template1 database
+ Fix pg_dump and pg_upgrade to support
+ cases where the postgres or template1 database
is in a non-default tablespace (Marti Raudsepp, Bruce Momjian)
- Fix pg_dump to handle object privileges sanely when
+ Fix pg_dump to handle object privileges sanely when
dumping from a server too old to have a particular privilege type
(Tom Lane)
@@ -3475,11 +3651,11 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
When dumping data types from pre-9.2 servers, and when dumping
functions or procedural languages from pre-7.3
- servers, pg_dump would
- produce GRANT/REVOKE commands that revoked the
+ servers, pg_dump would
+ produce GRANT/REVOKE commands that revoked the
owner's grantable privileges and instead granted all privileges
- to PUBLIC. Since the privileges involved are
- just USAGE and EXECUTE, this isn't a security
+ to PUBLIC. Since the privileges involved are
+ just USAGE and EXECUTE, 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.
@@ -3488,18 +3664,18 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
- Fix pg_dump to dump shell types (Tom Lane)
+ Fix pg_dump to dump shell types (Tom Lane)
Shell types (that is, not-yet-fully-defined types) aren't useful for
- much, but nonetheless pg_dump should dump them.
+ much, but nonetheless pg_dump should dump them.
- Fix assorted minor memory leaks in pg_dump and other
+ Fix assorted minor memory leaks in pg_dump and other
client-side programs (Michael Paquier)
@@ -3507,11 +3683,11 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
Fix spinlock assembly code for PPC hardware to be compatible
- with AIX's native assembler (Tom Lane)
+ with AIX's native assembler (Tom Lane)
- Building with gcc didn't work if gcc
+ Building with gcc didn't work if gcc
had been configured to use the native assembler, which is becoming more
common.
@@ -3519,14 +3695,14 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
- On AIX, test the -qlonglong compiler option
+ On AIX, test the -qlonglong compiler option
rather than just assuming it's safe to use (Noah Misch)
- On AIX, use -Wl,-brtllib link option to allow
+ On AIX, use -Wl,-brtllib link option to allow
symbols to be resolved at runtime (Noah Misch)
@@ -3538,38 +3714,38 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
Avoid use of inline functions when compiling with
- 32-bit xlc, due to compiler bugs (Noah Misch)
+ 32-bit xlc, due to compiler bugs (Noah Misch)
- Use librt for sched_yield() when necessary,
+ Use librt for sched_yield() when necessary,
which it is on some Solaris versions (Oskari Saarenmaa)
- Fix Windows install.bat script to handle target directory
+ Fix Windows install.bat script to handle target directory
names that contain spaces (Heikki Linnakangas)
- Make the numeric form of the PostgreSQL version number
- (e.g., 90405) readily available to extension Makefiles,
- as a variable named VERSION_NUM (Michael Paquier)
+ Make the numeric form of the PostgreSQL version number
+ (e.g., 90405) readily available to extension Makefiles,
+ as a variable named VERSION_NUM (Michael Paquier)
- Update time zone data files to tzdata release 2015g for
+ Update time zone data files to tzdata 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
- America/Fort_Nelson for the Canadian Northern Rockies.
+ America/Fort_Nelson for the Canadian Northern Rockies.
@@ -3618,7 +3794,7 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
With just the wrong timing of concurrent activity, a VACUUM
- FULL on a system catalog might fail to update the init file
+ FULL on a system catalog might fail to update the init file
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
@@ -3629,13 +3805,13 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
Avoid deadlock between incoming sessions and CREATE/DROP
- DATABASE (Tom Lane)
+ DATABASE (Tom Lane)
A new session starting in a database that is the target of
- a DROP DATABASE command, or is the template for
- a CREATE DATABASE command, could cause the command to wait
+ a DROP DATABASE command, or is the template for
+ a CREATE DATABASE command, could cause the command to wait
for five seconds and then fail, even if the new session would have
exited before that.
@@ -3681,12 +3857,12 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
- Avoid failures while fsync'ing data directory during
+ Avoid failures while fsync'ing data directory during
crash restart (Abhijit Menon-Sen, Tom Lane)
- In the previous minor releases we added a patch to fsync
+ In the previous minor releases we added a patch to fsync
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.
@@ -3700,36 +3876,36 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
- Fix pg_get_functiondef() to show
- functions' LEAKPROOF property, if set (Jeevan Chalke)
+ Fix pg_get_functiondef() to show
+ functions' LEAKPROOF property, if set (Jeevan Chalke)
- Remove configure's check prohibiting linking to a
- threaded libpython
- on OpenBSD (Tom Lane)
+ Remove configure's check prohibiting linking to a
+ threaded libpython
+ on OpenBSD (Tom Lane)
The failure this restriction was meant to prevent seems to not be a
- problem anymore on current OpenBSD
+ problem anymore on current OpenBSD
versions.
- Allow libpq to use TLS protocol versions beyond v1
+ Allow libpq to use TLS protocol versions beyond v1
(Noah Misch)
- For a long time, libpq was coded so that the only SSL
+ For a long time, libpq 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. (PostgreSQL servers were
+ TLS version with the server. (PostgreSQL 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.
@@ -3763,8 +3939,8 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
- However, if you use contrib/citext's
- regexp_matches() functions, see the changelog entry below
+ However, if you use contrib/citext's
+ regexp_matches() functions, see the changelog entry below
about that.
@@ -3802,7 +3978,7 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
- Our replacement implementation of snprintf() failed to
+ Our replacement implementation of snprintf() 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
@@ -3812,7 +3988,7 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
- It remains possible that some calls of the *printf()
+ It remains possible that some calls of the *printf()
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.
@@ -3822,15 +3998,15 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
- In contrib/pgcrypto, uniformly report decryption failures
- as Wrong key or corrupt data (Noah Misch)
+ In contrib/pgcrypto, uniformly report decryption failures
+ as Wrong key or corrupt data (Noah Misch)
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 pgcrypto's specific behaviors
+ While it's unknown whether pgcrypto's specific behaviors
are likewise exploitable, it seems better to avoid the risk by using a
one-size-fits-all message.
(CVE-2015-3167)
@@ -3839,16 +4015,16 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
- Fix incorrect declaration of contrib/citext's
- regexp_matches() functions (Tom Lane)
+ Fix incorrect declaration of contrib/citext's
+ regexp_matches() functions (Tom Lane)
- These functions should return setof text[], like the core
+ These functions should return setof text[], like the core
functions they are wrappers for; but they were incorrectly declared as
- returning just text[]. This mistake had two results: first,
+ returning just text[]. 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 g flag
+ should get is an empty set (zero rows). Second, the g flag
was effectively ignored, since you would get only one result array even
if there were multiple matches.
@@ -3856,16 +4032,16 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
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 PostgreSQL 9.5.
+ will not be changed by default until PostgreSQL 9.5.
In pre-9.5 branches, the old behavior exists in version 1.0 of
- the citext extension, while we have provided corrected
- declarations in version 1.1 (which is not installed by
+ the citext extension, while we have provided corrected
+ declarations in version 1.1 (which is not installed by
default). To adopt the fix in pre-9.5 branches, execute
- ALTER EXTENSION citext UPDATE TO '1.1' in each database in
- which citext is installed. (You can also update
+ ALTER EXTENSION citext UPDATE TO '1.1' in each database in
+ which citext is installed. (You can also update
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 citext's regexp_matches() functions.
+ use citext's regexp_matches() functions.
@@ -3907,7 +4083,7 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
This oversight in the planner has been observed to cause could
- not find RelOptInfo for given relids errors, but it seems possible
+ not find RelOptInfo for given relids errors, but it seems possible
that sometimes an incorrect query plan might get past that consistency
check and result in silently-wrong query output.
@@ -3935,7 +4111,7 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
This oversight has been seen to lead to failed to join all
- relations together errors in queries involving LATERAL,
+ relations together errors in queries involving LATERAL,
and that might happen in other cases as well.
@@ -3943,7 +4119,7 @@ Branch: REL9_2_STABLE [e90a629e1] 2015-09-22 14:58:38 -0700
Fix possible deadlock at startup
- when max_prepared_transactions is too small
+ when max_prepared_transactions is too small
(Heikki Linnakangas)
@@ -3964,14 +4140,14 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
- Avoid cannot GetMultiXactIdMembers() during recovery error
+ Avoid cannot GetMultiXactIdMembers() during recovery error
(Álvaro Herrera)
- Recursively fsync() the data directory after a crash
+ Recursively fsync() the data directory after a crash
(Abhijit Menon-Sen, Robert Haas)
@@ -3991,19 +4167,19 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
- Cope with unexpected signals in LockBufferForCleanup()
+ Cope with unexpected signals in LockBufferForCleanup()
(Andres Freund)
This oversight could result in spurious errors about multiple
- backends attempting to wait for pincount 1.
+ backends attempting to wait for pincount 1.
- Fix crash when doing COPY IN to a table with check
+ Fix crash when doing COPY IN to a table with check
constraints that contain whole-row references (Tom Lane)
@@ -4050,18 +4226,18 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
- ANALYZE executes index expressions many times; if there are
+ ANALYZE executes index expressions many times; if there are
slow functions in such an expression, it's desirable to be able to
- cancel the ANALYZE before that loop finishes.
+ cancel the ANALYZE before that loop finishes.
- Ensure tableoid of a foreign table is reported
- correctly when a READ COMMITTED recheck occurs after
- locking rows in SELECT FOR UPDATE, UPDATE,
- or DELETE (Etsuro Fujita)
+ Ensure tableoid of a foreign table is reported
+ correctly when a READ COMMITTED recheck occurs after
+ locking rows in SELECT FOR UPDATE, UPDATE,
+ or DELETE (Etsuro Fujita)
@@ -4074,20 +4250,20 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
- Recommend setting include_realm to 1 when using
+ Recommend setting include_realm to 1 when using
Kerberos/GSSAPI/SSPI authentication (Stephen Frost)
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 PostgreSQL 9.5.
+ it will become the default setting in PostgreSQL 9.5.
- Remove code for matching IPv4 pg_hba.conf entries to
+ Remove code for matching IPv4 pg_hba.conf entries to
IPv4-in-IPv6 addresses (Tom Lane)
@@ -4100,20 +4276,20 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
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 pg_hba.conf entries, which does not seem like a good
+ IPv4 pg_hba.conf entries, which does not seem like a good
thing to do in minor releases.)
- Report WAL flush, not insert, position in IDENTIFY_SYSTEM
+ Report WAL flush, not insert, position in IDENTIFY_SYSTEM
replication command (Heikki Linnakangas)
This avoids a possible startup failure
- in pg_receivexlog.
+ in pg_receivexlog.
@@ -4121,14 +4297,14 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
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 pg_ctl will wait for
+ service too soon; and ensure that pg_ctl will wait for
shutdown (Krystian Bigaj)
- Reduce risk of network deadlock when using libpq's
+ Reduce risk of network deadlock when using libpq's
non-blocking mode (Heikki Linnakangas)
@@ -4137,32 +4313,32 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
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 COPY FROM
- STDIN.) This worked properly in the normal blocking mode, but not
- so much in non-blocking mode. We've modified libpq
+ STDIN.) This worked properly in the normal blocking mode, but not
+ so much in non-blocking mode. We've modified libpq
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 PQconsumeInput() upon read-ready.
+ and be sure to call PQconsumeInput() upon read-ready.
- In libpq, fix misparsing of empty values in URI
+ In libpq, fix misparsing of empty values in URI
connection strings (Thomas Fanghaenel)
- Fix array handling in ecpg (Michael Meskes)
+ Fix array handling in ecpg (Michael Meskes)
- Fix psql to sanely handle URIs and conninfo strings as
- the first parameter to \connect
+ Fix psql to sanely handle URIs and conninfo strings as
+ the first parameter to \connect
(David Fetter, Andrew Dunstan, Álvaro Herrera)
@@ -4175,38 +4351,38 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
- Suppress incorrect complaints from psql on some
- platforms that it failed to write ~/.psql_history at exit
+ Suppress incorrect complaints from psql on some
+ platforms that it failed to write ~/.psql_history at exit
(Tom Lane)
This misbehavior was caused by a workaround for a bug in very old
- (pre-2006) versions of libedit. We fixed it by
+ (pre-2006) versions of libedit. We fixed it by
removing the workaround, which will cause a similar failure to appear
- for anyone still using such versions of libedit.
- Recommendation: upgrade that library, or use libreadline.
+ for anyone still using such versions of libedit.
+ Recommendation: upgrade that library, or use libreadline.
- Fix pg_dump's rule for deciding which casts are
+ Fix pg_dump's rule for deciding which casts are
system-provided casts that should not be dumped (Tom Lane)
- In pg_dump, fix failure to honor -Z
- compression level option together with -Fd
+ In pg_dump, fix failure to honor -Z
+ compression level option together with -Fd
(Michael Paquier)
- Make pg_dump consider foreign key relationships
+ Make pg_dump consider foreign key relationships
between extension configuration tables while choosing dump order
(Gilles Darold, Michael Paquier, Stephen Frost)
@@ -4219,14 +4395,14 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
- Fix dumping of views that are just VALUES(...) but have
+ Fix dumping of views that are just VALUES(...) but have
column aliases (Tom Lane)
- In pg_upgrade, force timeline 1 in the new cluster
+ In pg_upgrade, force timeline 1 in the new cluster
(Bruce Momjian)
@@ -4238,7 +4414,7 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
- In pg_upgrade, check for improperly non-connectable
+ In pg_upgrade, check for improperly non-connectable
databases before proceeding
(Bruce Momjian)
@@ -4246,28 +4422,28 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
- In pg_upgrade, quote directory paths
- properly in the generated delete_old_cluster script
+ In pg_upgrade, quote directory paths
+ properly in the generated delete_old_cluster script
(Bruce Momjian)
- In pg_upgrade, preserve database-level freezing info
+ In pg_upgrade, preserve database-level freezing info
properly
(Bruce Momjian)
This oversight could cause missing-clog-file errors for tables within
- the postgres and template1 databases.
+ the postgres and template1 databases.
- Run pg_upgrade and pg_resetxlog with
+ Run pg_upgrade and pg_resetxlog with
restricted privileges on Windows, so that they don't fail when run by
an administrator (Muhammad Asif Naeem)
@@ -4275,8 +4451,8 @@ Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
- Improve handling of readdir() failures when scanning
- directories in initdb and pg_basebackup
+ Improve handling of readdir() failures when scanning
+ directories in initdb and pg_basebackup
(Marco Nenciarini)
@@ -4288,18 +4464,18 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix failure in pg_receivexlog (Andres Freund)
+ Fix failure in pg_receivexlog (Andres Freund)
A patch merge mistake in 9.2.10 led to could not create archive
- status file errors.
+ status file errors.
- Fix slow sorting algorithm in contrib/intarray (Tom Lane)
+ Fix slow sorting algorithm in contrib/intarray (Tom Lane)
@@ -4311,7 +4487,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Update time zone data files to tzdata release 2015d
+ Update time zone data files to tzdata 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).
@@ -4346,11 +4522,11 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
However, if you are a Windows user and are using the Norwegian
- (Bokmål) locale, manual action is needed after the upgrade to
- replace any Norwegian (Bokmål)_Norway locale names stored
- in PostgreSQL system catalogs with the plain-ASCII
- alias Norwegian_Norway. For details see
-
+ (Bokmål) locale, manual action is needed after the upgrade to
+ replace any Norwegian (Bokmål)_Norway locale names stored
+ in PostgreSQL system catalogs with the plain-ASCII
+ alias Norwegian_Norway. For details see
+
@@ -4367,15 +4543,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix buffer overruns in to_char()
+ Fix buffer overruns in to_char()
(Bruce Momjian)
- When to_char() processes a numeric formatting template
- calling for a large number of digits, PostgreSQL
+ When to_char() processes a numeric formatting template
+ calling for a large number of digits, PostgreSQL
would read past the end of a buffer. When processing a crafted
- timestamp formatting template, PostgreSQL would write
+ timestamp formatting template, PostgreSQL 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.
@@ -4385,27 +4561,27 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix buffer overrun in replacement *printf() functions
+ Fix buffer overrun in replacement *printf() functions
(Tom Lane)
- PostgreSQL includes a replacement implementation
- of printf and related functions. This code will overrun
+ PostgreSQL includes a replacement implementation
+ of printf and related functions. This code will overrun
a stack buffer when formatting a floating point number (conversion
- specifiers e, E, f, F,
- g or G) with requested precision greater than
+ specifiers e, E, f, F,
+ g or G) 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 to_char() SQL function. While that is the only
- affected core PostgreSQL functionality, extension
+ the to_char() SQL function. While that is the only
+ affected core PostgreSQL functionality, extension
modules that use printf-family functions may be at risk as well.
- This issue primarily affects PostgreSQL on Windows.
- PostgreSQL uses the system implementation of these
+ This issue primarily affects PostgreSQL on Windows.
+ PostgreSQL uses the system implementation of these
functions where adequate, which it is on other modern platforms.
(CVE-2015-0242)
@@ -4413,12 +4589,12 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix buffer overruns in contrib/pgcrypto
+ Fix buffer overruns in contrib/pgcrypto
(Marko Tiikkaja, Noah Misch)
- Errors in memory size tracking within the pgcrypto
+ Errors in memory size tracking within the pgcrypto
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
@@ -4459,7 +4635,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Some server error messages show the values of columns that violate
a constraint, such as a unique constraint. If the user does not have
- SELECT privilege on all columns of the table, this could
+ SELECT 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.
@@ -4484,35 +4660,35 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Cope with the Windows locale named Norwegian (Bokmål)
+ Cope with the Windows locale named Norwegian (Bokmål)
(Heikki Linnakangas)
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, Norwegian_Norway.
+ name to a plain-ASCII alias, Norwegian_Norway.
Avoid possible data corruption if ALTER DATABASE SET
- TABLESPACE is used to move a database to a new tablespace and then
+ TABLESPACE is used to move a database to a new tablespace and then
shortly later move it back to its original tablespace (Tom Lane)
- Avoid corrupting tables when ANALYZE inside a transaction
+ Avoid corrupting tables when ANALYZE inside a transaction
is rolled back (Andres Freund, Tom Lane, Michael Paquier)
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 pg_class flags not set though they
+ with the relevant pg_class flags not set though they
should be.
@@ -4520,14 +4696,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Ensure that unlogged tables are copied correctly
- during CREATE DATABASE or ALTER DATABASE SET
- TABLESPACE (Pavan Deolasee, Andres Freund)
+ during CREATE DATABASE or ALTER DATABASE SET
+ TABLESPACE (Pavan Deolasee, Andres Freund)
- Fix DROP's dependency searching to correctly handle the
+ Fix DROP's dependency searching to correctly handle the
case where a table column is recursively visited before its table
(Petr Jelinek, Tom Lane)
@@ -4535,7 +4711,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 DROP EXTENSION unless CASCADE is
+ refuse a DROP EXTENSION unless CASCADE is
specified, which should not be required.
@@ -4547,22 +4723,22 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- In READ COMMITTED mode, queries that lock or update
+ In READ COMMITTED mode, queries that lock or update
recently-updated rows could crash as a result of this bug.
- Fix planning of SELECT FOR UPDATE when using a partial
+ Fix planning of SELECT FOR UPDATE when using a partial
index on a child table (Kyotaro Horiguchi)
- In READ COMMITTED mode, SELECT FOR UPDATE must
- also recheck the partial index's WHERE condition when
+ In READ COMMITTED mode, SELECT FOR UPDATE must
+ also recheck the partial index's WHERE condition when
rechecking a recently-updated row to see if it still satisfies the
- query's WHERE condition. This requirement was missed if the
+ query's WHERE 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.
@@ -4570,12 +4746,12 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix corner case wherein SELECT FOR UPDATE could return a row
+ Fix corner case wherein SELECT FOR UPDATE could return a row
twice, and possibly miss returning other rows (Tom Lane)
- In READ COMMITTED mode, a SELECT FOR UPDATE
+ In READ COMMITTED mode, a SELECT FOR UPDATE
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.
@@ -4585,7 +4761,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Reject duplicate column names in the referenced-columns list of
- a FOREIGN KEY declaration (David Rowley)
+ a FOREIGN KEY declaration (David Rowley)
@@ -4611,7 +4787,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix bugs in raising a numeric value to a large integral power
+ Fix bugs in raising a numeric value to a large integral power
(Tom Lane)
@@ -4624,19 +4800,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- In numeric_recv(), truncate away any fractional digits
- that would be hidden according to the value's dscale field
+ In numeric_recv(), truncate away any fractional digits
+ that would be hidden according to the value's dscale field
(Tom Lane)
- A numeric value's display scale (dscale) should
+ A numeric value's display scale (dscale) should
never be less than the number of nonzero fractional digits; but
apparently there's at least one broken client application that
- transmits binary numeric values in which that's true.
+ transmits binary numeric 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 hidden
+ The least risky fix seems to be to truncate away such hidden
digits on receipt, so that the value is indeed what it prints as.
@@ -4649,7 +4825,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Matching would often fail when the number of allowed iterations is
- limited by a ? quantifier or a bound expression.
+ limited by a ? quantifier or a bound expression.
@@ -4668,7 +4844,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix bugs in tsquery @> tsquery
+ Fix bugs in tsquery@>tsquery
operator (Heikki Linnakangas)
@@ -4699,14 +4875,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix namespace handling in xpath() (Ali Akbar)
+ Fix namespace handling in xpath() (Ali Akbar)
- Previously, the xml value resulting from
- an xpath() call would not have namespace declarations if
+ Previously, the xml value resulting from
+ an xpath() call would not have namespace declarations if
the namespace declarations were attached to an ancestor element in the
- input xml value, rather than to the specific element being
+ input xml value, rather than to the specific element being
returned. Propagate the ancestral declaration so that the result is
correct when considered in isolation.
@@ -4720,7 +4896,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- In some contexts, constructs like row_to_json(tab.*) may
+ In some contexts, constructs like row_to_json(tab.*) 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
@@ -4732,19 +4908,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix mishandling of system columns,
- particularly tableoid, in FDW queries (Etsuro Fujita)
+ particularly tableoid, in FDW queries (Etsuro Fujita)
- Avoid doing indexed_column = ANY
- (array) as an index qualifier if that leads
+ Avoid doing indexed_column = ANY
+ (array) as an index qualifier if that leads
to an inferior plan (Andrew Gierth)
- In some cases, = ANY conditions applied to non-first index
+ In some cases, = ANY 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.
@@ -4753,7 +4929,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix planner problems with nested append relations, such as inherited
- tables within UNION ALL subqueries (Tom Lane)
+ tables within UNION ALL subqueries (Tom Lane)
@@ -4766,8 +4942,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Exempt tables that have per-table cost_limit
- and/or cost_delay settings from autovacuum's global cost
+ Exempt tables that have per-table cost_limit
+ and/or cost_delay settings from autovacuum's global cost
balancing rules (Álvaro Herrera)
@@ -4793,7 +4969,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 only do anti-wraparound vacuums and
+ turned off, workers only do anti-wraparound vacuums and
not any other work.
@@ -4826,12 +5002,12 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix several cases where recovery logic improperly ignored WAL records
- for COMMIT/ABORT PREPARED (Heikki Linnakangas)
+ for COMMIT/ABORT PREPARED (Heikki Linnakangas)
The most notable oversight was
- that recovery_target_xid could not be used to stop at
+ that recovery_target_xid could not be used to stop at
a two-phase commit.
@@ -4845,7 +5021,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Avoid creating unnecessary .ready marker files for
+ Avoid creating unnecessary .ready marker files for
timeline history files (Fujii Masao)
@@ -4853,14 +5029,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix possible null pointer dereference when an empty prepared statement
- is used and the log_statement setting is mod
- or ddl (Fujii Masao)
+ is used and the log_statement setting is mod
+ or ddl (Fujii Masao)
- Change pgstat wait timeout warning message to be LOG level,
+ Change pgstat wait timeout warning message to be LOG level,
and rephrase it to be more understandable (Tom Lane)
@@ -4869,7 +5045,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 using stale statistics instead of
- current ones because stats collector is not responding.
+ current ones because stats collector is not responding.
@@ -4883,32 +5059,32 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Warn if macOS's setlocale() starts an unwanted extra
+ Warn if macOS's setlocale() starts an unwanted extra
thread inside the postmaster (Noah Misch)
- Fix processing of repeated dbname parameters
- in PQconnectdbParams() (Alex Shulgin)
+ Fix processing of repeated dbname parameters
+ in PQconnectdbParams() (Alex Shulgin)
Unexpected behavior ensued if the first occurrence
- of dbname contained a connection string or URI to be
+ of dbname contained a connection string or URI to be
expanded.
- Ensure that libpq reports a suitable error message on
+ Ensure that libpq reports a suitable error message on
unexpected socket EOF (Marko Tiikkaja, Tom Lane)
- Depending on kernel behavior, libpq might return an
+ Depending on kernel behavior, libpq might return an
empty error string rather than something useful when the server
unexpectedly closed the socket.
@@ -4916,14 +5092,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Clear any old error message during PQreset()
+ Clear any old error message during PQreset()
(Heikki Linnakangas)
- If PQreset() is called repeatedly, and the connection
+ If PQreset() is called repeatedly, and the connection
cannot be re-established, error messages from the failed connection
- attempts kept accumulating in the PGconn's error
+ attempts kept accumulating in the PGconn's error
string.
@@ -4931,32 +5107,32 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Properly handle out-of-memory conditions while parsing connection
- options in libpq (Alex Shulgin, Heikki Linnakangas)
+ options in libpq (Alex Shulgin, Heikki Linnakangas)
- Fix array overrun in ecpg's version
- of ParseDateTime() (Michael Paquier)
+ Fix array overrun in ecpg's version
+ of ParseDateTime() (Michael Paquier)
- In initdb, give a clearer error message if a password
+ In initdb, give a clearer error message if a password
file is specified but is empty (Mats Erik Andersson)
- Fix psql's \s command to work nicely with
+ Fix psql's \s command to work nicely with
libedit, and add pager support (Stepan Rutz, Tom Lane)
- When using libedit rather than readline, \s printed the
+ When using libedit rather than readline, \s 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
@@ -4966,7 +5142,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 psql
+ Multiline history entries written by older psql
versions will be read cleanly with this patch, but perhaps not
vice versa, depending on the exact libedit versions involved.
@@ -4974,17 +5150,17 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Improve consistency of parsing of psql's special
+ Improve consistency of parsing of psql's special
variables (Tom Lane)
- Allow variant spellings of on and off (such
- as 1/0) for ECHO_HIDDEN
- and ON_ERROR_ROLLBACK. Report a warning for unrecognized
- values for COMP_KEYWORD_CASE, ECHO,
- ECHO_HIDDEN, HISTCONTROL,
- ON_ERROR_ROLLBACK, and VERBOSITY. Recognize
+ Allow variant spellings of on and off (such
+ as 1/0) for ECHO_HIDDEN
+ and ON_ERROR_ROLLBACK. Report a warning for unrecognized
+ values for COMP_KEYWORD_CASE, ECHO,
+ ECHO_HIDDEN, HISTCONTROL,
+ ON_ERROR_ROLLBACK, and VERBOSITY. Recognize
all values for all these variables case-insensitively; previously
there was a mishmash of case-sensitive and case-insensitive behaviors.
@@ -4992,16 +5168,16 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix psql's expanded-mode display to work
- consistently when using border = 3
- and linestyle = ascii or unicode
+ Fix psql's expanded-mode display to work
+ consistently when using border = 3
+ and linestyle = ascii or unicode
(Stephen Frost)
- Improve performance of pg_dump when the database
+ Improve performance of pg_dump when the database
contains many instances of multiple dependency paths between the same
two objects (Tom Lane)
@@ -5009,7 +5185,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix pg_dumpall to restore its ability to dump from
+ Fix pg_dumpall to restore its ability to dump from
pre-8.1 servers (Gilles Darold)
@@ -5023,28 +5199,28 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix core dump in pg_dump --binary-upgrade on zero-column
+ Fix core dump in pg_dump --binary-upgrade on zero-column
composite type (Rushabh Lathia)
- Prevent WAL files created by pg_basebackup -x/-X from
+ Prevent WAL files created by pg_basebackup -x/-X from
being archived again when the standby is promoted (Andres Freund)
- Fix failure of contrib/auto_explain to print per-node
- timing information when doing EXPLAIN ANALYZE (Tom Lane)
+ Fix failure of contrib/auto_explain to print per-node
+ timing information when doing EXPLAIN ANALYZE (Tom Lane)
- Fix upgrade-from-unpackaged script for contrib/citext
+ Fix upgrade-from-unpackaged script for contrib/citext
(Tom Lane)
@@ -5052,7 +5228,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix block number checking
- in contrib/pageinspect's get_raw_page()
+ in contrib/pageinspect's get_raw_page()
(Tom Lane)
@@ -5064,7 +5240,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix contrib/pgcrypto's pgp_sym_decrypt()
+ Fix contrib/pgcrypto's pgp_sym_decrypt()
to not fail on messages whose length is 6 less than a power of 2
(Marko Tiikkaja)
@@ -5072,7 +5248,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix file descriptor leak in contrib/pg_test_fsync
+ Fix file descriptor leak in contrib/pg_test_fsync
(Jeff Janes)
@@ -5084,24 +5260,24 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Handle unexpected query results, especially NULLs, safely in
- contrib/tablefunc's connectby()
+ contrib/tablefunc's connectby()
(Michael Paquier)
- connectby() previously crashed if it encountered a NULL
+ connectby() previously crashed if it encountered a NULL
key value. It now prints that row but doesn't recurse further.
- Avoid a possible crash in contrib/xml2's
- xslt_process() (Mark Simonetti)
+ Avoid a possible crash in contrib/xml2's
+ xslt_process() (Mark Simonetti)
- libxslt seems to have an undocumented dependency on
+ libxslt seems to have an undocumented dependency on
the order in which resources are freed; reorder our calls to avoid a
crash.
@@ -5109,7 +5285,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Mark some contrib I/O functions with correct volatility
+ Mark some contrib I/O functions with correct volatility
properties (Tom Lane)
@@ -5143,29 +5319,29 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
With OpenLDAP versions 2.4.24 through 2.4.31,
- inclusive, PostgreSQL backends can crash at exit.
- Raise a warning during configure based on the
+ inclusive, PostgreSQL backends can crash at exit.
+ Raise a warning during configure based on the
compile-time OpenLDAP version number, and test the crashing scenario
- in the contrib/dblink regression test.
+ in the contrib/dblink regression test.
- In non-MSVC Windows builds, ensure libpq.dll is installed
+ In non-MSVC Windows builds, ensure libpq.dll is installed
with execute permissions (Noah Misch)
- Make pg_regress remove any temporary installation it
+ Make pg_regress remove any temporary installation it
created upon successful exit (Tom Lane)
This results in a very substantial reduction in disk space usage
- during make check-world, since that sequence involves
+ during make check-world, since that sequence involves
creation of numerous temporary installations.
@@ -5177,15 +5353,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Previously, PostgreSQL assumed that the UTC offset
- associated with a time zone abbreviation (such as EST)
+ Previously, PostgreSQL assumed that the UTC offset
+ associated with a time zone abbreviation (such as EST)
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, PostgreSQL will now associate the
+ In such timezones, PostgreSQL will now associate the
correct UTC offset with the abbreviation depending on the given date.
@@ -5197,9 +5373,9 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add CST (China Standard Time) to our lists.
- Remove references to ADT as Arabia Daylight Time, an
+ Remove references to ADT as Arabia Daylight Time, an
abbreviation that's been out of use since 2007; therefore, claiming
- there is a conflict with Atlantic Daylight Time doesn't seem
+ there is a conflict with Atlantic Daylight Time 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.
@@ -5208,21 +5384,21 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Update time zone data files to tzdata release 2015a.
+ Update time zone data files to tzdata release 2015a.
The IANA timezone database has adopted abbreviations of the form
- AxST/AxDT
+ AxST/AxDT
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 Default timezone abbreviation set.
- The Australia abbreviation set now contains only CST, EAST,
+ our Default timezone abbreviation set.
+ The Australia 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 Default abbreviation set.
+ Africa Standard Time in the Default abbreviation set.
@@ -5281,15 +5457,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Correctly initialize padding bytes in contrib/btree_gist
- indexes on bit columns (Heikki Linnakangas)
+ Correctly initialize padding bytes in contrib/btree_gist
+ indexes on bit columns (Heikki Linnakangas)
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 bit or bit varying
- columns should REINDEX those indexes after installing this
+ Users with GiST indexes on bit or bit varying
+ columns should REINDEX those indexes after installing this
update.
@@ -5335,7 +5511,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix possibly-incorrect cache invalidation during nested calls
- to ReceiveSharedInvalidMessages (Andres Freund)
+ to ReceiveSharedInvalidMessages (Andres Freund)
@@ -5347,14 +5523,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This oversight could result in variable not found in subplan
- target lists errors, or in silently wrong query results.
+ target lists errors, or in silently wrong query results.
- Fix could not find pathkey item to sort planner failures
- with UNION ALL over subqueries reading from tables with
+ Fix could not find pathkey item to sort planner failures
+ with UNION ALL over subqueries reading from tables with
inheritance children (Tom Lane)
@@ -5375,7 +5551,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Improve planner to drop constant-NULL inputs
- of AND/OR when possible (Tom Lane)
+ of AND/OR when possible (Tom Lane)
@@ -5387,13 +5563,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix identification of input type category in to_json()
+ Fix identification of input type category in to_json()
and friends (Tom Lane)
- This is known to have led to inadequate quoting of money
- fields in the JSON result, and there may have been wrong
+ This is known to have led to inadequate quoting of money
+ fields in the JSON result, and there may have been wrong
results for other data types as well.
@@ -5408,13 +5584,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 missing chunk number 0
- for toast value ... when the now-dangling pointer is used.
+ for toast value ... when the now-dangling pointer is used.
- Fix record type has not been registered failures with
+ Fix record type has not been registered failures with
whole-row references to the output of Append plan nodes (Tom Lane)
@@ -5429,7 +5605,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix query-lifespan memory leak while evaluating the arguments for a
- function in FROM (Tom Lane)
+ function in FROM (Tom Lane)
@@ -5442,7 +5618,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix data encoding error in hungarian.stop (Tom Lane)
+ Fix data encoding error in hungarian.stop (Tom Lane)
@@ -5463,19 +5639,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This could cause problems (at least spurious warnings, and at worst an
- infinite loop) if CREATE INDEX or CLUSTER were
+ infinite loop) if CREATE INDEX or CLUSTER were
done later in the same transaction.
- Clear pg_stat_activity.xact_start
- during PREPARE TRANSACTION (Andres Freund)
+ Clear pg_stat_activity.xact_start
+ during PREPARE TRANSACTION (Andres Freund)
- After the PREPARE, the originating session is no longer in
+ After the PREPARE, the originating session is no longer in
a transaction, so it should not continue to display a transaction
start time.
@@ -5483,7 +5659,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix REASSIGN OWNED to not fail for text search objects
+ Fix REASSIGN OWNED to not fail for text search objects
(Álvaro Herrera)
@@ -5495,14 +5671,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This ensures that the postmaster will properly clean up after itself
- if, for example, it receives SIGINT while still
+ if, for example, it receives SIGINT while still
starting up.
- Fix client host name lookup when processing pg_hba.conf
+ Fix client host name lookup when processing pg_hba.conf
entries that specify host names instead of IP addresses (Tom Lane)
@@ -5516,21 +5692,21 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Allow the root user to use postgres -C variable and
- postgres --describe-config (MauMau)
+ Allow the root user to use postgres -C variable and
+ postgres --describe-config (MauMau)
The prohibition on starting the server as root does not need to extend
to these operations, and relaxing it prevents failure
- of pg_ctl in some scenarios.
+ of pg_ctl in some scenarios.
Secure Unix-domain sockets of temporary postmasters started during
- make check (Noah Misch)
+ make check (Noah Misch)
@@ -5539,16 +5715,16 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 /tmp. The hazard remains however on platforms where
+ of /tmp. The hazard remains however on platforms where
Unix sockets are not supported, notably Windows, because then the
temporary postmaster must accept local TCP connections.
A useful side effect of this change is to simplify
- make check testing in builds that
- override DEFAULT_PGSOCKET_DIR. Popular non-default values
- like /var/run/postgresql are often not writable by the
+ make check testing in builds that
+ override DEFAULT_PGSOCKET_DIR. Popular non-default values
+ like /var/run/postgresql are often not writable by the
build user, requiring workarounds that will no longer be necessary.
@@ -5584,15 +5760,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- This oversight could cause initdb
- and pg_upgrade to fail on Windows, if the installation
- path contained both spaces and @ signs.
+ This oversight could cause initdb
+ and pg_upgrade to fail on Windows, if the installation
+ path contained both spaces and @ signs.
- Fix linking of libpython on macOS (Tom Lane)
+ Fix linking of libpython on macOS (Tom Lane)
@@ -5603,17 +5779,17 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Avoid buffer bloat in libpq when the server
+ Avoid buffer bloat in libpq when the server
consistently sends data faster than the client can absorb it
(Shin-ichi Morita, Tom Lane)
- libpq could be coerced into enlarging its input buffer
+ libpq could be coerced into enlarging its input buffer
until it runs out of memory (which would be reported misleadingly
- as lost synchronization with server). Under ordinary
+ as lost synchronization with server). Under ordinary
circumstances it's quite far-fetched that data could be continuously
- transmitted more quickly than the recv() loop can
+ transmitted more quickly than the recv() loop can
absorb it, but this has been observed when the client is artificially
slowed by scheduler constraints.
@@ -5621,15 +5797,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Ensure that LDAP lookup attempts in libpq time out as
+ Ensure that LDAP lookup attempts in libpq time out as
intended (Laurenz Albe)
- Fix ecpg to do the right thing when an array
- of char * is the target for a FETCH statement returning more
+ Fix ecpg to do the right thing when an array
+ of char * is the target for a FETCH statement returning more
than one row, as well as some other array-handling fixes
(Ashutosh Bapat)
@@ -5637,52 +5813,52 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix pg_restore's processing of old-style large object
+ Fix pg_restore's processing of old-style large object
comments (Tom Lane)
A direct-to-database restore from an archive file generated by a
- pre-9.0 version of pg_dump would usually fail if the
+ pre-9.0 version of pg_dump would usually fail if the
archive contained more than a few comments for large objects.
- Fix pg_upgrade for cases where the new server creates
+ Fix pg_upgrade for cases where the new server creates
a TOAST table but the old version did not (Bruce Momjian)
- This rare situation would manifest as relation OID mismatch
+ This rare situation would manifest as relation OID mismatch
errors.
- Prevent contrib/auto_explain from changing the output of
- a user's EXPLAIN (Tom Lane)
+ Prevent contrib/auto_explain from changing the output of
+ a user's EXPLAIN (Tom Lane)
- If auto_explain is active, it could cause
- an EXPLAIN (ANALYZE, TIMING OFF) command to nonetheless
+ If auto_explain is active, it could cause
+ an EXPLAIN (ANALYZE, TIMING OFF) command to nonetheless
print timing information.
- Fix query-lifespan memory leak in contrib/dblink
+ Fix query-lifespan memory leak in contrib/dblink
(MauMau, Joe Conway)
- In contrib/pgcrypto functions, ensure sensitive
+ In contrib/pgcrypto functions, ensure sensitive
information is cleared from stack variables before returning
(Marko Kreen)
@@ -5691,27 +5867,27 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Prevent use of already-freed memory in
- contrib/pgstattuple's pgstat_heap()
+ contrib/pgstattuple's pgstat_heap()
(Noah Misch)
- In contrib/uuid-ossp, cache the state of the OSSP UUID
+ In contrib/uuid-ossp, cache the state of the OSSP UUID
library across calls (Tom Lane)
This improves the efficiency of UUID generation and reduces the amount
- of entropy drawn from /dev/urandom, on platforms that
+ of entropy drawn from /dev/urandom, on platforms that
have that.
- Update time zone data files to tzdata release 2014e
+ Update time zone data files to tzdata release 2014e
for DST law changes in Crimea, Egypt, and Morocco.
@@ -5771,7 +5947,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Avoid race condition in checking transaction commit status during
- receipt of a NOTIFY message (Marko Tiikkaja)
+ receipt of a NOTIFY message (Marko Tiikkaja)
@@ -5795,7 +5971,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Remove incorrect code that tried to allow OVERLAPS with
+ Remove incorrect code that tried to allow OVERLAPS with
single-element row arguments (Joshua Yanovski)
@@ -5808,17 +5984,17 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Avoid getting more than AccessShareLock when de-parsing a
+ Avoid getting more than AccessShareLock when de-parsing a
rule or view (Dean Rasheed)
- This oversight resulted in pg_dump unexpectedly
- acquiring RowExclusiveLock locks on tables mentioned as
- the targets of INSERT/UPDATE/DELETE
+ This oversight resulted in pg_dump unexpectedly
+ acquiring RowExclusiveLock locks on tables mentioned as
+ the targets of INSERT/UPDATE/DELETE
commands in rules. While usually harmless, that could interfere with
concurrent transactions that tried to acquire, for example,
- ShareLock on those tables.
+ ShareLock on those tables.
@@ -5837,8 +6013,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix walsender's failure to shut down cleanly when client
- is pg_receivexlog (Fujii Masao)
+ Fix walsender's failure to shut down cleanly when client
+ is pg_receivexlog (Fujii Masao)
@@ -5858,13 +6034,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Prevent interrupts while reporting non-ERROR messages
+ Prevent interrupts while reporting non-ERROR messages
(Tom Lane)
This guards against rare server-process freezeups due to recursive
- entry to syslog(), and perhaps other related problems.
+ entry to syslog(), and perhaps other related problems.
@@ -5877,13 +6053,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix tracking of psql script line numbers
- during \copy from out-of-line data
+ Fix tracking of psql script line numbers
+ during \copy from out-of-line data
(Kumar Rajeev Rastogi, Amit Khandekar)
- \copy ... from incremented the script file line number
+ \copy ... from 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.
@@ -5892,14 +6068,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Prevent intermittent could not reserve shared memory region
+ Prevent intermittent could not reserve shared memory region
failures on recent Windows versions (MauMau)
- Update time zone data files to tzdata release 2014a
+ Update time zone data files to tzdata release 2014a
for DST law changes in Fiji and Turkey, plus historical changes in
Israel and Ukraine.
@@ -5945,19 +6121,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Shore up GRANT ... WITH ADMIN OPTION restrictions
+ Shore up GRANT ... WITH ADMIN OPTION restrictions
(Noah Misch)
- Granting a role without ADMIN OPTION is supposed to
+ Granting a role without ADMIN OPTION is supposed to
prevent the grantee from adding or removing members from the granted
role, but this restriction was easily bypassed by doing SET
- ROLE first. The security impact is mostly that a role member can
+ ROLE 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 SECURITY DEFINER functions.
+ anyway by creating views or SECURITY DEFINER functions.
(CVE-2014-0060)
@@ -5970,7 +6146,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
The primary role of PL validator functions is to be called implicitly
- during CREATE FUNCTION, but they are also normal SQL
+ during CREATE FUNCTION, 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.
@@ -5990,7 +6166,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 CREATE INDEX,
+ than other parts. At least in the case of CREATE INDEX,
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.
@@ -6004,12 +6180,12 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- The MAXDATELEN constant was too small for the longest
- possible value of type interval, allowing a buffer overrun
- in interval_out(). Although the datetime input
+ The MAXDATELEN constant was too small for the longest
+ possible value of type interval, allowing a buffer overrun
+ in interval_out(). 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 ecpg
+ input containing a very long timezone name. The ecpg
library contained these vulnerabilities along with some of its own.
(CVE-2014-0063)
@@ -6036,7 +6212,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Use strlcpy() and related functions to provide a clear
+ Use strlcpy() 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
@@ -6048,35 +6224,35 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Avoid crashing if crypt() returns NULL (Honza Horak,
+ Avoid crashing if crypt() returns NULL (Honza Horak,
Bruce Momjian)
- There are relatively few scenarios in which crypt()
- could return NULL, but contrib/chkpass would crash
+ There are relatively few scenarios in which crypt()
+ could return NULL, but contrib/chkpass would crash
if it did. One practical case in which this could be an issue is
- if libc is configured to refuse to execute unapproved
- hashing algorithms (e.g., FIPS mode).
+ if libc is configured to refuse to execute unapproved
+ hashing algorithms (e.g., FIPS mode).
(CVE-2014-0066)
- Document risks of make check in the regression testing
+ Document risks of make check in the regression testing
instructions (Noah Misch, Tom Lane)
- Since the temporary server started by make check
- uses trust authentication, another user on the same machine
+ Since the temporary server started by make check
+ uses trust 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
- make check when there are untrusted users on the
+ make check when there are untrusted users on the
same machine.
(CVE-2014-0067)
@@ -6091,7 +6267,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 bloat
+ this error has been observed to result in significant bloat
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
@@ -6111,20 +6287,20 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
was already consistent at the start of replay, thus possibly allowing
hot-standby queries before the database was really consistent. Other
symptoms such as PANIC: WAL contains references to invalid
- pages were also possible.
+ pages were also possible.
Fix improper locking of btree index pages while replaying
- a VACUUM operation in hot-standby mode (Andres Freund,
+ a VACUUM operation in hot-standby mode (Andres Freund,
Heikki Linnakangas, Tom Lane)
This error could result in PANIC: WAL contains references to
- invalid pages failures.
+ invalid pages failures.
@@ -6142,8 +6318,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- When pause_at_recovery_target
- and recovery_target_inclusive are both set, ensure the
+ When pause_at_recovery_target
+ and recovery_target_inclusive are both set, ensure the
target record is applied before pausing, not after (Heikki
Linnakangas)
@@ -6156,7 +6332,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Ensure that signal handlers don't attempt to use the
- process's MyProc pointer after it's no longer valid.
+ process's MyProc pointer after it's no longer valid.
@@ -6169,19 +6345,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix unsafe references to errno within error reporting
+ Fix unsafe references to errno within error reporting
logic (Christian Kruse)
This would typically lead to odd behaviors such as missing or
- inappropriate HINT fields.
+ inappropriate HINT fields.
- Fix possible crashes from using ereport() too early
+ Fix possible crashes from using ereport() too early
during server startup (Tom Lane)
@@ -6205,7 +6381,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix length checking for Unicode identifiers (U&"..."
+ Fix length checking for Unicode identifiers (U&"..."
syntax) containing escapes (Tom Lane)
@@ -6225,7 +6401,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 DROP ROLE.
+ list of role identifiers was permitted, such as DROP ROLE.
@@ -6239,19 +6415,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix possible crash due to invalid plan for nested sub-selects, such
- as WHERE (... x IN (SELECT ...) ...) IN (SELECT ...)
+ as WHERE (... x IN (SELECT ...) ...) IN (SELECT ...)
(Tom Lane)
- Fix UPDATE/DELETE of an inherited target table
- that has UNION ALL subqueries (Tom Lane)
+ Fix UPDATE/DELETE of an inherited target table
+ that has UNION ALL subqueries (Tom Lane)
- Without this fix, UNION ALL subqueries aren't correctly
+ Without this fix, UNION ALL 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).
@@ -6260,12 +6436,12 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Ensure that ANALYZE creates statistics for a table column
- even when all the values in it are too wide (Tom Lane)
+ Ensure that ANALYZE creates statistics for a table column
+ even when all the values in it are too wide (Tom Lane)
- ANALYZE intentionally omits very wide values from its
+ ANALYZE 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.
@@ -6273,21 +6449,21 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- In ALTER TABLE ... SET TABLESPACE, allow the database's
+ In ALTER TABLE ... SET TABLESPACE, allow the database's
default tablespace to be used without a permissions check
(Stephen Frost)
- CREATE TABLE has always allowed such usage,
- but ALTER TABLE didn't get the memo.
+ CREATE TABLE has always allowed such usage,
+ but ALTER TABLE didn't get the memo.
- Fix cannot accept a set error when some arms of
- a CASE return a set and others don't (Tom Lane)
+ Fix cannot accept a set error when some arms of
+ a CASE return a set and others don't (Tom Lane)
@@ -6319,12 +6495,12 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix possible misbehavior in plainto_tsquery()
+ Fix possible misbehavior in plainto_tsquery()
(Heikki Linnakangas)
- Use memmove() not memcpy() for copying
+ Use memmove() not memcpy() for copying
overlapping memory regions. There have been no field reports of
this actually causing trouble, but it's certainly risky.
@@ -6332,8 +6508,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix placement of permissions checks in pg_start_backup()
- and pg_stop_backup() (Andres Freund, Magnus Hagander)
+ Fix placement of permissions checks in pg_start_backup()
+ and pg_stop_backup() (Andres Freund, Magnus Hagander)
@@ -6344,44 +6520,44 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Accept SHIFT_JIS as an encoding name for locale checking
+ Accept SHIFT_JIS as an encoding name for locale checking
purposes (Tatsuo Ishii)
- Fix *-qualification of named parameters in SQL-language
+ Fix *-qualification of named parameters in SQL-language
functions (Tom Lane)
Given a composite-type parameter
- named foo, $1.* worked fine,
- but foo.* not so much.
+ named foo, $1.* worked fine,
+ but foo.* not so much.
- Fix misbehavior of PQhost() on Windows (Fujii Masao)
+ Fix misbehavior of PQhost() on Windows (Fujii Masao)
- It should return localhost if no host has been specified.
+ It should return localhost if no host has been specified.
- Improve error handling in libpq and psql
- for failures during COPY TO STDOUT/FROM STDIN (Tom Lane)
+ Improve error handling in libpq and psql
+ for failures during COPY TO STDOUT/FROM STDIN (Tom Lane)
In particular this fixes an infinite loop that could occur in 9.2 and
up if the server connection was lost during COPY FROM
- STDIN. Variants of that scenario might be possible in older
+ STDIN. Variants of that scenario might be possible in older
versions, or with other client applications.
@@ -6389,14 +6565,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix incorrect translation handling in
- some psql \d commands
+ some psql\d commands
(Peter Eisentraut, Tom Lane)
- Ensure pg_basebackup's background process is killed
+ Ensure pg_basebackup's background process is killed
when exiting its foreground process (Magnus Hagander)
@@ -6404,7 +6580,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix possible incorrect printing of filenames
- in pg_basebackup's verbose mode (Magnus Hagander)
+ in pg_basebackup's verbose mode (Magnus Hagander)
@@ -6417,20 +6593,20 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix misaligned descriptors in ecpg (MauMau)
+ Fix misaligned descriptors in ecpg (MauMau)
- In ecpg, handle lack of a hostname in the connection
+ In ecpg, handle lack of a hostname in the connection
parameters properly (Michael Meskes)
- Fix performance regression in contrib/dblink connection
+ Fix performance regression in contrib/dblink connection
startup (Joe Conway)
@@ -6441,15 +6617,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- In contrib/isn, fix incorrect calculation of the check
+ In contrib/isn, fix incorrect calculation of the check
digit for ISMN values (Fabien Coelho)
- Fix contrib/pg_stat_statement's handling
- of CURRENT_DATE and related constructs (Kyotaro
+ Fix contrib/pg_stat_statement's handling
+ of CURRENT_DATE and related constructs (Kyotaro
Horiguchi)
@@ -6463,28 +6639,28 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- In Mingw and Cygwin builds, install the libpq DLL
- in the bin directory (Andrew Dunstan)
+ In Mingw and Cygwin builds, install the libpq DLL
+ in the bin directory (Andrew Dunstan)
This duplicates what the MSVC build has long done. It should fix
- problems with programs like psql failing to start
+ problems with programs like psql failing to start
because they can't find the DLL.
- Avoid using the deprecated dllwrap tool in Cygwin builds
+ Avoid using the deprecated dllwrap tool in Cygwin builds
(Marco Atzeri)
- Don't generate plain-text HISTORY
- and src/test/regress/README files anymore (Tom Lane)
+ Don't generate plain-text HISTORY
+ and src/test/regress/README files anymore (Tom Lane)
@@ -6493,20 +6669,20 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 INSTALL file will still be maintained, as
+ The plain-text INSTALL file will still be maintained, as
there is arguably a use-case for that.
- Update time zone data files to tzdata release 2013i
+ Update time zone data files to tzdata release 2013i
for DST law changes in Jordan and historical changes in Cuba.
- In addition, the zones Asia/Riyadh87,
- Asia/Riyadh88, and Asia/Riyadh89 have been
+ In addition, the zones Asia/Riyadh87,
+ Asia/Riyadh88, and Asia/Riyadh89 have been
removed, as they are no longer maintained by IANA, and never
represented actual civil timekeeping practice.
@@ -6558,19 +6734,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix VACUUM's tests to see whether it can
- update relfrozenxid (Andres Freund)
+ Fix VACUUM's tests to see whether it can
+ update relfrozenxid (Andres Freund)
- In some cases VACUUM (either manual or autovacuum) could
- incorrectly advance a table's relfrozenxid value,
+ In some cases VACUUM (either manual or autovacuum) could
+ incorrectly advance a table's relfrozenxid 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 could not access status of transaction errors as a
+ to get could not access status of transaction 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.
@@ -6578,18 +6754,18 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
The issue can be ameliorated by, after upgrading, vacuuming all tables
in all databases while having vacuum_freeze_table_age
+ linkend="guc-vacuum-freeze-table-age">vacuum_freeze_table_age
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
- SELECT txid_current() < 2^31).
+ SELECT txid_current() < 2^31).
- Fix initialization of pg_clog and pg_subtrans
+ Fix initialization of pg_clog and pg_subtrans
during hot standby startup (Andres Freund, Heikki Linnakangas)
@@ -6620,13 +6796,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This could lead to corruption of the lock data structures in shared
- memory, causing lock already held and other odd errors.
+ memory, causing lock already held and other odd errors.
- Truncate pg_multixact contents during WAL replay
+ Truncate pg_multixact contents during WAL replay
(Andres Freund)
@@ -6637,14 +6813,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Ensure an anti-wraparound VACUUM counts a page as scanned
+ Ensure an anti-wraparound VACUUM counts a page as scanned
when it's only verified that no tuples need freezing (Sergey
Burladyan, Jeff Janes)
This bug could result in failing to
- advance relfrozenxid, so that the table would still be
+ advance relfrozenxid, 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.
@@ -6663,15 +6839,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix unexpected spgdoinsert() failure error during SP-GiST
+ Fix unexpected spgdoinsert() failure error during SP-GiST
index creation (Teodor Sigaev)
- Avoid flattening a subquery whose SELECT list contains a
- volatile function wrapped inside a sub-SELECT (Tom Lane)
+ Avoid flattening a subquery whose SELECT list contains a
+ volatile function wrapped inside a sub-SELECT (Tom Lane)
@@ -6688,14 +6864,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This error could lead to incorrect plans for queries involving
- multiple levels of subqueries within JOIN syntax.
+ multiple levels of subqueries within JOIN syntax.
Fix incorrect planning in cases where the same non-strict expression
- appears in multiple WHERE and outer JOIN
+ appears in multiple WHERE and outer JOIN
equality clauses (Tom Lane)
@@ -6763,13 +6939,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix array slicing of int2vector and oidvector values
+ Fix array slicing of int2vector and oidvector values
(Tom Lane)
Expressions of this kind are now implicitly promoted to
- regular int2 or oid arrays.
+ regular int2 or oid arrays.
@@ -6783,7 +6959,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 timeofday function to honor the simple GMT offset
+ the timeofday function to honor the simple GMT offset
zone.
@@ -6797,7 +6973,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Properly quote generated command lines in pg_ctl
+ Properly quote generated command lines in pg_ctl
(Naoya Anzai and Tom Lane)
@@ -6808,10 +6984,10 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix pg_dumpall to work when a source database
+ Fix pg_dumpall to work when a source database
sets default_transaction_read_only
- via ALTER DATABASE SET (Kevin Grittner)
+ linkend="guc-default-transaction-read-only">default_transaction_read_only
+ via ALTER DATABASE SET (Kevin Grittner)
@@ -6821,28 +6997,28 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Make ecpg search for quoted cursor names
+ Make ecpg search for quoted cursor names
case-sensitively (Zoltán Böszörményi)
- Fix ecpg's processing of lists of variables
- declared varchar (Zoltán Böszörményi)
+ Fix ecpg's processing of lists of variables
+ declared varchar (Zoltán Böszörményi)
- Make contrib/lo defend against incorrect trigger definitions
+ Make contrib/lo defend against incorrect trigger definitions
(Marc Cousin)
- Update time zone data files to tzdata release 2013h
+ Update time zone data files to tzdata release 2013h
for DST law changes in Argentina, Brazil, Jordan, Libya,
Liechtenstein, Morocco, and Palestine. Also, new timezone
abbreviations WIB, WIT, WITA for Indonesia.
@@ -6894,7 +7070,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- PostgreSQL case-folds non-ASCII characters only
+ PostgreSQL case-folds non-ASCII characters only
when using a single-byte server encoding.
@@ -6909,7 +7085,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix checkpoint memory leak in background writer when wal_level =
- hot_standby (Naoya Anzai)
+ hot_standby (Naoya Anzai)
@@ -6922,7 +7098,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix memory overcommit bug when work_mem is using more
+ Fix memory overcommit bug when work_mem is using more
than 24GB of memory (Stephen Frost)
@@ -6964,58 +7140,58 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Previously tests like col IS NOT TRUE and col IS
- NOT FALSE did not properly factor in NULL values when estimating
+ Previously tests like col IS NOT TRUE and col IS
+ NOT FALSE did not properly factor in NULL values when estimating
plan costs.
- Fix accounting for qualifier evaluation costs in UNION ALL
+ Fix accounting for qualifier evaluation costs in UNION ALL
and inheritance queries (Tom Lane)
This fixes cases where suboptimal query plans could be chosen if
- some WHERE clauses are expensive to calculate.
+ some WHERE clauses are expensive to calculate.
- Prevent pushing down WHERE clauses into unsafe
- UNION/INTERSECT subqueries (Tom Lane)
+ Prevent pushing down WHERE clauses into unsafe
+ UNION/INTERSECT subqueries (Tom Lane)
- Subqueries of a UNION or INTERSECT that
+ Subqueries of a UNION or INTERSECT that
contain set-returning functions or volatile functions in their
- SELECT lists could be improperly optimized, leading to
+ SELECT lists could be improperly optimized, leading to
run-time errors or incorrect query results.
- Fix rare case of failed to locate grouping columns
+ Fix rare case of failed to locate grouping columns
planner failure (Tom Lane)
- Fix pg_dump of foreign tables with dropped columns (Andrew Dunstan)
+ Fix pg_dump of foreign tables with dropped columns (Andrew Dunstan)
- Previously such cases could cause a pg_upgrade error.
+ Previously such cases could cause a pg_upgrade error.
- Reorder pg_dump processing of extension-related
+ Reorder pg_dump processing of extension-related
rules and event triggers (Joe Conway)
@@ -7023,7 +7199,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Force dumping of extension tables if specified by pg_dump
- -t or -n (Joe Conway)
+ -t or -n (Joe Conway)
@@ -7036,25 +7212,25 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix pg_restore -l with the directory archive to display
+ Fix pg_restore -l with the directory archive to display
the correct format name (Fujii Masao)
- Properly record index comments created using UNIQUE
- and PRIMARY KEY syntax (Andres Freund)
+ Properly record index comments created using UNIQUE
+ and PRIMARY KEY syntax (Andres Freund)
- This fixes a parallel pg_restore failure.
+ This fixes a parallel pg_restore failure.
- Cause pg_basebackup -x with an empty xlog directory
+ Cause pg_basebackup -x with an empty xlog directory
to throw an error rather than crashing (Magnus Hagander, Haruka
Takatsuka)
@@ -7093,13 +7269,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix REINDEX TABLE and REINDEX DATABASE
+ Fix REINDEX TABLE and REINDEX DATABASE
to properly revalidate constraints and mark invalidated indexes as
valid (Noah Misch)
- REINDEX INDEX has always worked properly.
+ REINDEX INDEX has always worked properly.
@@ -7112,7 +7288,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix possible deadlock during concurrent CREATE INDEX
- CONCURRENTLY operations (Tom Lane)
+ CONCURRENTLY operations (Tom Lane)
@@ -7124,7 +7300,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix regexp_matches() handling of zero-length matches
+ Fix regexp_matches() handling of zero-length matches
(Jeevan Chalke)
@@ -7148,14 +7324,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Prevent CREATE FUNCTION from checking SET
+ Prevent CREATE FUNCTION from checking SET
variables unless function body checking is enabled (Tom Lane)
- Allow ALTER DEFAULT PRIVILEGES to operate on schemas
+ Allow ALTER DEFAULT PRIVILEGES to operate on schemas
without requiring CREATE permission (Tom Lane)
@@ -7167,31 +7343,31 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Specifically, lessen keyword restrictions for role names, language
- names, EXPLAIN and COPY options, and
- SET values. This allows COPY ... (FORMAT
- BINARY) to work as expected; previously BINARY needed
+ names, EXPLAIN and COPY options, and
+ SET values. This allows COPY ... (FORMAT
+ BINARY) to work as expected; previously BINARY needed
to be quoted.
- Print proper line number during COPY failure (Heikki
+ Print proper line number during COPY failure (Heikki
Linnakangas)
- Fix pgp_pub_decrypt() so it works for secret keys with
+ Fix pgp_pub_decrypt() so it works for secret keys with
passwords (Marko Kreen)
- Make pg_upgrade use pg_dump
- --quote-all-identifiers to avoid problems with keyword changes
+ Make pg_upgrade use pg_dump
+ --quote-all-identifiers to avoid problems with keyword changes
between releases (Tom Lane)
@@ -7205,7 +7381,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Ensure that VACUUM ANALYZE still runs the ANALYZE phase
+ Ensure that VACUUM ANALYZE still runs the ANALYZE phase
if its attempt to truncate the file is cancelled due to lock conflicts
(Kevin Grittner)
@@ -7214,28 +7390,28 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Avoid possible failure when performing transaction control commands (e.g
- ROLLBACK) in prepared queries (Tom Lane)
+ ROLLBACK) in prepared queries (Tom Lane)
Ensure that floating-point data input accepts standard spellings
- of infinity on all platforms (Tom Lane)
+ of infinity on all platforms (Tom Lane)
- The C99 standard says that allowable spellings are inf,
- +inf, -inf, infinity,
- +infinity, and -infinity. Make sure we
- recognize these even if the platform's strtod function
+ The C99 standard says that allowable spellings are inf,
+ +inf, -inf, infinity,
+ +infinity, and -infinity. Make sure we
+ recognize these even if the platform's strtod function
doesn't.
- Avoid unnecessary reporting when track_activities is off
+ Avoid unnecessary reporting when track_activities is off
(Tom Lane)
@@ -7249,7 +7425,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Prevent crash when psql's PSQLRC variable
+ Prevent crash when psql's PSQLRC variable
contains a tilde (Bruce Momjian)
@@ -7262,7 +7438,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Update time zone data files to tzdata release 2013d
+ Update time zone data files to tzdata release 2013d
for DST law changes in Israel, Morocco, Palestine, and Paraguay.
Also, historical zone data corrections for Macquarie Island.
@@ -7297,7 +7473,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
However, this release corrects several errors in management of GiST
indexes. After installing this update, it is advisable to
- REINDEX any GiST indexes that meet one or more of the
+ REINDEX any GiST indexes that meet one or more of the
conditions described below.
@@ -7321,7 +7497,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
A connection request containing a database name that begins with
- - could be crafted to damage or destroy
+ - could be crafted to damage or destroy
files within the server's data directory, even if the request is
eventually rejected. (CVE-2013-1899)
@@ -7335,9 +7511,9 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This avoids a scenario wherein random numbers generated by
- contrib/pgcrypto functions might be relatively easy for
+ contrib/pgcrypto functions might be relatively easy for
another database user to guess. The risk is only significant when
- the postmaster is configured with ssl = on
+ the postmaster is configured with ssl = on
but most connections don't use SSL encryption. (CVE-2013-1900)
@@ -7350,7 +7526,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
An unprivileged database user could exploit this mistake to call
- pg_start_backup() or pg_stop_backup(),
+ pg_start_backup() or pg_stop_backup(),
thus possibly interfering with creation of routine backups.
(CVE-2013-1901)
@@ -7358,32 +7534,32 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix GiST indexes to not use fuzzy geometric comparisons when
+ Fix GiST indexes to not use fuzzy geometric comparisons when
it's not appropriate to do so (Alexander Korotkov)
- The core geometric types perform comparisons using fuzzy
- equality, but gist_box_same must do exact comparisons,
+ The core geometric types perform comparisons using fuzzy
+ equality, but gist_box_same must do exact comparisons,
else GiST indexes using it might become inconsistent. After installing
- this update, users should REINDEX any GiST indexes on
- box, polygon, circle, or point
- columns, since all of these use gist_box_same.
+ this update, users should REINDEX any GiST indexes on
+ box, polygon, circle, or point
+ columns, since all of these use gist_box_same.
Fix erroneous range-union and penalty logic in GiST indexes that use
- contrib/btree_gist for variable-width data types, that is
- text, bytea, bit, and numeric
+ contrib/btree_gist for variable-width data types, that is
+ text, bytea, bit, and numeric
columns (Tom Lane)
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 REINDEX such indexes
+ index bloat. Users are advised to REINDEX such indexes
after installing this update.
@@ -7398,21 +7574,21 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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
- REINDEX multi-column GiST indexes after installing this
+ REINDEX multi-column GiST indexes after installing this
update.
- Fix gist_point_consistent
+ Fix gist_point_consistent
to handle fuzziness consistently (Alexander Korotkov)
- Index scans on GiST indexes on point columns would sometimes
+ Index scans on GiST indexes on point columns would sometimes
yield results different from a sequential scan, because
- gist_point_consistent disagreed with the underlying
+ gist_point_consistent disagreed with the underlying
operator code about whether to do comparisons exactly or fuzzily.
@@ -7423,7 +7599,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- This bug could result in incorrect local pin count errors
+ This bug could result in incorrect local pin count errors
during replay, making recovery impossible.
@@ -7431,7 +7607,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Ensure we do crash recovery before entering archive recovery, if the
- database was not stopped cleanly and a recovery.conf file
+ database was not stopped cleanly and a recovery.conf file
is present (Heikki Linnakangas, Kyotaro Horiguchi, Mitsumasa Kondo)
@@ -7451,14 +7627,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix race condition in DELETE RETURNING (Tom Lane)
+ Fix race condition in DELETE RETURNING (Tom Lane)
- Under the right circumstances, DELETE RETURNING could
+ Under the right circumstances, DELETE RETURNING 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 RETURNING output, or
+ meanwhile, this would lead to garbage RETURNING output, or
even a crash.
@@ -7479,20 +7655,20 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix to_char() to use ASCII-only case-folding rules where
+ Fix to_char() to use ASCII-only case-folding rules where
appropriate (Tom Lane)
This fixes misbehavior of some template patterns that should be
- locale-independent, but mishandled I and
- i in Turkish locales.
+ locale-independent, but mishandled I and
+ i in Turkish locales.
- Fix unwanted rejection of timestamp 1999-12-31 24:00:00
+ Fix unwanted rejection of timestamp 1999-12-31 24:00:00
(Tom Lane)
@@ -7506,8 +7682,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix logic error when a single transaction does UNLISTEN
- then LISTEN (Tom Lane)
+ Fix logic error when a single transaction does UNLISTEN
+ then LISTEN (Tom Lane)
@@ -7525,14 +7701,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix performance issue in EXPLAIN (ANALYZE, TIMING OFF)
+ Fix performance issue in EXPLAIN (ANALYZE, TIMING OFF)
(Pavel Stehule)
- Remove useless picksplit doesn't support secondary split log
+ Remove useless picksplit doesn't support secondary split log
messages (Josh Hansen, Tom Lane)
@@ -7547,7 +7723,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Remove vestigial secondary-split support in
- gist_box_picksplit() (Tom Lane)
+ gist_box_picksplit() (Tom Lane)
@@ -7566,29 +7742,29 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Eliminate memory leaks in PL/Perl's spi_prepare() function
+ Eliminate memory leaks in PL/Perl's spi_prepare() function
(Alex Hunsaker, Tom Lane)
- Fix pg_dumpall to handle database names containing
- = correctly (Heikki Linnakangas)
+ Fix pg_dumpall to handle database names containing
+ = correctly (Heikki Linnakangas)
- Avoid crash in pg_dump when an incorrect connection
+ Avoid crash in pg_dump when an incorrect connection
string is given (Heikki Linnakangas)
- Ignore invalid indexes in pg_dump and
- pg_upgrade (Michael Paquier, Bruce Momjian)
+ Ignore invalid indexes in pg_dump and
+ pg_upgrade (Michael Paquier, Bruce Momjian)
@@ -7597,15 +7773,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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
- pg_dump wouldn't be expected to dump anyway.
- pg_upgrade now also skips invalid indexes rather than
+ pg_dump wouldn't be expected to dump anyway.
+ pg_upgrade now also skips invalid indexes rather than
failing.
- In pg_basebackup, include only the current server
+ In pg_basebackup, include only the current server
version's subdirectory when backing up a tablespace (Heikki
Linnakangas)
@@ -7613,16 +7789,16 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add a server version check in pg_basebackup and
- pg_receivexlog, so they fail cleanly with version
+ Add a server version check in pg_basebackup and
+ pg_receivexlog, so they fail cleanly with version
combinations that won't work (Heikki Linnakangas)
- Fix contrib/dblink to handle inconsistent settings of
- DateStyle or IntervalStyle safely (Daniel
+ Fix contrib/dblink to handle inconsistent settings of
+ DateStyle or IntervalStyle safely (Daniel
Farina, Tom Lane)
@@ -7630,7 +7806,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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
- dblink query will be interpreted correctly. Note however
+ dblink 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.
@@ -7639,25 +7815,25 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix contrib/pg_trgm's similarity() function
+ Fix contrib/pg_trgm's similarity() function
to return zero for trigram-less strings (Tom Lane)
- Previously it returned NaN due to internal division by zero.
+ Previously it returned NaN due to internal division by zero.
- Enable building PostgreSQL with Microsoft Visual
+ Enable building PostgreSQL with Microsoft Visual
Studio 2012 (Brar Piening, Noah Misch)
- Update time zone data files to tzdata release 2013b
+ Update time zone data files to tzdata release 2013b
for DST law changes in Chile, Haiti, Morocco, Paraguay, and some
Russian areas. Also, historical zone data corrections for numerous
places.
@@ -7665,12 +7841,12 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Also, update the time zone abbreviation files for recent changes in
- Russia and elsewhere: CHOT, GET,
- IRKT, KGT, KRAT, MAGT,
- MAWT, MSK, NOVT, OMST,
- TKT, VLAT, WST, YAKT,
- YEKT now follow their current meanings, and
- VOLT (Europe/Volgograd) and MIST
+ Russia and elsewhere: CHOT, GET,
+ IRKT, KGT, KRAT, MAGT,
+ MAWT, MSK, NOVT, OMST,
+ TKT, VLAT, WST, YAKT,
+ YEKT now follow their current meanings, and
+ VOLT (Europe/Volgograd) and MIST
(Antarctica/Macquarie) are added to the default abbreviations list.
@@ -7715,7 +7891,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Prevent execution of enum_recv from SQL (Tom Lane)
+ Prevent execution of enum_recv from SQL (Tom Lane)
@@ -7742,7 +7918,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This mistake could result in incorrect WAL ends before end of
- online backup errors.
+ online backup errors.
@@ -7824,8 +8000,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Improve performance of SPI_execute and related
- functions, thereby improving PL/pgSQL's EXECUTE
+ Improve performance of SPI_execute and related
+ functions, thereby improving PL/pgSQL's EXECUTE
(Heikki Linnakangas, Tom Lane)
@@ -7860,20 +8036,20 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix intermittent crash in DROP INDEX CONCURRENTLY (Tom Lane)
+ Fix intermittent crash in DROP INDEX CONCURRENTLY (Tom Lane)
Fix potential corruption of shared-memory lock table during
- CREATE/DROP INDEX CONCURRENTLY (Tom Lane)
+ CREATE/DROP INDEX CONCURRENTLY (Tom Lane)
- Fix COPY's multiple-tuple-insertion code for the case of
+ Fix COPY's multiple-tuple-insertion code for the case of
a tuple larger than page size minus fillfactor (Heikki Linnakangas)
@@ -7885,19 +8061,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Protect against race conditions when scanning
- pg_tablespace (Stephen Frost, Tom Lane)
+ pg_tablespace (Stephen Frost, Tom Lane)
- CREATE DATABASE and DROP DATABASE could
+ CREATE DATABASE and DROP DATABASE could
misbehave if there were concurrent updates of
- pg_tablespace entries.
+ pg_tablespace entries.
- Prevent DROP OWNED from trying to drop whole databases or
+ Prevent DROP OWNED from trying to drop whole databases or
tablespaces (Álvaro Herrera)
@@ -7909,13 +8085,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix error in vacuum_freeze_table_age
+ linkend="guc-vacuum-freeze-table-age">vacuum_freeze_table_age
implementation (Andres Freund)
In installations that have existed for more than vacuum_freeze_min_age
+ linkend="guc-vacuum-freeze-min-age">vacuum_freeze_min_age
transactions, this mistake prevented autovacuum from using partial-table
scans, so that a full-table scan would always happen instead.
@@ -7923,13 +8099,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Prevent misbehavior when a RowExpr or XmlExpr
+ Prevent misbehavior when a RowExpr or XmlExpr
is parse-analyzed twice (Andres Freund, Tom Lane)
This mistake could be user-visible in contexts such as
- CREATE TABLE LIKE INCLUDING INDEXES.
+ CREATE TABLE LIKE INCLUDING INDEXES.
@@ -7947,7 +8123,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
There were some issues with default privileges for types, and
- pg_dump failed to dump such privileges at all.
+ pg_dump failed to dump such privileges at all.
@@ -7967,13 +8143,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Reject out-of-range dates in to_date() (Hitoshi Harada)
+ Reject out-of-range dates in to_date() (Hitoshi Harada)
- Fix pg_extension_config_dump() to handle
+ Fix pg_extension_config_dump() to handle
extension-update cases properly (Tom Lane)
@@ -7991,7 +8167,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
The previous coding resulted in sometimes omitting the first line in
- the CONTEXT traceback for the error.
+ the CONTEXT traceback for the error.
@@ -8009,13 +8185,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- This bug affected psql and some other client programs.
+ This bug affected psql and some other client programs.
- Fix possible crash in psql's \? command
+ Fix possible crash in psql's \? command
when not connected to a database (Meng Qingzhong)
@@ -8023,74 +8199,74 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix possible error if a relation file is removed while
- pg_basebackup is running (Heikki Linnakangas)
+ pg_basebackup is running (Heikki Linnakangas)
- Tolerate timeline switches while pg_basebackup -X fetch
+ Tolerate timeline switches while pg_basebackup -X fetch
is backing up a standby server (Heikki Linnakangas)
- Make pg_dump exclude data of unlogged tables when
+ Make pg_dump exclude data of unlogged tables when
running on a hot-standby server (Magnus Hagander)
This would fail anyway because the data is not available on the standby
server, so it seems most convenient to assume
- automatically.
- Fix pg_upgrade to deal with invalid indexes safely
+ Fix pg_upgrade to deal with invalid indexes safely
(Bruce Momjian)
- Fix pg_upgrade's -O/-o options (Marti Raudsepp)
+ Fix pg_upgrade's -O/-o options (Marti Raudsepp)
- Fix one-byte buffer overrun in libpq's
- PQprintTuples (Xi Wang)
+ Fix one-byte buffer overrun in libpq's
+ PQprintTuples (Xi Wang)
This ancient function is not used anywhere by
- PostgreSQL itself, but it might still be used by some
+ PostgreSQL itself, but it might still be used by some
client code.
- Make ecpglib use translated messages properly
+ Make ecpglib use translated messages properly
(Chen Huajun)
- Properly install ecpg_compat and
- pgtypes libraries on MSVC (Jiang Guiqing)
+ Properly install ecpg_compat and
+ pgtypes libraries on MSVC (Jiang Guiqing)
- Include our version of isinf() in
- libecpg if it's not provided by the system
+ Include our version of isinf() in
+ libecpg if it's not provided by the system
(Jiang Guiqing)
@@ -8110,15 +8286,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Make pgxs build executables with the right
- .exe suffix when cross-compiling for Windows
+ Make pgxs build executables with the right
+ .exe suffix when cross-compiling for Windows
(Zoltan Boszormenyi)
- Add new timezone abbreviation FET (Tom Lane)
+ Add new timezone abbreviation FET (Tom Lane)
@@ -8153,7 +8329,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- However, you may need to perform REINDEX operations to
+ However, you may need to perform REINDEX operations to
correct problems in concurrently-built indexes, as described in the first
changelog item below.
@@ -8173,22 +8349,22 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix multiple bugs associated with CREATE/DROP INDEX
- CONCURRENTLY (Andres Freund, Tom Lane, Simon Riggs, Pavan Deolasee)
+ CONCURRENTLY (Andres Freund, Tom Lane, Simon Riggs, Pavan Deolasee)
- An error introduced while adding DROP INDEX CONCURRENTLY
+ An error introduced while adding DROP INDEX CONCURRENTLY
allowed incorrect indexing decisions to be made during the initial
- phase of CREATE INDEX CONCURRENTLY; so that indexes built
+ phase of CREATE INDEX CONCURRENTLY; so that indexes built
by that command could be corrupt. It is recommended that indexes
- built in 9.2.X with CREATE INDEX CONCURRENTLY be rebuilt
+ built in 9.2.X with CREATE INDEX CONCURRENTLY be rebuilt
after applying this update.
- In addition, fix CREATE/DROP INDEX CONCURRENTLY to use
+ In addition, fix CREATE/DROP INDEX CONCURRENTLY to use
in-place updates when changing the state of an index's
- pg_index row. This prevents race conditions that could
+ pg_index row. This prevents race conditions that could
cause concurrent sessions to miss updating the target index, thus
again resulting in corrupt concurrently-created indexes.
@@ -8196,33 +8372,33 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Also, fix various other operations to ensure that they ignore
invalid indexes resulting from a failed CREATE INDEX
- CONCURRENTLY command. The most important of these is
- VACUUM, because an auto-vacuum could easily be launched
+ CONCURRENTLY command. The most important of these is
+ VACUUM, because an auto-vacuum could easily be launched
on the table before corrective action can be taken to fix or remove
the invalid index.
- Also fix DROP INDEX CONCURRENTLY to not disable
+ Also fix DROP INDEX CONCURRENTLY to not disable
insertions into the target index until all queries using it are done.
- Also fix misbehavior if DROP INDEX CONCURRENTLY is
+ Also fix misbehavior if DROP INDEX CONCURRENTLY is
canceled: the previous coding could leave an un-droppable index behind.
- Correct predicate locking for DROP INDEX CONCURRENTLY
+ Correct predicate locking for DROP INDEX CONCURRENTLY
(Kevin Grittner)
Previously, SSI predicate locks were processed at the wrong time,
possibly leading to incorrect behavior of serializable transactions
- executing in parallel with the DROP.
+ executing in parallel with the DROP.
@@ -8280,13 +8456,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This oversight could prevent subsequent execution of certain
- operations such as CREATE INDEX CONCURRENTLY.
+ operations such as CREATE INDEX CONCURRENTLY.
- Avoid bogus out-of-sequence timeline ID errors in standby
+ Avoid bogus out-of-sequence timeline ID errors in standby
mode (Heikki Linnakangas)
@@ -8306,20 +8482,20 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix the syslogger process to not fail when
- log_rotation_age exceeds 2^31 milliseconds (about 25 days)
+ log_rotation_age exceeds 2^31 milliseconds (about 25 days)
(Tom Lane)
- Fix WaitLatch() to return promptly when the requested
+ Fix WaitLatch() to return promptly when the requested
timeout expires (Jeff Janes, Tom Lane)
With the previous coding, a steady stream of non-wait-terminating
- interrupts could delay return from WaitLatch()
+ interrupts could delay return from WaitLatch()
indefinitely. This has been shown to be a problem for the autovacuum
launcher process, and might cause trouble elsewhere as well.
@@ -8372,8 +8548,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
The planner could derive incorrect constraints from a clause equating
a non-strict construct to something else, for example
- WHERE COALESCE(foo, 0) = 0
- when foo is coming from the nullable side of an outer join.
+ WHERE COALESCE(foo, 0) = 0
+ when foo 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.
@@ -8381,13 +8557,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix SELECT DISTINCT with index-optimized
- MIN/MAX on an inheritance tree (Tom Lane)
+ Fix SELECT DISTINCT with index-optimized
+ MIN/MAX on an inheritance tree (Tom Lane)
The planner would fail with failed to re-find MinMaxAggInfo
- record given this combination of factors.
+ record given this combination of factors.
@@ -8407,7 +8583,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
A strict join clause can be sufficient to establish an
- x IS NOT NULL predicate, for example.
+ xIS NOT NULL predicate, for example.
This fixes a planner regression in 9.2, since previous versions could
make comparable deductions.
@@ -8434,10 +8610,10 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- This affects multicolumn NOT IN subplans, such as
- WHERE (a, b) NOT IN (SELECT x, y FROM ...)
- when for instance b and y are int4
- and int8 respectively. This mistake led to wrong answers
+ This affects multicolumn NOT IN subplans, such as
+ WHERE (a, b) NOT IN (SELECT x, y FROM ...)
+ when for instance b and y are int4
+ and int8 respectively. This mistake led to wrong answers
or crashes depending on the specific datatypes involved.
@@ -8450,8 +8626,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This oversight could result in wrong answers from merge joins whose
inner side is an index scan using an
- indexed_column =
- ANY(array) condition.
+ indexed_column =
+ ANY(array) condition.
@@ -8475,12 +8651,12 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Acquire buffer lock when re-fetching the old tuple for an
- AFTER ROW UPDATE/DELETE trigger (Andres Freund)
+ AFTER ROW UPDATE/DELETE trigger (Andres Freund)
In very unusual circumstances, this oversight could result in passing
- incorrect data to a trigger WHEN condition, or to the
+ incorrect data to a trigger WHEN 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.
@@ -8489,7 +8665,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix ALTER COLUMN TYPE to handle inherited check
+ Fix ALTER COLUMN TYPE to handle inherited check
constraints properly (Pavan Deolasee)
@@ -8501,7 +8677,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix ALTER EXTENSION SET SCHEMA's failure to move some
+ Fix ALTER EXTENSION SET SCHEMA's failure to move some
subsidiary objects into the new schema (Álvaro Herrera, Dimitri
Fontaine)
@@ -8509,7 +8685,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Handle CREATE TABLE AS EXECUTE correctly in extended query
+ Handle CREATE TABLE AS EXECUTE correctly in extended query
protocol (Tom Lane)
@@ -8517,7 +8693,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Don't modify the input parse tree in DROP RULE IF NOT
- EXISTS and DROP TRIGGER IF NOT EXISTS (Tom Lane)
+ EXISTS and DROP TRIGGER IF NOT EXISTS (Tom Lane)
@@ -8528,14 +8704,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix REASSIGN OWNED to handle grants on tablespaces
+ Fix REASSIGN OWNED to handle grants on tablespaces
(Álvaro Herrera)
- Ignore incorrect pg_attribute entries for system
+ Ignore incorrect pg_attribute entries for system
columns for views (Tom Lane)
@@ -8549,7 +8725,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix rule printing to dump INSERT INTO table
+ Fix rule printing to dump INSERT INTO table
DEFAULT VALUES correctly (Tom Lane)
@@ -8557,7 +8733,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Guard against stack overflow when there are too many
- UNION/INTERSECT/EXCEPT clauses
+ UNION/INTERSECT/EXCEPT clauses
in a query (Tom Lane)
@@ -8579,22 +8755,22 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix failure to advance XID epoch if XID wraparound happens during a
- checkpoint and wal_level is hot_standby
+ checkpoint and wal_level is hot_standby
(Tom Lane, Andres Freund)
While this mistake had no particular impact on
PostgreSQL itself, it was bad for
- applications that rely on txid_current() and related
+ applications that rely on txid_current() and related
functions: the TXID value would appear to go backwards.
- Fix pg_terminate_backend() and
- pg_cancel_backend() to not throw error for a non-existent
+ Fix pg_terminate_backend() and
+ pg_cancel_backend() to not throw error for a non-existent
target process (Josh Kupershmidt)
@@ -8607,7 +8783,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix display of
- pg_stat_replication.sync_state at a
+ pg_stat_replication.sync_state at a
page boundary (Kyotaro Horiguchi)
@@ -8621,7 +8797,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Formerly, this would result in something quite unhelpful, such as
- Non-recoverable failure in name resolution.
+ Non-recoverable failure in name resolution.
@@ -8646,8 +8822,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Make pg_ctl more robust about reading the
- postmaster.pid file (Heikki Linnakangas)
+ Make pg_ctl more robust about reading the
+ postmaster.pid file (Heikki Linnakangas)
@@ -8657,45 +8833,45 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix possible crash in psql if incorrectly-encoded data
- is presented and the client_encoding setting is a
+ Fix possible crash in psql if incorrectly-encoded data
+ is presented and the client_encoding setting is a
client-only encoding, such as SJIS (Jiang Guiqing)
- Make pg_dump dump SEQUENCE SET items in
+ Make pg_dump dump SEQUENCE SET items in
the data not pre-data section of the archive (Tom Lane)
This fixes an undesirable inconsistency between the meanings of
- and , and also fixes
dumping of sequences that are marked as extension configuration tables.
- Fix pg_dump's handling of DROP DATABASE
- commands in mode (Guillaume Lelarge)
- Beginning in 9.2.0, pg_dump --clean would issue a
- DROP DATABASE command, which was either useless or
+ Beginning in 9.2.0, pg_dump --clean would issue a
+ DROP DATABASE command, which was either useless or
dangerous depending on the usage scenario. It no longer does that.
- This change also fixes the combination of
- Fix pg_dump for views with circular dependencies and
+ Fix pg_dump for views with circular dependencies and
no relation options (Tom Lane)
@@ -8703,31 +8879,31 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 ALTER VIEW foo
- SET () which is invalid syntax.
+ SET () which is invalid syntax.
- Fix bugs in the restore.sql script emitted by
- pg_dump in tar output format (Tom Lane)
+ Fix bugs in the restore.sql script emitted by
+ pg_dump in tar output format (Tom Lane)
The script would fail outright on tables whose names include
upper-case characters. Also, make the script capable of restoring
- data in mode as well as the regular COPY mode.
- Fix pg_restore to accept POSIX-conformant
- tar files (Brian Weaver, Tom Lane)
+ Fix pg_restore to accept POSIX-conformant
+ tar files (Brian Weaver, Tom Lane)
- The original coding of pg_dump's tar
+ The original coding of pg_dump's tar
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
@@ -8738,82 +8914,82 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix tar files emitted by pg_basebackup to
+ Fix tar files emitted by pg_basebackup to
be POSIX conformant (Brian Weaver, Tom Lane)
- Fix pg_resetxlog to locate postmaster.pid
+ Fix pg_resetxlog to locate postmaster.pid
correctly when given a relative path to the data directory (Tom Lane)
- This mistake could lead to pg_resetxlog not noticing
+ This mistake could lead to pg_resetxlog not noticing
that there is an active postmaster using the data directory.
- Fix libpq's lo_import() and
- lo_export() functions to report file I/O errors properly
+ Fix libpq's lo_import() and
+ lo_export() functions to report file I/O errors properly
(Tom Lane)
- Fix ecpg's processing of nested structure pointer
+ Fix ecpg's processing of nested structure pointer
variables (Muhammad Usama)
- Fix ecpg's ecpg_get_data function to
+ Fix ecpg's ecpg_get_data function to
handle arrays properly (Michael Meskes)
- Prevent pg_upgrade from trying to process TOAST tables
+ Prevent pg_upgrade from trying to process TOAST tables
for system catalogs (Bruce Momjian)
- This fixes an error seen when the information_schema has
+ This fixes an error seen when the information_schema has
been dropped and recreated. Other failures were also possible.
- Improve pg_upgrade performance by setting
- synchronous_commit to off in the new cluster
+ Improve pg_upgrade performance by setting
+ synchronous_commit to off in the new cluster
(Bruce Momjian)
- Make contrib/pageinspect's btree page inspection
+ Make contrib/pageinspect's btree page inspection
functions take buffer locks while examining pages (Tom Lane)
- Work around unportable behavior of malloc(0) and
- realloc(NULL, 0) (Tom Lane)
+ Work around unportable behavior of malloc(0) and
+ realloc(NULL, 0) (Tom Lane)
- On platforms where these calls return NULL, some code
+ On platforms where these calls return NULL, some code
mistakenly thought that meant out-of-memory.
- This is known to have broken pg_dump for databases
+ This is known to have broken pg_dump for databases
containing no user-defined aggregates. There might be other cases
as well.
@@ -8821,19 +8997,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Ensure that make install for an extension creates the
- extension installation directory (Cédric Villemain)
+ Ensure that make install for an extension creates the
+ extension installation directory (Cédric Villemain)
- Previously, this step was missed if MODULEDIR was set in
+ Previously, this step was missed if MODULEDIR was set in
the extension's Makefile.
- Fix pgxs support for building loadable modules on AIX
+ Fix pgxs support for building loadable modules on AIX
(Tom Lane)
@@ -8844,7 +9020,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Update time zone data files to tzdata release 2012j
+ Update time zone data files to tzdata release 2012j
for DST law changes in Cuba, Israel, Jordan, Libya, Palestine, Western
Samoa, and portions of Brazil.
@@ -8877,8 +9053,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- However, you may need to perform REINDEX and/or
- VACUUM operations to recover from the effects of the data
+ However, you may need to perform REINDEX and/or
+ VACUUM operations to recover from the effects of the data
corruption bug described in the first changelog item below.
@@ -8903,7 +9079,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 visibility maps, which might lead to wrong answers
+ of table visibility maps, which might lead to wrong answers
from index-only scans. Table data proper cannot be corrupted by this
bug.
@@ -8911,16 +9087,16 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 REINDEX all btree and GIN
+ production installations REINDEX all btree and GIN
indexes at a convenient time after upgrading to 9.2.1.
- Also, it is recommended to perform a VACUUM of all tables
+ Also, it is recommended to perform a VACUUM of all tables
while having vacuum_freeze_table_age
+ linkend="guc-vacuum-freeze-table-age">vacuum_freeze_table_age
set to zero. This will fix any incorrect visibility map data. vacuum_cost_delay
+ linkend="guc-vacuum-cost-delay">vacuum_cost_delay
can be adjusted to reduce the performance impact of vacuuming, while
causing it to take longer to finish.
@@ -8929,14 +9105,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix possible incorrect sorting of output from queries involving
- WHERE indexed_column IN
- (list_of_values) (Tom Lane)
+ WHERE indexed_column IN
+ (list_of_values) (Tom Lane)
- Fix planner failure for queries involving GROUP BY
+ Fix planner failure for queries involving GROUP BY
expressions along with window functions and aggregates (Tom Lane)
@@ -8948,7 +9124,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This error could result in wrong answers from queries that scan the
- same WITH subquery multiple times.
+ same WITH subquery multiple times.
@@ -8961,7 +9137,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Improve selectivity estimation for text search queries involving
- prefixes, i.e. word:* patterns (Tom Lane)
+ prefixes, i.e. word:* patterns (Tom Lane)
@@ -8972,14 +9148,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
A command that needed no locks other than ones its transaction already
- had might fail to notice a concurrent GRANT or
- REVOKE that committed since the start of its transaction.
+ had might fail to notice a concurrent GRANT or
+ REVOKE that committed since the start of its transaction.
- Fix ANALYZE to not fail when a column is a domain over an
+ Fix ANALYZE to not fail when a column is a domain over an
array type (Tom Lane)
@@ -8998,7 +9174,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Some Linux distributions contain an incorrect version of
- pthread.h that results in incorrect compiled code in
+ pthread.h that results in incorrect compiled code in
PL/Perl, leading to crashes if a PL/Perl function calls another one
that throws an error.
@@ -9006,14 +9182,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Remove unnecessary dependency on pg_config from
- pg_upgrade (Peter Eisentraut)
+ Remove unnecessary dependency on pg_config from
+ pg_upgrade (Peter Eisentraut)
- Update time zone data files to tzdata release 2012f
+ Update time zone data files to tzdata release 2012f
for DST law changes in Fiji
@@ -9047,7 +9223,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Allow queries to retrieve data only from indexes, avoiding heap
- access (index-only scans)
+ access (index-only scans)
@@ -9069,14 +9245,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Allow streaming replication slaves to forward data to other slaves
(cascading
- replication)
+ replication)
Allow pg_basebackup
+ linkend="app-pgbasebackup">pg_basebackup
to make base backups from standby servers
@@ -9084,14 +9260,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add a pg_receivexlog
+ linkend="app-pgreceivewal">pg_receivexlog
tool to archive WAL file changes as they are written
- Add the SP-GiST (Space-Partitioned
+ Add the SP-GiST (Space-Partitioned
GiST) index access method
@@ -9112,14 +9288,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add a security_barrier
+ linkend="sql-createview">security_barrier
option for views
- Allow libpq connection strings to have the format of a
+ Allow libpq connection strings to have the format of a
URI
@@ -9127,7 +9303,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add a single-row processing
- mode to libpq for better handling of large
+ mode to libpq for better handling of large
result sets
@@ -9162,8 +9338,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Remove the spclocation field from pg_tablespace
+ Remove the spclocation field from pg_tablespace
(Magnus Hagander)
@@ -9173,23 +9349,23 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
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 pg_tablespace_location()
+ linkend="functions-info-catalog-table">pg_tablespace_location()
to allow querying of the symbolic links.
- Move tsvector most-common-element statistics to new
- pg_stats columns
+ Move tsvector most-common-element statistics to new
+ pg_stats columns
(Alexander Korotkov)
- Consult most_common_elems
- and most_common_elem_freqs for the data formerly
- available in most_common_vals
- and most_common_freqs for a tsvector column.
+ Consult most_common_elems
+ and most_common_elem_freqs for the data formerly
+ available in most_common_vals
+ and most_common_freqs for a tsvector column.
@@ -9204,14 +9380,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Remove hstore's =>
+ Remove hstore's =>
operator (Robert Haas)
- Users should now use hstore(text, text). Since
+ Users should now use hstore(text, text). Since
PostgreSQL 9.0, a warning message has been
- emitted when an operator named => is created because
+ emitted when an operator named => is created because
the SQL standard reserves that token for
another use.
@@ -9220,7 +9396,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Ensure that xpath()
+ linkend="functions-xml-processing">xpath()
escapes special characters in string values (Florian Pflug)
@@ -9233,13 +9409,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Make pg_relation_size()
+ linkend="functions-admin-dbobject">pg_relation_size()
and friends return NULL if the object does not exist (Phil Sorber)
This prevents queries that call these functions from returning
- errors immediately after a concurrent DROP.
+ errors immediately after a concurrent DROP.
@@ -9247,7 +9423,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Make EXTRACT(EPOCH FROM
- timestamp without time zone)
+ timestamp without time zone)
measure the epoch from local midnight, not UTC
midnight (Tom Lane)
@@ -9256,17 +9432,17 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This change reverts an ill-considered change made in release 7.3.
Measuring from UTC midnight was inconsistent
because it made the result dependent on the timezone setting, which
- computations for timestamp without time zone should not be.
+ linkend="guc-timezone">timezone setting, which
+ computations for timestamp without time zone should not be.
The previous behavior remains available by casting the input value
- to timestamp with time zone.
+ to timestamp with time zone.
- Properly parse time strings with trailing yesterday,
- today, and tomorrow (Dean Rasheed)
+ Properly parse time strings with trailing yesterday,
+ today, and tomorrow (Dean Rasheed)
@@ -9278,8 +9454,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix to_date() and
- to_timestamp() to wrap incomplete dates toward 2020
+ linkend="functions-formatting">to_date() and
+ to_timestamp() to wrap incomplete dates toward 2020
(Bruce Momjian)
@@ -9300,7 +9476,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Prevent ALTER
+ Prevent ALTER
DOMAIN from working on non-domain types (Peter
Eisentraut)
@@ -9314,15 +9490,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
No longer forcibly lowercase procedural language names in CREATE FUNCTION
+ linkend="sql-createfunction">CREATE FUNCTION
(Robert Haas)
While unquoted language identifiers are still lowercased, strings
and quoted identifiers are no longer forcibly down-cased.
- Thus for example CREATE FUNCTION ... LANGUAGE 'C'
- will no longer work; it must be spelled 'c', or better
+ Thus for example CREATE FUNCTION ... LANGUAGE 'C'
+ will no longer work; it must be spelled 'c', or better
omit the quotes.
@@ -9352,15 +9528,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Provide consistent backquote, variable
expansion, and quoted substring behavior in psql meta-command
+ linkend="app-psql">psql meta-command
arguments (Tom Lane)
Previously, such references were treated oddly when not separated by
- whitespace from adjacent text. For example 'FOO'BAR was
- output as FOO BAR (unexpected insertion of a space) and
- FOO'BAR'BAZ was output unchanged (not removing the quotes
+ whitespace from adjacent text. For example 'FOO'BAR was
+ output as FOO BAR (unexpected insertion of a space) and
+ FOO'BAR'BAZ was output unchanged (not removing the quotes
as most would expect).
@@ -9368,9 +9544,9 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
No longer treat clusterdb
+ linkend="app-clusterdb">clusterdb
table names as double-quoted; no longer treat reindexdb table
+ linkend="app-reindexdb">reindexdb table
and index names as double-quoted (Bruce Momjian)
@@ -9382,20 +9558,20 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- createuser
+ createuser
no longer prompts for option settings by default (Peter Eisentraut)
- Use to obtain the old behavior.
Disable prompting for the user name in dropuser unless
- is specified (Peter Eisentraut)
@@ -9417,36 +9593,36 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This allows changing the names and locations of the files that were
- previously hard-coded as server.crt,
- server.key, root.crt, and
- root.crl in the data directory.
- The server will no longer examine root.crt or
- root.crl by default; to load these files, the
+ previously hard-coded as server.crt,
+ server.key, root.crt, and
+ root.crl in the data directory.
+ The server will no longer examine root.crt or
+ root.crl by default; to load these files, the
associated parameters must be set to non-default values.
- Remove the silent_mode parameter (Heikki Linnakangas)
+ Remove the silent_mode parameter (Heikki Linnakangas)
Similar behavior can be obtained with pg_ctl start
- -l postmaster.log.
+ -l postmaster.log.
- Remove the wal_sender_delay parameter,
+ Remove the wal_sender_delay parameter,
as it is no longer needed (Tom Lane)
- Remove the custom_variable_classes parameter (Tom Lane)
+ Remove the custom_variable_classes parameter (Tom Lane)
@@ -9466,19 +9642,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Rename pg_stat_activity.procpid
- to pid, to match other system tables (Magnus Hagander)
+ linkend="monitoring-stats-views-table">pg_stat_activity.procpid
+ to pid, to match other system tables (Magnus Hagander)
- Create a separate pg_stat_activity column to
+ Create a separate pg_stat_activity column to
report process state (Scott Mead, Magnus Hagander)
- The previous query and query_start
+ The previous query and query_start
values now remain available for an idle session, allowing enhanced
analysis.
@@ -9486,8 +9662,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Rename pg_stat_activity.current_query to
- query because it is not cleared when the query
+ Rename pg_stat_activity.current_query to
+ query because it is not cleared when the query
completes (Magnus Hagander)
@@ -9495,24 +9671,24 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Change all SQL-level statistics timing values
- to be float8 columns measured in milliseconds (Tom Lane)
+ to be float8 columns measured in milliseconds (Tom Lane)
This change eliminates the designed-in assumption that the values
- are accurate to microseconds and no more (since the float8
+ are accurate to microseconds and no more (since the float8
values can be fractional).
The columns affected are
- pg_stat_user_functions.total_time,
- pg_stat_user_functions.self_time,
- pg_stat_xact_user_functions.total_time,
+ pg_stat_user_functions.total_time,
+ pg_stat_user_functions.self_time,
+ pg_stat_xact_user_functions.total_time,
and
- pg_stat_xact_user_functions.self_time.
+ pg_stat_xact_user_functions.self_time.
The statistics functions underlying these columns now also return
- float8 milliseconds, rather than bigint
+ float8 milliseconds, rather than bigint
microseconds.
- contrib/pg_stat_statements'
- total_time column is now also measured in
+ contrib/pg_stat_statements'
+ total_time column is now also measured in
milliseconds.
@@ -9546,7 +9722,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- This feature is often called index-only scans.
+ This feature is often called index-only scans.
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
@@ -9556,7 +9732,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add the SP-GiST (Space-Partitioned
+ Add the SP-GiST (Space-Partitioned
GiST) index access method (Teodor Sigaev, Oleg Bartunov, Tom
Lane)
@@ -9618,7 +9794,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Move the frequently accessed members of the PGPROC
+ Move the frequently accessed members of the PGPROC
shared memory array to a separate array (Pavan
Deolasee, Heikki Linnakangas, Robert Haas)
@@ -9663,7 +9839,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Make the number of CLOG buffers scale based on shared_buffers
+ linkend="guc-shared-buffers">shared_buffers
(Robert Haas, Simon Riggs, Tom Lane)
@@ -9724,7 +9900,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Previously, only wal_writer_delay
+ linkend="guc-wal-writer-delay">wal_writer_delay
triggered WAL flushing to disk; now filling a
WAL buffer also triggers WAL
writes.
@@ -9763,7 +9939,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
In the past, a prepared statement always had a single
- generic plan that was used for all parameter values, which
+ generic 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.
@@ -9781,7 +9957,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- The new parameterized path mechanism allows inner
+ The new parameterized path 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
@@ -9796,7 +9972,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Wrappers can now provide multiple access paths for their
+ Wrappers can now provide multiple access paths for their
tables, allowing more flexibility in join planning.
@@ -9809,14 +9985,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This check is only performed when constraint_exclusion
+ linkend="guc-constraint-exclusion">constraint_exclusion
is on.
- Allow indexed_col op ANY(ARRAY[...]) conditions to be
+ Allow indexed_col op ANY(ARRAY[...]) conditions to be
used in plain index scans and index-only scans (Tom Lane)
@@ -9827,14 +10003,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Support MIN/MAX index optimizations on
+ Support MIN/MAX index optimizations on
boolean columns (Marti Raudsepp)
- Account for set-returning functions in SELECT target
+ Account for set-returning functions in SELECT target
lists when setting row count estimates (Tom Lane)
@@ -9882,7 +10058,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Improve statistical estimates for subqueries using
- DISTINCT (Tom Lane)
+ DISTINCT (Tom Lane)
@@ -9897,13 +10073,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Do not treat role names and samerole specified in samerole specified in pg_hba.conf
as automatically including superusers (Andrew Dunstan)
- This makes it easier to use reject lines with group roles.
+ This makes it easier to use reject lines with group roles.
@@ -9958,7 +10134,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This logging is triggered by log_autovacuum_min_duration.
+ linkend="guc-log-autovacuum-min-duration">log_autovacuum_min_duration.
@@ -9977,7 +10153,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add pg_xlog_location_diff()
+ linkend="functions-admin-backup">pg_xlog_location_diff()
to simplify WAL location comparisons (Euler Taveira de Oliveira)
@@ -9995,15 +10171,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This allows different instances to use the event log
with different identifiers, by setting the event_source
+ linkend="guc-event-source">event_source
server parameter, which is similar to how syslog_ident works.
+ linkend="guc-syslog-ident">syslog_ident works.
- Change unexpected EOF messages to DEBUG1 level,
+ Change unexpected EOF messages to DEBUG1 level,
except when there is an open transaction (Magnus Hagander)
@@ -10025,14 +10201,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Track temporary file sizes and file counts in the pg_stat_database
+ linkend="pg-stat-database-view">pg_stat_database
system view (Tomas Vondra)
- Add a deadlock counter to the pg_stat_database
+ Add a deadlock counter to the pg_stat_database
system view (Magnus Hagander)
@@ -10040,7 +10216,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add a server parameter track_io_timing
+ linkend="guc-track-io-timing">track_io_timing
to track I/O timings (Ants Aasma, Robert Haas)
@@ -10048,7 +10224,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Report checkpoint timing information in pg_stat_bgwriter
+ linkend="pg-stat-bgwriter-view">pg_stat_bgwriter
(Greg Smith, Peter Geoghegan)
@@ -10065,7 +10241,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Silently ignore nonexistent schemas specified in search_path (Tom Lane)
+ linkend="guc-search-path">search_path (Tom Lane)
@@ -10077,12 +10253,12 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Allow superusers to set deadlock_timeout
+ linkend="guc-deadlock-timeout">deadlock_timeout
per-session, not just per-cluster (Noah Misch)
- This allows deadlock_timeout to be reduced for
+ This allows deadlock_timeout 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
@@ -10093,7 +10269,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add a server parameter temp_file_limit
+ linkend="guc-temp-file-limit">temp_file_limit
to constrain temporary file space usage per session (Mark Kirkwood)
@@ -10114,13 +10290,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add postmaster
option to query configuration parameters (Bruce Momjian)
- This allows pg_ctl to better handle cases where
- PGDATA or points to a configuration-only
directory.
@@ -10128,14 +10304,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Replace an empty locale name with the implied value in
- CREATE DATABASE
+ CREATE DATABASE
(Tom Lane)
This prevents cases where
- pg_database.datcollate or
- datctype could be interpreted differently after a
+ pg_database.datcollate or
+ datctype could be interpreted differently after a
server restart.
@@ -10170,22 +10346,22 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add an include_if_exists facility for configuration
+ Add an include_if_exists facility for configuration
files (Greg Smith)
- This works the same as include, except that an error
+ This works the same as include, except that an error
is not thrown if the file is missing.
- Identify the server time zone during initdb, and set
+ Identify the server time zone during initdb, and set
postgresql.conf entries
- timezone and
- log_timezone
+ timezone and
+ log_timezone
accordingly (Tom Lane)
@@ -10197,7 +10373,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Fix pg_settings to
+ linkend="view-pg-settings">pg_settings to
report postgresql.conf line numbers on Windows
(Tom Lane)
@@ -10220,7 +10396,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Allow streaming replication slaves to forward data to other slaves
(cascading
- replication) (Fujii Masao)
+ replication) (Fujii Masao)
@@ -10232,8 +10408,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add new synchronous_commit
- mode remote_write (Fujii Masao, Simon Riggs)
+ linkend="guc-synchronous-commit">synchronous_commit
+ mode remote_write (Fujii Masao, Simon Riggs)
@@ -10246,7 +10422,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add a pg_receivexlog
+ linkend="app-pgreceivewal">pg_receivexlog
tool to archive WAL file changes as they are written, rather
than waiting for completed WAL files (Magnus Hagander)
@@ -10255,7 +10431,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Allow pg_basebackup
+ linkend="app-pgbasebackup">pg_basebackup
to make base backups from standby servers (Jun Ishizuka, Fujii Masao)
@@ -10267,7 +10443,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Allow streaming of WAL files while pg_basebackup
+ Allow streaming of WAL files while pg_basebackup
is performing a backup (Magnus Hagander)
@@ -10306,19 +10482,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This change allows better results when a row value is converted to
- hstore or json type: the fields of the resulting
+ hstore or json type: the fields of the resulting
value will now have the expected names.
- Improve column labels used for sub-SELECT results
+ Improve column labels used for sub-SELECT results
(Marti Raudsepp)
- Previously, the generic label ?column? was used.
+ Previously, the generic label ?column? was used.
@@ -10348,7 +10524,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- When a row fails a CHECK or NOT NULL
+ When a row fails a CHECK or NOT NULL
constraint, show the row's contents as error detail (Jan
Kundrát)
@@ -10376,7 +10552,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This change adds locking that should eliminate cache lookup
- failed errors in many scenarios. Also, it is no longer possible
+ failed 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.
@@ -10384,8 +10560,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add CONCURRENTLY option to DROP INDEX
+ Add CONCURRENTLY option to DROP INDEX
(Simon Riggs)
@@ -10415,31 +10591,31 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Allow CHECK
- constraints to be declared NOT VALID (Álvaro
+ Allow CHECK
+ constraints to be declared NOT VALID (Álvaro
Herrera)
- Adding a NOT VALID constraint does not cause the table to
+ Adding a NOT VALID 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
- constraint_exclusion, since it is not certain that all
+ constraint_exclusion, since it is not certain that all
rows meet the constraint.
- The new ALTER TABLE VALIDATE command allows NOT
- VALID constraints to be checked for existing rows, after which
+ The new ALTER TABLE VALIDATE command allows NOT
+ VALID constraints to be checked for existing rows, after which
they are converted into ordinary constraints.
- Allow CHECK constraints to be declared NO
- INHERIT (Nikhil Sontakke, Alex Hunsaker, Álvaro Herrera)
+ Allow CHECK constraints to be declared NO
+ INHERIT (Nikhil Sontakke, Alex Hunsaker, Álvaro Herrera)
@@ -10450,7 +10626,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add the ability to rename
+ Add the ability to rename
constraints (Peter Eisentraut)
@@ -10459,32 +10635,32 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- <command>ALTER</>
+ <command>ALTER</command>
Reduce need to rebuild tables and indexes for certain ALTER TABLE
- ... ALTER COLUMN TYPE operations (Noah Misch)
+ linkend="sql-altertable">ALTER TABLE
+ ... ALTER COLUMN TYPE operations (Noah Misch)
- Increasing the length limit for a varchar or varbit
+ Increasing the length limit for a varchar or varbit
column, or removing the limit altogether, no longer requires a table
rewrite. Similarly, increasing the allowable precision of a
- numeric column, or changing a column from constrained
- numeric to unconstrained numeric, no longer
+ numeric column, or changing a column from constrained
+ numeric to unconstrained numeric, no longer
requires a table rewrite. Table rewrites are also avoided in similar
- cases involving the interval, timestamp, and
- timestamptz types.
+ cases involving the interval, timestamp, and
+ timestamptz types.
- Avoid having ALTER
+ Avoid having ALTER
TABLE revalidate foreign key constraints in some
cases where it is not necessary (Noah Misch)
@@ -10492,7 +10668,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add IF EXISTS options to some ALTER
+ Add IF EXISTS options to some ALTER
commands (Pavel Stehule)
@@ -10504,17 +10680,17 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add ALTER
- FOREIGN DATA WRAPPER ... RENAME
- and ALTER
- SERVER ... RENAME (Peter Eisentraut)
+ Add ALTER
+ FOREIGN DATA WRAPPER ... RENAME
+ and ALTER
+ SERVER ... RENAME (Peter Eisentraut)
- Add ALTER
- DOMAIN ... RENAME (Peter Eisentraut)
+ Add ALTER
+ DOMAIN ... RENAME (Peter Eisentraut)
@@ -10526,11 +10702,11 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Throw an error for ALTER DOMAIN ... DROP
- CONSTRAINT on a nonexistent constraint (Peter Eisentraut)
+ CONSTRAINT on a nonexistent constraint (Peter Eisentraut)
- An IF EXISTS option has been added to provide the
+ An IF EXISTS option has been added to provide the
previous behavior.
@@ -10540,7 +10716,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- <link linkend="SQL-CREATETABLE"><command>CREATE TABLE</></link>
+ <link linkend="sql-createtable"><command>CREATE TABLE</command></link>
@@ -10565,8 +10741,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Fix CREATE TABLE ... AS EXECUTE
- to handle WITH NO DATA and column name specifications
+ Fix CREATE TABLE ... AS EXECUTE
+ to handle WITH NO DATA and column name specifications
(Tom Lane)
@@ -10583,14 +10759,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add a security_barrier
+ linkend="sql-createview">security_barrier
option for views (KaiGai Kohei, Robert Haas)
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 WHERE clause of the view.
+ an insecure function into the WHERE clause of the view.
Such views can be expected to perform more poorly than ordinary
views.
@@ -10599,9 +10775,9 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add a new LEAKPROOF function
+ linkend="sql-createfunction">LEAKPROOF function
attribute to mark functions that can safely be pushed down
- into security_barrier views (KaiGai Kohei)
+ into security_barrier views (KaiGai Kohei)
@@ -10611,8 +10787,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- This adds support for the SQL-conforming
- USAGE privilege on types and domains. The intent is
+ This adds support for the SQL-conforming
+ USAGE 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.
@@ -10628,7 +10804,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Because the object is being created by SELECT INTO
or CREATE TABLE AS, the creator would ordinarily
have insert permissions; but there are corner cases where this is not
- true, such as when ALTER DEFAULT PRIVILEGES has removed
+ true, such as when ALTER DEFAULT PRIVILEGES has removed
such permissions.
@@ -10646,20 +10822,20 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Allow VACUUM to more
+ Allow VACUUM to more
easily skip pages that cannot be locked (Simon Riggs, Robert Haas)
- This change should greatly reduce the incidence of VACUUM
- getting stuck waiting for other sessions.
+ This change should greatly reduce the incidence of VACUUM
+ getting stuck waiting for other sessions.
- Make EXPLAIN
- (BUFFERS) count blocks dirtied and written (Robert Haas)
+ Make EXPLAIN
+ (BUFFERS) count blocks dirtied and written (Robert Haas)
@@ -10677,8 +10853,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- This is accomplished by setting the new TIMING option to
- FALSE.
+ This is accomplished by setting the new TIMING option to
+ FALSE.
@@ -10719,41 +10895,41 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add array_to_json()
- and row_to_json() (Andrew Dunstan)
+ linkend="functions-json">array_to_json()
+ and row_to_json() (Andrew Dunstan)
- Add a SMALLSERIAL
+ Add a SMALLSERIAL
data type (Mike Pultz)
- This is like SERIAL, except it stores the sequence in
- a two-byte integer column (int2).
+ This is like SERIAL, except it stores the sequence in
+ a two-byte integer column (int2).
- Allow domains to be
- declared NOT VALID (Álvaro Herrera)
+ Allow domains to be
+ declared NOT VALID (Álvaro Herrera)
This option can be set at domain creation time, or via ALTER
- DOMAIN ... ADD CONSTRAINT ... NOT
- VALID. ALTER DOMAIN ... VALIDATE
- CONSTRAINT fully validates the constraint.
+ DOMAIN ... ADD CONSTRAINT ... NOT
+ VALID. ALTER DOMAIN ... VALIDATE
+ CONSTRAINT fully validates the constraint.
Support more locale-specific formatting options for the money data type (Tom Lane)
+ linkend="datatype-money">money data type (Tom Lane)
@@ -10766,22 +10942,22 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add bitwise and, or, and not
- operators for the macaddr data type (Brendan Jurd)
+ Add bitwise and, or, and not
+ operators for the macaddr data type (Brendan Jurd)
Allow xpath() to
+ linkend="functions-xml-processing">xpath() to
return a single-element XML array when supplied a
scalar value (Florian Pflug)
Previously, it returned an empty array. This change will also
- cause xpath_exists() to return true, not false,
+ cause xpath_exists() to return true, not false,
for such expressions.
@@ -10805,9 +10981,9 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Allow non-superusers to use pg_cancel_backend()
+ linkend="functions-admin-signal">pg_cancel_backend()
and pg_terminate_backend()
+ linkend="functions-admin-signal">pg_terminate_backend()
on other sessions belonging to the same user
(Magnus Hagander, Josh Kupershmidt, Dan Farina)
@@ -10827,8 +11003,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This allows multiple transactions to share identical views of the
database state.
Snapshots are exported via pg_export_snapshot()
- and imported via SET
+ linkend="functions-snapshot-synchronization">pg_export_snapshot()
+ and imported via SET
TRANSACTION SNAPSHOT. Only snapshots from
currently-running transactions can be imported.
@@ -10838,7 +11014,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Support COLLATION
- FOR on expressions (Peter Eisentraut)
+ FOR on expressions (Peter Eisentraut)
@@ -10849,23 +11025,23 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add pg_opfamily_is_visible()
+ linkend="functions-info-schema-table">pg_opfamily_is_visible()
(Josh Kupershmidt)
- Add a numeric variant of pg_size_pretty()
- for use with pg_xlog_location_diff() (Fujii Masao)
+ Add a numeric variant of pg_size_pretty()
+ for use with pg_xlog_location_diff() (Fujii Masao)
Add a pg_trigger_depth()
+ linkend="functions-info-session-table">pg_trigger_depth()
function (Kevin Grittner)
@@ -10877,8 +11053,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Allow string_agg()
- to process bytea values (Pavel Stehule)
+ linkend="functions-aggregate-table">string_agg()
+ to process bytea values (Pavel Stehule)
@@ -10889,7 +11065,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- For example, ^(\w+)( \1)+$. Previous releases did not
+ For example, ^(\w+)( \1)+$. Previous releases did not
check that the back-reference actually matched the first occurrence.
@@ -10906,22 +11082,22 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add information schema views
- role_udt_grants, udt_privileges,
- and user_defined_types (Peter Eisentraut)
+ role_udt_grants, udt_privileges,
+ and user_defined_types (Peter Eisentraut)
Add composite-type attributes to the
- information schema element_types view
+ information schema element_types view
(Peter Eisentraut)
- Implement interval_type columns in the information
+ Implement interval_type columns in the information
schema (Peter Eisentraut)
@@ -10933,23 +11109,23 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Implement collation-related columns in the information schema
- attributes, columns,
- domains, and element_types
+ attributes, columns,
+ domains, and element_types
views (Peter Eisentraut)
- Implement the with_hierarchy column in the
- information schema table_privileges view (Peter
+ Implement the with_hierarchy column in the
+ information schema table_privileges view (Peter
Eisentraut)
- Add display of sequence USAGE privileges to information
+ Add display of sequence USAGE privileges to information
schema (Peter Eisentraut)
@@ -10980,7 +11156,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Allow the PL/pgSQL OPEN cursor command to supply
+ Allow the PL/pgSQL OPEN cursor command to supply
parameters by name (Yeb Havinga)
@@ -11002,7 +11178,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Improve performance and memory consumption for long chains of
- ELSIF clauses (Tom Lane)
+ ELSIF clauses (Tom Lane)
@@ -11083,31 +11259,31 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add initdb
- options and
(Peter Eisentraut)
- This allows separate control of local and
- host pg_hba.conf authentication
- settings. still controls both.
- Add
- Add the
@@ -11115,15 +11291,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Give command-line tools the ability to specify the name of the
- database to connect to, and fall back to template1
- if a postgres database connection fails (Robert Haas)
+ database to connect to, and fall back to template1
+ if a postgres database connection fails (Robert Haas)
- <link linkend="APP-PSQL"><application>psql</></link>
+ <link linkend="app-psql"><application>psql</application></link>
@@ -11134,7 +11310,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- This adds the auto option to the \x
+ This adds the auto option to the \x
command, which switches to the expanded mode when the normal
output would be wider than the screen.
@@ -11147,32 +11323,32 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- This is done with a new command \ir.
+ This is done with a new command \ir.
Add support for non-ASCII characters in
- psql variable names (Tom Lane)
+ psql variable names (Tom Lane)
- Add support for major-version-specific .psqlrc files
+ Add support for major-version-specific .psqlrc files
(Bruce Momjian)
- psql already supported minor-version-specific
- .psqlrc files.
+ psql already supported minor-version-specific
+ .psqlrc files.
- Provide environment variable overrides for psql
+ Provide environment variable overrides for psql
history and startup file locations (Andrew Dunstan)
@@ -11184,15 +11360,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add a \setenv command to modify
+ Add a \setenv command to modify
the environment variables passed to child processes (Andrew Dunstan)
- Name psql's temporary editor files with a
- .sql extension (Peter Eisentraut)
+ Name psql's temporary editor files with a
+ .sql extension (Peter Eisentraut)
@@ -11202,19 +11378,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Allow psql to use zero-byte field and record
+ Allow psql to use zero-byte field and record
separators (Peter Eisentraut)
Various shell tools use zero-byte (NUL) separators,
- e.g. find.
+ e.g. find.
- Make the \timing option report times for
+ Make the \timing option report times for
failed queries (Magnus Hagander)
@@ -11225,13 +11401,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Unify and tighten psql's treatment of \copy
- and SQL COPY (Noah Misch)
+ Unify and tighten psql's treatment of \copy
+ and SQL COPY (Noah Misch)
This fix makes failure behavior more predictable and honors
- \set ON_ERROR_ROLLBACK.
+ \set ON_ERROR_ROLLBACK.
@@ -11245,21 +11421,21 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Make \d on a sequence show the
+ Make \d on a sequence show the
table/column name owning it (Magnus Hagander)
- Show statistics target for columns in \d+ (Magnus
+ Show statistics target for columns in \d+ (Magnus
Hagander)
- Show role password expiration dates in \du
+ Show role password expiration dates in \du
(Fabrízio de Royes Mello)
@@ -11271,8 +11447,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- These are included in the output of \dC+,
- \dc+, \dD+, and \dL respectively.
+ These are included in the output of \dC+,
+ \dc+, \dD+, and \dL respectively.
@@ -11283,15 +11459,15 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- These are included in the output of \des+,
- \det+, and \dew+ for foreign servers, foreign
+ These are included in the output of \des+,
+ \det+, and \dew+ for foreign servers, foreign
tables, and foreign data wrappers respectively.
- Change \dd to display comments only for object types
+ Change \dd to display comments only for object types
without their own backslash command (Josh Kupershmidt)
@@ -11307,9 +11483,9 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- In psql tab completion, complete SQL
+ In psql tab completion, complete SQL
keywords in either upper or lower case according to the new COMP_KEYWORD_CASE
+ linkend="app-psql-variables">COMP_KEYWORD_CASE
setting (Peter Eisentraut)
@@ -11348,14 +11524,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- <link linkend="APP-PGDUMP"><application>pg_dump</></link>
+ <link linkend="app-pgdump"><application>pg_dump</application></link>
- Add an
@@ -11366,13 +11542,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add a
- Valid values are pre-data, data,
- and post-data. The option can be
+ Valid values are pre-data, data,
+ and post-data. The option can be
given more than once to select two or more sections.
@@ -11380,7 +11556,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Make pg_dumpall dump all
+ linkend="app-pg-dumpall">pg_dumpall dump all
roles first, then all configuration settings on roles (Phil Sorber)
@@ -11392,8 +11568,8 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Allow pg_dumpall to avoid errors if the
- postgres database is missing in the new cluster
+ Allow pg_dumpall to avoid errors if the
+ postgres database is missing in the new cluster
(Robert Haas)
@@ -11418,13 +11594,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Tighten rules for when extension configuration tables are dumped
- by pg_dump (Tom Lane)
+ by pg_dump (Tom Lane)
- Make pg_dump emit more useful dependency
+ Make pg_dump emit more useful dependency
information (Tom Lane)
@@ -11438,7 +11614,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Improve pg_dump's performance when dumping many
+ Improve pg_dump's performance when dumping many
database objects (Tom Lane)
@@ -11450,19 +11626,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- <link linkend="libpq"><application>libpq</></link>
+ <link linkend="libpq"><application>libpq</application></link>
- Allow libpq connection strings to have the format of a
+ Allow libpq connection strings to have the format of a
URI
(Alexander Shulgin)
- The syntax begins with postgres://. This can allow
+ The syntax begins with postgres://. This can allow
applications to avoid implementing their own parser for URIs
representing database connections.
@@ -11489,30 +11665,30 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Previously, libpq always collected the entire query
+ Previously, libpq always collected the entire query
result in memory before passing it back to the application.
- Add const qualifiers to the declarations of the functions
- PQconnectdbParams, PQconnectStartParams,
- and PQpingParams (Lionel Elie Mamane)
+ Add const qualifiers to the declarations of the functions
+ PQconnectdbParams, PQconnectStartParams,
+ and PQpingParams (Lionel Elie Mamane)
- Allow the .pgpass file to include escaped characters
+ Allow the .pgpass file to include escaped characters
in the password field (Robert Haas)
- Make library functions use abort() instead of
- exit() when it is necessary to terminate the process
+ Make library functions use abort() instead of
+ exit() when it is necessary to terminate the process
(Peter Eisentraut)
@@ -11557,7 +11733,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Install plpgsql.h into include/server during installation
+ Install plpgsql.h into include/server during installation
(Heikki Linnakangas)
@@ -11583,14 +11759,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Improve the concurrent transaction regression tests
- (isolationtester) (Noah Misch)
+ (isolationtester) (Noah Misch)
- Modify thread_test to create its test files in
- the current directory, rather than /tmp (Bruce Momjian)
+ Modify thread_test to create its test files in
+ the current directory, rather than /tmp (Bruce Momjian)
@@ -11639,7 +11815,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add a pg_upgrade test suite (Peter Eisentraut)
+ Add a pg_upgrade test suite (Peter Eisentraut)
@@ -11659,14 +11835,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add options to git_changelog for use in major
+ Add options to git_changelog for use in major
release note creation (Bruce Momjian)
- Support Linux's /proc/self/oom_score_adj API (Tom Lane)
+ Support Linux's /proc/self/oom_score_adj API (Tom Lane)
@@ -11688,13 +11864,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
This improvement does not apply to
- dblink_send_query()/dblink_get_result().
+ dblink_send_query()/dblink_get_result().
- Support force_not_null option in force_not_null option in file_fdw (Shigeru Hanada)
@@ -11702,7 +11878,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Implement dry-run mode for pg_archivecleanup
+ linkend="pgarchivecleanup">pg_archivecleanup
(Gabriele Bartolini)
@@ -11714,29 +11890,29 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add new pgbench switches
- , , and
+ (Robert Haas)
Change pg_test_fsync to test
+ linkend="pgtestfsync">pg_test_fsync to test
for a fixed amount of time, rather than a fixed number of cycles
(Bruce Momjian)
- The /cycles option was removed, and
+ /seconds added.
Add a pg_test_timing
+ linkend="pgtesttiming">pg_test_timing
utility to measure clock monotonicity and timing overhead (Ants
Aasma, Greg Smith)
@@ -11753,19 +11929,19 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- <link linkend="pgupgrade"><application>pg_upgrade</></link>
+ <link linkend="pgupgrade"><application>pg_upgrade</application></link>
- Adjust pg_upgrade environment variables (Bruce
+ Adjust pg_upgrade environment variables (Bruce
Momjian)
Rename data, bin, and port environment
- variables to begin with PG, and support
+ variables to begin with PG, and support
PGPORTOLD/PGPORTNEW, to replace
PGPORT.
@@ -11773,22 +11949,22 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Overhaul pg_upgrade logging and failure reporting
+ Overhaul pg_upgrade logging and failure reporting
(Bruce Momjian)
Create four append-only log files, and delete them on success.
- Add
- Make pg_upgrade create a script to incrementally
+ Make pg_upgrade create a script to incrementally
generate more accurate optimizer statistics (Bruce Momjian)
@@ -11800,14 +11976,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Allow pg_upgrade to upgrade an old cluster that
- does not have a postgres database (Bruce Momjian)
+ Allow pg_upgrade to upgrade an old cluster that
+ does not have a postgres database (Bruce Momjian)
- Allow pg_upgrade to handle cases where some
+ Allow pg_upgrade to handle cases where some
old or new databases are missing, as long as they are empty
(Bruce Momjian)
@@ -11815,14 +11991,14 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Allow pg_upgrade to handle configuration-only
+ Allow pg_upgrade to handle configuration-only
directory installations (Bruce Momjian)
- In pg_upgrade, add /
options to pass parameters to the servers (Bruce Momjian)
@@ -11833,7 +12009,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Change pg_upgrade to use port 50432 by default
+ Change pg_upgrade to use port 50432 by default
(Bruce Momjian)
@@ -11844,7 +12020,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Reduce cluster locking in pg_upgrade (Bruce
+ Reduce cluster locking in pg_upgrade (Bruce
Momjian)
@@ -11859,13 +12035,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- <link linkend="pgstatstatements"><application>pg_stat_statements</></link>
+ <link linkend="pgstatstatements"><application>pg_stat_statements</application></link>
- Allow pg_stat_statements to aggregate similar
+ Allow pg_stat_statements to aggregate similar
queries via SQL text normalization (Peter Geoghegan, Tom Lane)
@@ -11878,13 +12054,13 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Add dirtied and written block counts and read/write times to
- pg_stat_statements (Robert Haas, Ants Aasma)
+ pg_stat_statements (Robert Haas, Ants Aasma)
- Prevent pg_stat_statements from double-counting
+ Prevent pg_stat_statements from double-counting
PREPARE and EXECUTE commands
(Tom Lane)
@@ -11900,7 +12076,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Support SECURITY LABEL on global objects (KaiGai
+ Support SECURITY LABEL on global objects (KaiGai
Kohei, Robert Haas)
@@ -11925,7 +12101,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Add sepgsql_setcon() and related functions to control
+ Add sepgsql_setcon() and related functions to control
the sepgsql security domain (KaiGai Kohei)
@@ -11954,7 +12130,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Use gmake STYLE=website draft.
+ Use gmake STYLE=website draft.
@@ -11967,7 +12143,7 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
Document that user/database names are preserved with double-quoting
- by command-line tools like vacuumdb (Bruce
+ by command-line tools like vacuumdb (Bruce
Momjian)
@@ -11981,12 +12157,12 @@ Branch: REL9_2_STABLE [6b700301c] 2015-02-17 16:03:00 +0100
- Deprecate use of GLOBAL and LOCAL in
- CREATE TEMP TABLE (Noah Misch)
+ Deprecate use of GLOBAL and LOCAL in
+ CREATE TEMP TABLE (Noah Misch)
- PostgreSQL has long treated these keyword as no-ops,
+ PostgreSQL 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.
diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml
index 946e636d8bf..82f705522e6 100644
--- a/doc/src/sgml/release-9.3.sgml
+++ b/doc/src/sgml/release-9.3.sgml
@@ -1,6 +1,198 @@
+
+ Release 9.3.20
+
+
+ Release date:
+ 2017-11-09
+
+
+
+ This release contains a variety of fixes from 9.3.19.
+ For information about new features in the 9.3 major release, see
+ .
+
+
+
+ Migration to Version 9.3.20
+
+
+ A dump/restore is not required for those running 9.3.X.
+
+
+
+ However, if you are upgrading from a version earlier than 9.3.18,
+ see .
+
+
+
+
+
+ Changes
+
+
+
+
+
+ Properly reject attempts to convert infinite float values to
+ type numeric (Tom Lane, KaiGai Kohei)
+
+
+
+ Previously the behavior was platform-dependent.
+
+
+
+
+
+ Fix corner-case crashes when columns have been added to the end of a
+ view (Tom Lane)
+
+
+
+
+
+ Record proper dependencies when a view or rule
+ contains FieldSelect
+ or FieldStore expression nodes (Tom Lane)
+
+
+
+ Lack of these dependencies could allow a column or data
+ type DROP 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.
+
+
+
+
+
+ Correctly detect hashability of range data types (Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+ Fix low-probability loss of NOTIFY messages due to
+ XID wraparound (Marko Tiikkaja, Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+ Prevent low-probability crash in processing of nested trigger firings
+ (Tom Lane)
+
+
+
+
+
+ Correctly restore the umask setting when file creation fails
+ in COPY or lo_export()
+ (Peter Eisentraut)
+
+
+
+
+
+ Give a better error message for duplicate column names
+ in ANALYZE (Nathan Bossart)
+
+
+
+
+
+ Fix mis-parsing of the last line in a
+ non-newline-terminated pg_hba.conf file
+ (Tom Lane)
+
+
+
+
+
+ Fix libpq to not require user's home
+ directory to exist (Tom Lane)
+
+
+
+ In v10, failure to find the home directory while trying to
+ read ~/.pgpass 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 ~/.pg_service.conf, though this was less
+ obvious since that file is not sought unless a service name is
+ specified.
+
+
+
+
+
+ Fix libpq to guard against integer
+ overflow in the row count of a PGresult
+ (Michael Paquier)
+
+
+
+
+
+ Fix ecpg's handling of out-of-scope cursor
+ declarations with pointer or array variables (Michael Meskes)
+
+
+
+
+
+ Make ecpglib's Informix-compatibility mode ignore fractional digits in
+ integer input strings, as expected (Gao Zengqi, Michael Meskes)
+
+
+
+
+
+ Sync our copy of the timezone library with IANA release tzcode2017c
+ (Tom Lane)
+
+
+
+ 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 posixrules file exists in the timezone data
+ directory, now match current US law rather than what it was a dozen
+ years ago.
+
+
+
+
+
+ Update time zone data files to tzdata
+ 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.
+
+
+
+
+
+
+
+
Release 9.3.19
@@ -37,20 +229,20 @@
Show foreign tables
- in information_schema.table_privileges
+ in information_schema.table_privileges
view (Peter Eisentraut)
- All other relevant information_schema views include
+ All other relevant information_schema views include
foreign tables, but this one ignored them.
- Since this view definition is installed by initdb,
+ Since this view definition is installed by initdb,
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 psql:
+ in psql:
SET search_path TO information_schema;
CREATE OR REPLACE VIEW table_privileges AS
@@ -89,21 +281,21 @@ CREATE OR REPLACE VIEW table_privileges AS
OR grantee.rolname = 'PUBLIC');
This must be repeated in each database to be fixed,
- including template0.
+ including template0.
Clean up handling of a fatal exit (e.g., due to receipt
- of SIGTERM) that occurs while trying to execute
- a ROLLBACK of a failed transaction (Tom Lane)
+ of SIGTERM) that occurs while trying to execute
+ a ROLLBACK of a failed transaction (Tom Lane)
This situation could result in an assertion failure. In production
builds, the exit would still occur, but it would log an unexpected
- message about cannot drop active portal.
+ message about cannot drop active portal.
@@ -120,7 +312,7 @@ CREATE OR REPLACE VIEW table_privileges AS
- Certain ALTER commands that change the definition of a
+ Certain ALTER 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,
@@ -132,7 +324,7 @@ CREATE OR REPLACE VIEW table_privileges AS
- Fix crash in pg_restore when using parallel mode and
+ Fix crash in pg_restore when using parallel mode and
using a list file to select a subset of items to restore
(Fabrízio de Royes Mello)
@@ -140,13 +332,13 @@ CREATE OR REPLACE VIEW table_privileges AS
- Change ecpg's parser to allow RETURNING
+ Change ecpg's parser to allow RETURNING
clauses without attached C variables (Michael Meskes)
- This allows ecpg programs to contain SQL constructs
- that use RETURNING internally (for example, inside a CTE)
+ This allows ecpg programs to contain SQL constructs
+ that use RETURNING internally (for example, inside a CTE)
rather than using it to define values to be returned to the client.
@@ -158,12 +350,12 @@ CREATE OR REPLACE VIEW table_privileges AS
This fix avoids possible crashes of PL/Perl due to inconsistent
- assumptions about the width of time_t values.
+ assumptions about the width of time_t values.
A side-effect that may be visible to extension developers is
- that _USE_32BIT_TIME_T is no longer defined globally
- in PostgreSQL Windows builds. This is not expected
- to cause problems, because type time_t is not used
- in any PostgreSQL API definitions.
+ that _USE_32BIT_TIME_T is no longer defined globally
+ in PostgreSQL Windows builds. This is not expected
+ to cause problems, because type time_t is not used
+ in any PostgreSQL API definitions.
@@ -213,7 +405,7 @@ CREATE OR REPLACE VIEW table_privileges AS
Further restrict visibility
- of pg_user_mappings.umoptions, to
+ of pg_user_mappings.umoptions, to
protect passwords stored as user mapping options
(Noah Misch)
@@ -221,11 +413,11 @@ CREATE OR REPLACE VIEW table_privileges AS
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 USAGE permission on the associated foreign server.
+ have USAGE 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 information_schema.user_mapping_options does not
- show the options in such cases, pg_user_mappings
+ Since information_schema.user_mapping_options does not
+ show the options in such cases, pg_user_mappings
should not either.
(CVE-2017-7547)
@@ -240,15 +432,15 @@ CREATE OR REPLACE VIEW table_privileges AS
Restart the postmaster after adding allow_system_table_mods
- = true to postgresql.conf. (In versions
- supporting ALTER SYSTEM, you can use that to make the
+ = true to postgresql.conf. (In versions
+ supporting ALTER SYSTEM, you can use that to make the
configuration change, but you'll still need a restart.)
- In each database of the cluster,
+ In each database of the cluster,
run the following commands as superuser:
SET search_path = pg_catalog;
@@ -279,15 +471,15 @@ CREATE OR REPLACE VIEW pg_user_mappings AS
- Do not forget to include the template0
- and template1 databases, or the vulnerability will still
- exist in databases you create later. To fix template0,
+ Do not forget to include the template0
+ and template1 databases, or the vulnerability will still
+ exist in databases you create later. To fix template0,
you'll need to temporarily make it accept connections.
- In PostgreSQL 9.5 and later, you can use
+ In PostgreSQL 9.5 and later, you can use
ALTER DATABASE template0 WITH ALLOW_CONNECTIONS true;
- and then after fixing template0, undo that with
+ and then after fixing template0, undo that with
ALTER DATABASE template0 WITH ALLOW_CONNECTIONS false;
@@ -301,7 +493,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Finally, remove the allow_system_table_mods configuration
+ Finally, remove the allow_system_table_mods configuration
setting, and again restart the postmaster.
@@ -315,16 +507,16 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- libpq ignores empty password specifications, and does
+ libpq 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 psql or other libpq-based
+ via psql or other libpq-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-libpq-based client,
+ However, with a modified or non-libpq-based client,
logging in could be possible, depending on which authentication
method is configured. In particular the most common
- method, md5, accepted empty passwords.
+ method, md5, accepted empty passwords.
Change the server to reject empty passwords in all cases.
(CVE-2017-7546)
@@ -424,28 +616,28 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Fix possible creation of an invalid WAL segment when a standby is
- promoted just after it processes an XLOG_SWITCH WAL
+ promoted just after it processes an XLOG_SWITCH WAL
record (Andres Freund)
- Fix SIGHUP and SIGUSR1 handling in
+ Fix SIGHUP and SIGUSR1 handling in
walsender processes (Petr Jelinek, Andres Freund)
- Fix unnecessarily slow restarts of walreceiver
+ Fix unnecessarily slow restarts of walreceiver
processes due to race condition in postmaster (Tom Lane)
- Fix cases where an INSERT or UPDATE assigns
+ Fix cases where an INSERT or UPDATE assigns
to more than one element of a column that is of domain-over-array
type (Tom Lane)
@@ -453,7 +645,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Allow window functions to be used in sub-SELECTs that
+ Allow window functions to be used in sub-SELECTs that
are within the arguments of an aggregate function (Tom Lane)
@@ -461,56 +653,56 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Move autogenerated array types out of the way during
- ALTER ... RENAME (Vik Fearing)
+ ALTER ... RENAME (Vik Fearing)
Previously, we would rename a conflicting autogenerated array type
- out of the way during CREATE; this fix extends that
+ out of the way during CREATE; this fix extends that
behavior to renaming operations.
- Ensure that ALTER USER ... SET accepts all the syntax
- variants that ALTER ROLE ... SET does (Peter Eisentraut)
+ Ensure that ALTER USER ... SET accepts all the syntax
+ variants that ALTER ROLE ... SET does (Peter Eisentraut)
Properly update dependency info when changing a datatype I/O
- function's argument or return type from opaque to the
+ function's argument or return type from opaque to the
correct type (Heikki Linnakangas)
- CREATE TYPE updates I/O functions declared in this
+ CREATE TYPE updates I/O functions declared in this
long-obsolete style, but it forgot to record a dependency on the
- type, allowing a subsequent DROP TYPE to leave broken
+ type, allowing a subsequent DROP TYPE to leave broken
function definitions behind.
- Reduce memory usage when ANALYZE processes
- a tsvector column (Heikki Linnakangas)
+ Reduce memory usage when ANALYZE processes
+ a tsvector column (Heikki Linnakangas)
Fix unnecessary precision loss and sloppy rounding when multiplying
- or dividing money values by integers or floats (Tom Lane)
+ or dividing money values by integers or floats (Tom Lane)
Tighten checks for whitespace in functions that parse identifiers,
- such as regprocedurein() (Tom Lane)
+ such as regprocedurein() (Tom Lane)
@@ -521,20 +713,20 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Use relevant #define symbols from Perl while
- compiling PL/Perl (Ashutosh Sharma, Tom Lane)
+ Use relevant #define symbols from Perl while
+ compiling PL/Perl (Ashutosh Sharma, Tom Lane)
This avoids portability problems, typically manifesting as
- a handshake mismatch during library load, when working with
+ a handshake mismatch during library load, when working with
recent Perl versions.
- In libpq, reset GSS/SASL and SSPI authentication
+ In libpq, reset GSS/SASL and SSPI authentication
state properly after a failed connection attempt (Michael Paquier)
@@ -547,9 +739,9 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- In psql, fix failure when COPY FROM STDIN
+ In psql, fix failure when COPY FROM STDIN
is ended with a keyboard EOF signal and then another COPY
- FROM STDIN is attempted (Thomas Munro)
+ FROM STDIN is attempted (Thomas Munro)
@@ -560,8 +752,8 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_dump and pg_restore to
- emit REFRESH MATERIALIZED VIEW commands last (Tom Lane)
+ Fix pg_dump and pg_restore to
+ emit REFRESH MATERIALIZED VIEW commands last (Tom Lane)
@@ -572,7 +764,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_dump with the option to
drop event triggers as expected (Tom Lane)
@@ -585,14 +777,14 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_dump to not emit invalid SQL for an empty
+ Fix pg_dump to not emit invalid SQL for an empty
operator class (Daniel Gustafsson)
- Fix pg_dump output to stdout on Windows (Kuntal Ghosh)
+ Fix pg_dump output to stdout on Windows (Kuntal Ghosh)
@@ -603,14 +795,14 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_get_ruledef() to print correct output for
- the ON SELECT rule of a view whose columns have been
+ Fix pg_get_ruledef() to print correct output for
+ the ON SELECT rule of a view whose columns have been
renamed (Tom Lane)
- In some corner cases, pg_dump relies
- on pg_get_ruledef() to dump views, so that this error
+ In some corner cases, pg_dump relies
+ on pg_get_ruledef() to dump views, so that this error
could result in dump/reload failures.
@@ -618,13 +810,13 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Fix dumping of outer joins with empty constraints, such as the result
- of a NATURAL LEFT JOIN with no common columns (Tom Lane)
+ of a NATURAL LEFT JOIN with no common columns (Tom Lane)
- Fix dumping of function expressions in the FROM clause in
+ Fix dumping of function expressions in the FROM clause in
cases where the expression does not deparse into something that looks
like a function call (Tom Lane)
@@ -632,7 +824,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_basebackup output to stdout on Windows
+ Fix pg_basebackup output to stdout on Windows
(Haribabu Kommi)
@@ -644,8 +836,8 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_upgrade to ensure that the ending WAL record
- does not have = minimum
+ Fix pg_upgrade to ensure that the ending WAL record
+ does not have = minimum
(Bruce Momjian)
@@ -657,9 +849,9 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- In postgres_fdw, re-establish connections to remote
- servers after ALTER SERVER or ALTER USER
- MAPPING commands (Kyotaro Horiguchi)
+ In postgres_fdw, re-establish connections to remote
+ servers after ALTER SERVER or ALTER USER
+ MAPPING commands (Kyotaro Horiguchi)
@@ -670,7 +862,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- In postgres_fdw, allow cancellation of remote
+ In postgres_fdw, allow cancellation of remote
transaction control commands (Robert Haas, Rafia Sabih)
@@ -682,7 +874,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Always use , not , when building
shared libraries with gcc (Tom Lane)
@@ -702,27 +894,27 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- In MSVC builds, handle the case where the openssl
- library is not within a VC subdirectory (Andrew Dunstan)
+ In MSVC builds, handle the case where the openssl
+ library is not within a VC subdirectory (Andrew Dunstan)
- In MSVC builds, add proper include path for libxml2
+ In MSVC builds, add proper include path for libxml2
header files (Andrew Dunstan)
This fixes a former need to move things around in standard Windows
- installations of libxml2.
+ installations of libxml2.
In MSVC builds, recognize a Tcl library that is
- named tcl86.lib (Noah Misch)
+ named tcl86.lib (Noah Misch)
@@ -772,18 +964,18 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Restrict visibility
- of pg_user_mappings.umoptions, to
+ of pg_user_mappings.umoptions, to
protect passwords stored as user mapping options
(Michael Paquier, Feike Steenbergen)
The previous coding allowed the owner of a foreign server object,
- or anyone he has granted server USAGE permission to,
+ or anyone he has granted server USAGE 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
- information_schema.user_mapping_options, namely that
+ information_schema.user_mapping_options, namely that
these options are visible to the user being mapped, or if the mapping
is for PUBLIC and the current user is the server
owner, or if the current user is a superuser.
@@ -807,7 +999,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Some selectivity estimation functions in the planner will apply
user-defined operators to values obtained
- from pg_statistic, such as most common values and
+ from pg_statistic, 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,
@@ -821,17 +1013,17 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Restore libpq's recognition of
- the PGREQUIRESSL environment variable (Daniel Gustafsson)
+ Restore libpq's recognition of
+ the PGREQUIRESSL environment variable (Daniel Gustafsson)
Processing of this environment variable was unintentionally dropped
- in PostgreSQL 9.3, but its documentation remained.
+ in PostgreSQL 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 PGSSLMODE, to avoid
+ but give it lower priority than PGSSLMODE, to avoid
breaking configurations that work correctly with post-9.3 code.
(CVE-2017-7485)
@@ -839,7 +1031,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix possible corruption of init forks of unlogged indexes
+ Fix possible corruption of init forks of unlogged indexes
(Robert Haas, Michael Paquier)
@@ -852,7 +1044,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix incorrect reconstruction of pg_subtrans entries
+ Fix incorrect reconstruction of pg_subtrans entries
when a standby server replays a prepared but uncommitted two-phase
transaction (Tom Lane)
@@ -860,7 +1052,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
In most cases this turned out to have no visible ill effects, but in
corner cases it could result in circular references
- in pg_subtrans, potentially causing infinite loops
+ in pg_subtrans, potentially causing infinite loops
in queries that examine rows modified by the two-phase transaction.
@@ -875,19 +1067,19 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
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 ALTER TABLE
- ... RENAME.
+ ... RENAME.
Skip tablespace privilege checks when ALTER TABLE ... ALTER
- COLUMN TYPE rebuilds an existing index (Noah Misch)
+ COLUMN TYPE rebuilds an existing index (Noah Misch)
The command failed if the calling user did not currently have
- CREATE privilege for the tablespace containing the index.
+ CREATE privilege for the tablespace containing the index.
That behavior seems unhelpful, so skip the check, allowing the
index to be rebuilt where it is.
@@ -895,27 +1087,27 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse
- to child tables when the constraint is marked NO INHERIT
+ Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse
+ to child tables when the constraint is marked NO INHERIT
(Amit Langote)
- This fix prevents unwanted constraint does not exist failures
+ This fix prevents unwanted constraint does not exist failures
when no matching constraint is present in the child tables.
- Fix VACUUM to account properly for pages that could not
+ Fix VACUUM to account properly for pages that could not
be scanned due to conflicting page pins (Andrew Gierth)
This tended to lead to underestimation of the number of tuples in
the table. In the worst case of a small heavily-contended
- table, VACUUM could incorrectly report that the table
+ table, VACUUM could incorrectly report that the table
contained no tuples, leading to very bad planning choices.
@@ -929,33 +1121,33 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix cursor_to_xml() to produce valid output
- with tableforest = false
+ Fix cursor_to_xml() to produce valid output
+ with tableforest = false
(Thomas Munro, Peter Eisentraut)
- Previously it failed to produce a wrapping <table>
+ Previously it failed to produce a wrapping <table>
element.
- Improve performance of pg_timezone_names view
+ Improve performance of pg_timezone_names view
(Tom Lane, David Rowley)
- Fix sloppy handling of corner-case errors from lseek()
- and close() (Tom Lane)
+ Fix sloppy handling of corner-case errors from lseek()
+ and close() (Tom Lane)
Neither of these system calls are likely to fail in typical situations,
- but if they did, fd.c could get quite confused.
+ but if they did, fd.c could get quite confused.
@@ -973,21 +1165,21 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix ecpg to support COMMIT PREPARED
- and ROLLBACK PREPARED (Masahiko Sawada)
+ Fix ecpg to support COMMIT PREPARED
+ and ROLLBACK PREPARED (Masahiko Sawada)
Fix a double-free error when processing dollar-quoted string literals
- in ecpg (Michael Meskes)
+ in ecpg (Michael Meskes)
- In pg_dump, fix incorrect schema and owner marking for
+ In pg_dump, fix incorrect schema and owner marking for
comments and security labels of some types of database objects
(Giuseppe Broccolo, Tom Lane)
@@ -1002,20 +1194,20 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Avoid emitting an invalid list file in pg_restore -l
+ Avoid emitting an invalid list file in pg_restore -l
when SQL object names contain newlines (Tom Lane)
Replace newlines by spaces, which is sufficient to make the output
- valid for pg_restore -L's purposes.
+ valid for pg_restore -L's purposes.
- Fix pg_upgrade to transfer comments and security labels
- attached to large objects (blobs) (Stephen Frost)
+ Fix pg_upgrade to transfer comments and security labels
+ attached to large objects (blobs) (Stephen Frost)
@@ -1027,26 +1219,26 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Improve error handling
- in contrib/adminpack's pg_file_write()
+ in contrib/adminpack's pg_file_write()
function (Noah Misch)
Notably, it failed to detect errors reported
- by fclose().
+ by fclose().
- In contrib/dblink, avoid leaking the previous unnamed
+ In contrib/dblink, avoid leaking the previous unnamed
connection when establishing a new unnamed connection (Joe Conway)
- Fix contrib/pg_trgm's extraction of trigrams from regular
+ Fix contrib/pg_trgm's extraction of trigrams from regular
expressions (Tom Lane)
@@ -1059,7 +1251,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- In contrib/postgres_fdw,
+ In contrib/postgres_fdw,
transmit query cancellation requests to the remote server
(Michael Paquier, Etsuro Fujita)
@@ -1101,7 +1293,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Update time zone data files to tzdata release 2017b
+ Update time zone data files to tzdata 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
@@ -1115,9 +1307,9 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
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, PostgreSQL
+ abbreviation. At least for the time being, PostgreSQL
will continue to accept such removed abbreviations for timestamp input.
- But they will not be shown in the pg_timezone_names
+ But they will not be shown in the pg_timezone_names
view nor used for output.
@@ -1130,15 +1322,15 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
The Microsoft MSVC build scripts neglected to install
- the posixrules file in the timezone directory tree.
+ the posixrules 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 US/Eastern zone. If you don't want that, remove
- the posixrules file, or replace it with a copy of some
+ the US/Eastern zone. If you don't want that, remove
+ the posixrules file, or replace it with a copy of some
other zone file (see ). Note that
due to caching, you may need to restart the server to get such changes
to take effect.
@@ -1192,15 +1384,15 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Fix a race condition that could cause indexes built
- with CREATE INDEX CONCURRENTLY to be corrupt
+ with CREATE INDEX CONCURRENTLY to be corrupt
(Pavan Deolasee, Tom Lane)
- If CREATE INDEX CONCURRENTLY was used to build an index
+ If CREATE INDEX CONCURRENTLY was used to build an index
that depends on a column not previously indexed, then rows
updated by transactions that ran concurrently with
- the CREATE INDEX command could have received incorrect
+ the CREATE INDEX 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.
@@ -1209,13 +1401,13 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Unconditionally WAL-log creation of the init fork for an
+ Unconditionally WAL-log creation of the init fork for an
unlogged table (Michael Paquier)
Previously, this was skipped when
- = minimal, but actually it's necessary even in that case
+ = minimal, but actually it's necessary even in that case
to ensure that the unlogged table is properly reset to empty after a
crash.
@@ -1269,7 +1461,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Make sure ALTER TABLE preserves index tablespace
+ Make sure ALTER TABLE preserves index tablespace
assignments when rebuilding indexes (Tom Lane, Michael Paquier)
@@ -1287,15 +1479,15 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- This avoids could not find trigger NNN
- or relation NNN has no triggers errors.
+ This avoids could not find trigger NNN
+ or relation NNN has no triggers errors.
Fix processing of OID column when a table with OIDs is associated to
- a parent with OIDs via ALTER TABLE ... INHERIT (Amit
+ a parent with OIDs via ALTER TABLE ... INHERIT (Amit
Langote)
@@ -1309,7 +1501,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Report correct object identity during ALTER TEXT SEARCH
- CONFIGURATION (Artur Zakirov)
+ CONFIGURATION (Artur Zakirov)
@@ -1339,13 +1531,13 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Prevent multicolumn expansion of foo.* in
- an UPDATE source expression (Tom Lane)
+ Prevent multicolumn expansion of foo.* in
+ an UPDATE source expression (Tom Lane)
This led to UPDATE target count mismatch --- internal
- error. Now the syntax is understood as a whole-row variable,
+ error. Now the syntax is understood as a whole-row variable,
as it would be in other contexts.
@@ -1353,12 +1545,12 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Ensure that column typmods are determined accurately for
- multi-row VALUES constructs (Tom Lane)
+ multi-row VALUES constructs (Tom Lane)
This fixes problems occurring when the first value in a column has a
- determinable typmod (e.g., length for a varchar value) but
+ determinable typmod (e.g., length for a varchar value) but
later values don't share the same limit.
@@ -1373,15 +1565,15 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
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 (U&'...') or Unicode identifier
- (U&"...").
+ string literal (U&'...') or Unicode identifier
+ (U&"...").
Ensure that a purely negative text search query, such
- as !foo, matches empty tsvectors (Tom Dunstan)
+ as !foo, matches empty tsvectors (Tom Dunstan)
@@ -1392,33 +1584,33 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Prevent crash when ts_rewrite() replaces a non-top-level
+ Prevent crash when ts_rewrite() replaces a non-top-level
subtree with an empty query (Artur Zakirov)
- Fix performance problems in ts_rewrite() (Tom Lane)
+ Fix performance problems in ts_rewrite() (Tom Lane)
- Fix ts_rewrite()'s handling of nested NOT operators
+ Fix ts_rewrite()'s handling of nested NOT operators
(Tom Lane)
- Fix array_fill() to handle empty arrays properly (Tom Lane)
+ Fix array_fill() to handle empty arrays properly (Tom Lane)
- Fix one-byte buffer overrun in quote_literal_cstr()
+ Fix one-byte buffer overrun in quote_literal_cstr()
(Heikki Linnakangas)
@@ -1430,8 +1622,8 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Prevent multiple calls of pg_start_backup()
- and pg_stop_backup() from running concurrently (Michael
+ Prevent multiple calls of pg_start_backup()
+ and pg_stop_backup() from running concurrently (Michael
Paquier)
@@ -1443,15 +1635,15 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Avoid discarding interval-to-interval casts
+ Avoid discarding interval-to-interval casts
that aren't really no-ops (Tom Lane)
In some cases, a cast that should result in zeroing out
- low-order interval fields was mistakenly deemed to be a
+ low-order interval fields was mistakenly deemed to be a
no-op and discarded. An example is that casting from INTERVAL
- MONTH to INTERVAL YEAR failed to clear the months field.
+ MONTH to INTERVAL YEAR failed to clear the months field.
@@ -1464,14 +1656,14 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_dump to dump user-defined casts and transforms
+ Fix pg_dump to dump user-defined casts and transforms
that use built-in functions (Stephen Frost)
- Fix possible pg_basebackup failure on standby
+ Fix possible pg_basebackup failure on standby
server when including WAL files (Amit Kapila, Robert Haas)
@@ -1490,21 +1682,21 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix PL/Tcl to support triggers on tables that have .tupno
+ Fix PL/Tcl to support triggers on tables that have .tupno
as a column name (Tom Lane)
This matches the (previously undocumented) behavior of
- PL/Tcl's spi_exec and spi_execp commands,
- namely that a magic .tupno column is inserted only if
+ PL/Tcl's spi_exec and spi_execp commands,
+ namely that a magic .tupno column is inserted only if
there isn't a real column named that.
- Allow DOS-style line endings in ~/.pgpass files,
+ Allow DOS-style line endings in ~/.pgpass files,
even on Unix (Vik Fearing)
@@ -1516,23 +1708,23 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix one-byte buffer overrun if ecpg is given a file
+ Fix one-byte buffer overrun if ecpg is given a file
name that ends with a dot (Takayuki Tsunakawa)
- Fix psql's tab completion for ALTER DEFAULT
- PRIVILEGES (Gilles Darold, Stephen Frost)
+ Fix psql's tab completion for ALTER DEFAULT
+ PRIVILEGES (Gilles Darold, Stephen Frost)
- In psql, treat an empty or all-blank setting of
- the PAGER environment variable as meaning no
- pager (Tom Lane)
+ In psql, treat an empty or all-blank setting of
+ the PAGER environment variable as meaning no
+ pager (Tom Lane)
@@ -1543,22 +1735,22 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Improve contrib/dblink's reporting of
- low-level libpq errors, such as out-of-memory
+ Improve contrib/dblink's reporting of
+ low-level libpq errors, such as out-of-memory
(Joe Conway)
- Teach contrib/dblink to ignore irrelevant server options
- when it uses a contrib/postgres_fdw foreign server as
+ Teach contrib/dblink to ignore irrelevant server options
+ when it uses a contrib/postgres_fdw foreign server as
the source of connection options (Corey Huinker)
Previously, if the foreign server object had options that were not
- also libpq connection options, an error occurred.
+ also libpq connection options, an error occurred.
@@ -1584,7 +1776,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Update time zone data files to tzdata release 2016j
+ Update time zone data files to tzdata 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.
@@ -1648,7 +1840,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
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 could not read block XXX:
+ producing errors like could not read block XXX:
read only 0 of 8192 bytes. Checksum failures in the
visibility map are also possible, if checksumming is enabled.
@@ -1656,19 +1848,19 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Procedures for determining whether there is a problem and repairing it
if so are discussed at
- .
+ .
- Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that
+ Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that
have been updated by a subsequently-aborted transaction
(Álvaro Herrera)
- In 9.5 and later, the SELECT would sometimes fail to
+ In 9.5 and later, the SELECT 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.
@@ -1702,71 +1894,71 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix EXPLAIN to emit valid XML when
+ Fix EXPLAIN to emit valid XML when
is on (Markus Winand)
Previously the XML output-format option produced syntactically invalid
- tags such as <I/O-Read-Time>. That is now
- rendered as <I-O-Read-Time>.
+ tags such as <I/O-Read-Time>. That is now
+ rendered as <I-O-Read-Time>.
Suppress printing of zeroes for unmeasured times
- in EXPLAIN (Maksim Milyutin)
+ in EXPLAIN (Maksim Milyutin)
Certain option combinations resulted in printing zero values for times
that actually aren't ever measured in that combination. Our general
- policy in EXPLAIN is not to print such fields at all, so
+ policy in EXPLAIN is not to print such fields at all, so
do that consistently in all cases.
- Fix timeout length when VACUUM is waiting for exclusive
+ Fix timeout length when VACUUM is waiting for exclusive
table lock so that it can truncate the table (Simon Riggs)
The timeout was meant to be 50 milliseconds, but it was actually only
- 50 microseconds, causing VACUUM to give up on truncation
+ 50 microseconds, causing VACUUM to give up on truncation
much more easily than intended. Set it to the intended value.
- Fix bugs in merging inherited CHECK constraints while
+ Fix bugs in merging inherited CHECK constraints while
creating or altering a table (Tom Lane, Amit Langote)
- Allow identical CHECK constraints to be added to a parent
+ Allow identical CHECK 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 NOT VALID
+ constraint from the parent table with a NOT VALID
constraint on the child. Likewise, prevent merging of a NO
- INHERIT child constraint with an inherited constraint.
+ INHERIT child constraint with an inherited constraint.
Remove artificial restrictions on the values accepted
- by numeric_in() and numeric_recv()
+ by numeric_in() and numeric_recv()
(Tom Lane)
We allow numeric values up to the limit of the storage format (more
- than 1e100000), so it seems fairly pointless
- that numeric_in() rejected scientific-notation exponents
- above 1000. Likewise, it was silly for numeric_recv() to
+ than 1e100000), so it seems fairly pointless
+ that numeric_in() rejected scientific-notation exponents
+ above 1000. Likewise, it was silly for numeric_recv() to
reject more than 1000 digits in an input value.
@@ -1788,7 +1980,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Disallow starting a standalone backend with standby_mode
+ Disallow starting a standalone backend with standby_mode
turned on (Michael Paquier)
@@ -1802,7 +1994,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Don't try to share SSL contexts across multiple connections
- in libpq (Heikki Linnakangas)
+ in libpq (Heikki Linnakangas)
@@ -1813,30 +2005,30 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Avoid corner-case memory leak in libpq (Tom Lane)
+ Avoid corner-case memory leak in libpq (Tom Lane)
The reported problem involved leaking an error report
- during PQreset(), but there might be related cases.
+ during PQreset(), but there might be related cases.
- Make ecpg's and
options work consistently with our other executables (Haribabu Kommi)
- In pg_dump, never dump range constructor functions
+ In pg_dump, never dump range constructor functions
(Tom Lane)
- This oversight led to pg_upgrade failures with
+ This oversight led to pg_upgrade failures with
extensions containing range types, due to duplicate creation of the
constructor functions.
@@ -1844,8 +2036,8 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- In pg_xlogdump, retry opening new WAL segments when
- using option (Magnus Hagander)
@@ -1856,7 +2048,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_xlogdump to cope with a WAL file that begins
+ Fix pg_xlogdump to cope with a WAL file that begins
with a continuation record spanning more than one page (Pavan
Deolasee)
@@ -1864,8 +2056,8 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix contrib/intarray/bench/bench.pl to print the results
- of the EXPLAIN it does when given the option
(Daniel Gustafsson)
@@ -1886,17 +2078,17 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
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 tzdata
+ their time zone database, as they did in tzdata
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 pg_timezone_abbrevs view to fail altogether.
+ the pg_timezone_abbrevs view to fail altogether.
- Update time zone data files to tzdata release 2016h
+ Update time zone data files to tzdata 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,
@@ -1909,15 +2101,15 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
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, PostgreSQL
+ abbreviation. At least for the time being, PostgreSQL
will continue to accept such removed abbreviations for timestamp input.
- But they will not be shown in the pg_timezone_names
+ But they will not be shown in the pg_timezone_names
view nor used for output.
- In this update, AMT is no longer shown as being in use to
- mean Armenia Time. Therefore, we have changed the Default
+ In this update, AMT is no longer shown as being in use to
+ mean Armenia Time. Therefore, we have changed the Default
abbreviation set to interpret it as Amazon Time, thus UTC-4 not UTC+4.
@@ -1963,17 +2155,17 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Fix possible mis-evaluation of
- nested CASE-WHEN expressions (Heikki
+ nested CASE-WHEN expressions (Heikki
Linnakangas, Michael Paquier, Tom Lane)
- A CASE expression appearing within the test value
- subexpression of another CASE could become confused about
+ A CASE expression appearing within the test value
+ subexpression of another CASE 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 CASE expression could result in passing the wrong test
- value to functions called within a CASE expression in the
+ a CASE expression could result in passing the wrong test
+ value to functions called within a CASE 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)
@@ -1987,7 +2179,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Numerous places in vacuumdb and other client programs
+ Numerous places in vacuumdb 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
@@ -1996,22 +2188,22 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Fix handling of paired double quotes
- in psql's \connect
- and \password commands to match the documentation.
+ in psql's \connect
+ and \password commands to match the documentation.
- Introduce a new
- pg_dumpall now refuses to deal with database and role
+ pg_dumpall 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.
@@ -2021,40 +2213,40 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
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 pg_dumpall or other routine maintenance
+ executes pg_dumpall or other routine maintenance
operations. (CVE-2016-5424)
- Fix corner-case misbehaviors for IS NULL/IS NOT
- NULL applied to nested composite values (Andrew Gierth, Tom Lane)
+ Fix corner-case misbehaviors for IS NULL/IS NOT
+ NULL applied to nested composite values (Andrew Gierth, Tom Lane)
- The SQL standard specifies that IS NULL should return
+ The SQL standard specifies that IS NULL should return
TRUE for a row of all null values (thus ROW(NULL,NULL) IS
- NULL yields TRUE), but this is not meant to apply recursively
- (thus ROW(NULL, ROW(NULL,NULL)) IS NULL yields FALSE).
+ NULL yields TRUE), but this is not meant to apply recursively
+ (thus ROW(NULL, ROW(NULL,NULL)) IS NULL yields FALSE).
The core executor got this right, but certain planner optimizations
treated the test as recursive (thus producing TRUE in both cases),
- and contrib/postgres_fdw could produce remote queries
+ and contrib/postgres_fdw could produce remote queries
that misbehaved similarly.
- Make the inet and cidr data types properly reject
+ Make the inet and cidr data types properly reject
IPv6 addresses with too many colon-separated fields (Tom Lane)
- Prevent crash in close_ps()
- (the point ## lseg operator)
+ Prevent crash in close_ps()
+ (the point##lseg operator)
for NaN input coordinates (Tom Lane)
@@ -2065,19 +2257,19 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Avoid possible crash in pg_get_expr() when inconsistent
+ Avoid possible crash in pg_get_expr() when inconsistent
values are passed to it (Michael Paquier, Thomas Munro)
- Fix several one-byte buffer over-reads in to_number()
+ Fix several one-byte buffer over-reads in to_number()
(Peter Eisentraut)
- In several cases the to_number() function would read one
+ In several cases the to_number() 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.
@@ -2087,8 +2279,8 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Do not run the planner on the query contained in CREATE
- MATERIALIZED VIEW or CREATE TABLE AS
- when WITH NO DATA is specified (Michael Paquier,
+ MATERIALIZED VIEW or CREATE TABLE AS
+ when WITH NO DATA is specified (Michael Paquier,
Tom Lane)
@@ -2102,7 +2294,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Avoid unsafe intermediate state during expensive paths
- through heap_update() (Masahiko Sawada, Andres Freund)
+ through heap_update() (Masahiko Sawada, Andres Freund)
@@ -2128,15 +2320,15 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Avoid unnecessary could not serialize access errors when
- acquiring FOR KEY SHARE row locks in serializable mode
+ Avoid unnecessary could not serialize access errors when
+ acquiring FOR KEY SHARE row locks in serializable mode
(Álvaro Herrera)
- Avoid crash in postgres -C when the specified variable
+ Avoid crash in postgres -C when the specified variable
has a null string value (Michael Paquier)
@@ -2165,12 +2357,12 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Avoid consuming a transaction ID during VACUUM
+ Avoid consuming a transaction ID during VACUUM
(Alexander Korotkov)
- Some cases in VACUUM unnecessarily caused an XID to be
+ Some cases in VACUUM 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.
@@ -2179,12 +2371,12 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Avoid canceling hot-standby queries during VACUUM FREEZE
+ Avoid canceling hot-standby queries during VACUUM FREEZE
(Simon Riggs, Álvaro Herrera)
- VACUUM FREEZE on an otherwise-idle master server could
+ VACUUM FREEZE on an otherwise-idle master server could
result in unnecessary cancellations of queries on its standby
servers.
@@ -2199,15 +2391,15 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
The usual symptom of this bug is errors
- like MultiXactId NNN has not been created
+ like MultiXactId NNN has not been created
yet -- apparent wraparound.
- When a manual ANALYZE specifies a column list, don't
- reset the table's changes_since_analyze counter
+ When a manual ANALYZE specifies a column list, don't
+ reset the table's changes_since_analyze counter
(Tom Lane)
@@ -2219,7 +2411,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix ANALYZE's overestimation of n_distinct
+ Fix ANALYZE's overestimation of n_distinct
for a unique or nearly-unique column with many null entries (Tom
Lane)
@@ -2254,8 +2446,8 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix contrib/btree_gin to handle the smallest
- possible bigint value correctly (Peter Eisentraut)
+ Fix contrib/btree_gin to handle the smallest
+ possible bigint value correctly (Peter Eisentraut)
@@ -2268,53 +2460,53 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
It's planned to switch to two-part instead of three-part server
version numbers for releases after 9.6. Make sure
- that PQserverVersion() returns the correct value for
+ that PQserverVersion() returns the correct value for
such cases.
- Fix ecpg's code for unsigned long long
+ Fix ecpg's code for unsigned long long
array elements (Michael Meskes)
- In pg_dump with both
- Improve handling of SIGTERM/control-C in
- parallel pg_dump and pg_restore (Tom
+ Improve handling of SIGTERM/control-C in
+ parallel pg_dump and pg_restore (Tom
Lane)
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 CREATE INDEX.
+ are doing something long-running such as a CREATE INDEX.
- Fix error reporting in parallel pg_dump
- and pg_restore (Tom Lane)
+ Fix error reporting in parallel pg_dump
+ and pg_restore (Tom Lane)
- Previously, errors reported by pg_dump
- or pg_restore worker processes might never make it to
+ Previously, errors reported by pg_dump
+ or pg_restore 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 stderr. In some cases this will result in
+ everything to stderr. 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.
@@ -2322,8 +2514,8 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Ensure that parallel pg_dump
- or pg_restore on Windows will shut down properly
+ Ensure that parallel pg_dump
+ or pg_restore on Windows will shut down properly
after an error (Kyotaro Horiguchi)
@@ -2335,7 +2527,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Make pg_dump behave better when built without zlib
+ Make pg_dump behave better when built without zlib
support (Kyotaro Horiguchi)
@@ -2347,7 +2539,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Make pg_basebackup accept -Z 0 as
+ Make pg_basebackup accept -Z 0 as
specifying no compression (Fujii Masao)
@@ -2368,13 +2560,13 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Be more predictable about reporting statement timeout
- versus lock timeout (Tom Lane)
+ Be more predictable about reporting statement timeout
+ versus lock timeout (Tom Lane)
On heavily loaded machines, the regression tests sometimes failed due
- to reporting lock timeout even though the statement timeout
+ to reporting lock timeout even though the statement timeout
should have occurred first.
@@ -2394,7 +2586,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Update our copy of the timezone code to match
- IANA's tzcode release 2016c (Tom Lane)
+ IANA's tzcode release 2016c (Tom Lane)
@@ -2406,7 +2598,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Update time zone data files to tzdata release 2016f
+ Update time zone data files to tzdata release 2016f
for DST law changes in Kemerovo and Novosibirsk, plus historical
corrections for Azerbaijan, Belarus, and Morocco.
@@ -2462,7 +2654,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
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 libpq concurrently with
+ uses SSL connections in libpq 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.
@@ -2471,7 +2663,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix failed to build any N-way joins
+ Fix failed to build any N-way joins
planner error with a full join enclosed in the right-hand side of a
left join (Tom Lane)
@@ -2485,10 +2677,10 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Given a three-or-more-way equivalence class of variables, such
- as X.X = Y.Y = Z.Z, it was possible for the planner to omit
+ as X.X = Y.Y = Z.Z, 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 WHERE clauses. For various reasons, erroneous plans
+ the WHERE clauses. For various reasons, erroneous plans
were seldom selected in practice, so that this bug has gone undetected
for a long time.
@@ -2496,8 +2688,8 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix possible misbehavior of TH, th,
- and Y,YYY format codes in to_timestamp()
+ Fix possible misbehavior of TH, th,
+ and Y,YYY format codes in to_timestamp()
(Tom Lane)
@@ -2509,28 +2701,28 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix dumping of rules and views in which the array
- argument of a value operator
- ANY (array) construct is a sub-SELECT
+ Fix dumping of rules and views in which the array
+ argument of a valueoperator
+ ANY (array) construct is a sub-SELECT
(Tom Lane)
- Make pg_regress use a startup timeout from the
- PGCTLTIMEOUT environment variable, if that's set (Tom Lane)
+ Make pg_regress use a startup timeout from the
+ PGCTLTIMEOUT environment variable, if that's set (Tom Lane)
This is for consistency with a behavior recently added
- to pg_ctl; it eases automated testing on slow machines.
+ to pg_ctl; it eases automated testing on slow machines.
- Fix pg_upgrade to correctly restore extension
+ Fix pg_upgrade to correctly restore extension
membership for operator families containing only one operator class
(Tom Lane)
@@ -2538,20 +2730,20 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
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 pg_dump
+ immediate ill effects, but would cause later pg_dump
runs to emit output that would cause (harmless) errors on restore.
- Fix pg_upgrade to not fail when new-cluster TOAST rules
+ Fix pg_upgrade to not fail when new-cluster TOAST rules
differ from old (Tom Lane)
- pg_upgrade had special-case code to handle the
- situation where the new PostgreSQL version thinks that
+ pg_upgrade had special-case code to handle the
+ situation where the new PostgreSQL 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
@@ -2586,22 +2778,22 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Reduce the number of SysV semaphores used by a build configured with
- (Tom Lane)
- Rename internal function strtoi()
- to strtoint() to avoid conflict with a NetBSD library
+ Rename internal function strtoi()
+ to strtoint() to avoid conflict with a NetBSD library
function (Thomas Munro)
- Fix reporting of errors from bind()
- and listen() system calls on Windows (Tom Lane)
+ Fix reporting of errors from bind()
+ and listen() system calls on Windows (Tom Lane)
@@ -2614,19 +2806,19 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix putenv() to work properly with Visual Studio 2013
+ Fix putenv() to work properly with Visual Studio 2013
(Michael Paquier)
- Avoid possibly-unsafe use of Windows' FormatMessage()
+ Avoid possibly-unsafe use of Windows' FormatMessage()
function (Christian Ullrich)
- Use the FORMAT_MESSAGE_IGNORE_INSERTS flag where
+ Use the FORMAT_MESSAGE_IGNORE_INSERTS flag where
appropriate. No live bug is known to exist here, but it seems like a
good idea to be careful.
@@ -2634,9 +2826,9 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Update time zone data files to tzdata release 2016d
+ Update time zone data files to tzdata release 2016d
for DST law changes in Russia and Venezuela. There are new zone
- names Europe/Kirov and Asia/Tomsk to reflect
+ names Europe/Kirov and Asia/Tomsk to reflect
the fact that these regions now have different time zone histories from
adjacent regions.
@@ -2683,56 +2875,56 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Fix incorrect handling of NULL index entries in
- indexed ROW() comparisons (Tom Lane)
+ indexed ROW() comparisons (Tom Lane)
An index search using a row comparison such as ROW(a, b) >
- ROW('x', 'y') would stop upon reaching a NULL entry in
- the b column, ignoring the fact that there might be
- non-NULL b values associated with later values
- of a.
+ ROW('x', 'y') would stop upon reaching a NULL entry in
+ the b column, ignoring the fact that there might be
+ non-NULL b values associated with later values
+ of a.
Avoid unlikely data-loss scenarios due to renaming files without
- adequate fsync() calls before and after (Michael Paquier,
+ adequate fsync() calls before and after (Michael Paquier,
Tomas Vondra, Andres Freund)
- Correctly handle cases where pg_subtrans is close to XID
+ Correctly handle cases where pg_subtrans is close to XID
wraparound during server startup (Jeff Janes)
- Fix corner-case crash due to trying to free localeconv()
+ Fix corner-case crash due to trying to free localeconv()
output strings more than once (Tom Lane)
- Fix parsing of affix files for ispell dictionaries
+ Fix parsing of affix files for ispell dictionaries
(Tom Lane)
The code could go wrong if the affix file contained any characters
whose byte length changes during case-folding, for
- example I in Turkish UTF8 locales.
+ example I in Turkish UTF8 locales.
- Avoid use of sscanf() to parse ispell
+ Avoid use of sscanf() to parse ispell
dictionary files (Artur Zakirov)
@@ -2758,27 +2950,27 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix psql's tab completion logic to handle multibyte
+ Fix psql's tab completion logic to handle multibyte
characters properly (Kyotaro Horiguchi, Robert Haas)
- Fix psql's tab completion for
- SECURITY LABEL (Tom Lane)
+ Fix psql's tab completion for
+ SECURITY LABEL (Tom Lane)
- Pressing TAB after SECURITY LABEL might cause a crash
+ Pressing TAB after SECURITY LABEL might cause a crash
or offering of inappropriate keywords.
- Make pg_ctl accept a wait timeout from the
- PGCTLTIMEOUT environment variable, if none is specified on
+ Make pg_ctl accept a wait timeout from the
+ PGCTLTIMEOUT environment variable, if none is specified on
the command line (Noah Misch)
@@ -2792,26 +2984,26 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Fix incorrect test for Windows service status
- in pg_ctl (Manuel Mathar)
+ in pg_ctl (Manuel Mathar)
The previous set of minor releases attempted to
- fix pg_ctl to properly determine whether to send log
+ fix pg_ctl to properly determine whether to send log
messages to Window's Event Log, but got the test backwards.
- Fix pgbench to correctly handle the combination
- of -C and -M prepared options (Tom Lane)
+ Fix pgbench to correctly handle the combination
+ of -C and -M prepared options (Tom Lane)
- In pg_upgrade, skip creating a deletion script when
+ In pg_upgrade, skip creating a deletion script when
the new data directory is inside the old data directory (Bruce
Momjian)
@@ -2839,21 +3031,21 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Fix multiple mistakes in the statistics returned
- by contrib/pgstattuple's pgstatindex()
+ by contrib/pgstattuple's pgstatindex()
function (Tom Lane)
- Remove dependency on psed in MSVC builds, since it's no
+ Remove dependency on psed in MSVC builds, since it's no
longer provided by core Perl (Michael Paquier, Andrew Dunstan)
- Update time zone data files to tzdata release 2016c
+ Update time zone data files to tzdata 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
@@ -2914,25 +3106,25 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Perform an immediate shutdown if the postmaster.pid file
+ Perform an immediate shutdown if the postmaster.pid file
is removed (Tom Lane)
The postmaster now checks every minute or so
- that postmaster.pid is still there and still contains its
+ that postmaster.pid is still there and still contains its
own PID. If not, it performs an immediate shutdown, as though it had
- received SIGQUIT. The main motivation for this change
+ received SIGQUIT. 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 postmaster.pid and then starts a new
+ DBA forcibly removes postmaster.pid and then starts a new
postmaster.
- In SERIALIZABLE transaction isolation mode, serialization
+ In SERIALIZABLE transaction isolation mode, serialization
anomalies could be missed due to race conditions during insertions
(Kevin Grittner, Thomas Munro)
@@ -2941,7 +3133,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Fix failure to emit appropriate WAL records when doing ALTER
- TABLE ... SET TABLESPACE for unlogged relations (Michael Paquier,
+ TABLE ... SET TABLESPACE for unlogged relations (Michael Paquier,
Andres Freund)
@@ -2967,21 +3159,21 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix ALTER COLUMN TYPE to reconstruct inherited check
+ Fix ALTER COLUMN TYPE to reconstruct inherited check
constraints properly (Tom Lane)
- Fix REASSIGN OWNED to change ownership of composite types
+ Fix REASSIGN OWNED to change ownership of composite types
properly (Álvaro Herrera)
- Fix REASSIGN OWNED and ALTER OWNER to correctly
+ Fix REASSIGN OWNED and ALTER OWNER to correctly
update granted-permissions lists when changing owners of data types,
foreign data wrappers, or foreign servers (Bruce Momjian,
Álvaro Herrera)
@@ -2990,7 +3182,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix REASSIGN OWNED to ignore foreign user mappings,
+ Fix REASSIGN OWNED to ignore foreign user mappings,
rather than fail (Álvaro Herrera)
@@ -3004,13 +3196,13 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix planner's handling of LATERAL references (Tom
+ Fix planner's handling of LATERAL references (Tom
Lane)
This fixes some corner cases that led to failed to build any
- N-way joins or could not devise a query plan planner
+ N-way joins or could not devise a query plan planner
failures.
@@ -3032,22 +3224,22 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Speed up generation of unique table aliases in EXPLAIN and
+ Speed up generation of unique table aliases in EXPLAIN and
rule dumping, and ensure that generated aliases do not
- exceed NAMEDATALEN (Tom Lane)
+ exceed NAMEDATALEN (Tom Lane)
- Fix dumping of whole-row Vars in ROW()
- and VALUES() lists (Tom Lane)
+ Fix dumping of whole-row Vars in ROW()
+ and VALUES() lists (Tom Lane)
- Fix possible internal overflow in numeric division
+ Fix possible internal overflow in numeric division
(Dean Rasheed)
@@ -3099,7 +3291,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
This causes the code to emit regular expression is too
- complex errors in some cases that previously used unreasonable
+ complex errors in some cases that previously used unreasonable
amounts of time and memory.
@@ -3112,14 +3304,14 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Make %h and %r escapes
- in log_line_prefix work for messages emitted due
- to log_connections (Tom Lane)
+ Make %h and %r escapes
+ in log_line_prefix work for messages emitted due
+ to log_connections (Tom Lane)
- Previously, %h/%r started to work just after a
- new session had emitted the connection received log message;
+ Previously, %h/%r started to work just after a
+ new session had emitted the connection received log message;
now they work for that message too.
@@ -3132,7 +3324,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
This oversight resulted in failure to recover from crashes
- whenever logging_collector is turned on.
+ whenever logging_collector is turned on.
@@ -3158,13 +3350,13 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- In psql, ensure that libreadline's idea
+ In psql, ensure that libreadline's idea
of the screen size is updated when the terminal window size changes
(Merlin Moncure)
- Previously, libreadline did not notice if the window
+ Previously, libreadline did not notice if the window
was resized during query output, leading to strange behavior during
later input of multiline queries.
@@ -3172,15 +3364,15 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix psql's \det command to interpret its
- pattern argument the same way as other \d commands with
+ Fix psql's \det command to interpret its
+ pattern argument the same way as other \d commands with
potentially schema-qualified patterns do (Reece Hart)
- Avoid possible crash in psql's \c command
+ Avoid possible crash in psql's \c command
when previous connection was via Unix socket and command specifies a
new hostname and same username (Tom Lane)
@@ -3188,21 +3380,21 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- In pg_ctl start -w, test child process status directly
+ In pg_ctl start -w, test child process status directly
rather than relying on heuristics (Tom Lane, Michael Paquier)
- Previously, pg_ctl relied on an assumption that the new
- postmaster would always create postmaster.pid within five
+ Previously, pg_ctl relied on an assumption that the new
+ postmaster would always create postmaster.pid within five
seconds. But that can fail on heavily-loaded systems,
- causing pg_ctl to report incorrectly that the
+ causing pg_ctl to report incorrectly that the
postmaster failed to start.
Except on Windows, this change also means that a pg_ctl start
- -w done immediately after another such command will now reliably
+ -w 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.
@@ -3210,23 +3402,23 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- In pg_ctl start -w, don't attempt to use a wildcard listen
+ In pg_ctl start -w, don't attempt to use a wildcard listen
address to connect to the postmaster (Kondo Yuta)
- On Windows, pg_ctl would fail to detect postmaster
- startup if listen_addresses is set to 0.0.0.0
- or ::, because it would try to use that value verbatim as
+ On Windows, pg_ctl would fail to detect postmaster
+ startup if listen_addresses is set to 0.0.0.0
+ or ::, because it would try to use that value verbatim as
the address to connect to, which doesn't work. Instead assume
- that 127.0.0.1 or ::1, respectively, is the
+ that 127.0.0.1 or ::1, respectively, is the
right thing to use.
- In pg_ctl on Windows, check service status to decide
+ In pg_ctl on Windows, check service status to decide
where to send output, rather than checking if standard output is a
terminal (Michael Paquier)
@@ -3234,18 +3426,18 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- In pg_dump and pg_basebackup, adopt
+ In pg_dump and pg_basebackup, adopt
the GNU convention for handling tar-archive members exceeding 8GB
(Tom Lane)
- The POSIX standard for tar file format does not allow
+ The POSIX standard for tar file format does not allow
archive member files to exceed 8GB, but most modern implementations
- of tar support an extension that fixes that. Adopt
- this extension so that pg_dump with no
longer fails on tables with more than 8GB of data, and so
- that pg_basebackup can handle files larger than 8GB.
+ that pg_basebackup 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
@@ -3255,51 +3447,51 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix assorted corner-case bugs in pg_dump's processing
+ Fix assorted corner-case bugs in pg_dump's processing
of extension member objects (Tom Lane)
- Make pg_dump mark a view's triggers as needing to be
+ Make pg_dump mark a view's triggers as needing to be
processed after its rule, to prevent possible failure during
- parallel pg_restore (Tom Lane)
+ parallel pg_restore (Tom Lane)
Ensure that relation option values are properly quoted
- in pg_dump (Kouhei Sutou, Tom Lane)
+ in pg_dump (Kouhei Sutou, Tom Lane)
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 pg_dump. This is not an issue with any
- reloption currently supported by core PostgreSQL, but
+ issued by pg_dump. This is not an issue with any
+ reloption currently supported by core PostgreSQL, but
extensions could allow reloptions that cause the problem.
- Avoid repeated password prompts during parallel pg_dump
+ Avoid repeated password prompts during parallel pg_dump
(Zeus Kronion)
- Fix pg_upgrade's file-copying code to handle errors
+ Fix pg_upgrade's file-copying code to handle errors
properly on Windows (Bruce Momjian)
- Install guards in pgbench against corner-case overflow
+ Install guards in pgbench against corner-case overflow
conditions during evaluation of script-specified division or modulo
operators (Fabien Coelho, Michael Paquier)
@@ -3308,22 +3500,22 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Fix failure to localize messages emitted
- by pg_receivexlog and pg_recvlogical
+ by pg_receivexlog and pg_recvlogical
(Ioseph Kim)
- Avoid dump/reload problems when using both plpython2
- and plpython3 (Tom Lane)
+ Avoid dump/reload problems when using both plpython2
+ and plpython3 (Tom Lane)
- In principle, both versions of PL/Python can be used in
+ In principle, both versions of PL/Python can be used in
the same database, though not in the same session (because the two
- versions of libpython cannot safely be used concurrently).
- However, pg_restore and pg_upgrade both
+ versions of libpython cannot safely be used concurrently).
+ However, pg_restore and pg_upgrade both
do things that can fall foul of the same-session restriction. Work
around that by changing the timing of the check.
@@ -3331,42 +3523,42 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix PL/Python regression tests to pass with Python 3.5
+ Fix PL/Python regression tests to pass with Python 3.5
(Peter Eisentraut)
- Fix premature clearing of libpq's input buffer when
+ Fix premature clearing of libpq's input buffer when
socket EOF is seen (Tom Lane)
- This mistake caused libpq to sometimes not report the
+ This mistake caused libpq to sometimes not report the
backend's final error message before reporting server closed the
- connection unexpectedly.
+ connection unexpectedly.
- Prevent certain PL/Java parameters from being set by
+ Prevent certain PL/Java parameters from being set by
non-superusers (Noah Misch)
- This change mitigates a PL/Java security bug
- (CVE-2016-0766), which was fixed in PL/Java by marking
+ This change mitigates a PL/Java security bug
+ (CVE-2016-0766), which was fixed in PL/Java by marking
these parameters as superuser-only. To fix the security hazard for
- sites that update PostgreSQL more frequently
- than PL/Java, make the core code aware of them also.
+ sites that update PostgreSQL more frequently
+ than PL/Java, make the core code aware of them also.
- Improve libpq's handling of out-of-memory situations
+ Improve libpq's handling of out-of-memory situations
(Michael Paquier, Amit Kapila, Heikki Linnakangas)
@@ -3374,36 +3566,36 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Fix order of arguments
- in ecpg-generated typedef statements
+ in ecpg-generated typedef statements
(Michael Meskes)
- Use %g not %f format
- in ecpg's PGTYPESnumeric_from_double()
+ Use %g not %f format
+ in ecpg's PGTYPESnumeric_from_double()
(Tom Lane)
- Fix ecpg-supplied header files to not contain comments
+ Fix ecpg-supplied header files to not contain comments
continued from a preprocessor directive line onto the next line
(Michael Meskes)
- Such a comment is rejected by ecpg. It's not yet clear
- whether ecpg itself should be changed.
+ Such a comment is rejected by ecpg. It's not yet clear
+ whether ecpg itself should be changed.
- Fix hstore_to_json_loose()'s test for whether
- an hstore value can be converted to a JSON number (Tom Lane)
+ Fix hstore_to_json_loose()'s test for whether
+ an hstore value can be converted to a JSON number (Tom Lane)
@@ -3414,14 +3606,14 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Ensure that contrib/pgcrypto's crypt()
+ Ensure that contrib/pgcrypto's crypt()
function can be interrupted by query cancel (Andreas Karlsson)
- Accept flex versions later than 2.5.x
+ Accept flex versions later than 2.5.x
(Tom Lane, Michael Paquier)
@@ -3445,19 +3637,19 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Install our missing script where PGXS builds can find it
+ Install our missing script where PGXS builds can find it
(Jim Nasby)
This allows sane behavior in a PGXS build done on a machine where build
- tools such as bison are missing.
+ tools such as bison are missing.
- Ensure that dynloader.h is included in the installed
+ Ensure that dynloader.h is included in the installed
header files in MSVC builds (Bruce Momjian, Michael Paquier)
@@ -3465,11 +3657,11 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Add variant regression test expected-output file to match behavior of
- current libxml2 (Tom Lane)
+ current libxml2 (Tom Lane)
- The fix for libxml2's CVE-2015-7499 causes it not to
+ The fix for libxml2'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.
@@ -3478,7 +3670,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Update time zone data files to tzdata release 2016a for
+ Update time zone data files to tzdata release 2016a for
DST law changes in Cayman Islands, Metlakatla, and Trans-Baikal
Territory (Zabaykalsky Krai), plus historical corrections for Pakistan.
@@ -3524,13 +3716,13 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Guard against stack overflows in json parsing
+ Guard against stack overflows in json parsing
(Oskari Saarenmaa)
- If an application constructs PostgreSQL json
- or jsonb values from arbitrary user input, the application's
+ If an application constructs PostgreSQL json
+ or jsonb values from arbitrary user input, the application's
users can reliably crash the PostgreSQL server, causing momentary
denial of service. (CVE-2015-5289)
@@ -3538,8 +3730,8 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix contrib/pgcrypto to detect and report
- too-short crypt() salts (Josh Kupershmidt)
+ Fix contrib/pgcrypto to detect and report
+ too-short crypt() salts (Josh Kupershmidt)
@@ -3572,13 +3764,13 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix insertion of relations into the relation cache init file
+ Fix insertion of relations into the relation cache init file
(Tom Lane)
An oversight in a patch in the most recent minor releases
- caused pg_trigger_tgrelid_tgname_index to be omitted
+ caused pg_trigger_tgrelid_tgname_index 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
@@ -3596,7 +3788,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Improve LISTEN startup time when there are many unread
+ Improve LISTEN startup time when there are many unread
notifications (Matt Newell)
@@ -3608,7 +3800,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- This was seen primarily when restoring pg_dump output
+ This was seen primarily when restoring pg_dump output
for databases with many thousands of tables.
@@ -3623,13 +3815,13 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
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 ssl_renegotiation_limit to zero (disabled).
+ of ssl_renegotiation_limit to zero (disabled).
- Lower the minimum values of the *_freeze_max_age parameters
+ Lower the minimum values of the *_freeze_max_age parameters
(Andres Freund)
@@ -3641,7 +3833,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Limit the maximum value of wal_buffers to 2GB to avoid
+ Limit the maximum value of wal_buffers to 2GB to avoid
server crashes (Josh Berkus)
@@ -3649,15 +3841,15 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Avoid logging complaints when a parameter that can only be set at
- server start appears multiple times in postgresql.conf,
- and fix counting of line numbers after an include_dir
+ server start appears multiple times in postgresql.conf,
+ and fix counting of line numbers after an include_dir
directive (Tom Lane)
- Fix rare internal overflow in multiplication of numeric values
+ Fix rare internal overflow in multiplication of numeric values
(Dean Rasheed)
@@ -3665,21 +3857,21 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Guard against hard-to-reach stack overflows involving record types,
- range types, json, jsonb, tsquery,
- ltxtquery and query_int (Noah Misch)
+ range types, json, jsonb, tsquery,
+ ltxtquery and query_int (Noah Misch)
- Fix handling of DOW and DOY in datetime input
+ Fix handling of DOW and DOY in datetime input
(Greg Stark)
These tokens aren't meant to be used in datetime values, but previously
they resulted in opaque internal error messages rather
- than invalid input syntax.
+ than invalid input syntax.
@@ -3692,7 +3884,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Add recursion depth protections to regular expression, SIMILAR
- TO, and LIKE matching (Tom Lane)
+ TO, and LIKE matching (Tom Lane)
@@ -3744,22 +3936,22 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix unexpected out-of-memory situation during sort errors
- when using tuplestores with small work_mem settings (Tom
+ Fix unexpected out-of-memory situation during sort errors
+ when using tuplestores with small work_mem settings (Tom
Lane)
- Fix very-low-probability stack overrun in qsort (Tom Lane)
+ Fix very-low-probability stack overrun in qsort (Tom Lane)
- Fix invalid memory alloc request size failure in hash joins
- with large work_mem settings (Tomas Vondra, Tom Lane)
+ Fix invalid memory alloc request size failure in hash joins
+ with large work_mem settings (Tomas Vondra, Tom Lane)
@@ -3772,9 +3964,9 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
These mistakes could lead to incorrect query plans that would give wrong
answers, or to assertion failures in assert-enabled builds, or to odd
planner errors such as could not devise a query plan for the
- given query, could not find pathkey item to
- sort, plan should not reference subplan's variable,
- or failed to assign all NestLoopParams to plan nodes.
+ given query, could not find pathkey item to
+ sort, plan should not reference subplan's variable,
+ or failed to assign all NestLoopParams to plan nodes.
Thanks are due to Andreas Seltenreich and Piotr Stefaniak for fuzz
testing that exposed these problems.
@@ -3782,7 +3974,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Improve planner's performance for UPDATE/DELETE
+ Improve planner's performance for UPDATE/DELETE
on large inheritance sets (Tom Lane, Dean Rasheed)
@@ -3803,12 +3995,12 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
During postmaster shutdown, ensure that per-socket lock files are
removed and listen sockets are closed before we remove
- the postmaster.pid file (Tom Lane)
+ the postmaster.pid file (Tom Lane)
This avoids race-condition failures if an external script attempts to
- start a new postmaster as soon as pg_ctl stop returns.
+ start a new postmaster as soon as pg_ctl stop returns.
@@ -3835,7 +4027,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Do not print a WARNING when an autovacuum worker is already
+ Do not print a WARNING when an autovacuum worker is already
gone when we attempt to signal it, and reduce log verbosity for such
signals (Tom Lane)
@@ -3872,7 +4064,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- VACUUM attempted to recycle such pages, but did so in a
+ VACUUM attempted to recycle such pages, but did so in a
way that wasn't crash-safe.
@@ -3880,44 +4072,44 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Fix off-by-one error that led to otherwise-harmless warnings
- about apparent wraparound in subtrans/multixact truncation
+ about apparent wraparound in subtrans/multixact truncation
(Thomas Munro)
- Fix misreporting of CONTINUE and MOVE statement
- types in PL/pgSQL's error context messages
+ Fix misreporting of CONTINUE and MOVE statement
+ types in PL/pgSQL's error context messages
(Pavel Stehule, Tom Lane)
- Fix PL/Perl to handle non-ASCII error
+ Fix PL/Perl to handle non-ASCII error
message texts correctly (Alex Hunsaker)
- Fix PL/Python crash when returning the string
- representation of a record result (Tom Lane)
+ Fix PL/Python crash when returning the string
+ representation of a record result (Tom Lane)
- Fix some places in PL/Tcl that neglected to check for
- failure of malloc() calls (Michael Paquier, Álvaro
+ Fix some places in PL/Tcl that neglected to check for
+ failure of malloc() calls (Michael Paquier, Álvaro
Herrera)
- In contrib/isn, fix output of ISBN-13 numbers that begin
+ In contrib/isn, fix output of ISBN-13 numbers that begin
with 979 (Fabien Coelho)
@@ -3929,20 +4121,20 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Improve contrib/postgres_fdw's handling of
+ Improve contrib/postgres_fdw's handling of
collation-related decisions (Tom Lane)
The main user-visible effect is expected to be that comparisons
- involving varchar columns will be sent to the remote server
+ involving varchar columns will be sent to the remote server
for execution in more cases than before.
- Improve libpq's handling of out-of-memory conditions
+ Improve libpq's handling of out-of-memory conditions
(Michael Paquier, Heikki Linnakangas)
@@ -3950,64 +4142,64 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Fix memory leaks and missing out-of-memory checks
- in ecpg (Michael Paquier)
+ in ecpg (Michael Paquier)
- Fix psql's code for locale-aware formatting of numeric
+ Fix psql's code for locale-aware formatting of numeric
output (Tom Lane)
- The formatting code invoked by \pset numericlocale on
+ The formatting code invoked by \pset numericlocale on
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 money data type.
+ output from the money data type.
- Prevent crash in psql's \c command when
+ Prevent crash in psql's \c command when
there is no current connection (Noah Misch)
- Make pg_dump handle inherited NOT VALID
+ Make pg_dump handle inherited NOT VALID
check constraints correctly (Tom Lane)
- Fix selection of default zlib compression level
- in pg_dump's directory output format (Andrew Dunstan)
+ Fix selection of default zlib compression level
+ in pg_dump's directory output format (Andrew Dunstan)
- Ensure that temporary files created during a pg_dump
- run with tar-format output are not world-readable (Michael
+ Ensure that temporary files created during a pg_dump
+ run with tar-format output are not world-readable (Michael
Paquier)
- Fix pg_dump and pg_upgrade to support
- cases where the postgres or template1 database
+ Fix pg_dump and pg_upgrade to support
+ cases where the postgres or template1 database
is in a non-default tablespace (Marti Raudsepp, Bruce Momjian)
- Fix pg_dump to handle object privileges sanely when
+ Fix pg_dump to handle object privileges sanely when
dumping from a server too old to have a particular privilege type
(Tom Lane)
@@ -4015,11 +4207,11 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
When dumping data types from pre-9.2 servers, and when dumping
functions or procedural languages from pre-7.3
- servers, pg_dump would
- produce GRANT/REVOKE commands that revoked the
+ servers, pg_dump would
+ produce GRANT/REVOKE commands that revoked the
owner's grantable privileges and instead granted all privileges
- to PUBLIC. Since the privileges involved are
- just USAGE and EXECUTE, this isn't a security
+ to PUBLIC. Since the privileges involved are
+ just USAGE and EXECUTE, 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.
@@ -4028,18 +4220,18 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Fix pg_dump to dump shell types (Tom Lane)
+ Fix pg_dump to dump shell types (Tom Lane)
Shell types (that is, not-yet-fully-defined types) aren't useful for
- much, but nonetheless pg_dump should dump them.
+ much, but nonetheless pg_dump should dump them.
- Fix assorted minor memory leaks in pg_dump and other
+ Fix assorted minor memory leaks in pg_dump and other
client-side programs (Michael Paquier)
@@ -4047,11 +4239,11 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Fix spinlock assembly code for PPC hardware to be compatible
- with AIX's native assembler (Tom Lane)
+ with AIX's native assembler (Tom Lane)
- Building with gcc didn't work if gcc
+ Building with gcc didn't work if gcc
had been configured to use the native assembler, which is becoming more
common.
@@ -4059,14 +4251,14 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- On AIX, test the -qlonglong compiler option
+ On AIX, test the -qlonglong compiler option
rather than just assuming it's safe to use (Noah Misch)
- On AIX, use -Wl,-brtllib link option to allow
+ On AIX, use -Wl,-brtllib link option to allow
symbols to be resolved at runtime (Noah Misch)
@@ -4078,38 +4270,38 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Avoid use of inline functions when compiling with
- 32-bit xlc, due to compiler bugs (Noah Misch)
+ 32-bit xlc, due to compiler bugs (Noah Misch)
- Use librt for sched_yield() when necessary,
+ Use librt for sched_yield() when necessary,
which it is on some Solaris versions (Oskari Saarenmaa)
- Fix Windows install.bat script to handle target directory
+ Fix Windows install.bat script to handle target directory
names that contain spaces (Heikki Linnakangas)
- Make the numeric form of the PostgreSQL version number
- (e.g., 90405) readily available to extension Makefiles,
- as a variable named VERSION_NUM (Michael Paquier)
+ Make the numeric form of the PostgreSQL version number
+ (e.g., 90405) readily available to extension Makefiles,
+ as a variable named VERSION_NUM (Michael Paquier)
- Update time zone data files to tzdata release 2015g for
+ Update time zone data files to tzdata 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
- America/Fort_Nelson for the Canadian Northern Rockies.
+ America/Fort_Nelson for the Canadian Northern Rockies.
@@ -4141,7 +4333,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
However, if you are upgrading an installation that was previously
- upgraded using a pg_upgrade version between 9.3.0 and
+ upgraded using a pg_upgrade version between 9.3.0 and
9.3.4 inclusive, see the first changelog entry below.
@@ -4164,52 +4356,52 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Recent PostgreSQL releases introduced mechanisms to
+ Recent PostgreSQL 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 pg_upgrade could also cause such a failure, in
- installations that had used pg_upgrade versions
+ bug in pg_upgrade could also cause such a failure, in
+ installations that had used pg_upgrade versions
between 9.3.0 and 9.3.4.
- The pg_upgrade bug in question was that it would
- set oldestMultiXid to 1 in pg_control even
+ The pg_upgrade bug in question was that it would
+ set oldestMultiXid to 1 in pg_control 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 oldestMultiXid value can be
+ autovacuuming until a correct oldestMultiXid value can be
determined. If that would pose a hardship, users can avoid it by
- doing manual vacuuming before upgrading to this release.
+ doing manual vacuuming before upgrading to this release.
In detail:
- Check whether pg_controldata reports Latest
- checkpoint's oldestMultiXid to be 1. If not, there's nothing
+ Check whether pg_controldata reports Latest
+ checkpoint's oldestMultiXid to be 1. If not, there's nothing
to do.
- Look in PGDATA/pg_multixact/offsets to see if there's a
- file named 0000. If there is, there's nothing to do.
+ Look in PGDATA/pg_multixact/offsets to see if there's a
+ file named 0000. If there is, there's nothing to do.
Otherwise, for each table that has
- pg_class.relminmxid equal to 1,
- VACUUM that table with
+ pg_class.relminmxid equal to 1,
+ VACUUM that table with
both
and set to
zero. (You can use the vacuum cost delay parameters described
in to reduce
the performance consequences for concurrent sessions.) You must
- use PostgreSQL 9.3.5 or later to perform this step.
+ use PostgreSQL 9.3.5 or later to perform this step.
@@ -4223,7 +4415,7 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
With just the wrong timing of concurrent activity, a VACUUM
- FULL on a system catalog might fail to update the init file
+ FULL on a system catalog might fail to update the init file
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
@@ -4234,13 +4426,13 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
Avoid deadlock between incoming sessions and CREATE/DROP
- DATABASE (Tom Lane)
+ DATABASE (Tom Lane)
A new session starting in a database that is the target of
- a DROP DATABASE command, or is the template for
- a CREATE DATABASE command, could cause the command to wait
+ a DROP DATABASE command, or is the template for
+ a CREATE DATABASE command, could cause the command to wait
for five seconds and then fail, even if the new session would have
exited before that.
@@ -4302,12 +4494,12 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Avoid failures while fsync'ing data directory during
+ Avoid failures while fsync'ing data directory during
crash restart (Abhijit Menon-Sen, Tom Lane)
- In the previous minor releases we added a patch to fsync
+ In the previous minor releases we added a patch to fsync
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.
@@ -4319,28 +4511,28 @@ Branch: REL9_2_STABLE [37f30b251] 2016-04-18 13:19:52 -0400
- Also apply the same rules in initdb --sync-only.
+ Also apply the same rules in initdb --sync-only.
This case is less critical but it should act similarly.
- Fix pg_get_functiondef() to show
- functions' LEAKPROOF property, if set (Jeevan Chalke)
+ Fix pg_get_functiondef() to show
+ functions' LEAKPROOF property, if set (Jeevan Chalke)
- Remove configure's check prohibiting linking to a
- threaded libpython
- on OpenBSD (Tom Lane)
+ Remove configure's check prohibiting linking to a
+ threaded libpython
+ on OpenBSD (Tom Lane)
The failure this restriction was meant to prevent seems to not be a
- problem anymore on current OpenBSD
+ problem anymore on current OpenBSD
versions.
@@ -4355,15 +4547,15 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- Allow libpq to use TLS protocol versions beyond v1
+ Allow libpq to use TLS protocol versions beyond v1
(Noah Misch)
- For a long time, libpq was coded so that the only SSL
+ For a long time, libpq 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. (PostgreSQL servers were
+ TLS version with the server. (PostgreSQL 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.
@@ -4397,8 +4589,8 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- However, if you use contrib/citext's
- regexp_matches() functions, see the changelog entry below
+ However, if you use contrib/citext's
+ regexp_matches() functions, see the changelog entry below
about that.
@@ -4436,7 +4628,7 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- Our replacement implementation of snprintf() failed to
+ Our replacement implementation of snprintf() 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
@@ -4446,7 +4638,7 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- It remains possible that some calls of the *printf()
+ It remains possible that some calls of the *printf()
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.
@@ -4456,15 +4648,15 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- In contrib/pgcrypto, uniformly report decryption failures
- as Wrong key or corrupt data (Noah Misch)
+ In contrib/pgcrypto, uniformly report decryption failures
+ as Wrong key or corrupt data (Noah Misch)
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 pgcrypto's specific behaviors
+ While it's unknown whether pgcrypto's specific behaviors
are likewise exploitable, it seems better to avoid the risk by using a
one-size-fits-all message.
(CVE-2015-3167)
@@ -4479,7 +4671,7 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
Under certain usage patterns, the existing defenses against this might
- be insufficient, allowing pg_multixact/members files to be
+ be insufficient, allowing pg_multixact/members 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
@@ -4491,16 +4683,16 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- Fix incorrect declaration of contrib/citext's
- regexp_matches() functions (Tom Lane)
+ Fix incorrect declaration of contrib/citext's
+ regexp_matches() functions (Tom Lane)
- These functions should return setof text[], like the core
+ These functions should return setof text[], like the core
functions they are wrappers for; but they were incorrectly declared as
- returning just text[]. This mistake had two results: first,
+ returning just text[]. 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 g flag
+ should get is an empty set (zero rows). Second, the g flag
was effectively ignored, since you would get only one result array even
if there were multiple matches.
@@ -4508,16 +4700,16 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
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 PostgreSQL 9.5.
+ will not be changed by default until PostgreSQL 9.5.
In pre-9.5 branches, the old behavior exists in version 1.0 of
- the citext extension, while we have provided corrected
- declarations in version 1.1 (which is not installed by
+ the citext extension, while we have provided corrected
+ declarations in version 1.1 (which is not installed by
default). To adopt the fix in pre-9.5 branches, execute
- ALTER EXTENSION citext UPDATE TO '1.1' in each database in
- which citext is installed. (You can also update
+ ALTER EXTENSION citext UPDATE TO '1.1' in each database in
+ which citext is installed. (You can also update
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 citext's regexp_matches() functions.
+ use citext's regexp_matches() functions.
@@ -4559,7 +4751,7 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
This oversight in the planner has been observed to cause could
- not find RelOptInfo for given relids errors, but it seems possible
+ not find RelOptInfo for given relids errors, but it seems possible
that sometimes an incorrect query plan might get past that consistency
check and result in silently-wrong query output.
@@ -4587,7 +4779,7 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
This oversight has been seen to lead to failed to join all
- relations together errors in queries involving LATERAL,
+ relations together errors in queries involving LATERAL,
and that might happen in other cases as well.
@@ -4595,7 +4787,7 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
Fix possible deadlock at startup
- when max_prepared_transactions is too small
+ when max_prepared_transactions is too small
(Heikki Linnakangas)
@@ -4609,7 +4801,7 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- Recursively fsync() the data directory after a crash
+ Recursively fsync() the data directory after a crash
(Abhijit Menon-Sen, Robert Haas)
@@ -4629,19 +4821,19 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- Cope with unexpected signals in LockBufferForCleanup()
+ Cope with unexpected signals in LockBufferForCleanup()
(Andres Freund)
This oversight could result in spurious errors about multiple
- backends attempting to wait for pincount 1.
+ backends attempting to wait for pincount 1.
- Fix crash when doing COPY IN to a table with check
+ Fix crash when doing COPY IN to a table with check
constraints that contain whole-row references (Tom Lane)
@@ -4688,18 +4880,18 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- ANALYZE executes index expressions many times; if there are
+ ANALYZE executes index expressions many times; if there are
slow functions in such an expression, it's desirable to be able to
- cancel the ANALYZE before that loop finishes.
+ cancel the ANALYZE before that loop finishes.
- Ensure tableoid of a foreign table is reported
- correctly when a READ COMMITTED recheck occurs after
- locking rows in SELECT FOR UPDATE, UPDATE,
- or DELETE (Etsuro Fujita)
+ Ensure tableoid of a foreign table is reported
+ correctly when a READ COMMITTED recheck occurs after
+ locking rows in SELECT FOR UPDATE, UPDATE,
+ or DELETE (Etsuro Fujita)
@@ -4719,20 +4911,20 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- Recommend setting include_realm to 1 when using
+ Recommend setting include_realm to 1 when using
Kerberos/GSSAPI/SSPI authentication (Stephen Frost)
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 PostgreSQL 9.5.
+ it will become the default setting in PostgreSQL 9.5.
- Remove code for matching IPv4 pg_hba.conf entries to
+ Remove code for matching IPv4 pg_hba.conf entries to
IPv4-in-IPv6 addresses (Tom Lane)
@@ -4745,20 +4937,20 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
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 pg_hba.conf entries, which does not seem like a good
+ IPv4 pg_hba.conf entries, which does not seem like a good
thing to do in minor releases.)
- Report WAL flush, not insert, position in IDENTIFY_SYSTEM
+ Report WAL flush, not insert, position in IDENTIFY_SYSTEM
replication command (Heikki Linnakangas)
This avoids a possible startup failure
- in pg_receivexlog.
+ in pg_receivexlog.
@@ -4766,14 +4958,14 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
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 pg_ctl will wait for
+ service too soon; and ensure that pg_ctl will wait for
shutdown (Krystian Bigaj)
- Reduce risk of network deadlock when using libpq's
+ Reduce risk of network deadlock when using libpq's
non-blocking mode (Heikki Linnakangas)
@@ -4782,32 +4974,32 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
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 COPY FROM
- STDIN.) This worked properly in the normal blocking mode, but not
- so much in non-blocking mode. We've modified libpq
+ STDIN.) This worked properly in the normal blocking mode, but not
+ so much in non-blocking mode. We've modified libpq
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 PQconsumeInput() upon read-ready.
+ and be sure to call PQconsumeInput() upon read-ready.
- In libpq, fix misparsing of empty values in URI
+ In libpq, fix misparsing of empty values in URI
connection strings (Thomas Fanghaenel)
- Fix array handling in ecpg (Michael Meskes)
+ Fix array handling in ecpg (Michael Meskes)
- Fix psql to sanely handle URIs and conninfo strings as
- the first parameter to \connect
+ Fix psql to sanely handle URIs and conninfo strings as
+ the first parameter to \connect
(David Fetter, Andrew Dunstan, Álvaro Herrera)
@@ -4820,38 +5012,38 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- Suppress incorrect complaints from psql on some
- platforms that it failed to write ~/.psql_history at exit
+ Suppress incorrect complaints from psql on some
+ platforms that it failed to write ~/.psql_history at exit
(Tom Lane)
This misbehavior was caused by a workaround for a bug in very old
- (pre-2006) versions of libedit. We fixed it by
+ (pre-2006) versions of libedit. We fixed it by
removing the workaround, which will cause a similar failure to appear
- for anyone still using such versions of libedit.
- Recommendation: upgrade that library, or use libreadline.
+ for anyone still using such versions of libedit.
+ Recommendation: upgrade that library, or use libreadline.
- Fix pg_dump's rule for deciding which casts are
+ Fix pg_dump's rule for deciding which casts are
system-provided casts that should not be dumped (Tom Lane)
- In pg_dump, fix failure to honor -Z
- compression level option together with -Fd
+ In pg_dump, fix failure to honor -Z
+ compression level option together with -Fd
(Michael Paquier)
- Make pg_dump consider foreign key relationships
+ Make pg_dump consider foreign key relationships
between extension configuration tables while choosing dump order
(Gilles Darold, Michael Paquier, Stephen Frost)
@@ -4864,21 +5056,21 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- Avoid possible pg_dump failure when concurrent sessions
+ Avoid possible pg_dump failure when concurrent sessions
are creating and dropping temporary functions (Tom Lane)
- Fix dumping of views that are just VALUES(...) but have
+ Fix dumping of views that are just VALUES(...) but have
column aliases (Tom Lane)
- In pg_upgrade, force timeline 1 in the new cluster
+ In pg_upgrade, force timeline 1 in the new cluster
(Bruce Momjian)
@@ -4890,7 +5082,7 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- In pg_upgrade, check for improperly non-connectable
+ In pg_upgrade, check for improperly non-connectable
databases before proceeding
(Bruce Momjian)
@@ -4898,28 +5090,28 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- In pg_upgrade, quote directory paths
- properly in the generated delete_old_cluster script
+ In pg_upgrade, quote directory paths
+ properly in the generated delete_old_cluster script
(Bruce Momjian)
- In pg_upgrade, preserve database-level freezing info
+ In pg_upgrade, preserve database-level freezing info
properly
(Bruce Momjian)
This oversight could cause missing-clog-file errors for tables within
- the postgres and template1 databases.
+ the postgres and template1 databases.
- Run pg_upgrade and pg_resetxlog with
+ Run pg_upgrade and pg_resetxlog with
restricted privileges on Windows, so that they don't fail when run by
an administrator (Muhammad Asif Naeem)
@@ -4927,15 +5119,15 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- Improve handling of readdir() failures when scanning
- directories in initdb and pg_basebackup
+ Improve handling of readdir() failures when scanning
+ directories in initdb and pg_basebackup
(Marco Nenciarini)
- Fix slow sorting algorithm in contrib/intarray (Tom Lane)
+ Fix slow sorting algorithm in contrib/intarray (Tom Lane)
@@ -4953,7 +5145,7 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
- Update time zone data files to tzdata release 2015d
+ Update time zone data files to tzdata 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).
@@ -4988,11 +5180,11 @@ Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
However, if you are a Windows user and are using the Norwegian
- (Bokmål) locale, manual action is needed after the upgrade to
- replace any Norwegian (Bokmål)_Norway locale names stored
- in PostgreSQL system catalogs with the plain-ASCII
- alias Norwegian_Norway. For details see
-
+ (Bokmål) locale, manual action is needed after the upgrade to
+ replace any Norwegian (Bokmål)_Norway locale names stored
+ in PostgreSQL system catalogs with the plain-ASCII
+ alias Norwegian_Norway. For details see
+
@@ -5026,15 +5218,15 @@ Branch: REL9_0_STABLE [56b970f2e] 2015-02-02 10:00:52 -0500
- Fix buffer overruns in to_char()
+ Fix buffer overruns in to_char()
(Bruce Momjian)
- When to_char() processes a numeric formatting template
- calling for a large number of digits, PostgreSQL
+ When to_char() processes a numeric formatting template
+ calling for a large number of digits, PostgreSQL
would read past the end of a buffer. When processing a crafted
- timestamp formatting template, PostgreSQL would write
+ timestamp formatting template, PostgreSQL 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.
@@ -5054,27 +5246,27 @@ Branch: REL9_0_STABLE [9e05c5063] 2015-02-02 10:00:52 -0500
- Fix buffer overrun in replacement *printf() functions
+ Fix buffer overrun in replacement *printf() functions
(Tom Lane)
- PostgreSQL includes a replacement implementation
- of printf and related functions. This code will overrun
+ PostgreSQL includes a replacement implementation
+ of printf and related functions. This code will overrun
a stack buffer when formatting a floating point number (conversion
- specifiers e, E, f, F,
- g or G) with requested precision greater than
+ specifiers e, E, f, F,
+ g or G) 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 to_char() SQL function. While that is the only
- affected core PostgreSQL functionality, extension
+ the to_char() SQL function. While that is the only
+ affected core PostgreSQL functionality, extension
modules that use printf-family functions may be at risk as well.
- This issue primarily affects PostgreSQL on Windows.
- PostgreSQL uses the system implementation of these
+ This issue primarily affects PostgreSQL on Windows.
+ PostgreSQL uses the system implementation of these
functions where adequate, which it is on other modern platforms.
(CVE-2015-0242)
@@ -5099,12 +5291,12 @@ Branch: REL9_0_STABLE [0a3ee8a5f] 2015-02-02 10:00:52 -0500
- Fix buffer overruns in contrib/pgcrypto
+ Fix buffer overruns in contrib/pgcrypto
(Marko Tiikkaja, Noah Misch)
- Errors in memory size tracking within the pgcrypto
+ Errors in memory size tracking within the pgcrypto
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
@@ -5165,7 +5357,7 @@ Branch: REL9_0_STABLE [3a2063369] 2015-01-28 12:33:29 -0500
Some server error messages show the values of columns that violate
a constraint, such as a unique constraint. If the user does not have
- SELECT privilege on all columns of the table, this could
+ SELECT 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.
@@ -5214,14 +5406,14 @@ Branch: REL9_2_STABLE [6bf343c6e] 2015-01-16 13:10:23 +0200
- Cope with the Windows locale named Norwegian (Bokmål)
+ Cope with the Windows locale named Norwegian (Bokmål)
(Heikki Linnakangas)
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, Norwegian_Norway.
+ name to a plain-ASCII alias, Norwegian_Norway.
@@ -5236,7 +5428,7 @@ Branch: REL9_0_STABLE [45a607d5c] 2014-11-04 13:24:26 -0500
Avoid possible data corruption if ALTER DATABASE SET
- TABLESPACE is used to move a database to a new tablespace and then
+ TABLESPACE is used to move a database to a new tablespace and then
shortly later move it back to its original tablespace (Tom Lane)
@@ -5256,14 +5448,14 @@ Branch: REL9_0_STABLE [73f950fc8] 2014-10-30 13:03:39 -0400
- Avoid corrupting tables when ANALYZE inside a transaction
+ Avoid corrupting tables when ANALYZE inside a transaction
is rolled back (Andres Freund, Tom Lane, Michael Paquier)
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 pg_class flags not set though they
+ with the relevant pg_class flags not set though they
should be.
@@ -5278,8 +5470,8 @@ Branch: REL9_1_STABLE [d5fef87e9] 2014-10-20 23:47:45 +0200
Ensure that unlogged tables are copied correctly
- during CREATE DATABASE or ALTER DATABASE SET
- TABLESPACE (Pavan Deolasee, Andres Freund)
+ during CREATE DATABASE or ALTER DATABASE SET
+ TABLESPACE (Pavan Deolasee, Andres Freund)
@@ -5291,12 +5483,12 @@ Branch: REL9_3_STABLE [e35db342a] 2014-09-22 16:19:59 -0400
Fix incorrect processing
- of CreateEventTrigStmt.eventname (Petr
+ of CreateEventTrigStmt.eventname (Petr
Jelinek)
- This could result in misbehavior if CREATE EVENT TRIGGER
+ This could result in misbehavior if CREATE EVENT TRIGGER
were executed as a prepared query, or via extended query protocol.
@@ -5310,7 +5502,7 @@ Branch: REL9_1_STABLE [94d5d57d5] 2014-11-11 17:00:28 -0500
- Fix DROP's dependency searching to correctly handle the
+ Fix DROP's dependency searching to correctly handle the
case where a table column is recursively visited before its table
(Petr Jelinek, Tom Lane)
@@ -5318,7 +5510,7 @@ Branch: REL9_1_STABLE [94d5d57d5] 2014-11-11 17:00:28 -0500
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 DROP EXTENSION unless CASCADE is
+ refuse a DROP EXTENSION unless CASCADE is
specified, which should not be required.
@@ -5340,7 +5532,7 @@ Branch: REL9_0_STABLE [5308e085b] 2015-01-15 18:52:38 -0500
- In READ COMMITTED mode, queries that lock or update
+ In READ COMMITTED mode, queries that lock or update
recently-updated rows could crash as a result of this bug.
@@ -5369,8 +5561,8 @@ Branch: REL9_3_STABLE [54a8abc2b] 2015-01-04 15:48:29 -0300
Fix failure to wait when a transaction tries to acquire a FOR
- NO KEY EXCLUSIVE tuple lock, while multiple other transactions
- currently hold FOR SHARE locks (Álvaro Herrera)
+ NO KEY EXCLUSIVE tuple lock, while multiple other transactions
+ currently hold FOR SHARE locks (Álvaro Herrera)
@@ -5384,15 +5576,15 @@ Branch: REL9_0_STABLE [662eebdc6] 2014-12-11 21:02:41 -0500
- Fix planning of SELECT FOR UPDATE when using a partial
+ Fix planning of SELECT FOR UPDATE when using a partial
index on a child table (Kyotaro Horiguchi)
- In READ COMMITTED mode, SELECT FOR UPDATE must
- also recheck the partial index's WHERE condition when
+ In READ COMMITTED mode, SELECT FOR UPDATE must
+ also recheck the partial index's WHERE condition when
rechecking a recently-updated row to see if it still satisfies the
- query's WHERE condition. This requirement was missed if the
+ query's WHERE 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.
@@ -5408,12 +5600,12 @@ Branch: REL9_0_STABLE [f5e4e92fb] 2014-12-11 19:37:17 -0500
- Fix corner case wherein SELECT FOR UPDATE could return a row
+ Fix corner case wherein SELECT FOR UPDATE could return a row
twice, and possibly miss returning other rows (Tom Lane)
- In READ COMMITTED mode, a SELECT FOR UPDATE
+ In READ COMMITTED mode, a SELECT FOR UPDATE
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.
@@ -5429,7 +5621,7 @@ Branch: REL9_3_STABLE [939f0fb67] 2015-01-15 13:18:19 -0500
- Improve performance of EXPLAIN with large range tables
+ Improve performance of EXPLAIN with large range tables
(Tom Lane)
@@ -5445,7 +5637,7 @@ Branch: REL9_0_STABLE [4ff49746e] 2014-08-09 13:46:52 -0400
Reject duplicate column names in the referenced-columns list of
- a FOREIGN KEY declaration (David Rowley)
+ a FOREIGN KEY declaration (David Rowley)
@@ -5462,7 +5654,7 @@ Branch: REL9_3_STABLE [6306d0712] 2014-07-22 13:30:14 -0400
- Re-enable error for SELECT ... OFFSET -1 (Tom Lane)
+ Re-enable error for SELECT ... OFFSET -1 (Tom Lane)
@@ -5499,7 +5691,7 @@ Branch: REL9_3_STABLE [8571ecb24] 2014-12-02 15:02:43 -0500
- Fix json_agg() to not return extra trailing right
+ Fix json_agg() to not return extra trailing right
brackets in its result (Tom Lane)
@@ -5514,7 +5706,7 @@ Branch: REL9_0_STABLE [26f8a4691] 2014-09-11 23:31:06 -0400
- Fix bugs in raising a numeric value to a large integral power
+ Fix bugs in raising a numeric value to a large integral power
(Tom Lane)
@@ -5535,19 +5727,19 @@ Branch: REL9_0_STABLE [e6550626c] 2014-12-01 15:25:18 -0500
- In numeric_recv(), truncate away any fractional digits
- that would be hidden according to the value's dscale field
+ In numeric_recv(), truncate away any fractional digits
+ that would be hidden according to the value's dscale field
(Tom Lane)
- A numeric value's display scale (dscale) should
+ A numeric value's display scale (dscale) should
never be less than the number of nonzero fractional digits; but
apparently there's at least one broken client application that
- transmits binary numeric values in which that's true.
+ transmits binary numeric 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 hidden
+ The least risky fix seems to be to truncate away such hidden
digits on receipt, so that the value is indeed what it prints as.
@@ -5566,7 +5758,7 @@ Branch: REL9_2_STABLE [3359a818c] 2014-09-23 20:25:39 -0400
Matching would often fail when the number of allowed iterations is
- limited by a ? quantifier or a bound expression.
+ limited by a ? quantifier or a bound expression.
@@ -5601,7 +5793,7 @@ Branch: REL9_0_STABLE [10059c2da] 2014-10-27 10:51:38 +0200
- Fix bugs in tsquery @> tsquery
+ Fix bugs in tsquery@>tsquery
operator (Heikki Linnakangas)
@@ -5658,14 +5850,14 @@ Branch: REL9_0_STABLE [cebb3f032] 2015-01-17 22:37:32 -0500
- Fix namespace handling in xpath() (Ali Akbar)
+ Fix namespace handling in xpath() (Ali Akbar)
- Previously, the xml value resulting from
- an xpath() call would not have namespace declarations if
+ Previously, the xml value resulting from
+ an xpath() call would not have namespace declarations if
the namespace declarations were attached to an ancestor element in the
- input xml value, rather than to the specific element being
+ input xml value, rather than to the specific element being
returned. Propagate the ancestral declaration so that the result is
correct when considered in isolation.
@@ -5685,7 +5877,7 @@ Branch: REL9_2_STABLE [19ccaf9d4] 2014-11-10 15:21:26 -0500
- In some contexts, constructs like row_to_json(tab.*) may
+ In some contexts, constructs like row_to_json(tab.*) 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
@@ -5703,7 +5895,7 @@ Branch: REL9_2_STABLE [906599f65] 2014-11-22 16:01:15 -0500
Fix mishandling of system columns,
- particularly tableoid, in FDW queries (Etsuro Fujita)
+ particularly tableoid, in FDW queries (Etsuro Fujita)
@@ -5721,7 +5913,7 @@ Branch: REL9_3_STABLE [527ff8baf] 2015-01-30 12:30:43 -0500
- This patch fixes corner-case unexpected operator NNNN planner
+ This patch fixes corner-case unexpected operator NNNN planner
errors, and improves the selectivity estimates for some other cases.
@@ -5734,13 +5926,13 @@ Branch: REL9_2_STABLE [4586572d7] 2014-10-26 16:12:32 -0400
- Avoid doing indexed_column = ANY
- (array) as an index qualifier if that leads
+ Avoid doing indexed_column = ANY
+ (array) as an index qualifier if that leads
to an inferior plan (Andrew Gierth)
- In some cases, = ANY conditions applied to non-first index
+ In some cases, = ANY 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.
@@ -5753,9 +5945,9 @@ Branch: REL9_3_STABLE [4e54685d0] 2014-10-20 12:23:48 -0400
- Fix variable not found in subplan target list planner
+ Fix variable not found in subplan target list planner
failure when an inline-able SQL function taking a composite argument
- is used in a LATERAL subselect and the composite argument
+ is used in a LATERAL subselect and the composite argument
is a lateral reference (Tom Lane)
@@ -5771,7 +5963,7 @@ Branch: REL9_0_STABLE [288f15b7c] 2014-10-01 19:30:41 -0400
Fix planner problems with nested append relations, such as inherited
- tables within UNION ALL subqueries (Tom Lane)
+ tables within UNION ALL subqueries (Tom Lane)
@@ -5800,8 +5992,8 @@ Branch: REL9_0_STABLE [50a757698] 2014-10-03 13:01:27 -0300
- Exempt tables that have per-table cost_limit
- and/or cost_delay settings from autovacuum's global cost
+ Exempt tables that have per-table cost_limit
+ and/or cost_delay settings from autovacuum's global cost
balancing rules (Álvaro Herrera)
@@ -5835,7 +6027,7 @@ Branch: REL9_0_STABLE [91b4a881c] 2014-07-30 14:42:12 -0400
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 only do anti-wraparound vacuums and
+ turned off, workers only do anti-wraparound vacuums and
not any other work.
@@ -5899,12 +6091,12 @@ Branch: REL9_0_STABLE [804983961] 2014-07-29 11:58:17 +0300
Fix several cases where recovery logic improperly ignored WAL records
- for COMMIT/ABORT PREPARED (Heikki Linnakangas)
+ for COMMIT/ABORT PREPARED (Heikki Linnakangas)
The most notable oversight was
- that recovery_target_xid could not be used to stop at
+ that recovery_target_xid could not be used to stop at
a two-phase commit.
@@ -5932,7 +6124,7 @@ Branch: REL9_0_STABLE [83c7bfb9a] 2014-11-06 21:26:21 +0900
- Avoid creating unnecessary .ready marker files for
+ Avoid creating unnecessary .ready marker files for
timeline history files (Fujii Masao)
@@ -5948,8 +6140,8 @@ Branch: REL9_0_STABLE [857a5d6b5] 2014-09-05 02:19:57 +0900
Fix possible null pointer dereference when an empty prepared statement
- is used and the log_statement setting is mod
- or ddl (Fujii Masao)
+ is used and the log_statement setting is mod
+ or ddl (Fujii Masao)
@@ -5965,7 +6157,7 @@ Branch: REL9_0_STABLE [a1a8d0249] 2015-01-19 23:01:46 -0500
- Change pgstat wait timeout warning message to be LOG level,
+ Change pgstat wait timeout warning message to be LOG level,
and rephrase it to be more understandable (Tom Lane)
@@ -5974,7 +6166,7 @@ Branch: REL9_0_STABLE [a1a8d0249] 2015-01-19 23:01:46 -0500
case, but it occurs often enough on our slower buildfarm members to be
a nuisance. Reduce it to LOG level, and expend a bit more effort on
the wording: it now reads using stale statistics instead of
- current ones because stats collector is not responding.
+ current ones because stats collector is not responding.
@@ -6018,7 +6210,7 @@ Branch: REL9_0_STABLE [2e4946169] 2015-01-07 22:46:20 -0500
- Warn if macOS's setlocale() starts an unwanted extra
+ Warn if macOS's setlocale() starts an unwanted extra
thread inside the postmaster (Noah Misch)
@@ -6033,13 +6225,13 @@ Branch: REL9_0_STABLE [9880fea4f] 2014-11-25 17:39:09 +0200
- Fix processing of repeated dbname parameters
- in PQconnectdbParams() (Alex Shulgin)
+ Fix processing of repeated dbname parameters
+ in PQconnectdbParams() (Alex Shulgin)
Unexpected behavior ensued if the first occurrence
- of dbname contained a connection string or URI to be
+ of dbname contained a connection string or URI to be
expanded.
@@ -6054,12 +6246,12 @@ Branch: REL9_0_STABLE [ac6e87537] 2014-10-22 18:42:01 -0400
- Ensure that libpq reports a suitable error message on
+ Ensure that libpq reports a suitable error message on
unexpected socket EOF (Marko Tiikkaja, Tom Lane)
- Depending on kernel behavior, libpq might return an
+ Depending on kernel behavior, libpq might return an
empty error string rather than something useful when the server
unexpectedly closed the socket.
@@ -6075,14 +6267,14 @@ Branch: REL9_0_STABLE [49ef4eba2] 2014-10-29 14:35:39 +0200
- Clear any old error message during PQreset()
+ Clear any old error message during PQreset()
(Heikki Linnakangas)
- If PQreset() is called repeatedly, and the connection
+ If PQreset() is called repeatedly, and the connection
cannot be re-established, error messages from the failed connection
- attempts kept accumulating in the PGconn's error
+ attempts kept accumulating in the PGconn's error
string.
@@ -6098,7 +6290,7 @@ Branch: REL9_0_STABLE [1f3517039] 2014-11-25 14:10:54 +0200
Properly handle out-of-memory conditions while parsing connection
- options in libpq (Alex Shulgin, Heikki Linnakangas)
+ options in libpq (Alex Shulgin, Heikki Linnakangas)
@@ -6112,8 +6304,8 @@ Branch: REL9_0_STABLE [d9a1e9de5] 2014-10-06 21:23:50 -0400
- Fix array overrun in ecpg's version
- of ParseDateTime() (Michael Paquier)
+ Fix array overrun in ecpg's version
+ of ParseDateTime() (Michael Paquier)
@@ -6127,7 +6319,7 @@ Branch: REL9_0_STABLE [d67be559e] 2014-12-05 14:30:55 +0200
- In initdb, give a clearer error message if a password
+ In initdb, give a clearer error message if a password
file is specified but is empty (Mats Erik Andersson)
@@ -6142,12 +6334,12 @@ Branch: REL9_0_STABLE [44c518328] 2014-09-08 16:10:05 -0400
- Fix psql's \s command to work nicely with
+ Fix psql's \s command to work nicely with
libedit, and add pager support (Stepan Rutz, Tom Lane)
- When using libedit rather than readline, \s printed the
+ When using libedit rather than readline, \s 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
@@ -6157,7 +6349,7 @@ Branch: REL9_0_STABLE [44c518328] 2014-09-08 16:10:05 -0400
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 psql
+ Multiline history entries written by older psql
versions will be read cleanly with this patch, but perhaps not
vice versa, depending on the exact libedit versions involved.
@@ -6175,17 +6367,17 @@ Branch: REL9_0_STABLE [2600e4436] 2014-12-31 12:17:12 -0500
- Improve consistency of parsing of psql's special
+ Improve consistency of parsing of psql's special
variables (Tom Lane)
- Allow variant spellings of on and off (such
- as 1/0) for ECHO_HIDDEN
- and ON_ERROR_ROLLBACK. Report a warning for unrecognized
- values for COMP_KEYWORD_CASE, ECHO,
- ECHO_HIDDEN, HISTCONTROL,
- ON_ERROR_ROLLBACK, and VERBOSITY. Recognize
+ Allow variant spellings of on and off (such
+ as 1/0) for ECHO_HIDDEN
+ and ON_ERROR_ROLLBACK. Report a warning for unrecognized
+ values for COMP_KEYWORD_CASE, ECHO,
+ ECHO_HIDDEN, HISTCONTROL,
+ ON_ERROR_ROLLBACK, and VERBOSITY. Recognize
all values for all these variables case-insensitively; previously
there was a mishmash of case-sensitive and case-insensitive behaviors.
@@ -6198,8 +6390,8 @@ Branch: REL9_3_STABLE [4b1953079] 2014-11-28 02:44:40 +0900
- Make psql's \watch command display
- nulls as specified by \pset null (Fujii Masao)
+ Make psql's \watch command display
+ nulls as specified by \pset null (Fujii Masao)
@@ -6213,9 +6405,9 @@ Branch: REL9_0_STABLE [1f89fc218] 2014-09-12 11:24:39 -0400
- Fix psql's expanded-mode display to work
- consistently when using border = 3
- and linestyle = ascii or unicode
+ Fix psql's expanded-mode display to work
+ consistently when using border = 3
+ and linestyle = ascii or unicode
(Stephen Frost)
@@ -6229,7 +6421,7 @@ Branch: REL9_3_STABLE [bb1e2426b] 2015-01-05 19:27:09 -0500
- Fix pg_dump to handle comments on event triggers
+ Fix pg_dump to handle comments on event triggers
without failing (Tom Lane)
@@ -6243,8 +6435,8 @@ Branch: REL9_3_STABLE [cc609c46f] 2015-01-30 09:01:36 -0600
- Allow parallel pg_dump to
- use (Kevin Grittner)
@@ -6257,7 +6449,7 @@ Branch: REL9_1_STABLE [40c333c39] 2014-07-25 19:48:54 -0400
- Improve performance of pg_dump when the database
+ Improve performance of pg_dump when the database
contains many instances of multiple dependency paths between the same
two objects (Tom Lane)
@@ -6271,7 +6463,7 @@ Branch: REL9_2_STABLE [3c5ce5102] 2014-11-13 18:19:35 -0500
- Fix pg_dumpall to restore its ability to dump from
+ Fix pg_dumpall to restore its ability to dump from
pre-8.1 servers (Gilles Darold)
@@ -6301,7 +6493,7 @@ Branch: REL9_0_STABLE [31021e7ba] 2014-10-17 12:49:15 -0400
- Fix core dump in pg_dump --binary-upgrade on zero-column
+ Fix core dump in pg_dump --binary-upgrade on zero-column
composite type (Rushabh Lathia)
@@ -6314,7 +6506,7 @@ Branch: REL9_3_STABLE [26a4e0ed7] 2014-11-15 01:21:11 +0100
Fix failure to fsync tables in nondefault tablespaces
- during pg_upgrade (Abhijit Menon-Sen, Andres Freund)
+ during pg_upgrade (Abhijit Menon-Sen, Andres Freund)
@@ -6330,7 +6522,7 @@ Branch: REL9_3_STABLE [fca9f349b] 2014-08-07 14:56:13 -0400
- In pg_upgrade, cope with cases where the new cluster
+ In pg_upgrade, cope with cases where the new cluster
creates a TOAST table for a table that didn't previously have one
(Bruce Momjian)
@@ -6347,8 +6539,8 @@ Branch: REL9_3_STABLE [24ae44914] 2014-08-04 11:45:45 -0400
- In pg_upgrade, don't try to
- set autovacuum_multixact_freeze_max_age for the old cluster
+ In pg_upgrade, don't try to
+ set autovacuum_multixact_freeze_max_age for the old cluster
(Bruce Momjian)
@@ -6365,12 +6557,12 @@ Branch: REL9_3_STABLE [5724f491d] 2014-09-11 18:39:46 -0400
- In pg_upgrade, preserve the transaction ID epoch
+ In pg_upgrade, preserve the transaction ID epoch
(Bruce Momjian)
- This oversight did not bother PostgreSQL proper,
+ This oversight did not bother PostgreSQL proper,
but could confuse some external replication tools.
@@ -6386,7 +6578,7 @@ Branch: REL9_1_STABLE [2a0bfa4d6] 2015-01-03 20:54:13 +0100
- Prevent WAL files created by pg_basebackup -x/-X from
+ Prevent WAL files created by pg_basebackup -x/-X from
being archived again when the standby is promoted (Andres Freund)
@@ -6398,7 +6590,7 @@ Branch: REL9_3_STABLE [9747a9898] 2014-08-02 15:19:45 +0900
- Fix memory leak in pg_receivexlog (Fujii Masao)
+ Fix memory leak in pg_receivexlog (Fujii Masao)
@@ -6409,7 +6601,7 @@ Branch: REL9_3_STABLE [39217ce41] 2014-08-02 14:59:10 +0900
- Fix unintended suppression of pg_receivexlog verbose
+ Fix unintended suppression of pg_receivexlog verbose
messages (Fujii Masao)
@@ -6422,8 +6614,8 @@ Branch: REL9_2_STABLE [5ff8c2d7d] 2014-09-19 13:19:05 -0400
- Fix failure of contrib/auto_explain to print per-node
- timing information when doing EXPLAIN ANALYZE (Tom Lane)
+ Fix failure of contrib/auto_explain to print per-node
+ timing information when doing EXPLAIN ANALYZE (Tom Lane)
@@ -6436,7 +6628,7 @@ Branch: REL9_1_STABLE [9807c8220] 2014-08-28 18:21:20 -0400
- Fix upgrade-from-unpackaged script for contrib/citext
+ Fix upgrade-from-unpackaged script for contrib/citext
(Tom Lane)
@@ -6449,7 +6641,7 @@ Branch: REL9_3_STABLE [f44290b7b] 2014-11-04 16:54:59 -0500
Avoid integer overflow and buffer overrun
- in contrib/hstore's hstore_to_json()
+ in contrib/hstore's hstore_to_json()
(Heikki Linnakangas)
@@ -6461,7 +6653,7 @@ Branch: REL9_3_STABLE [55c880797] 2014-12-01 11:44:48 -0500
- Fix recognition of numbers in hstore_to_json_loose(),
+ Fix recognition of numbers in hstore_to_json_loose(),
so that JSON numbers and strings are correctly distinguished
(Andrew Dunstan)
@@ -6478,7 +6670,7 @@ Branch: REL9_0_STABLE [9dc2a3fd0] 2014-07-22 11:46:04 -0400
Fix block number checking
- in contrib/pageinspect's get_raw_page()
+ in contrib/pageinspect's get_raw_page()
(Tom Lane)
@@ -6498,7 +6690,7 @@ Branch: REL9_0_STABLE [ef5a3b957] 2014-11-11 17:22:58 -0500
- Fix contrib/pgcrypto's pgp_sym_decrypt()
+ Fix contrib/pgcrypto's pgp_sym_decrypt()
to not fail on messages whose length is 6 less than a power of 2
(Marko Tiikkaja)
@@ -6513,7 +6705,7 @@ Branch: REL9_1_STABLE [a855c90a7] 2014-11-19 12:26:06 -0500
- Fix file descriptor leak in contrib/pg_test_fsync
+ Fix file descriptor leak in contrib/pg_test_fsync
(Jeff Janes)
@@ -6535,12 +6727,12 @@ Branch: REL9_0_STABLE [dc9a506e6] 2015-01-29 20:18:46 -0500
Handle unexpected query results, especially NULLs, safely in
- contrib/tablefunc's connectby()
+ contrib/tablefunc's connectby()
(Michael Paquier)
- connectby() previously crashed if it encountered a NULL
+ connectby() previously crashed if it encountered a NULL
key value. It now prints that row but doesn't recurse further.
@@ -6555,12 +6747,12 @@ Branch: REL9_0_STABLE [6a694bbab] 2014-11-27 11:13:03 -0500
- Avoid a possible crash in contrib/xml2's
- xslt_process() (Mark Simonetti)
+ Avoid a possible crash in contrib/xml2's
+ xslt_process() (Mark Simonetti)
- libxslt seems to have an undocumented dependency on
+ libxslt seems to have an undocumented dependency on
the order in which resources are freed; reorder our calls to avoid a
crash.
@@ -6575,7 +6767,7 @@ Branch: REL9_1_STABLE [7225abf00] 2014-11-05 11:34:25 -0500
- Mark some contrib I/O functions with correct volatility
+ Mark some contrib I/O functions with correct volatility
properties (Tom Lane)
@@ -6696,10 +6888,10 @@ Branch: REL9_0_STABLE [4c6d0abde] 2014-07-22 11:02:25 -0400
With OpenLDAP versions 2.4.24 through 2.4.31,
- inclusive, PostgreSQL backends can crash at exit.
- Raise a warning during configure based on the
+ inclusive, PostgreSQL backends can crash at exit.
+ Raise a warning during configure based on the
compile-time OpenLDAP version number, and test the crashing scenario
- in the contrib/dblink regression test.
+ in the contrib/dblink regression test.
@@ -6713,7 +6905,7 @@ Branch: REL9_0_STABLE [e6841c4d6] 2014-08-18 23:01:23 -0400
- In non-MSVC Windows builds, ensure libpq.dll is installed
+ In non-MSVC Windows builds, ensure libpq.dll is installed
with execute permissions (Noah Misch)
@@ -6730,13 +6922,13 @@ Branch: REL9_0_STABLE [338ff75fc] 2015-01-19 23:44:33 -0500
- Make pg_regress remove any temporary installation it
+ Make pg_regress remove any temporary installation it
created upon successful exit (Tom Lane)
This results in a very substantial reduction in disk space usage
- during make check-world, since that sequence involves
+ during make check-world, since that sequence involves
creation of numerous temporary installations.
@@ -6756,15 +6948,15 @@ Branch: REL9_0_STABLE [870a980aa] 2014-10-16 15:22:26 -0400
- Previously, PostgreSQL assumed that the UTC offset
- associated with a time zone abbreviation (such as EST)
+ Previously, PostgreSQL assumed that the UTC offset
+ associated with a time zone abbreviation (such as EST)
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, PostgreSQL will now associate the
+ In such timezones, PostgreSQL will now associate the
correct UTC offset with the abbreviation depending on the given date.
@@ -6789,9 +6981,9 @@ Branch: REL9_0_STABLE [8b70023af] 2014-12-24 16:35:54 -0500
Add CST (China Standard Time) to our lists.
- Remove references to ADT as Arabia Daylight Time, an
+ Remove references to ADT as Arabia Daylight Time, an
abbreviation that's been out of use since 2007; therefore, claiming
- there is a conflict with Atlantic Daylight Time doesn't seem
+ there is a conflict with Atlantic Daylight Time 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.
@@ -6818,21 +7010,21 @@ Branch: REL9_0_STABLE [b6391f587] 2014-10-04 14:18:43 -0400
- Update time zone data files to tzdata release 2015a.
+ Update time zone data files to tzdata release 2015a.
The IANA timezone database has adopted abbreviations of the form
- AxST/AxDT
+ AxST/AxDT
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 Default timezone abbreviation set.
- The Australia abbreviation set now contains only CST, EAST,
+ our Default timezone abbreviation set.
+ The Australia 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 Default abbreviation set.
+ Africa Standard Time in the Default abbreviation set.
@@ -6873,7 +7065,7 @@ Branch: REL9_0_STABLE [b6391f587] 2014-10-04 14:18:43 -0400
However, this release corrects a logic error
- in pg_upgrade, as well as an index corruption problem in
+ in pg_upgrade, 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.
@@ -6900,15 +7092,15 @@ Branch: REL9_3_STABLE [cc5841809] 2014-06-24 16:11:06 -0400
- In pg_upgrade, remove pg_multixact files
- left behind by initdb (Bruce Momjian)
+ In pg_upgrade, remove pg_multixact files
+ left behind by initdb (Bruce Momjian)
- If you used a pre-9.3.5 version of pg_upgrade to
+ If you used a pre-9.3.5 version of pg_upgrade to
upgrade a database cluster to 9.3, it might have left behind a file
- $PGDATA/pg_multixact/offsets/0000 that should not be
- there and will eventually cause problems in VACUUM.
+ $PGDATA/pg_multixact/offsets/0000 that should not be
+ there and will eventually cause problems in VACUUM.
However, in common cases this file is actually valid and
must not be removed.
To determine whether your installation has this problem, run this
@@ -6921,9 +7113,9 @@ SELECT EXISTS (SELECT * FROM list WHERE file = '0000') AND
EXISTS (SELECT * FROM list WHERE file != '0000')
AS file_0000_removal_required;
- If this query returns t, manually remove the file
- $PGDATA/pg_multixact/offsets/0000.
- Do nothing if the query returns f.
+ If this query returns t, manually remove the file
+ $PGDATA/pg_multixact/offsets/0000.
+ Do nothing if the query returns f.
@@ -6939,15 +7131,15 @@ Branch: REL8_4_STABLE [e31d77c96] 2014-05-13 15:27:43 +0300
- Correctly initialize padding bytes in contrib/btree_gist
- indexes on bit columns (Heikki Linnakangas)
+ Correctly initialize padding bytes in contrib/btree_gist
+ indexes on bit columns (Heikki Linnakangas)
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 bit or bit varying
- columns should REINDEX those indexes after installing this
+ Users with GiST indexes on bit or bit varying
+ columns should REINDEX those indexes after installing this
update.
@@ -7032,7 +7224,7 @@ Branch: REL9_3_STABLE [167a2535f] 2014-06-09 15:17:23 -0400
- Fix wraparound handling for pg_multixact/members
+ Fix wraparound handling for pg_multixact/members
(Álvaro Herrera)
@@ -7046,12 +7238,12 @@ Branch: REL9_3_STABLE [9a28c3752] 2014-06-27 14:43:52 -0400
- Truncate pg_multixact during checkpoints, not
- during VACUUM (Álvaro Herrera)
+ Truncate pg_multixact during checkpoints, not
+ during VACUUM (Álvaro Herrera)
- This change ensures that pg_multixact segments can't be
+ This change ensures that pg_multixact segments can't be
removed if they'd still be needed during WAL replay after a crash.
@@ -7082,7 +7274,7 @@ Branch: REL8_4_STABLE [3ada1fab8] 2014-05-05 14:43:55 -0400
Fix possibly-incorrect cache invalidation during nested calls
- to ReceiveSharedInvalidMessages (Andres Freund)
+ to ReceiveSharedInvalidMessages (Andres Freund)
@@ -7108,8 +7300,8 @@ Branch: REL9_1_STABLE [555d0b200] 2014-06-26 10:42:08 -0700
- Fix could not find pathkey item to sort planner failures
- with UNION ALL over subqueries reading from tables with
+ Fix could not find pathkey item to sort planner failures
+ with UNION ALL over subqueries reading from tables with
inheritance children (Tom Lane)
@@ -7148,7 +7340,7 @@ Branch: REL9_2_STABLE [0901dbab3] 2014-04-29 13:12:33 -0400
Improve planner to drop constant-NULL inputs
- of AND/OR when possible (Tom Lane)
+ of AND/OR when possible (Tom Lane)
@@ -7166,8 +7358,8 @@ Branch: REL9_3_STABLE [d359f71ac] 2014-04-03 22:02:27 -0400
- Ensure that the planner sees equivalent VARIADIC and
- non-VARIADIC function calls as equivalent (Tom Lane)
+ Ensure that the planner sees equivalent VARIADIC and
+ non-VARIADIC function calls as equivalent (Tom Lane)
@@ -7188,13 +7380,13 @@ Branch: REL9_3_STABLE [a1fc36495] 2014-06-24 21:22:47 -0700
- Fix handling of nested JSON objects
- in json_populate_recordset() and friends
+ Fix handling of nested JSON objects
+ in json_populate_recordset() and friends
(Michael Paquier, Tom Lane)
- A nested JSON object could result in previous fields of the
+ A nested JSON object could result in previous fields of the
parent object not being shown in the output.
@@ -7208,13 +7400,13 @@ Branch: REL9_2_STABLE [25c933c5c] 2014-05-09 12:55:06 -0400
- Fix identification of input type category in to_json()
+ Fix identification of input type category in to_json()
and friends (Tom Lane)
- This is known to have led to inadequate quoting of money
- fields in the JSON result, and there may have been wrong
+ This is known to have led to inadequate quoting of money
+ fields in the JSON result, and there may have been wrong
results for other data types as well.
@@ -7239,7 +7431,7 @@ Branch: REL8_4_STABLE [70debcf09] 2014-05-01 15:19:23 -0400
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 missing chunk number 0
- for toast value ... when the now-dangling pointer is used.
+ for toast value ... when the now-dangling pointer is used.
@@ -7256,7 +7448,7 @@ Branch: REL8_4_STABLE [a81fbcfb3] 2014-07-11 19:12:56 -0400
- Fix record type has not been registered failures with
+ Fix record type has not been registered failures with
whole-row references to the output of Append plan nodes (Tom Lane)
@@ -7292,7 +7484,7 @@ Branch: REL8_4_STABLE [d297c91d4] 2014-06-19 22:14:00 -0400
Fix query-lifespan memory leak while evaluating the arguments for a
- function in FROM (Tom Lane)
+ function in FROM (Tom Lane)
@@ -7327,7 +7519,7 @@ Branch: REL8_4_STABLE [f3f40434b] 2014-06-10 22:49:08 -0400
- Fix data encoding error in hungarian.stop (Tom Lane)
+ Fix data encoding error in hungarian.stop (Tom Lane)
@@ -7367,7 +7559,7 @@ Branch: REL8_4_STABLE [80d45ae4e] 2014-06-04 23:27:38 +0200
This could cause problems (at least spurious warnings, and at worst an
- infinite loop) if CREATE INDEX or CLUSTER were
+ infinite loop) if CREATE INDEX or CLUSTER were
done later in the same transaction.
@@ -7384,12 +7576,12 @@ Branch: REL8_4_STABLE [82fbd88a7] 2014-04-24 13:30:14 -0400
- Clear pg_stat_activity.xact_start
- during PREPARE TRANSACTION (Andres Freund)
+ Clear pg_stat_activity.xact_start
+ during PREPARE TRANSACTION (Andres Freund)
- After the PREPARE, the originating session is no longer in
+ After the PREPARE, the originating session is no longer in
a transaction, so it should not continue to display a transaction
start time.
@@ -7408,7 +7600,7 @@ Branch: REL8_4_STABLE [4b767789d] 2014-07-15 13:24:07 -0400
- Fix REASSIGN OWNED to not fail for text search objects
+ Fix REASSIGN OWNED to not fail for text search objects
(Álvaro Herrera)
@@ -7422,8 +7614,8 @@ Branch: REL9_3_STABLE [e86cfc4bb] 2014-06-27 14:43:45 -0400
- Prevent pg_class.relminmxid values from
- going backwards during VACUUM FULL (Álvaro Herrera)
+ Prevent pg_class.relminmxid values from
+ going backwards during VACUUM FULL (Álvaro Herrera)
@@ -7461,7 +7653,7 @@ Branch: REL9_3_STABLE [e31193d49] 2014-05-01 20:22:39 -0400
Fix dumping of rules/views when subsequent addition of a column has
- resulted in multiple input columns matching a USING
+ resulted in multiple input columns matching a USING
specification (Tom Lane)
@@ -7476,7 +7668,7 @@ Branch: REL9_3_STABLE [b978ab5f6] 2014-07-19 14:29:05 -0400
Repair view printing for some cases involving functions
- in FROM that return a composite type containing dropped
+ in FROM that return a composite type containing dropped
columns (Tom Lane)
@@ -7498,7 +7690,7 @@ Branch: REL8_4_STABLE [969735cf1] 2014-04-05 18:16:24 -0400
This ensures that the postmaster will properly clean up after itself
- if, for example, it receives SIGINT while still
+ if, for example, it receives SIGINT while still
starting up.
@@ -7513,7 +7705,7 @@ Branch: REL9_1_STABLE [b7a424371] 2014-04-02 17:11:34 -0400
- Fix client host name lookup when processing pg_hba.conf
+ Fix client host name lookup when processing pg_hba.conf
entries that specify host names instead of IP addresses (Tom Lane)
@@ -7534,14 +7726,14 @@ Branch: REL9_2_STABLE [6d25eb314] 2014-04-04 22:03:42 -0400
- Allow the root user to use postgres -C variable and
- postgres --describe-config (MauMau)
+ Allow the root user to use postgres -C variable and
+ postgres --describe-config (MauMau)
The prohibition on starting the server as root does not need to extend
to these operations, and relaxing it prevents failure
- of pg_ctl in some scenarios.
+ of pg_ctl in some scenarios.
@@ -7559,7 +7751,7 @@ Branch: REL8_4_STABLE [95cefd30e] 2014-06-14 09:41:18 -0400
Secure Unix-domain sockets of temporary postmasters started during
- make check (Noah Misch)
+ make check (Noah Misch)
@@ -7568,16 +7760,16 @@ Branch: REL8_4_STABLE [95cefd30e] 2014-06-14 09:41:18 -0400
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 /tmp. The hazard remains however on platforms where
+ of /tmp. The hazard remains however on platforms where
Unix sockets are not supported, notably Windows, because then the
temporary postmaster must accept local TCP connections.
A useful side effect of this change is to simplify
- make check testing in builds that
- override DEFAULT_PGSOCKET_DIR. Popular non-default values
- like /var/run/postgresql are often not writable by the
+ make check testing in builds that
+ override DEFAULT_PGSOCKET_DIR. Popular non-default values
+ like /var/run/postgresql are often not writable by the
build user, requiring workarounds that will no longer be necessary.
@@ -7651,9 +7843,9 @@ Branch: REL8_4_STABLE [e3f273ff6] 2014-04-30 10:39:03 +0300
- This oversight could cause initdb
- and pg_upgrade to fail on Windows, if the installation
- path contained both spaces and @ signs.
+ This oversight could cause initdb
+ and pg_upgrade to fail on Windows, if the installation
+ path contained both spaces and @ signs.
@@ -7669,7 +7861,7 @@ Branch: REL8_4_STABLE [ae41bb4be] 2014-05-30 18:18:32 -0400
- Fix linking of libpython on macOS (Tom Lane)
+ Fix linking of libpython on macOS (Tom Lane)
@@ -7690,17 +7882,17 @@ Branch: REL8_4_STABLE [664ac3de7] 2014-05-07 21:38:50 -0400
- Avoid buffer bloat in libpq when the server
+ Avoid buffer bloat in libpq when the server
consistently sends data faster than the client can absorb it
(Shin-ichi Morita, Tom Lane)
- libpq could be coerced into enlarging its input buffer
+ libpq could be coerced into enlarging its input buffer
until it runs out of memory (which would be reported misleadingly
- as lost synchronization with server). Under ordinary
+ as lost synchronization with server). Under ordinary
circumstances it's quite far-fetched that data could be continuously
- transmitted more quickly than the recv() loop can
+ transmitted more quickly than the recv() loop can
absorb it, but this has been observed when the client is artificially
slowed by scheduler constraints.
@@ -7718,7 +7910,7 @@ Branch: REL8_4_STABLE [b4ae2e37d] 2014-04-16 18:59:48 +0200
- Ensure that LDAP lookup attempts in libpq time out as
+ Ensure that LDAP lookup attempts in libpq time out as
intended (Laurenz Albe)
@@ -7741,8 +7933,8 @@ Branch: REL9_0_STABLE [0c2eb989e] 2014-04-09 12:12:32 +0200
- Fix ecpg to do the right thing when an array
- of char * is the target for a FETCH statement returning more
+ Fix ecpg to do the right thing when an array
+ of char * is the target for a FETCH statement returning more
than one row, as well as some other array-handling fixes
(Ashutosh Bapat)
@@ -7756,13 +7948,13 @@ Branch: REL9_3_STABLE [3080bbaa9] 2014-03-29 17:34:03 -0400
- Fix pg_dump to cope with a materialized view that
+ Fix pg_dump to cope with a materialized view that
depends on a table's primary key (Tom Lane)
This occurs if the view's query relies on functional dependency to
- abbreviate a GROUP BY list. pg_dump got
+ abbreviate a GROUP BY list. pg_dump got
sufficiently confused that it dumped the materialized view as a
regular view.
@@ -7776,7 +7968,7 @@ Branch: REL9_3_STABLE [63817f86b] 2014-03-18 10:38:38 -0400
- Fix parsing of pg_dumpall's switch
(Tom Lane)
@@ -7794,13 +7986,13 @@ Branch: REL8_4_STABLE [6adddac8a] 2014-06-12 20:14:55 -0400
- Fix pg_restore's processing of old-style large object
+ Fix pg_restore's processing of old-style large object
comments (Tom Lane)
A direct-to-database restore from an archive file generated by a
- pre-9.0 version of pg_dump would usually fail if the
+ pre-9.0 version of pg_dump would usually fail if the
archive contained more than a few comments for large objects.
@@ -7815,12 +8007,12 @@ Branch: REL9_2_STABLE [759c9fb63] 2014-07-07 13:24:08 -0400
- Fix pg_upgrade for cases where the new server creates
+ Fix pg_upgrade for cases where the new server creates
a TOAST table but the old version did not (Bruce Momjian)
- This rare situation would manifest as relation OID mismatch
+ This rare situation would manifest as relation OID mismatch
errors.
@@ -7839,9 +8031,9 @@ Branch: REL9_3_STABLE [e7984cca0] 2014-07-21 11:42:05 -0400
- In pg_upgrade,
- preserve pg_database.datminmxid
- and pg_class.relminmxid values from the
+ In pg_upgrade,
+ preserve pg_database.datminmxid
+ and pg_class.relminmxid 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)
@@ -7864,13 +8056,13 @@ Branch: REL9_2_STABLE [31f579f09] 2014-05-20 12:20:57 -0400
- Prevent contrib/auto_explain from changing the output of
- a user's EXPLAIN (Tom Lane)
+ Prevent contrib/auto_explain from changing the output of
+ a user's EXPLAIN (Tom Lane)
- If auto_explain is active, it could cause
- an EXPLAIN (ANALYZE, TIMING OFF) command to nonetheless
+ If auto_explain is active, it could cause
+ an EXPLAIN (ANALYZE, TIMING OFF) command to nonetheless
print timing information.
@@ -7885,7 +8077,7 @@ Branch: REL9_2_STABLE [3e2cfa42f] 2014-06-20 12:27:04 -0700
- Fix query-lifespan memory leak in contrib/dblink
+ Fix query-lifespan memory leak in contrib/dblink
(MauMau, Joe Conway)
@@ -7902,7 +8094,7 @@ Branch: REL8_4_STABLE [df2e62603] 2014-04-17 12:37:53 -0400
- In contrib/pgcrypto functions, ensure sensitive
+ In contrib/pgcrypto functions, ensure sensitive
information is cleared from stack variables before returning
(Marko Kreen)
@@ -7919,7 +8111,7 @@ Branch: REL9_2_STABLE [f6d6b7b1e] 2014-06-30 17:00:40 -0400
Prevent use of already-freed memory in
- contrib/pgstattuple's pgstat_heap()
+ contrib/pgstattuple's pgstat_heap()
(Noah Misch)
@@ -7936,13 +8128,13 @@ Branch: REL8_4_STABLE [fd785441f] 2014-05-29 13:51:18 -0400
- In contrib/uuid-ossp, cache the state of the OSSP UUID
+ In contrib/uuid-ossp, cache the state of the OSSP UUID
library across calls (Tom Lane)
This improves the efficiency of UUID generation and reduces the amount
- of entropy drawn from /dev/urandom, on platforms that
+ of entropy drawn from /dev/urandom, on platforms that
have that.
@@ -7960,7 +8152,7 @@ Branch: REL8_4_STABLE [c51da696b] 2014-07-19 15:01:45 -0400
- Update time zone data files to tzdata release 2014e
+ Update time zone data files to tzdata release 2014e
for DST law changes in Crimea, Egypt, and Morocco.
@@ -8071,7 +8263,7 @@ Branch: REL9_0_STABLE [7aea1050e] 2014-03-13 12:03:07 -0400
Avoid race condition in checking transaction commit status during
- receipt of a NOTIFY message (Marko Tiikkaja)
+ receipt of a NOTIFY message (Marko Tiikkaja)
@@ -8089,8 +8281,8 @@ Branch: REL9_3_STABLE [3973034e6] 2014-03-06 11:37:04 -0500
- Allow materialized views to be referenced in UPDATE
- and DELETE commands (Michael Paquier)
+ Allow materialized views to be referenced in UPDATE
+ and DELETE commands (Michael Paquier)
@@ -8133,7 +8325,7 @@ Branch: REL8_4_STABLE [dd378dd1e] 2014-02-18 12:44:36 -0500
- Remove incorrect code that tried to allow OVERLAPS with
+ Remove incorrect code that tried to allow OVERLAPS with
single-element row arguments (Joshua Yanovski)
@@ -8156,17 +8348,17 @@ Branch: REL8_4_STABLE [f043bddfe] 2014-03-06 19:31:22 -0500
- Avoid getting more than AccessShareLock when de-parsing a
+ Avoid getting more than AccessShareLock when de-parsing a
rule or view (Dean Rasheed)
- This oversight resulted in pg_dump unexpectedly
- acquiring RowExclusiveLock locks on tables mentioned as
- the targets of INSERT/UPDATE/DELETE
+ This oversight resulted in pg_dump unexpectedly
+ acquiring RowExclusiveLock locks on tables mentioned as
+ the targets of INSERT/UPDATE/DELETE
commands in rules. While usually harmless, that could interfere with
concurrent transactions that tried to acquire, for example,
- ShareLock on those tables.
+ ShareLock on those tables.
@@ -8201,9 +8393,9 @@ Branch: REL9_3_STABLE [e8655a77f] 2014-02-21 17:10:49 -0500
Use non-default selectivity estimates for
- value IN (list) and
- value operator ANY
- (array)
+ value IN (list) and
+ valueoperator ANY
+ (array)
expressions when the righthand side is a stable expression (Tom Lane)
@@ -8217,16 +8409,16 @@ Branch: REL9_3_STABLE [13ea43ab8] 2014-03-05 13:03:29 -0300
Remove the correct per-database statistics file during DROP
- DATABASE (Tomas Vondra)
+ DATABASE (Tomas Vondra)
This fix prevents a permanent leak of statistics file space.
- Users who have done many DROP DATABASE commands since
- upgrading to PostgreSQL 9.3 may wish to check their
+ Users who have done many DROP DATABASE commands since
+ upgrading to PostgreSQL 9.3 may wish to check their
statistics directory and delete statistics files that do not
correspond to any existing database. Please note
- that db_0.stat should not be removed.
+ that db_0.stat should not be removed.
@@ -8238,12 +8430,12 @@ Branch: REL9_3_STABLE [dcd1131c8] 2014-03-06 21:40:50 +0200
- Fix walsender ping logic to avoid inappropriate
+ Fix walsender ping logic to avoid inappropriate
disconnects under continuous load (Andres Freund, Heikki Linnakangas)
- walsender failed to send ping messages to the client
+ walsender 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 elapsed.
@@ -8260,8 +8452,8 @@ Branch: REL9_1_STABLE [65e8dbb18] 2014-03-17 20:42:35 +0900
- Fix walsender's failure to shut down cleanly when client
- is pg_receivexlog (Fujii Masao)
+ Fix walsender's failure to shut down cleanly when client
+ is pg_receivexlog (Fujii Masao)
@@ -8324,13 +8516,13 @@ Branch: REL8_4_STABLE [172c53e92] 2014-03-13 20:59:57 -0400
- Prevent interrupts while reporting non-ERROR messages
+ Prevent interrupts while reporting non-ERROR messages
(Tom Lane)
This guards against rare server-process freezeups due to recursive
- entry to syslog(), and perhaps other related problems.
+ entry to syslog(), and perhaps other related problems.
@@ -8358,13 +8550,13 @@ Branch: REL9_2_STABLE [b315b767f] 2014-03-10 15:47:13 -0400
- Fix tracking of psql script line numbers
- during \copy from out-of-line data
+ Fix tracking of psql script line numbers
+ during \copy from out-of-line data
(Kumar Rajeev Rastogi, Amit Khandekar)
- \copy ... from incremented the script file line number
+ \copy ... from 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.
@@ -8379,12 +8571,12 @@ Branch: REL9_3_STABLE [73f0483fd] 2014-03-07 16:36:50 -0500
- Fix contrib/postgres_fdw to handle multiple join
+ Fix contrib/postgres_fdw to handle multiple join
conditions properly (Tom Lane)
- This oversight could result in sending WHERE clauses to
+ This oversight could result in sending WHERE 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,
@@ -8404,7 +8596,7 @@ Branch: REL9_0_STABLE [665515539] 2014-03-16 11:47:37 +0100
- Prevent intermittent could not reserve shared memory region
+ Prevent intermittent could not reserve shared memory region
failures on recent Windows versions (MauMau)
@@ -8421,7 +8613,7 @@ Branch: REL8_4_STABLE [6e6c2c2e1] 2014-03-15 13:36:57 -0400
- Update time zone data files to tzdata release 2014a
+ Update time zone data files to tzdata release 2014a
for DST law changes in Fiji and Turkey, plus historical changes in
Israel and Ukraine.
@@ -8494,19 +8686,19 @@ Branch: REL8_4_STABLE [ff35425c8] 2014-02-17 09:33:38 -0500
- Shore up GRANT ... WITH ADMIN OPTION restrictions
+ Shore up GRANT ... WITH ADMIN OPTION restrictions
(Noah Misch)
- Granting a role without ADMIN OPTION is supposed to
+ Granting a role without ADMIN OPTION is supposed to
prevent the grantee from adding or removing members from the granted
role, but this restriction was easily bypassed by doing SET
- ROLE first. The security impact is mostly that a role member can
+ ROLE 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 SECURITY DEFINER functions.
+ anyway by creating views or SECURITY DEFINER functions.
(CVE-2014-0060)
@@ -8529,7 +8721,7 @@ Branch: REL8_4_STABLE [823b9dc25] 2014-02-17 09:33:38 -0500
The primary role of PL validator functions is to be called implicitly
- during CREATE FUNCTION, but they are also normal SQL
+ during CREATE FUNCTION, 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.
@@ -8559,7 +8751,7 @@ Branch: REL8_4_STABLE [e46476133] 2014-02-17 09:33:38 -0500
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 CREATE INDEX,
+ than other parts. At least in the case of CREATE INDEX,
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.
@@ -8583,12 +8775,12 @@ Branch: REL8_4_STABLE [d0ed1a6c0] 2014-02-17 09:33:39 -0500
- The MAXDATELEN constant was too small for the longest
- possible value of type interval, allowing a buffer overrun
- in interval_out(). Although the datetime input
+ The MAXDATELEN constant was too small for the longest
+ possible value of type interval, allowing a buffer overrun
+ in interval_out(). 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 ecpg
+ input containing a very long timezone name. The ecpg
library contained these vulnerabilities along with some of its own.
(CVE-2014-0063)
@@ -8635,7 +8827,7 @@ Branch: REL8_4_STABLE [69d2bc14a] 2014-02-17 11:20:38 -0500
- Use strlcpy() and related functions to provide a clear
+ Use strlcpy() 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
@@ -8657,16 +8849,16 @@ Branch: REL8_4_STABLE [69d2bc14a] 2014-02-17 11:20:38 -0500
- Avoid crashing if crypt() returns NULL (Honza Horak,
+ Avoid crashing if crypt() returns NULL (Honza Horak,
Bruce Momjian)
- There are relatively few scenarios in which crypt()
- could return NULL, but contrib/chkpass would crash
+ There are relatively few scenarios in which crypt()
+ could return NULL, but contrib/chkpass would crash
if it did. One practical case in which this could be an issue is
- if libc is configured to refuse to execute unapproved
- hashing algorithms (e.g., FIPS mode).
+ if libc is configured to refuse to execute unapproved
+ hashing algorithms (e.g., FIPS mode).
(CVE-2014-0066)
@@ -8683,19 +8875,19 @@ Branch: REL8_4_STABLE [f58663ab1] 2014-02-17 11:24:51 -0500
- Document risks of make check in the regression testing
+ Document risks of make check in the regression testing
instructions (Noah Misch, Tom Lane)
- Since the temporary server started by make check
- uses trust authentication, another user on the same machine
+ Since the temporary server started by make check
+ uses trust 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
- make check when there are untrusted users on the
+ make check when there are untrusted users on the
same machine.
(CVE-2014-0067)
@@ -8716,7 +8908,7 @@ Branch: REL9_3_STABLE [8e9a16ab8] 2013-12-16 11:29:51 -0300
The logic for tuple freezing was unable to handle some cases involving
freezing of
- multixact
+ multixact
IDs, with the practical effect that shared row-level locks
might be forgotten once old enough.
@@ -8725,7 +8917,7 @@ Branch: REL9_3_STABLE [8e9a16ab8] 2013-12-16 11:29:51 -0300
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 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. 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.)
@@ -8783,8 +8975,8 @@ Branch: REL9_3_STABLE [db1014bc4] 2013-12-18 13:31:27 -0300
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 SELECT FOR KEY SHARE
- and SELECT FOR NO KEY UPDATE might also have suffered
+ Applications using the new commands SELECT FOR KEY SHARE
+ and SELECT FOR NO KEY UPDATE might also have suffered
locking failures of this kind.
@@ -8797,7 +8989,7 @@ Branch: REL9_3_STABLE [c6cd27e36] 2013-12-05 12:21:55 -0300
- Prevent forgetting valid row locks when one of several
+ Prevent forgetting valid row locks when one of several
holders of a row lock aborts (Álvaro Herrera)
@@ -8822,8 +9014,8 @@ Branch: REL9_3_STABLE [2dcc48c35] 2013-12-05 17:47:51 -0300
This mistake could result in spurious could not serialize access
- due to concurrent update errors in REPEATABLE READ
- and SERIALIZABLE transaction isolation modes.
+ due to concurrent update errors in REPEATABLE READ
+ and SERIALIZABLE transaction isolation modes.
@@ -8836,7 +9028,7 @@ Branch: REL9_3_STABLE [03db79459] 2014-01-02 18:17:07 -0300
Handle wraparound correctly during extension or truncation
- of pg_multixact/members
+ of pg_multixact/members
(Andres Freund, Álvaro Herrera)
@@ -8849,7 +9041,7 @@ Branch: REL9_3_STABLE [948a3dfbb] 2014-01-02 18:17:29 -0300
- Fix handling of 5-digit filenames in pg_multixact/members
+ Fix handling of 5-digit filenames in pg_multixact/members
(Álvaro Herrera)
@@ -8886,7 +9078,7 @@ Branch: REL9_3_STABLE [85d3b3c3a] 2013-12-19 16:39:59 -0300
This fixes a performance regression from pre-9.3 versions when doing
- SELECT FOR UPDATE followed by UPDATE/DELETE.
+ SELECT FOR UPDATE followed by UPDATE/DELETE.
@@ -8900,7 +9092,7 @@ Branch: REL9_3_STABLE [762bd379a] 2014-02-14 15:18:34 +0200
During archive recovery, prefer highest timeline number when WAL
segments with the same ID are present in both the archive
- and pg_xlog/ (Kyotaro Horiguchi)
+ and pg_xlog/ (Kyotaro Horiguchi)
@@ -8929,7 +9121,7 @@ Branch: REL8_4_STABLE [9620fede9] 2014-02-12 14:52:32 -0500
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 bloat
+ this error has been observed to result in significant bloat
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
@@ -8958,7 +9150,7 @@ Branch: REL9_0_STABLE [5301c8395] 2014-01-08 14:34:21 +0200
was already consistent at the start of replay, thus possibly allowing
hot-standby queries before the database was really consistent. Other
symptoms such as PANIC: WAL contains references to invalid
- pages were also possible.
+ pages were also possible.
@@ -8986,13 +9178,13 @@ Branch: REL9_0_STABLE [5d742b9ce] 2014-01-14 17:35:00 -0500
Fix improper locking of btree index pages while replaying
- a VACUUM operation in hot-standby mode (Andres Freund,
+ a VACUUM operation in hot-standby mode (Andres Freund,
Heikki Linnakangas, Tom Lane)
This error could result in PANIC: WAL contains references to
- invalid pages failures.
+ invalid pages failures.
@@ -9028,8 +9220,8 @@ Branch: REL9_1_STABLE [0402f2441] 2014-01-08 23:31:01 +0200
- When pause_at_recovery_target
- and recovery_target_inclusive are both set, ensure the
+ When pause_at_recovery_target
+ and recovery_target_inclusive are both set, ensure the
target record is applied before pausing, not after (Heikki
Linnakangas)
@@ -9058,14 +9250,14 @@ Branch: REL9_3_STABLE [478af9b79] 2013-12-13 11:50:25 -0500
Prevent timeout interrupts from taking control away from mainline
- code unless ImmediateInterruptOK is set
+ code unless ImmediateInterruptOK is set
(Andres Freund, Tom Lane)
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 stuck spinlocks,
+ timeout occurred. We have seen reports of stuck spinlocks,
ERRORs being unexpectedly promoted to PANICs, unkillable backends,
and other misbehaviors.
@@ -9088,7 +9280,7 @@ Branch: REL8_4_STABLE [458b20f2d] 2014-01-31 21:41:09 -0500
Ensure that signal handlers don't attempt to use the
- process's MyProc pointer after it's no longer valid.
+ process's MyProc pointer after it's no longer valid.
@@ -9119,13 +9311,13 @@ Branch: REL8_4_STABLE [01b882fd8] 2014-01-29 20:04:14 -0500
- Fix unsafe references to errno within error reporting
+ Fix unsafe references to errno within error reporting
logic (Christian Kruse)
This would typically lead to odd behaviors such as missing or
- inappropriate HINT fields.
+ inappropriate HINT fields.
@@ -9141,7 +9333,7 @@ Branch: REL8_4_STABLE [d0070ac81] 2014-01-11 16:35:44 -0500
- Fix possible crashes from using ereport() too early
+ Fix possible crashes from using ereport() too early
during server startup (Tom Lane)
@@ -9185,7 +9377,7 @@ Branch: REL8_4_STABLE [a8a46d846] 2014-02-13 14:24:58 -0500
- Fix length checking for Unicode identifiers (U&"..."
+ Fix length checking for Unicode identifiers (U&"..."
syntax) containing escapes (Tom Lane)
@@ -9227,7 +9419,7 @@ Branch: REL9_0_STABLE [f2eede9b5] 2014-01-21 23:01:40 -0500
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 DROP ROLE.
+ list of role identifiers was permitted, such as DROP ROLE.
@@ -9259,7 +9451,7 @@ Branch: REL8_4_STABLE [884c6384a] 2013-12-10 16:10:36 -0500
Fix possible crash due to invalid plan for nested sub-selects, such
- as WHERE (... x IN (SELECT ...) ...) IN (SELECT ...)
+ as WHERE (... x IN (SELECT ...) ...) IN (SELECT ...)
(Tom Lane)
@@ -9272,13 +9464,13 @@ Branch: REL9_3_STABLE [a4aa854ca] 2014-01-30 14:51:19 -0500
- Fix mishandling of WHERE conditions pulled up from
- a LATERAL subquery (Tom Lane)
+ Fix mishandling of WHERE conditions pulled up from
+ a LATERAL subquery (Tom Lane)
The typical symptom of this bug was a JOIN qualification
- cannot refer to other relations error, though subtle logic
+ cannot refer to other relations error, though subtle logic
errors in created plans seem possible as well.
@@ -9291,8 +9483,8 @@ Branch: REL9_3_STABLE [27ff4cfe7] 2014-01-11 19:03:15 -0500
- Disallow LATERAL references to the target table of
- an UPDATE/DELETE (Tom Lane)
+ Disallow LATERAL references to the target table of
+ an UPDATE/DELETE (Tom Lane)
@@ -9310,12 +9502,12 @@ Branch: REL9_2_STABLE [5d545b7ed] 2013-12-14 17:34:00 -0500
- Fix UPDATE/DELETE of an inherited target table
- that has UNION ALL subqueries (Tom Lane)
+ Fix UPDATE/DELETE of an inherited target table
+ that has UNION ALL subqueries (Tom Lane)
- Without this fix, UNION ALL subqueries aren't correctly
+ Without this fix, UNION ALL 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).
@@ -9330,7 +9522,7 @@ Branch: REL9_3_STABLE [663f8419b] 2013-12-23 22:18:23 -0500
- Fix ANALYZE to not fail on a column that's a domain over
+ Fix ANALYZE to not fail on a column that's a domain over
a range type (Tom Lane)
@@ -9347,12 +9539,12 @@ Branch: REL8_4_STABLE [00b77771a] 2014-01-11 13:42:11 -0500
- Ensure that ANALYZE creates statistics for a table column
- even when all the values in it are too wide (Tom Lane)
+ Ensure that ANALYZE creates statistics for a table column
+ even when all the values in it are too wide (Tom Lane)
- ANALYZE intentionally omits very wide values from its
+ ANALYZE 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.
@@ -9370,14 +9562,14 @@ Branch: REL8_4_STABLE [0fb4e3ceb] 2014-01-18 18:50:47 -0500
- In ALTER TABLE ... SET TABLESPACE, allow the database's
+ In ALTER TABLE ... SET TABLESPACE, allow the database's
default tablespace to be used without a permissions check
(Stephen Frost)
- CREATE TABLE has always allowed such usage,
- but ALTER TABLE didn't get the memo.
+ CREATE TABLE has always allowed such usage,
+ but ALTER TABLE didn't get the memo.
@@ -9405,8 +9597,8 @@ Branch: REL8_4_STABLE [57ac7d8a7] 2014-01-08 20:18:24 -0500
- Fix cannot accept a set error when some arms of
- a CASE return a set and others don't (Tom Lane)
+ Fix cannot accept a set error when some arms of
+ a CASE return a set and others don't (Tom Lane)
@@ -9487,12 +9679,12 @@ Branch: REL8_4_STABLE [6141983fb] 2014-02-10 10:00:50 +0200
- Fix possible misbehavior in plainto_tsquery()
+ Fix possible misbehavior in plainto_tsquery()
(Heikki Linnakangas)
- Use memmove() not memcpy() for copying
+ Use memmove() not memcpy() for copying
overlapping memory regions. There have been no field reports of
this actually causing trouble, but it's certainly risky.
@@ -9508,8 +9700,8 @@ Branch: REL9_1_STABLE [026a91f86] 2014-01-07 18:00:36 +0100
- Fix placement of permissions checks in pg_start_backup()
- and pg_stop_backup() (Andres Freund, Magnus Hagander)
+ Fix placement of permissions checks in pg_start_backup()
+ and pg_stop_backup() (Andres Freund, Magnus Hagander)
@@ -9530,7 +9722,7 @@ Branch: REL8_4_STABLE [69f77d756] 2013-12-15 11:11:11 +0900
- Accept SHIFT_JIS as an encoding name for locale checking
+ Accept SHIFT_JIS as an encoding name for locale checking
purposes (Tatsuo Ishii)
@@ -9544,14 +9736,14 @@ Branch: REL9_2_STABLE [888b56570] 2014-02-03 14:46:57 -0500
- Fix *-qualification of named parameters in SQL-language
+ Fix *-qualification of named parameters in SQL-language
functions (Tom Lane)
Given a composite-type parameter
- named foo, $1.* worked fine,
- but foo.* not so much.
+ named foo, $1.* worked fine,
+ but foo.* not so much.
@@ -9567,11 +9759,11 @@ Branch: REL8_4_STABLE [5525529db] 2014-01-23 23:02:30 +0900
- Fix misbehavior of PQhost() on Windows (Fujii Masao)
+ Fix misbehavior of PQhost() on Windows (Fujii Masao)
- It should return localhost if no host has been specified.
+ It should return localhost if no host has been specified.
@@ -9587,14 +9779,14 @@ Branch: REL8_4_STABLE [7644a7bd8] 2014-02-13 18:45:32 -0500
- Improve error handling in libpq and psql
- for failures during COPY TO STDOUT/FROM STDIN (Tom Lane)
+ Improve error handling in libpq and psql
+ for failures during COPY TO STDOUT/FROM STDIN (Tom Lane)
In particular this fixes an infinite loop that could occur in 9.2 and
up if the server connection was lost during COPY FROM
- STDIN. Variants of that scenario might be possible in older
+ STDIN. Variants of that scenario might be possible in older
versions, or with other client applications.
@@ -9609,7 +9801,7 @@ Branch: REL9_2_STABLE [fa28f9cba] 2014-01-04 16:05:23 -0500
Fix incorrect translation handling in
- some psql \d commands
+ some psql\d commands
(Peter Eisentraut, Tom Lane)
@@ -9623,7 +9815,7 @@ Branch: REL9_2_STABLE [0ae288d2d] 2014-02-12 14:51:00 +0100
- Ensure pg_basebackup's background process is killed
+ Ensure pg_basebackup's background process is killed
when exiting its foreground process (Magnus Hagander)
@@ -9639,7 +9831,7 @@ Branch: REL9_1_STABLE [c6e5c4dd1] 2014-02-09 12:09:55 +0100
Fix possible incorrect printing of filenames
- in pg_basebackup's verbose mode (Magnus Hagander)
+ in pg_basebackup's verbose mode (Magnus Hagander)
@@ -9670,7 +9862,7 @@ Branch: REL8_4_STABLE [d68a65b01] 2014-01-09 15:58:37 +0100
- Fix misaligned descriptors in ecpg (MauMau)
+ Fix misaligned descriptors in ecpg (MauMau)
@@ -9686,7 +9878,7 @@ Branch: REL8_4_STABLE [96de4939c] 2014-01-01 12:44:58 +0100
- In ecpg, handle lack of a hostname in the connection
+ In ecpg, handle lack of a hostname in the connection
parameters properly (Michael Meskes)
@@ -9703,7 +9895,7 @@ Branch: REL8_4_STABLE [6c8b16e30] 2013-12-07 16:56:34 -0800
- Fix performance regression in contrib/dblink connection
+ Fix performance regression in contrib/dblink connection
startup (Joe Conway)
@@ -9724,7 +9916,7 @@ Branch: REL8_4_STABLE [492b68541] 2014-01-13 15:44:14 +0200
- In contrib/isn, fix incorrect calculation of the check
+ In contrib/isn, fix incorrect calculation of the check
digit for ISMN values (Fabien Coelho)
@@ -9737,7 +9929,7 @@ Branch: REL9_3_STABLE [27902bc91] 2013-12-12 19:07:53 +0900
- Fix contrib/pgbench's progress logging to avoid overflow
+ Fix contrib/pgbench's progress logging to avoid overflow
when the scale factor is large (Tatsuo Ishii)
@@ -9751,8 +9943,8 @@ Branch: REL9_2_STABLE [27ab1eb7e] 2014-01-21 16:34:35 -0500
- Fix contrib/pg_stat_statement's handling
- of CURRENT_DATE and related constructs (Kyotaro
+ Fix contrib/pg_stat_statement's handling
+ of CURRENT_DATE and related constructs (Kyotaro
Horiguchi)
@@ -9766,7 +9958,7 @@ Branch: REL9_3_STABLE [eb3d350db] 2014-02-03 21:30:28 -0500
Improve lost-connection error handling
- in contrib/postgres_fdw (Tom Lane)
+ in contrib/postgres_fdw (Tom Lane)
@@ -9799,13 +9991,13 @@ Branch: REL8_4_STABLE [ae3c98b9b] 2014-02-01 15:16:52 -0500
- In Mingw and Cygwin builds, install the libpq DLL
- in the bin directory (Andrew Dunstan)
+ In Mingw and Cygwin builds, install the libpq DLL
+ in the bin directory (Andrew Dunstan)
This duplicates what the MSVC build has long done. It should fix
- problems with programs like psql failing to start
+ problems with programs like psql failing to start
because they can't find the DLL.
@@ -9821,7 +10013,7 @@ Branch: REL9_0_STABLE [1c0bf372f] 2014-02-01 16:14:15 -0500
- Avoid using the deprecated dllwrap tool in Cygwin builds
+ Avoid using the deprecated dllwrap tool in Cygwin builds
(Marco Atzeri)
@@ -9850,8 +10042,8 @@ Branch: REL8_4_STABLE [432735cbf] 2014-02-10 20:48:30 -0500
- Don't generate plain-text HISTORY
- and src/test/regress/README files anymore (Tom Lane)
+ Don't generate plain-text HISTORY
+ and src/test/regress/README files anymore (Tom Lane)
@@ -9860,7 +10052,7 @@ Branch: REL8_4_STABLE [432735cbf] 2014-02-10 20:48:30 -0500
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 INSTALL file will still be maintained, as
+ The plain-text INSTALL file will still be maintained, as
there is arguably a use-case for that.
@@ -9877,13 +10069,13 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
- Update time zone data files to tzdata release 2013i
+ Update time zone data files to tzdata release 2013i
for DST law changes in Jordan and historical changes in Cuba.
- In addition, the zones Asia/Riyadh87,
- Asia/Riyadh88, and Asia/Riyadh89 have been
+ In addition, the zones Asia/Riyadh87,
+ Asia/Riyadh88, and Asia/Riyadh89 have been
removed, as they are no longer maintained by IANA, and never
represented actual civil timekeeping practice.
@@ -9935,19 +10127,19 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
- Fix VACUUM's tests to see whether it can
- update relfrozenxid (Andres Freund)
+ Fix VACUUM's tests to see whether it can
+ update relfrozenxid (Andres Freund)
- In some cases VACUUM (either manual or autovacuum) could
- incorrectly advance a table's relfrozenxid value,
+ In some cases VACUUM (either manual or autovacuum) could
+ incorrectly advance a table's relfrozenxid 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 could not access status of transaction errors as a
+ to get could not access status of transaction 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.
@@ -9955,12 +10147,12 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
The issue can be ameliorated by, after upgrading, vacuuming all tables
in all databases while having vacuum_freeze_table_age
+ linkend="guc-vacuum-freeze-table-age">vacuum_freeze_table_age
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
- SELECT txid_current() < 2^31).
+ SELECT txid_current() < 2^31).
@@ -9972,14 +10164,14 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
These bugs could lead to could not access status of
- transaction errors, or to duplicate or vanishing rows.
+ transaction errors, or to duplicate or vanishing rows.
Users upgrading from releases prior to 9.3.0 are not affected.
The issue can be ameliorated by, after upgrading, vacuuming all tables
in all databases while having vacuum_freeze_table_age
+ linkend="guc-vacuum-freeze-table-age">vacuum_freeze_table_age
set to zero. This will fix latent corruption but will not be able to
fix all pre-existing data errors.
@@ -9995,7 +10187,7 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
- Fix initialization of pg_clog and pg_subtrans
+ Fix initialization of pg_clog and pg_subtrans
during hot standby startup (Andres Freund, Heikki Linnakangas)
@@ -10028,7 +10220,7 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
These bugs could result in incorrect behavior, such as locking or even
updating the wrong row, in the presence of concurrent updates.
- Spurious unable to fetch updated version of tuple errors
+ Spurious unable to fetch updated version of tuple errors
were also possible.
@@ -10040,7 +10232,7 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
This could lead to corruption of the lock data structures in shared
- memory, causing lock already held and other odd errors.
+ memory, causing lock already held and other odd errors.
@@ -10057,7 +10249,7 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
- Truncate pg_multixact contents during WAL replay
+ Truncate pg_multixact contents during WAL replay
(Andres Freund)
@@ -10068,14 +10260,14 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
- Ensure an anti-wraparound VACUUM counts a page as scanned
+ Ensure an anti-wraparound VACUUM counts a page as scanned
when it's only verified that no tuples need freezing (Sergey
Burladyan, Jeff Janes)
This bug could result in failing to
- advance relfrozenxid, so that the table would still be
+ advance relfrozenxid, 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.
@@ -10104,7 +10296,7 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
- Fix unexpected spgdoinsert() failure error during SP-GiST
+ Fix unexpected spgdoinsert() failure error during SP-GiST
index creation (Teodor Sigaev)
@@ -10122,12 +10314,12 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
- Historically PostgreSQL has accepted queries like
+ Historically PostgreSQL has accepted queries like
SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
although a strict reading of the SQL standard would forbid the
- duplicate usage of table alias x. A misguided change in
+ duplicate usage of table alias x. A misguided change in
9.3.0 caused it to reject some such cases that were formerly accepted.
Restore the previous behavior.
@@ -10135,8 +10327,8 @@ SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
- Avoid flattening a subquery whose SELECT list contains a
- volatile function wrapped inside a sub-SELECT (Tom Lane)
+ Avoid flattening a subquery whose SELECT list contains a
+ volatile function wrapped inside a sub-SELECT (Tom Lane)
@@ -10153,14 +10345,14 @@ SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
This error could lead to incorrect plans for queries involving
- multiple levels of subqueries within JOIN syntax.
+ multiple levels of subqueries within JOIN syntax.
Fix incorrect planning in cases where the same non-strict expression
- appears in multiple WHERE and outer JOIN
+ appears in multiple WHERE and outer JOIN
equality clauses (Tom Lane)
@@ -10248,20 +10440,20 @@ SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
- Fix array slicing of int2vector and oidvector values
+ Fix array slicing of int2vector and oidvector values
(Tom Lane)
Expressions of this kind are now implicitly promoted to
- regular int2 or oid arrays.
+ regular int2 or oid arrays.
- Return a valid JSON value when converting an empty hstore value
- to json
+ Return a valid JSON value when converting an empty hstore value
+ to json
(Oskari Saarenmaa)
@@ -10276,7 +10468,7 @@ SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
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 timeofday function to honor the simple GMT offset
+ the timeofday function to honor the simple GMT offset
zone.
@@ -10290,7 +10482,7 @@ SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
- Properly quote generated command lines in pg_ctl
+ Properly quote generated command lines in pg_ctl
(Naoya Anzai and Tom Lane)
@@ -10301,10 +10493,10 @@ SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
- Fix pg_dumpall to work when a source database
+ Fix pg_dumpall to work when a source database
sets default_transaction_read_only
- via ALTER DATABASE SET (Kevin Grittner)
+ linkend="guc-default-transaction-read-only">default_transaction_read_only
+ via ALTER DATABASE SET (Kevin Grittner)
@@ -10314,19 +10506,19 @@ SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
- Fix pg_isready to handle its option
properly (Fabrízio de Royes Mello and Fujii Masao)
- Fix parsing of WAL file names in pg_receivexlog
+ Fix parsing of WAL file names in pg_receivexlog
(Heikki Linnakangas)
- This error made pg_receivexlog unable to restart
+ This error made pg_receivexlog unable to restart
streaming after stopping, once at least 4 GB of WAL had been written.
@@ -10334,34 +10526,34 @@ SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
Report out-of-disk-space failures properly
- in pg_upgrade (Peter Eisentraut)
+ in pg_upgrade (Peter Eisentraut)
- Make ecpg search for quoted cursor names
+ Make ecpg search for quoted cursor names
case-sensitively (Zoltán Böszörményi)
- Fix ecpg's processing of lists of variables
- declared varchar (Zoltán Böszörményi)
+ Fix ecpg's processing of lists of variables
+ declared varchar (Zoltán Böszörményi)
- Make contrib/lo defend against incorrect trigger definitions
+ Make contrib/lo defend against incorrect trigger definitions
(Marc Cousin)
- Update time zone data files to tzdata release 2013h
+ Update time zone data files to tzdata release 2013h
for DST law changes in Argentina, Brazil, Jordan, Libya,
Liechtenstein, Morocco, and Palestine. Also, new timezone
abbreviations WIB, WIT, WITA for Indonesia.
@@ -10395,7 +10587,7 @@ SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
- However, if you use the hstore extension, see the
+ However, if you use the hstore extension, see the
first changelog entry.
@@ -10408,18 +10600,18 @@ SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
- Ensure new-in-9.3 JSON functionality is added to the hstore
+ Ensure new-in-9.3 JSON functionality is added to the hstore
extension during an update (Andrew Dunstan)
- Users who upgraded a pre-9.3 database containing hstore
+ Users who upgraded a pre-9.3 database containing hstore
should execute
ALTER EXTENSION hstore UPDATE;
after installing 9.3.1, to add two new JSON functions and a cast.
- (If hstore is already up to date, this command does
+ (If hstore is already up to date, this command does
nothing.)
@@ -10452,14 +10644,14 @@ ALTER EXTENSION hstore UPDATE;
- Fix timeline handling bugs in pg_receivexlog
+ Fix timeline handling bugs in pg_receivexlog
(Heikki Linnakangas, Andrew Gierth)
- Prevent CREATE FUNCTION from checking SET
+ Prevent CREATE FUNCTION from checking SET
variables unless function body checking is enabled (Tom Lane)
@@ -10488,7 +10680,7 @@ ALTER EXTENSION hstore UPDATE;
Overview
- Major enhancements in PostgreSQL 9.3 include:
+ Major enhancements in PostgreSQL 9.3 include:
@@ -10497,7 +10689,7 @@ ALTER EXTENSION hstore UPDATE;
- Add materialized
+ Add materialized
views
@@ -10505,29 +10697,29 @@ ALTER EXTENSION hstore UPDATE;
Make simple views auto-updatable
+ linkend="sql-createview-updatable-views">auto-updatable
- Add many features for the JSON data type,
+ Add many features for the JSON data type,
including operators and functions
- to extract elements from JSON values
+ to extract elements from JSON values
- Implement SQL-standard LATERAL option for
- FROM-clause subqueries and function calls
+ Implement SQL-standard LATERAL option for
+ FROM-clause subqueries and function calls
- Allow foreign data
+ Allow foreign data
wrappers to support writes (inserts/updates/deletes) on foreign
tables
@@ -10535,9 +10727,9 @@ ALTER EXTENSION hstore UPDATE;
- Add a Postgres foreign
+ Add a Postgres foreign
data wrapper to allow access to
- other Postgres servers
+ other Postgres servers
@@ -10582,8 +10774,8 @@ ALTER EXTENSION hstore UPDATE;
A dump/restore using pg_dumpall, or use
- of pg_upgrade, is
+ linkend="app-pg-dumpall">pg_dumpall, or use
+ of pg_upgrade, is
required for those wishing to migrate data from any previous release.
@@ -10599,21 +10791,21 @@ ALTER EXTENSION hstore UPDATE;
- Rename replication_timeout to wal_sender_timeout
+ Rename replication_timeout to wal_sender_timeout
(Amit Kapila)
This setting controls the WAL sender timeout.
+ linkend="wal">WAL sender timeout.
Require superuser privileges to set commit_delay
+ linkend="guc-commit-delay">commit_delay
because it can now potentially delay other sessions (Simon Riggs)
@@ -10625,7 +10817,7 @@ ALTER EXTENSION hstore UPDATE;
Users who have set work_mem based on the
+ linkend="guc-work-mem">work_mem based on the
previous behavior may need to revisit that setting.
@@ -10642,7 +10834,7 @@ ALTER EXTENSION hstore UPDATE;
Throw an error if a tuple to be updated or deleted has already been
- updated or deleted by a BEFORE trigger (Kevin Grittner)
+ updated or deleted by a BEFORE trigger (Kevin Grittner)
@@ -10652,7 +10844,7 @@ ALTER EXTENSION hstore UPDATE;
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 AFTER trigger.
+ an AFTER trigger.
@@ -10664,16 +10856,16 @@ ALTER EXTENSION hstore UPDATE;
- Change multicolumn ON UPDATE
- SET NULL/SET DEFAULT foreign key actions to affect
+ Change multicolumn ON UPDATE
+ SET NULL/SET DEFAULT foreign key actions to affect
all columns of the constraint, not just those changed in the
- UPDATE (Tom Lane)
+ UPDATE (Tom Lane)
Previously, we would set only those referencing columns that
correspond to referenced columns that were changed by
- the UPDATE. This was what was required by SQL-92,
+ the UPDATE. This was what was required by SQL-92,
but more recent editions of the SQL standard specify the new behavior.
@@ -10681,35 +10873,35 @@ ALTER EXTENSION hstore UPDATE;
Force cached plans to be replanned if the search_path changes
+ linkend="guc-search-path">search_path changes
(Tom Lane)
Previously, cached plans already generated in the current session were
not redone if the query was re-executed with a
- new search_path setting, resulting in surprising behavior.
+ new search_path setting, resulting in surprising behavior.
Fix to_number()
+ linkend="functions-formatting-table">to_number()
to properly handle a period used as a thousands separator (Tom Lane)
Previously, a period was considered to be a decimal point even when
- the locale says it isn't and the D format code is used to
+ the locale says it isn't and the D format code is used to
specify use of the locale-specific decimal point. This resulted in
- wrong answers if FM format was also used.
+ wrong answers if FM format was also used.
- Fix STRICT non-set-returning functions that have
+ Fix STRICT non-set-returning functions that have
set-returning functions in their arguments to properly return null
rows (Tom Lane)
@@ -10722,14 +10914,14 @@ ALTER EXTENSION hstore UPDATE;
- Store WAL in a continuous
+ Store WAL in a continuous
stream, rather than skipping the last 16MB segment every 4GB
(Heikki Linnakangas)
- Previously, WAL files with names ending in FF
- were not used because of this skipping. If you have WAL
+ Previously, WAL files with names ending in FF
+ were not used because of this skipping. If you have WAL
backup or restore scripts that took this behavior into account, they
will need to be adjusted.
@@ -10738,15 +10930,15 @@ ALTER EXTENSION hstore UPDATE;
In pg_constraint.confmatchtype,
- store the default foreign key match type (non-FULL,
- non-PARTIAL) as s for simple
+ linkend="catalog-pg-constraint">pg_constraint.confmatchtype,
+ store the default foreign key match type (non-FULL,
+ non-PARTIAL) as s for simple
(Tom Lane)
- Previously this case was represented by u
- for unspecified.
+ Previously this case was represented by u
+ for unspecified.
@@ -10783,10 +10975,10 @@ ALTER EXTENSION hstore UPDATE;
This change improves concurrency and reduces the probability of
deadlocks when updating tables involved in a foreign-key constraint.
- UPDATEs that do not change any columns referenced in a
- foreign key now take the new NO KEY UPDATE lock mode on
- the row, while foreign key checks use the new KEY SHARE
- lock mode, which does not conflict with NO KEY UPDATE.
+ UPDATEs that do not change any columns referenced in a
+ foreign key now take the new NO KEY UPDATE lock mode on
+ the row, while foreign key checks use the new KEY SHARE
+ lock mode, which does not conflict with NO KEY UPDATE.
So there is no blocking unless a foreign-key column is changed.
@@ -10794,7 +10986,7 @@ ALTER EXTENSION hstore UPDATE;
Add configuration variable lock_timeout to
+ linkend="guc-lock-timeout">lock_timeout to
allow limiting how long a session will wait to acquire any one lock
(Zoltán Böszörményi)
@@ -10811,21 +11003,21 @@ ALTER EXTENSION hstore UPDATE;
- Add SP-GiST
+ Add SP-GiST
support for range data types (Alexander Korotkov)
- Allow GiST indexes to be
+ Allow GiST indexes to be
unlogged (Jeevan Chalke)
- Improve performance of GiST index insertion by randomizing
+ Improve performance of GiST index insertion by randomizing
the choice of which page to descend to when there are multiple equally
good alternatives (Heikki Linnakangas)
@@ -10863,7 +11055,7 @@ ALTER EXTENSION hstore UPDATE;
Improve optimizer's hash table size estimate for
- doing DISTINCT via hash aggregation (Tom Lane)
+ doing DISTINCT via hash aggregation (Tom Lane)
@@ -10893,7 +11085,7 @@ ALTER EXTENSION hstore UPDATE;
- Add COPY FREEZE
+ Add COPY FREEZE
option to avoid the overhead of marking tuples as frozen later
(Simon Riggs, Jeff Davis)
@@ -10902,7 +11094,7 @@ ALTER EXTENSION hstore UPDATE;
Improve performance of NUMERIC calculations
+ linkend="datatype-numeric">NUMERIC calculations
(Kyotaro Horiguchi)
@@ -10910,20 +11102,20 @@ ALTER EXTENSION hstore UPDATE;
Improve synchronization of sessions waiting for commit_delay
+ linkend="guc-commit-delay">commit_delay
(Peter Geoghegan)
- This greatly improves the usefulness of commit_delay.
+ This greatly improves the usefulness of commit_delay.
Improve performance of the CREATE TEMPORARY TABLE ... ON
- COMMIT DELETE ROWS option by not truncating such temporary
+ linkend="sql-createtable">CREATE TEMPORARY TABLE ... ON
+ COMMIT DELETE ROWS option by not truncating such temporary
tables in transactions that haven't touched any temporary tables
(Heikki Linnakangas)
@@ -10948,7 +11140,7 @@ ALTER EXTENSION hstore UPDATE;
This speeds up lock bookkeeping at statement completion in
multi-statement transactions that hold many locks; it is particularly
- useful for pg_dump.
+ useful for pg_dump.
@@ -10960,7 +11152,7 @@ ALTER EXTENSION hstore UPDATE;
This speeds up sessions that create many tables in successive
- small transactions, such as a pg_restore run.
+ small transactions, such as a pg_restore run.
@@ -10989,7 +11181,7 @@ ALTER EXTENSION hstore UPDATE;
The checksum option can be set during initdb.
+ linkend="app-initdb">initdb.
@@ -11042,7 +11234,7 @@ ALTER EXTENSION hstore UPDATE;
When an authentication failure occurs, log the relevant
- pg_hba.conf
+ pg_hba.conf
line, to ease debugging of unintended failures
(Magnus Hagander)
@@ -11050,23 +11242,23 @@ ALTER EXTENSION hstore UPDATE;
- Improve LDAP error
+ Improve LDAP error
reporting and documentation (Peter Eisentraut)
- Add support for specifying LDAP authentication parameters
- in URL format, per RFC 4516 (Peter Eisentraut)
+ Add support for specifying LDAP authentication parameters
+ in URL format, per RFC 4516 (Peter Eisentraut)
Change the ssl_ciphers parameter
- to start with DEFAULT, rather than ALL,
+ linkend="guc-ssl-ciphers">ssl_ciphers parameter
+ to start with DEFAULT, rather than ALL,
then remove insecure ciphers (Magnus Hagander)
@@ -11078,12 +11270,12 @@ ALTER EXTENSION hstore UPDATE;
Parse and load pg_ident.conf
+ linkend="auth-username-maps">pg_ident.conf
once, not during each connection (Amit Kapila)
- This is similar to how pg_hba.conf is processed.
+ This is similar to how pg_hba.conf is processed.
@@ -11103,8 +11295,8 @@ ALTER EXTENSION hstore UPDATE;
- On Unix-like systems, mmap() is now used for most
- of PostgreSQL's shared memory. For most users, this
+ On Unix-like systems, mmap() is now used for most
+ of PostgreSQL's shared memory. For most users, this
will eliminate any need to adjust kernel parameters for shared memory.
@@ -11117,8 +11309,8 @@ ALTER EXTENSION hstore UPDATE;
The configuration parameter
- unix_socket_directory is replaced by unix_socket_directories,
+ unix_socket_directory is replaced by unix_socket_directories,
which accepts a list of directories.
@@ -11131,7 +11323,7 @@ ALTER EXTENSION hstore UPDATE;
Such a directory is specified with include_dir in the server
+ linkend="config-includes">include_dir in the server
configuration file.
@@ -11139,14 +11331,14 @@ ALTER EXTENSION hstore UPDATE;
Increase the maximum initdb-configured value for shared_buffers
+ linkend="app-initdb">initdb-configured value for shared_buffers
to 128MB (Robert Haas)
This is the maximum value that initdb will attempt to set in postgresql.conf;
+ linkend="config-setting-configuration-file">postgresql.conf;
the previous maximum was 32MB.
@@ -11154,7 +11346,7 @@ ALTER EXTENSION hstore UPDATE;
Remove the external
- PID file, if any, on postmaster exit
+ PID file, if any, on postmaster exit
(Peter Eisentraut)
@@ -11186,10 +11378,10 @@ ALTER EXTENSION hstore UPDATE;
- Add SQL functions pg_is_in_backup()
+ Add SQL functions pg_is_in_backup()
and pg_backup_start_time()
+ linkend="functions-admin-backup">pg_backup_start_time()
(Gilles Darold)
@@ -11201,7 +11393,7 @@ ALTER EXTENSION hstore UPDATE;
Improve performance of streaming log shipping with synchronous_commit
+ linkend="guc-synchronous-commit">synchronous_commit
disabled (Andres Freund)
@@ -11216,12 +11408,12 @@ ALTER EXTENSION hstore UPDATE;
Add the last checkpoint's redo location to pg_controldata's
+ linkend="app-pgcontroldata">pg_controldata's
output (Fujii Masao)
- This information is useful for determining which WAL
+ This information is useful for determining which WAL
files are needed for restore.
@@ -11229,7 +11421,7 @@ ALTER EXTENSION hstore UPDATE;
Allow tools like pg_receivexlog
+ linkend="app-pgreceivewal">pg_receivexlog
to run on computers with different architectures (Heikki
Linnakangas)
@@ -11245,9 +11437,9 @@ ALTER EXTENSION hstore UPDATE;
Make pg_basebackup
-
@@ -11259,10 +11451,10 @@ ALTER EXTENSION hstore UPDATE;
Allow pg_receivexlog
+ linkend="app-pgreceivewal">pg_receivexlog
and pg_basebackup
- to handle streaming timeline switches
(Heikki Linnakangas)
@@ -11270,8 +11462,8 @@ ALTER EXTENSION hstore UPDATE;
Add wal_receiver_timeout
- parameter to control the WAL receiver's timeout
+ linkend="guc-wal-receiver-timeout">wal_receiver_timeout
+ parameter to control the WAL receiver's timeout
(Amit Kapila)
@@ -11282,7 +11474,7 @@ ALTER EXTENSION hstore UPDATE;
- Change the WAL record format to
+ Change the WAL record format to
allow splitting the record header across pages (Heikki Linnakangas)
@@ -11303,23 +11495,23 @@ ALTER EXTENSION hstore UPDATE;
- Implement SQL-standard LATERAL option for
- FROM-clause subqueries and function calls (Tom Lane)
+ Implement SQL-standard LATERAL option for
+ FROM-clause subqueries and function calls (Tom Lane)
- This feature allows subqueries and functions in FROM to
- reference columns from other tables in the FROM
- clause. The LATERAL keyword is optional for functions.
+ This feature allows subqueries and functions in FROM to
+ reference columns from other tables in the FROM
+ clause. The LATERAL keyword is optional for functions.
Add support for piping COPY and psql \copy
+ linkend="sql-copy">COPY and psql\copy
data to/from an external program (Etsuro Fujita)
@@ -11327,8 +11519,8 @@ ALTER EXTENSION hstore UPDATE;
Allow a multirow VALUES clause in a rule
- to reference OLD/NEW (Tom Lane)
+ linkend="sql-values">VALUES clause in a rule
+ to reference OLD/NEW (Tom Lane)
@@ -11355,7 +11547,7 @@ ALTER EXTENSION hstore UPDATE;
- Allow foreign data
+ Allow foreign data
wrappers to support writes (inserts/updates/deletes) on foreign
tables (KaiGai Kohei)
@@ -11363,15 +11555,15 @@ ALTER EXTENSION hstore UPDATE;
- Add CREATE SCHEMA ... IF
- NOT EXISTS clause (Fabrízio de Royes Mello)
+ Add CREATE SCHEMA ... IF
+ NOT EXISTS clause (Fabrízio de Royes Mello)
- Make REASSIGN
- OWNED also change ownership of shared objects
+ Make REASSIGN
+ OWNED also change ownership of shared objects
(Álvaro Herrera)
@@ -11379,28 +11571,28 @@ ALTER EXTENSION hstore UPDATE;
Make CREATE
- AGGREGATE complain if the given initial value string is not
+ AGGREGATE complain if the given initial value string is not
valid input for the transition datatype (Tom Lane)
- Suppress CREATE
- TABLE's messages about implicit index and sequence creation
+ Suppress CREATE
+ TABLE's messages about implicit index and sequence creation
(Robert Haas)
- These messages now appear at DEBUG1 verbosity, so that
+ These messages now appear at DEBUG1 verbosity, so that
they will not be shown by default.
- Allow DROP TABLE IF
- EXISTS to succeed when a non-existent schema is specified
+ Allow DROP TABLE IF
+ EXISTS to succeed when a non-existent schema is specified
in the table name (Bruce Momjian)
@@ -11427,14 +11619,14 @@ ALTER EXTENSION hstore UPDATE;
- <command>ALTER</>
+ <command>ALTER</command>
- Support IF NOT EXISTS option in ALTER TYPE ... ADD VALUE
+ Support IF NOT EXISTS option in ALTER TYPE ... ADD VALUE
(Andrew Dunstan)
@@ -11445,22 +11637,22 @@ ALTER EXTENSION hstore UPDATE;
- Add ALTER ROLE ALL
- SET to establish settings for all users (Peter Eisentraut)
+ Add ALTER ROLE ALL
+ SET to establish settings for all users (Peter Eisentraut)
This allows settings to apply to all users in all databases. ALTER DATABASE SET
+ linkend="sql-alterdatabase">ALTER DATABASE SET
already allowed addition of settings for all users in a single
- database. postgresql.conf has a similar effect.
+ database. postgresql.conf has a similar effect.
- Add support for ALTER RULE
- ... RENAME (Ali Dar)
+ Add support for ALTER RULE
+ ... RENAME (Ali Dar)
@@ -11469,13 +11661,13 @@ ALTER EXTENSION hstore UPDATE;
- <link linkend="rules-views"><command>VIEWs</></link>
+ <link linkend="rules-views"><command>VIEWs</command></link>
- Add materialized
+ Add materialized
views (Kevin Grittner)
@@ -11491,7 +11683,7 @@ ALTER EXTENSION hstore UPDATE;
Make simple views auto-updatable
+ linkend="sql-createview-updatable-views">auto-updatable
(Dean Rasheed)
@@ -11499,20 +11691,20 @@ ALTER EXTENSION hstore UPDATE;
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 INSTEAD OF triggers
- or INSTEAD rules.
+ linkend="sql-createtrigger">INSTEAD OF triggers
+ or INSTEAD rules.
- Add CREATE RECURSIVE
- VIEW syntax (Peter Eisentraut)
+ Add CREATE RECURSIVE
+ VIEW syntax (Peter Eisentraut)
Internally this is translated into CREATE VIEW ... WITH
- RECURSIVE ....
+ RECURSIVE ....
@@ -11545,7 +11737,7 @@ ALTER EXTENSION hstore UPDATE;
- Increase the maximum size of large
+ Increase the maximum size of large
objects from 2GB to 4TB (Nozomi Anzai, Yugo Nagata)
@@ -11558,8 +11750,8 @@ ALTER EXTENSION hstore UPDATE;
Allow text timezone
- designations, e.g. America/Chicago, in the
- T field of ISO-format timestamptz
+ designations, e.g. America/Chicago, in the
+ T field of ISO-format timestamptz
input (Bruce Momjian)
@@ -11567,20 +11759,20 @@ ALTER EXTENSION hstore UPDATE;
- <link linkend="datatype-json"><type>JSON</></link>
+ <link linkend="datatype-json"><type>JSON</type></link>
Add operators and functions
- to extract elements from JSON values (Andrew Dunstan)
+ to extract elements from JSON values (Andrew Dunstan)
- Allow JSON values to be JSON values to be converted into records
(Andrew Dunstan)
@@ -11589,7 +11781,7 @@ ALTER EXTENSION hstore UPDATE;
Add functions to convert
- scalars, records, and hstore values to JSON (Andrew
+ scalars, records, and hstore values to JSON (Andrew
Dunstan)
@@ -11609,9 +11801,9 @@ ALTER EXTENSION hstore UPDATE;
Add array_remove()
+ linkend="array-functions-table">array_remove()
and array_replace()
+ linkend="array-functions-table">array_replace()
functions (Marco Nenciarini, Gabriele Bartolini)
@@ -11619,10 +11811,10 @@ ALTER EXTENSION hstore UPDATE;
Allow concat()
+ linkend="functions-string-other">concat()
and format()
- to properly expand VARIADIC-labeled arguments
+ linkend="functions-string-format">format()
+ to properly expand VARIADIC-labeled arguments
(Pavel Stehule)
@@ -11630,7 +11822,7 @@ ALTER EXTENSION hstore UPDATE;
Improve format()
+ linkend="functions-string-format">format()
to provide field width and left/right alignment options (Pavel Stehule)
@@ -11638,29 +11830,29 @@ ALTER EXTENSION hstore UPDATE;
Make to_char(),
+ linkend="functions-formatting-table">to_char(),
to_date(),
+ linkend="functions-formatting-table">to_date(),
and to_timestamp()
+ linkend="functions-formatting-table">to_timestamp()
handle negative (BC) century values properly
(Bruce Momjian)
Previously the behavior was either wrong or inconsistent
- with positive/AD handling, e.g. with the format mask
- IYYY-IW-DY.
+ with positive/AD handling, e.g. with the format mask
+ IYYY-IW-DY.
Make to_date()
+ linkend="functions-formatting-table">to_date()
and to_timestamp()
- return proper results when mixing ISO and Gregorian
+ linkend="functions-formatting-table">to_timestamp()
+ return proper results when mixing ISO and Gregorian
week/day designations (Bruce Momjian)
@@ -11668,27 +11860,27 @@ ALTER EXTENSION hstore UPDATE;
Cause pg_get_viewdef()
- to start a new line by default after each SELECT target
- list entry and FROM entry (Marko Tiikkaja)
+ linkend="functions-info-catalog-table">pg_get_viewdef()
+ to start a new line by default after each SELECT target
+ list entry and FROM entry (Marko Tiikkaja)
This reduces line length in view printing, for instance in pg_dump output.
+ linkend="app-pgdump">pg_dump output.
- Fix map_sql_value_to_xml_value() to print values of
+ Fix map_sql_value_to_xml_value() to print values of
domain types the same way their base type would be printed
(Pavel Stehule)
There are special formatting rules for certain built-in types such as
- boolean; these rules now also apply to domains over these
+ boolean; these rules now also apply to domains over these
types.
@@ -11707,13 +11899,13 @@ ALTER EXTENSION hstore UPDATE;
- Allow PL/pgSQL to use RETURN with a composite-type
+ Allow PL/pgSQL to use RETURN with a composite-type
expression (Asif Rehman)
Previously, in a function returning a composite type,
- RETURN could only reference a variable of that type.
+ RETURN could only reference a variable of that type.
@@ -11728,14 +11920,14 @@ ALTER EXTENSION hstore UPDATE;
Allow PL/pgSQL to access the number of rows processed by
- COPY (Pavel Stehule)
+ COPY (Pavel Stehule)
- A COPY executed in a PL/pgSQL function now updates the
+ A COPY executed in a PL/pgSQL function now updates the
value retrieved by GET DIAGNOSTICS
- x = ROW_COUNT.
+ x = ROW_COUNT.
@@ -11779,9 +11971,9 @@ ALTER EXTENSION hstore UPDATE;
- Handle SPI errors raised
- explicitly (with PL/Python's RAISE) the same as
- internal SPI errors (Oskari Saarenmaa and Jan Urbanski)
+ Handle SPI errors raised
+ explicitly (with PL/Python's RAISE) the same as
+ internal SPI errors (Oskari Saarenmaa and Jan Urbanski)
@@ -11798,7 +11990,7 @@ ALTER EXTENSION hstore UPDATE;
- Prevent leakage of SPI tuple tables during subtransaction
+ Prevent leakage of SPI tuple tables during subtransaction
abort (Tom Lane)
@@ -11809,7 +12001,7 @@ ALTER EXTENSION hstore UPDATE;
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. SPI_freetuptable()
+ linkend="spi-spi-freetupletable">SPI_freetuptable()
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.
@@ -11817,8 +12009,8 @@ ALTER EXTENSION hstore UPDATE;
- Allow SPI functions to access the number of rows processed
- by COPY (Pavel Stehule)
+ Allow SPI functions to access the number of rows processed
+ by COPY (Pavel Stehule)
@@ -11834,35 +12026,35 @@ ALTER EXTENSION hstore UPDATE;
Add command-line utility pg_isready to
+ linkend="app-pg-isready">pg_isready to
check if the server is ready to accept connections (Phil Sorber)
- Support multiple
This is similar to the way pg_dump's
- option works.
- Add
@@ -11870,7 +12062,7 @@ ALTER EXTENSION hstore UPDATE;
Add libpq function PQconninfo()
+ linkend="libpq-pqconninfo">PQconninfo()
to return connection information (Zoltán
Böszörményi, Magnus Hagander)
@@ -11879,27 +12071,27 @@ ALTER EXTENSION hstore UPDATE;
- <link linkend="APP-PSQL"><application>psql</></link>
+ <link linkend="app-psql"><application>psql</application></link>
- Adjust function cost settings so psql tab
+ Adjust function cost settings so psql tab
completion and pattern searching are more efficient (Tom Lane)
- Improve psql's tab completion coverage (Jeff Janes,
+ Improve psql's tab completion coverage (Jeff Janes,
Dean Rasheed, Peter Eisentraut, Magnus Hagander)
- Allow the psql
mode to work when reading from standard input (Fabien Coelho,
Robert Haas)
@@ -11911,61 +12103,61 @@ ALTER EXTENSION hstore UPDATE;
- Remove psql warning when connecting to an older
+ Remove psql warning when connecting to an older
server (Peter Eisentraut)
A warning is still issued when connecting to a server of a newer major
- version than psql's.
+ version than psql's.
- <link linkend="APP-PSQL-meta-commands">Backslash Commands</link>
+ <link linkend="app-psql-meta-commands">Backslash Commands</link>
- Add psql command \watch to repeatedly
+ Add psql command \watch to repeatedly
execute a SQL command (Will Leinweber)
- Add psql command \gset to store query
- results in psql variables (Pavel Stehule)
+ Add psql command \gset to store query
+ results in psql variables (Pavel Stehule)
- Add SSL information to psql's
- \conninfo command (Alastair Turner)
+ Add SSL information to psql's
+ \conninfo command (Alastair Turner)
- Add Security column to psql's
- \df+ output (Jon Erdman)
+ Add Security column to psql's
+ \df+ output (Jon Erdman)
- Allow psql command \l to accept a database
+ Allow psql command \l to accept a database
name pattern (Peter Eisentraut)
- In psql, do not allow \connect to
+ In psql, do not allow \connect to
use defaults if there is no active connection (Bruce Momjian)
@@ -11977,7 +12169,7 @@ ALTER EXTENSION hstore UPDATE;
Properly reset state after failure of a SQL command executed with
- psql's \g file
+ psql's \gfile
(Tom Lane)
@@ -11998,8 +12190,8 @@ ALTER EXTENSION hstore UPDATE;
- Add a latex-longtable output format to
- psql (Bruce Momjian)
+ Add a latex-longtable output format to
+ psql (Bruce Momjian)
@@ -12009,21 +12201,21 @@ ALTER EXTENSION hstore UPDATE;
- Add a border=3 output mode to the psql
- latex format (Bruce Momjian)
+ Add a border=3 output mode to the psql
+ latex format (Bruce Momjian)
- In psql's tuples-only and expanded output modes, no
- longer emit (No rows) for zero rows (Peter Eisentraut)
+ In psql's tuples-only and expanded output modes, no
+ longer emit (No rows) for zero rows (Peter Eisentraut)
- In psql's unaligned, expanded output mode, no longer
+ In psql's unaligned, expanded output mode, no longer
print an empty line for zero rows (Peter Eisentraut)
@@ -12035,34 +12227,34 @@ ALTER EXTENSION hstore UPDATE;
- <link linkend="APP-PGDUMP"><application>pg_dump</></link>
+ <link linkend="app-pgdump"><application>pg_dump</application></link>
- Add pg_dump option to dump tables in
parallel (Joachim Wieland)
- Make pg_dump output functions in a more predictable
+ Make pg_dump output functions in a more predictable
order (Joel Jacobson)
- Fix tar files emitted by pg_dump
- to be POSIX conformant (Brian Weaver, Tom Lane)
+ Fix tar files emitted by pg_dump
+ to be POSIX conformant (Brian Weaver, Tom Lane)
- Add
@@ -12076,7 +12268,7 @@ ALTER EXTENSION hstore UPDATE;
- <link linkend="APP-INITDB"><application>initdb</></link>
+ <link linkend="app-initdb"><application>initdb</application></link>
@@ -12087,19 +12279,19 @@ ALTER EXTENSION hstore UPDATE;
This insures data integrity in event of a system crash shortly after
- initdb. This can be disabled by using .
- Add initdb option to sync the data directory to durable
storage (Bruce Momjian)
This is used by pg_upgrade.
+ linkend="pgupgrade">pg_upgrade.
@@ -12131,14 +12323,14 @@ ALTER EXTENSION hstore UPDATE;
- Create a centralized timeout API (Zoltán
+ Create a centralized timeout API (Zoltán
Böszörményi)
- Create libpgcommon and move pg_malloc() and other
+ Create libpgcommon and move pg_malloc() and other
functions there (Álvaro Herrera, Andres Freund)
@@ -12155,15 +12347,15 @@ ALTER EXTENSION hstore UPDATE;
- Use SA_RESTART for all signals,
- including SIGALRM (Tom Lane)
+ Use SA_RESTART for all signals,
+ including SIGALRM (Tom Lane)
Ensure that the correct text domain is used when
- translating errcontext() messages
+ translating errcontext() messages
(Heikki Linnakangas)
@@ -12176,7 +12368,7 @@ ALTER EXTENSION hstore UPDATE;
- Provide support for static assertions that will fail at
+ Provide support for static assertions that will fail at
compile time if some compile-time-constant condition is not met
(Andres Freund, Tom Lane)
@@ -12184,14 +12376,14 @@ ALTER EXTENSION hstore UPDATE;
- Support Assert() in client-side code (Andrew Dunstan)
+ Support Assert() in client-side code (Andrew Dunstan)
- Add decoration to inform the C compiler that some ereport()
- and elog() calls do not return (Peter Eisentraut,
+ Add decoration to inform the C compiler that some ereport()
+ and elog() calls do not return (Peter Eisentraut,
Andres Freund, Tom Lane, Heikki Linnakangas)
@@ -12200,7 +12392,7 @@ ALTER EXTENSION hstore UPDATE;
Allow options to be passed to the regression
test output comparison utility via PG_REGRESS_DIFF_OPTS
+ linkend="regress-evaluation">PG_REGRESS_DIFF_OPTS
(Peter Eisentraut)
@@ -12208,43 +12400,43 @@ ALTER EXTENSION hstore UPDATE;
Add isolation tests for CREATE INDEX
- CONCURRENTLY (Abhijit Menon-Sen)
+ linkend="sql-createindex">CREATE INDEX
+ CONCURRENTLY (Abhijit Menon-Sen)
- Remove typedefs for int2/int4 as they are better
- represented as int16/int32 (Peter Eisentraut)
+ Remove typedefs for int2/int4 as they are better
+ represented as int16/int32 (Peter Eisentraut)
Fix install-strip on Mac OS
- X (Peter Eisentraut)
+ X (Peter Eisentraut)
Remove configure flag
- , as it is no longer supported
(Bruce Momjian)
- Rewrite pgindent in Perl (Andrew Dunstan)
+ Rewrite pgindent in Perl (Andrew Dunstan)
Provide Emacs macro to set Perl formatting to
- match PostgreSQL's perltidy settings (Peter Eisentraut)
+ match PostgreSQL's perltidy settings (Peter Eisentraut)
@@ -12257,25 +12449,25 @@ ALTER EXTENSION hstore UPDATE;
- Change the way UESCAPE is lexed, to significantly reduce
+ Change the way UESCAPE is lexed, to significantly reduce
the size of the lexer tables (Heikki Linnakangas)
- Centralize flex and bison
- make rules (Peter Eisentraut)
+ Centralize flex and bison
+ make rules (Peter Eisentraut)
- This is useful for pgxs authors.
+ This is useful for pgxs authors.
- Change many internal backend functions to return object OIDs
+ Change many internal backend functions to return object OIDs
rather than void (Dimitri Fontaine)
@@ -12299,7 +12491,7 @@ ALTER EXTENSION hstore UPDATE;
Add function pg_identify_object()
+ linkend="functions-info-catalog-table">pg_identify_object()
to produce a machine-readable description of a database object
(Álvaro Herrera)
@@ -12307,7 +12499,7 @@ ALTER EXTENSION hstore UPDATE;
- Add post-ALTER-object server hooks (KaiGai Kohei)
+ Add post-ALTER-object server hooks (KaiGai Kohei)
@@ -12321,28 +12513,28 @@ ALTER EXTENSION hstore UPDATE;
Provide a tool to help detect timezone abbreviation changes when
- updating the src/timezone/data files
+ updating the src/timezone/data files
(Tom Lane)
- Add pkg-config support for libpq
- and ecpg libraries (Peter Eisentraut)
+ Add pkg-config support for libpq
+ and ecpg libraries (Peter Eisentraut)
- Remove src/tools/backend, now that the content is on
- the PostgreSQL wiki (Bruce Momjian)
+ Remove src/tools/backend, now that the content is on
+ the PostgreSQL wiki (Bruce Momjian)
- Split out WAL reading as
+ Split out WAL reading as
an independent facility (Heikki Linnakangas, Andres Freund)
@@ -12350,13 +12542,13 @@ ALTER EXTENSION hstore UPDATE;
Use a 64-bit integer to represent WAL positions
- (XLogRecPtr) instead of two 32-bit integers
+ linkend="wal">WAL positions
+ (XLogRecPtr) instead of two 32-bit integers
(Heikki Linnakangas)
- Generally, tools that need to read the WAL format
+ Generally, tools that need to read the WAL format
will need to be adjusted.
@@ -12371,7 +12563,7 @@ ALTER EXTENSION hstore UPDATE;
Allow PL/Python on OS
- X to build against custom versions of Python
+ X to build against custom versions of Python
(Peter Eisentraut)
@@ -12387,9 +12579,9 @@ ALTER EXTENSION hstore UPDATE;
- Add a Postgres foreign
+ Add a Postgres foreign
data wrapper contrib module to allow access to
- other Postgres servers (Shigeru Hanada)
+ other Postgres servers (Shigeru Hanada)
@@ -12399,7 +12591,7 @@ ALTER EXTENSION hstore UPDATE;
- Add pg_xlogdump
+ Add pg_xlogdump
contrib program (Andres Freund)
@@ -12407,46 +12599,46 @@ ALTER EXTENSION hstore UPDATE;
Add support for indexing of regular-expression searches in
- pg_trgm
+ pg_trgm
(Alexander Korotkov)
- Improve pg_trgm's
+ Improve pg_trgm's
handling of multibyte characters (Tom Lane)
On a platform that does not have the wcstombs() or towlower() library
functions, this could result in an incompatible change in the contents
- of pg_trgm indexes for non-ASCII data. In such cases,
- REINDEX those indexes to ensure correct search results.
+ of pg_trgm indexes for non-ASCII data. In such cases,
+ REINDEX those indexes to ensure correct search results.
Add a pgstattuple function to report
- the size of the pending-insertions list of a GIN index
+ the size of the pending-insertions list of a GIN index
(Fujii Masao)
- Make oid2name,
- pgbench, and
- vacuumlo set
- fallback_application_name (Amit Kapila)
+ Make oid2name,
+ pgbench, and
+ vacuumlo set
+ fallback_application_name (Amit Kapila)
Improve output of pg_test_timing
+ linkend="pgtesttiming">pg_test_timing
(Bruce Momjian)
@@ -12454,7 +12646,7 @@ ALTER EXTENSION hstore UPDATE;
Improve output of pg_test_fsync
+ linkend="pgtestfsync">pg_test_fsync
(Peter Geoghegan)
@@ -12466,9 +12658,9 @@ ALTER EXTENSION hstore UPDATE;
- When using this FDW to define the target of a dblink
+ When using this FDW to define the target of a dblink
connection, instead of using a hard-wired list of connection options,
- the underlying libpq library is consulted to see what
+ the underlying libpq library is consulted to see what
connection options it supports.
@@ -12476,26 +12668,26 @@ ALTER EXTENSION hstore UPDATE;
- <link linkend="pgupgrade"><application>pg_upgrade</></link>
+ <link linkend="pgupgrade"><application>pg_upgrade</application></link>
- Allow pg_upgrade to do dumps and restores in
+ Allow pg_upgrade to do dumps and restores in
parallel (Bruce Momjian, Andrew Dunstan)
This allows parallel schema dump/restore of databases, as well as
parallel copy/link of data files per tablespace. Use the
- option to specify the level of parallelism.
- Make pg_upgrade create Unix-domain sockets in
+ Make pg_upgrade create Unix-domain sockets in
the current directory (Bruce Momjian, Tom Lane)
@@ -12507,7 +12699,7 @@ ALTER EXTENSION hstore UPDATE;
- Make pg_upgrade mode properly
detect the location of non-default socket directories (Bruce
Momjian, Tom Lane)
@@ -12515,21 +12707,21 @@ ALTER EXTENSION hstore UPDATE;
- Improve performance of pg_upgrade for databases
+ Improve performance of pg_upgrade for databases
with many tables (Bruce Momjian)
- Improve pg_upgrade's logs by showing
+ Improve pg_upgrade's logs by showing
executed commands (Álvaro Herrera)
- Improve pg_upgrade's status display during
+ Improve pg_upgrade's status display during
copy/link (Bruce Momjian)
@@ -12539,33 +12731,33 @@ ALTER EXTENSION hstore UPDATE;
- <link linkend="pgbench"><application>pgbench</></link>
+ <link linkend="pgbench"><application>pgbench</application></link>
- Add
This adds foreign key constraints to the standard tables created by
- pgbench, for use in foreign key performance testing.
+ pgbench, for use in foreign key performance testing.
- Allow pgbench to aggregate performance statistics
- and produce output every
seconds (Tomas Vondra)
- Add pgbench option
to control the percentage of transactions logged (Tomas Vondra)
@@ -12573,29 +12765,29 @@ ALTER EXTENSION hstore UPDATE;
Reduce and improve the status message output of
- pgbench's initialization mode (Robert Haas,
+ pgbench's initialization mode (Robert Haas,
Peter Eisentraut)
- Add pgbench mode to print one output
line every five seconds (Tomas Vondra)
- Output pgbench elapsed and estimated remaining
+ Output pgbench elapsed and estimated remaining
time during initialization (Tomas Vondra)
- Allow pgbench to use much larger scale factors,
- by changing relevant columns from integer to bigint
+ Allow pgbench to use much larger scale factors,
+ by changing relevant columns from integer to bigint
when the requested scale factor exceeds 20000
(Greg Smith)
@@ -12614,21 +12806,21 @@ ALTER EXTENSION hstore UPDATE;
- Allow EPUB-format documentation to be created
+ Allow EPUB-format documentation to be created
(Peter Eisentraut)
- Update FreeBSD kernel configuration documentation
+ Update FreeBSD kernel configuration documentation
(Brad Davis)
- Improve WINDOW
+ Improve WINDOW
function documentation (Bruce Momjian, Florian Pflug)
@@ -12636,7 +12828,7 @@ ALTER EXTENSION hstore UPDATE;
Add instructions for setting
- up the documentation tool chain on macOS
+ up the documentation tool chain on macOS
(Peter Eisentraut)
@@ -12644,7 +12836,7 @@ ALTER EXTENSION hstore UPDATE;
Improve commit_delay
+ linkend="guc-commit-delay">commit_delay
documentation (Peter Geoghegan)
diff --git a/doc/src/sgml/release-9.4.sgml b/doc/src/sgml/release-9.4.sgml
index c665f90ca10..ab47dc50ddd 100644
--- a/doc/src/sgml/release-9.4.sgml
+++ b/doc/src/sgml/release-9.4.sgml
@@ -1,6 +1,242 @@
+
+ Release 9.4.15
+
+
+ Release date:
+ 2017-11-09
+
+
+
+ This release contains a variety of fixes from 9.4.14.
+ For information about new features in the 9.4 major release, see
+ .
+
+
+
+ Migration to Version 9.4.15
+
+
+ A dump/restore is not required for those running 9.4.X.
+
+
+
+ However, if you are upgrading from a version earlier than 9.4.13,
+ see .
+
+
+
+
+ Changes
+
+
+
+
+
+ Fix crash when logical decoding is invoked from a SPI-using function,
+ in particular any function written in a PL language
+ (Tom Lane)
+
+
+
+
+
+ Fix json_build_array(),
+ json_build_object(), and their jsonb
+ equivalents to handle explicit VARIADIC arguments
+ correctly (Michael Paquier)
+
+
+
+
+
+ Properly reject attempts to convert infinite float values to
+ type numeric (Tom Lane, KaiGai Kohei)
+
+
+
+ Previously the behavior was platform-dependent.
+
+
+
+
+
+ Fix corner-case crashes when columns have been added to the end of a
+ view (Tom Lane)
+
+
+
+
+
+ Record proper dependencies when a view or rule
+ contains FieldSelect
+ or FieldStore expression nodes (Tom Lane)
+
+
+
+ Lack of these dependencies could allow a column or data
+ type DROP 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.
+
+
+
+
+
+ Correctly detect hashability of range data types (Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+ Fix low-probability loss of NOTIFY messages due to
+ XID wraparound (Marko Tiikkaja, Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+ Avoid SIGBUS crash on Linux when a DSM memory
+ request exceeds the space available in tmpfs
+ (Thomas Munro)
+
+
+
+
+
+ Prevent low-probability crash in processing of nested trigger firings
+ (Tom Lane)
+
+
+
+
+
+ Allow COPY's FREEZE option to
+ work when the transaction isolation level is REPEATABLE
+ READ or higher (Noah Misch)
+
+
+
+ This case was unintentionally broken by a previous bug fix.
+
+
+
+
+
+ Correctly restore the umask setting when file creation fails
+ in COPY or lo_export()
+ (Peter Eisentraut)
+
+
+
+
+
+ Give a better error message for duplicate column names
+ in ANALYZE (Nathan Bossart)
+
+
+
+
+
+ Fix mis-parsing of the last line in a
+ non-newline-terminated pg_hba.conf file
+ (Tom Lane)
+
+
+
+
+
+ Fix libpq to not require user's home
+ directory to exist (Tom Lane)
+
+
+
+ In v10, failure to find the home directory while trying to
+ read ~/.pgpass 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 ~/.pg_service.conf, though this was less
+ obvious since that file is not sought unless a service name is
+ specified.
+
+
+
+
+
+ Fix libpq to guard against integer
+ overflow in the row count of a PGresult
+ (Michael Paquier)
+
+
+
+
+
+ Fix ecpg's handling of out-of-scope cursor
+ declarations with pointer or array variables (Michael Meskes)
+
+
+
+
+
+ In ecpglib, correctly handle backslashes in string literals depending
+ on whether standard_conforming_strings is set
+ (Tsunakawa Takayuki)
+
+
+
+
+
+ Make ecpglib's Informix-compatibility mode ignore fractional digits in
+ integer input strings, as expected (Gao Zengqi, Michael Meskes)
+
+
+
+
+
+ Sync our copy of the timezone library with IANA release tzcode2017c
+ (Tom Lane)
+
+
+
+ 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 posixrules file exists in the timezone data
+ directory, now match current US law rather than what it was a dozen
+ years ago.
+
+
+
+
+
+ Update time zone data files to tzdata
+ 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.
+
+
+
+
+
+
+
+
Release 9.4.14
@@ -53,20 +289,20 @@ Branch: REL9_4_STABLE [b51c8efc6] 2017-08-24 15:21:32 -0700
Show foreign tables
- in information_schema.table_privileges
+ in information_schema.table_privileges
view (Peter Eisentraut)
- All other relevant information_schema views include
+ All other relevant information_schema views include
foreign tables, but this one ignored them.
- Since this view definition is installed by initdb,
+ Since this view definition is installed by initdb,
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 psql:
+ in psql:
SET search_path TO information_schema;
CREATE OR REPLACE VIEW table_privileges AS
@@ -105,21 +341,21 @@ CREATE OR REPLACE VIEW table_privileges AS
OR grantee.rolname = 'PUBLIC');
This must be repeated in each database to be fixed,
- including template0.
+ including template0.
Clean up handling of a fatal exit (e.g., due to receipt
- of SIGTERM) that occurs while trying to execute
- a ROLLBACK of a failed transaction (Tom Lane)
+ of SIGTERM) that occurs while trying to execute
+ a ROLLBACK of a failed transaction (Tom Lane)
This situation could result in an assertion failure. In production
builds, the exit would still occur, but it would log an unexpected
- message about cannot drop active portal.
+ message about cannot drop active portal.
@@ -136,7 +372,7 @@ CREATE OR REPLACE VIEW table_privileges AS
- Certain ALTER commands that change the definition of a
+ Certain ALTER commands that change the definition of a
composite type or domain type are supposed to fail if there are any
stored values of that type in the database, because they lack the
infrastructure needed to update or check such values. Previously,
@@ -148,7 +384,7 @@ CREATE OR REPLACE VIEW table_privileges AS
- Fix crash in pg_restore when using parallel mode and
+ Fix crash in pg_restore when using parallel mode and
using a list file to select a subset of items to restore
(Fabrízio de Royes Mello)
@@ -156,13 +392,13 @@ CREATE OR REPLACE VIEW table_privileges AS
- Change ecpg's parser to allow RETURNING
+ Change ecpg's parser to allow RETURNING
clauses without attached C variables (Michael Meskes)
- This allows ecpg programs to contain SQL constructs
- that use RETURNING internally (for example, inside a CTE)
+ This allows ecpg programs to contain SQL constructs
+ that use RETURNING internally (for example, inside a CTE)
rather than using it to define values to be returned to the client.
@@ -174,12 +410,12 @@ CREATE OR REPLACE VIEW table_privileges AS
This fix avoids possible crashes of PL/Perl due to inconsistent
- assumptions about the width of time_t values.
+ assumptions about the width of time_t values.
A side-effect that may be visible to extension developers is
- that _USE_32BIT_TIME_T is no longer defined globally
- in PostgreSQL Windows builds. This is not expected
- to cause problems, because type time_t is not used
- in any PostgreSQL API definitions.
+ that _USE_32BIT_TIME_T is no longer defined globally
+ in PostgreSQL Windows builds. This is not expected
+ to cause problems, because type time_t is not used
+ in any PostgreSQL API definitions.
@@ -228,7 +464,7 @@ CREATE OR REPLACE VIEW table_privileges AS
Further restrict visibility
- of pg_user_mappings.umoptions, to
+ of pg_user_mappings.umoptions, to
protect passwords stored as user mapping options
(Noah Misch)
@@ -236,11 +472,11 @@ CREATE OR REPLACE VIEW table_privileges AS
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 USAGE permission on the associated foreign server.
+ have USAGE 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 information_schema.user_mapping_options does not
- show the options in such cases, pg_user_mappings
+ Since information_schema.user_mapping_options does not
+ show the options in such cases, pg_user_mappings
should not either.
(CVE-2017-7547)
@@ -255,15 +491,15 @@ CREATE OR REPLACE VIEW table_privileges AS
Restart the postmaster after adding allow_system_table_mods
- = true to postgresql.conf. (In versions
- supporting ALTER SYSTEM, you can use that to make the
+ = true to postgresql.conf. (In versions
+ supporting ALTER SYSTEM, you can use that to make the
configuration change, but you'll still need a restart.)
- In each database of the cluster,
+ In each database of the cluster,
run the following commands as superuser:
SET search_path = pg_catalog;
@@ -294,15 +530,15 @@ CREATE OR REPLACE VIEW pg_user_mappings AS
- Do not forget to include the template0
- and template1 databases, or the vulnerability will still
- exist in databases you create later. To fix template0,
+ Do not forget to include the template0
+ and template1 databases, or the vulnerability will still
+ exist in databases you create later. To fix template0,
you'll need to temporarily make it accept connections.
- In PostgreSQL 9.5 and later, you can use
+ In PostgreSQL 9.5 and later, you can use
ALTER DATABASE template0 WITH ALLOW_CONNECTIONS true;
- and then after fixing template0, undo that with
+ and then after fixing template0, undo that with
ALTER DATABASE template0 WITH ALLOW_CONNECTIONS false;
@@ -316,7 +552,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Finally, remove the allow_system_table_mods configuration
+ Finally, remove the allow_system_table_mods configuration
setting, and again restart the postmaster.
@@ -330,16 +566,16 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- libpq ignores empty password specifications, and does
+ libpq 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 psql or other libpq-based
+ via psql or other libpq-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-libpq-based client,
+ However, with a modified or non-libpq-based client,
logging in could be possible, depending on which authentication
method is configured. In particular the most common
- method, md5, accepted empty passwords.
+ method, md5, accepted empty passwords.
Change the server to reject empty passwords in all cases.
(CVE-2017-7546)
@@ -347,13 +583,13 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Make lo_put() check for UPDATE privilege on
+ Make lo_put() check for UPDATE privilege on
the target large object (Tom Lane, Michael Paquier)
- lo_put() should surely require the same permissions
- as lowrite(), but the check was missing, allowing any
+ lo_put() should surely require the same permissions
+ as lowrite(), but the check was missing, allowing any
user to change the data in a large object.
(CVE-2017-7548)
@@ -460,21 +696,21 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Fix possible creation of an invalid WAL segment when a standby is
- promoted just after it processes an XLOG_SWITCH WAL
+ promoted just after it processes an XLOG_SWITCH WAL
record (Andres Freund)
- Fix walsender to exit promptly when client requests
+ Fix walsender to exit promptly when client requests
shutdown (Tom Lane)
- Fix SIGHUP and SIGUSR1 handling in
+ Fix SIGHUP and SIGUSR1 handling in
walsender processes (Petr Jelinek, Andres Freund)
@@ -488,7 +724,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix unnecessarily slow restarts of walreceiver
+ Fix unnecessarily slow restarts of walreceiver
processes due to race condition in postmaster (Tom Lane)
@@ -505,7 +741,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
Logical decoding crashed on tuples that are wider than 64KB (after
compression, but with all data in-line). The case arises only
- when REPLICA IDENTITY FULL is enabled for a table
+ when REPLICA IDENTITY FULL is enabled for a table
containing such tuples.
@@ -553,7 +789,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix cases where an INSERT or UPDATE assigns
+ Fix cases where an INSERT or UPDATE assigns
to more than one element of a column that is of domain-over-array
type (Tom Lane)
@@ -561,7 +797,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Allow window functions to be used in sub-SELECTs that
+ Allow window functions to be used in sub-SELECTs that
are within the arguments of an aggregate function (Tom Lane)
@@ -569,56 +805,56 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
Move autogenerated array types out of the way during
- ALTER ... RENAME (Vik Fearing)
+ ALTER ... RENAME (Vik Fearing)
Previously, we would rename a conflicting autogenerated array type
- out of the way during CREATE; this fix extends that
+ out of the way during CREATE; this fix extends that
behavior to renaming operations.
- Ensure that ALTER USER ... SET accepts all the syntax
- variants that ALTER ROLE ... SET does (Peter Eisentraut)
+ Ensure that ALTER USER ... SET accepts all the syntax
+ variants that ALTER ROLE ... SET does (Peter Eisentraut)
Properly update dependency info when changing a datatype I/O
- function's argument or return type from opaque to the
+ function's argument or return type from opaque to the
correct type (Heikki Linnakangas)
- CREATE TYPE updates I/O functions declared in this
+ CREATE TYPE updates I/O functions declared in this
long-obsolete style, but it forgot to record a dependency on the
- type, allowing a subsequent DROP TYPE to leave broken
+ type, allowing a subsequent DROP TYPE to leave broken
function definitions behind.
- Reduce memory usage when ANALYZE processes
- a tsvector column (Heikki Linnakangas)
+ Reduce memory usage when ANALYZE processes
+ a tsvector column (Heikki Linnakangas)
Fix unnecessary precision loss and sloppy rounding when multiplying
- or dividing money values by integers or floats (Tom Lane)
+ or dividing money values by integers or floats (Tom Lane)
Tighten checks for whitespace in functions that parse identifiers,
- such as regprocedurein() (Tom Lane)
+ such as regprocedurein() (Tom Lane)
@@ -629,20 +865,20 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Use relevant #define symbols from Perl while
- compiling PL/Perl (Ashutosh Sharma, Tom Lane)
+ Use relevant #define symbols from Perl while
+ compiling PL/Perl (Ashutosh Sharma, Tom Lane)
This avoids portability problems, typically manifesting as
- a handshake mismatch during library load, when working with
+ a handshake mismatch during library load, when working with
recent Perl versions.
- In libpq, reset GSS/SASL and SSPI authentication
+ In libpq, reset GSS/SASL and SSPI authentication
state properly after a failed connection attempt (Michael Paquier)
@@ -655,9 +891,9 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- In psql, fix failure when COPY FROM STDIN
+ In psql, fix failure when COPY FROM STDIN
is ended with a keyboard EOF signal and then another COPY
- FROM STDIN is attempted (Thomas Munro)
+ FROM STDIN is attempted (Thomas Munro)
@@ -668,8 +904,8 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix pg_dump and pg_restore to
- emit REFRESH MATERIALIZED VIEW commands last (Tom Lane)
+ Fix pg_dump and pg_restore to
+ emit REFRESH MATERIALIZED VIEW commands last (Tom Lane)
@@ -680,15 +916,15 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Improve pg_dump/pg_restore's
- reporting of error conditions originating in zlib
+ Improve pg_dump/pg_restore's
+ reporting of error conditions originating in zlib
(Vladimir Kunschikov, Álvaro Herrera)
- Fix pg_dump with the option to
drop event triggers as expected (Tom Lane)
@@ -701,14 +937,14 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix pg_dump to not emit invalid SQL for an empty
+ Fix pg_dump to not emit invalid SQL for an empty
operator class (Daniel Gustafsson)
- Fix pg_dump output to stdout on Windows (Kuntal Ghosh)
+ Fix pg_dump output to stdout on Windows (Kuntal Ghosh)
@@ -719,14 +955,14 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix pg_get_ruledef() to print correct output for
- the ON SELECT rule of a view whose columns have been
+ Fix pg_get_ruledef() to print correct output for
+ the ON SELECT rule of a view whose columns have been
renamed (Tom Lane)
- In some corner cases, pg_dump relies
- on pg_get_ruledef() to dump views, so that this error
+ In some corner cases, pg_dump relies
+ on pg_get_ruledef() to dump views, so that this error
could result in dump/reload failures.
@@ -734,13 +970,13 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
Fix dumping of outer joins with empty constraints, such as the result
- of a NATURAL LEFT JOIN with no common columns (Tom Lane)
+ of a NATURAL LEFT JOIN with no common columns (Tom Lane)
- Fix dumping of function expressions in the FROM clause in
+ Fix dumping of function expressions in the FROM clause in
cases where the expression does not deparse into something that looks
like a function call (Tom Lane)
@@ -748,7 +984,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix pg_basebackup output to stdout on Windows
+ Fix pg_basebackup output to stdout on Windows
(Haribabu Kommi)
@@ -760,8 +996,8 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix pg_upgrade to ensure that the ending WAL record
- does not have = minimum
+ Fix pg_upgrade to ensure that the ending WAL record
+ does not have = minimum
(Bruce Momjian)
@@ -773,9 +1009,9 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- In postgres_fdw, re-establish connections to remote
- servers after ALTER SERVER or ALTER USER
- MAPPING commands (Kyotaro Horiguchi)
+ In postgres_fdw, re-establish connections to remote
+ servers after ALTER SERVER or ALTER USER
+ MAPPING commands (Kyotaro Horiguchi)
@@ -786,7 +1022,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- In postgres_fdw, allow cancellation of remote
+ In postgres_fdw, allow cancellation of remote
transaction control commands (Robert Haas, Rafia Sabih)
@@ -798,14 +1034,14 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Increase MAX_SYSCACHE_CALLBACKS to provide more room for
+ Increase MAX_SYSCACHE_CALLBACKS to provide more room for
extensions (Tom Lane)
- Always use , not , when building
shared libraries with gcc (Tom Lane)
@@ -825,34 +1061,34 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- In MSVC builds, handle the case where the openssl
- library is not within a VC subdirectory (Andrew Dunstan)
+ In MSVC builds, handle the case where the openssl
+ library is not within a VC subdirectory (Andrew Dunstan)
- In MSVC builds, add proper include path for libxml2
+ In MSVC builds, add proper include path for libxml2
header files (Andrew Dunstan)
This fixes a former need to move things around in standard Windows
- installations of libxml2.
+ installations of libxml2.
In MSVC builds, recognize a Tcl library that is
- named tcl86.lib (Noah Misch)
+ named tcl86.lib (Noah Misch)
- In MSVC builds, honor PROVE_FLAGS settings
- on vcregress.pl's command line (Andrew Dunstan)
+ In MSVC builds, honor PROVE_FLAGS settings
+ on vcregress.pl's command line (Andrew Dunstan)
@@ -889,7 +1125,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
Also, if you are using third-party replication tools that depend
- on logical decoding, see the fourth changelog entry below.
+ on logical decoding, see the fourth changelog entry below.
@@ -906,18 +1142,18 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
Restrict visibility
- of pg_user_mappings.umoptions, to
+ of pg_user_mappings.umoptions, to
protect passwords stored as user mapping options
(Michael Paquier, Feike Steenbergen)
The previous coding allowed the owner of a foreign server object,
- or anyone he has granted server USAGE permission to,
+ or anyone he has granted server USAGE 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
- information_schema.user_mapping_options, namely that
+ information_schema.user_mapping_options, namely that
these options are visible to the user being mapped, or if the mapping
is for PUBLIC and the current user is the server
owner, or if the current user is a superuser.
@@ -941,7 +1177,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
Some selectivity estimation functions in the planner will apply
user-defined operators to values obtained
- from pg_statistic, such as most common values and
+ from pg_statistic, such as most common values and
histogram entries. This occurs before table permissions are checked,
so a nefarious user could exploit the behavior to obtain these values
for table columns he does not have permission to read. To fix,
@@ -955,17 +1191,17 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Restore libpq's recognition of
- the PGREQUIRESSL environment variable (Daniel Gustafsson)
+ Restore libpq's recognition of
+ the PGREQUIRESSL environment variable (Daniel Gustafsson)
Processing of this environment variable was unintentionally dropped
- in PostgreSQL 9.3, but its documentation remained.
+ in PostgreSQL 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 PGSSLMODE, to avoid
+ but give it lower priority than PGSSLMODE, to avoid
breaking configurations that work correctly with post-9.3 code.
(CVE-2017-7485)
@@ -996,7 +1232,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix possible corruption of init forks of unlogged indexes
+ Fix possible corruption of init forks of unlogged indexes
(Robert Haas, Michael Paquier)
@@ -1009,7 +1245,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix incorrect reconstruction of pg_subtrans entries
+ Fix incorrect reconstruction of pg_subtrans entries
when a standby server replays a prepared but uncommitted two-phase
transaction (Tom Lane)
@@ -1017,21 +1253,21 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
In most cases this turned out to have no visible ill effects, but in
corner cases it could result in circular references
- in pg_subtrans, potentially causing infinite loops
+ in pg_subtrans, potentially causing infinite loops
in queries that examine rows modified by the two-phase transaction.
- Avoid possible crash in walsender due to failure
+ Avoid possible crash in walsender due to failure
to initialize a string buffer (Stas Kelvich, Fujii Masao)
- Fix postmaster's handling of fork() failure for a
+ Fix postmaster's handling of fork() failure for a
background worker process (Tom Lane)
@@ -1052,19 +1288,19 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
Due to lack of a cache flush step between commands in an extension
script file, non-utility queries might not see the effects of an
immediately preceding catalog change, such as ALTER TABLE
- ... RENAME.
+ ... RENAME.
Skip tablespace privilege checks when ALTER TABLE ... ALTER
- COLUMN TYPE rebuilds an existing index (Noah Misch)
+ COLUMN TYPE rebuilds an existing index (Noah Misch)
The command failed if the calling user did not currently have
- CREATE privilege for the tablespace containing the index.
+ CREATE privilege for the tablespace containing the index.
That behavior seems unhelpful, so skip the check, allowing the
index to be rebuilt where it is.
@@ -1072,27 +1308,27 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse
- to child tables when the constraint is marked NO INHERIT
+ Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse
+ to child tables when the constraint is marked NO INHERIT
(Amit Langote)
- This fix prevents unwanted constraint does not exist failures
+ This fix prevents unwanted constraint does not exist failures
when no matching constraint is present in the child tables.
- Fix VACUUM to account properly for pages that could not
+ Fix VACUUM to account properly for pages that could not
be scanned due to conflicting page pins (Andrew Gierth)
This tended to lead to underestimation of the number of tuples in
the table. In the worst case of a small heavily-contended
- table, VACUUM could incorrectly report that the table
+ table, VACUUM could incorrectly report that the table
contained no tuples, leading to very bad planning choices.
@@ -1106,12 +1342,12 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix integer-overflow problems in interval comparison (Kyotaro
+ Fix integer-overflow problems in interval comparison (Kyotaro
Horiguchi, Tom Lane)
- The comparison operators for type interval could yield wrong
+ The comparison operators for type interval could yield wrong
answers for intervals larger than about 296000 years. Indexes on
columns containing such large values should be reindexed, since they
may be corrupt.
@@ -1120,21 +1356,21 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix cursor_to_xml() to produce valid output
- with tableforest = false
+ Fix cursor_to_xml() to produce valid output
+ with tableforest = false
(Thomas Munro, Peter Eisentraut)
- Previously it failed to produce a wrapping <table>
+ Previously it failed to produce a wrapping <table>
element.
- Fix roundoff problems in float8_timestamptz()
- and make_interval() (Tom Lane)
+ Fix roundoff problems in float8_timestamptz()
+ and make_interval() (Tom Lane)
@@ -1146,7 +1382,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Improve performance of pg_timezone_names view
+ Improve performance of pg_timezone_names view
(Tom Lane, David Rowley)
@@ -1160,13 +1396,13 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix sloppy handling of corner-case errors from lseek()
- and close() (Tom Lane)
+ Fix sloppy handling of corner-case errors from lseek()
+ and close() (Tom Lane)
Neither of these system calls are likely to fail in typical situations,
- but if they did, fd.c could get quite confused.
+ but if they did, fd.c could get quite confused.
@@ -1184,21 +1420,21 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Fix ecpg to support COMMIT PREPARED
- and ROLLBACK PREPARED (Masahiko Sawada)
+ Fix ecpg to support COMMIT PREPARED
+ and ROLLBACK PREPARED (Masahiko Sawada)
Fix a double-free error when processing dollar-quoted string literals
- in ecpg (Michael Meskes)
+ in ecpg (Michael Meskes)
- In pg_dump, fix incorrect schema and owner marking for
+ In pg_dump, fix incorrect schema and owner marking for
comments and security labels of some types of database objects
(Giuseppe Broccolo, Tom Lane)
@@ -1213,20 +1449,20 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- Avoid emitting an invalid list file in pg_restore -l
+ Avoid emitting an invalid list file in pg_restore -l
when SQL object names contain newlines (Tom Lane)
Replace newlines by spaces, which is sufficient to make the output
- valid for pg_restore -L's purposes.
+ valid for pg_restore -L's purposes.
- Fix pg_upgrade to transfer comments and security labels
- attached to large objects (blobs) (Stephen Frost)
+ Fix pg_upgrade to transfer comments and security labels
+ attached to large objects (blobs) (Stephen Frost)
@@ -1238,26 +1474,26 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
Improve error handling
- in contrib/adminpack's pg_file_write()
+ in contrib/adminpack's pg_file_write()
function (Noah Misch)
Notably, it failed to detect errors reported
- by fclose().
+ by fclose().
- In contrib/dblink, avoid leaking the previous unnamed
+ In contrib/dblink, avoid leaking the previous unnamed
connection when establishing a new unnamed connection (Joe Conway)
- Fix contrib/pg_trgm's extraction of trigrams from regular
+ Fix contrib/pg_trgm's extraction of trigrams from regular
expressions (Tom Lane)
@@ -1270,7 +1506,7 @@ Branch: REL9_4_STABLE [23a2b818f] 2017-08-05 14:56:40 -0700
- In contrib/postgres_fdw,
+ In contrib/postgres_fdw,
transmit query cancellation requests to the remote server
(Michael Paquier, Etsuro Fujita)
@@ -1320,7 +1556,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Update time zone data files to tzdata release 2017b
+ Update time zone data files to tzdata release 2017b
for DST law changes in Chile, Haiti, and Mongolia, plus historical
corrections for Ecuador, Kazakhstan, Liberia, and Spain.
Switch to numeric abbreviations for numerous time zones in South
@@ -1334,9 +1570,9 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
or no currency among the local population. They are in process of
reversing that policy in favor of using numeric UTC offsets in zones
where there is no evidence of real-world use of an English
- abbreviation. At least for the time being, PostgreSQL
+ abbreviation. At least for the time being, PostgreSQL
will continue to accept such removed abbreviations for timestamp input.
- But they will not be shown in the pg_timezone_names
+ But they will not be shown in the pg_timezone_names
view nor used for output.
@@ -1349,15 +1585,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
The Microsoft MSVC build scripts neglected to install
- the posixrules file in the timezone directory tree.
+ the posixrules 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 US/Eastern zone. If you don't want that, remove
- the posixrules file, or replace it with a copy of some
+ the US/Eastern zone. If you don't want that, remove
+ the posixrules file, or replace it with a copy of some
other zone file (see ). Note that
due to caching, you may need to restart the server to get such changes
to take effect.
@@ -1410,15 +1646,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
Fix a race condition that could cause indexes built
- with CREATE INDEX CONCURRENTLY to be corrupt
+ with CREATE INDEX CONCURRENTLY to be corrupt
(Pavan Deolasee, Tom Lane)
- If CREATE INDEX CONCURRENTLY was used to build an index
+ If CREATE INDEX CONCURRENTLY was used to build an index
that depends on a column not previously indexed, then rows
updated by transactions that ran concurrently with
- the CREATE INDEX command could have received incorrect
+ the CREATE INDEX command could have received incorrect
index entries. If you suspect this may have happened, the most
reliable solution is to rebuild affected indexes after installing
this update.
@@ -1435,19 +1671,19 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
Backends failed to account for this snapshot when advertising their
oldest xmin, potentially allowing concurrent vacuuming operations to
remove data that was still needed. This led to transient failures
- along the lines of cache lookup failed for relation 1255.
+ along the lines of cache lookup failed for relation 1255.
- Unconditionally WAL-log creation of the init fork for an
+ Unconditionally WAL-log creation of the init fork for an
unlogged table (Michael Paquier)
Previously, this was skipped when
- = minimal, but actually it's necessary even in that case
+ = minimal, but actually it's necessary even in that case
to ensure that the unlogged table is properly reset to empty after a
crash.
@@ -1513,7 +1749,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Make sure ALTER TABLE preserves index tablespace
+ Make sure ALTER TABLE preserves index tablespace
assignments when rebuilding indexes (Tom Lane, Michael Paquier)
@@ -1528,7 +1764,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
Fix incorrect updating of trigger function properties when changing a
foreign-key constraint's deferrability properties with ALTER
- TABLE ... ALTER CONSTRAINT (Tom Lane)
+ TABLE ... ALTER CONSTRAINT (Tom Lane)
@@ -1544,15 +1780,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- This avoids could not find trigger NNN
- or relation NNN has no triggers errors.
+ This avoids could not find trigger NNN
+ or relation NNN has no triggers errors.
Fix processing of OID column when a table with OIDs is associated to
- a parent with OIDs via ALTER TABLE ... INHERIT (Amit
+ a parent with OIDs via ALTER TABLE ... INHERIT (Amit
Langote)
@@ -1565,7 +1801,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Fix CREATE OR REPLACE VIEW to update the view query
+ Fix CREATE OR REPLACE VIEW to update the view query
before attempting to apply the new view options (Dean Rasheed)
@@ -1578,7 +1814,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
Report correct object identity during ALTER TEXT SEARCH
- CONFIGURATION (Artur Zakirov)
+ CONFIGURATION (Artur Zakirov)
@@ -1608,13 +1844,13 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Prevent multicolumn expansion of foo.* in
- an UPDATE source expression (Tom Lane)
+ Prevent multicolumn expansion of foo.* in
+ an UPDATE source expression (Tom Lane)
This led to UPDATE target count mismatch --- internal
- error. Now the syntax is understood as a whole-row variable,
+ error. Now the syntax is understood as a whole-row variable,
as it would be in other contexts.
@@ -1622,12 +1858,12 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
Ensure that column typmods are determined accurately for
- multi-row VALUES constructs (Tom Lane)
+ multi-row VALUES constructs (Tom Lane)
This fixes problems occurring when the first value in a column has a
- determinable typmod (e.g., length for a varchar value) but
+ determinable typmod (e.g., length for a varchar value) but
later values don't share the same limit.
@@ -1642,15 +1878,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
Normally, a Unicode surrogate leading character must be followed by a
Unicode surrogate trailing character, but the check for this was
missed if the leading character was the last character in a Unicode
- string literal (U&'...') or Unicode identifier
- (U&"...").
+ string literal (U&'...') or Unicode identifier
+ (U&"...").
Ensure that a purely negative text search query, such
- as !foo, matches empty tsvectors (Tom Dunstan)
+ as !foo, matches empty tsvectors (Tom Dunstan)
@@ -1661,33 +1897,33 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Prevent crash when ts_rewrite() replaces a non-top-level
+ Prevent crash when ts_rewrite() replaces a non-top-level
subtree with an empty query (Artur Zakirov)
- Fix performance problems in ts_rewrite() (Tom Lane)
+ Fix performance problems in ts_rewrite() (Tom Lane)
- Fix ts_rewrite()'s handling of nested NOT operators
+ Fix ts_rewrite()'s handling of nested NOT operators
(Tom Lane)
- Fix array_fill() to handle empty arrays properly (Tom Lane)
+ Fix array_fill() to handle empty arrays properly (Tom Lane)
- Fix one-byte buffer overrun in quote_literal_cstr()
+ Fix one-byte buffer overrun in quote_literal_cstr()
(Heikki Linnakangas)
@@ -1699,8 +1935,8 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Prevent multiple calls of pg_start_backup()
- and pg_stop_backup() from running concurrently (Michael
+ Prevent multiple calls of pg_start_backup()
+ and pg_stop_backup() from running concurrently (Michael
Paquier)
@@ -1712,15 +1948,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Avoid discarding interval-to-interval casts
+ Avoid discarding interval-to-interval casts
that aren't really no-ops (Tom Lane)
In some cases, a cast that should result in zeroing out
- low-order interval fields was mistakenly deemed to be a
+ low-order interval fields was mistakenly deemed to be a
no-op and discarded. An example is that casting from INTERVAL
- MONTH to INTERVAL YEAR failed to clear the months field.
+ MONTH to INTERVAL YEAR failed to clear the months field.
@@ -1733,28 +1969,28 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Fix pg_dump to dump user-defined casts and transforms
+ Fix pg_dump to dump user-defined casts and transforms
that use built-in functions (Stephen Frost)
- Fix pg_restore with
to behave more sanely if an archive contains
- unrecognized DROP commands (Tom Lane)
+ unrecognized DROP commands (Tom Lane)
This doesn't fix any live bug, but it may improve the behavior in
- future if pg_restore is used with an archive
- generated by a later pg_dump version.
+ future if pg_restore is used with an archive
+ generated by a later pg_dump version.
- Fix pg_basebackup's rate limiting in the presence of
+ Fix pg_basebackup's rate limiting in the presence of
slow I/O (Antonin Houska)
@@ -1767,15 +2003,15 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Fix pg_basebackup's handling of
- symlinked pg_stat_tmp and pg_replslot
+ Fix pg_basebackup's handling of
+ symlinked pg_stat_tmp and pg_replslot
subdirectories (Magnus Hagander, Michael Paquier)
- Fix possible pg_basebackup failure on standby
+ Fix possible pg_basebackup failure on standby
server when including WAL files (Amit Kapila, Robert Haas)
@@ -1794,21 +2030,21 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Fix PL/Tcl to support triggers on tables that have .tupno
+ Fix PL/Tcl to support triggers on tables that have .tupno
as a column name (Tom Lane)
This matches the (previously undocumented) behavior of
- PL/Tcl's spi_exec and spi_execp commands,
- namely that a magic .tupno column is inserted only if
+ PL/Tcl's spi_exec and spi_execp commands,
+ namely that a magic .tupno column is inserted only if
there isn't a real column named that.
- Allow DOS-style line endings in ~/.pgpass files,
+ Allow DOS-style line endings in ~/.pgpass files,
even on Unix (Vik Fearing)
@@ -1820,23 +2056,23 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Fix one-byte buffer overrun if ecpg is given a file
+ Fix one-byte buffer overrun if ecpg is given a file
name that ends with a dot (Takayuki Tsunakawa)
- Fix psql's tab completion for ALTER DEFAULT
- PRIVILEGES (Gilles Darold, Stephen Frost)
+ Fix psql's tab completion for ALTER DEFAULT
+ PRIVILEGES (Gilles Darold, Stephen Frost)
- In psql, treat an empty or all-blank setting of
- the PAGER environment variable as meaning no
- pager (Tom Lane)
+ In psql, treat an empty or all-blank setting of
+ the PAGER environment variable as meaning no
+ pager (Tom Lane)
@@ -1847,22 +2083,22 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Improve contrib/dblink's reporting of
- low-level libpq errors, such as out-of-memory
+ Improve contrib/dblink's reporting of
+ low-level libpq errors, such as out-of-memory
(Joe Conway)
- Teach contrib/dblink to ignore irrelevant server options
- when it uses a contrib/postgres_fdw foreign server as
+ Teach contrib/dblink to ignore irrelevant server options
+ when it uses a contrib/postgres_fdw foreign server as
the source of connection options (Corey Huinker)
Previously, if the foreign server object had options that were not
- also libpq connection options, an error occurred.
+ also libpq connection options, an error occurred.
@@ -1888,7 +2124,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Update time zone data files to tzdata release 2016j
+ Update time zone data files to tzdata release 2016j
for DST law changes in northern Cyprus (adding a new zone
Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga,
and Antarctica/Casey.
@@ -1951,7 +2187,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
crash recovery, or to be written incorrectly on a standby server.
Bogus entries in a free space map could lead to attempts to access
pages that have been truncated away from the relation itself, typically
- producing errors like could not read block XXX:
+ producing errors like could not read block XXX:
read only 0 of 8192 bytes. Checksum failures in the
visibility map are also possible, if checksumming is enabled.
@@ -1959,7 +2195,7 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
Procedures for determining whether there is a problem and repairing it
if so are discussed at
- .
+ .
@@ -1970,20 +2206,20 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- The typical symptom was unexpected GIN leaf action errors
+ The typical symptom was unexpected GIN leaf action errors
during WAL replay.
- Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that
+ Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that
have been updated by a subsequently-aborted transaction
(Álvaro Herrera)
- In 9.5 and later, the SELECT would sometimes fail to
+ In 9.5 and later, the SELECT 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.
@@ -2017,79 +2253,79 @@ Branch: REL9_2_STABLE [fb50c38e9] 2017-04-17 13:52:42 -0400
- Fix query-lifespan memory leak in a bulk UPDATE on a table
- with a PRIMARY KEY or REPLICA IDENTITY index
+ Fix query-lifespan memory leak in a bulk UPDATE on a table
+ with a PRIMARY KEY or REPLICA IDENTITY index
(Tom Lane)
- Fix EXPLAIN to emit valid XML when
+ Fix EXPLAIN to emit valid XML when
is on (Markus Winand)
Previously the XML output-format option produced syntactically invalid
- tags such as <I/O-Read-Time>. That is now
- rendered as <I-O-Read-Time>.
+ tags such as <I/O-Read-Time>. That is now
+ rendered as <I-O-Read-Time>.
Suppress printing of zeroes for unmeasured times
- in EXPLAIN (Maksim Milyutin)
+ in EXPLAIN (Maksim Milyutin)
Certain option combinations resulted in printing zero values for times
that actually aren't ever measured in that combination. Our general
- policy in EXPLAIN is not to print such fields at all, so
+ policy in EXPLAIN is not to print such fields at all, so
do that consistently in all cases.
- Fix timeout length when VACUUM is waiting for exclusive
+ Fix timeout length when VACUUM is waiting for exclusive
table lock so that it can truncate the table (Simon Riggs)
The timeout was meant to be 50 milliseconds, but it was actually only
- 50 microseconds, causing VACUUM to give up on truncation
+ 50 microseconds, causing VACUUM to give up on truncation
much more easily than intended. Set it to the intended value.
- Fix bugs in merging inherited CHECK constraints while
+ Fix bugs in merging inherited CHECK constraints while
creating or altering a table (Tom Lane, Amit Langote)
- Allow identical CHECK constraints to be added to a parent
+ Allow identical CHECK 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 NOT VALID
+ constraint from the parent table with a NOT VALID
constraint on the child. Likewise, prevent merging of a NO
- INHERIT child constraint with an inherited constraint.
+ INHERIT child constraint with an inherited constraint.
Remove artificial restrictions on the values accepted
- by numeric_in() and numeric_recv()
+ by numeric_in() and numeric_recv()
(Tom Lane)
We allow numeric values up to the limit of the storage format (more
- than 1e100000), so it seems fairly pointless
- that numeric_in() rejected scientific-notation exponents
- above 1000. Likewise, it was silly for numeric_recv() to
+ than 1e100000), so it seems fairly pointless
+ that numeric_in() rejected scientific-notation exponents
+ above 1000. Likewise, it was silly for numeric_recv() to
reject more than 1000 digits in an input value.
@@ -2134,7 +2370,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- Disallow starting a standalone backend with standby_mode
+ Disallow starting a standalone backend with standby_mode
turned on (Michael Paquier)
@@ -2153,7 +2389,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
This failure to reset all of the fields of the slot could
- prevent VACUUM from removing dead tuples.
+ prevent VACUUM from removing dead tuples.
@@ -2164,7 +2400,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- This avoids possible failures during munmap() on systems
+ This avoids possible failures during munmap() on systems
with atypical default huge page sizes. Except in crash-recovery
cases, there were no ill effects other than a log message.
@@ -2178,7 +2414,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
Previously, the same value would be chosen every time, because it was
- derived from random() but srandom() had not
+ derived from random() but srandom() had not
yet been called. While relatively harmless, this was not the intended
behavior.
@@ -2191,8 +2427,8 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- Windows sometimes returns ERROR_ACCESS_DENIED rather
- than ERROR_ALREADY_EXISTS when there is an existing
+ Windows sometimes returns ERROR_ACCESS_DENIED rather
+ than ERROR_ALREADY_EXISTS when there is an existing
segment. This led to postmaster startup failure due to believing that
the former was an unrecoverable error.
@@ -2201,7 +2437,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
Don't try to share SSL contexts across multiple connections
- in libpq (Heikki Linnakangas)
+ in libpq (Heikki Linnakangas)
@@ -2212,30 +2448,30 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- Avoid corner-case memory leak in libpq (Tom Lane)
+ Avoid corner-case memory leak in libpq (Tom Lane)
The reported problem involved leaking an error report
- during PQreset(), but there might be related cases.
+ during PQreset(), but there might be related cases.
- Make ecpg's and
options work consistently with our other executables (Haribabu Kommi)
- Fix pgbench's calculation of average latency
+ Fix pgbench's calculation of average latency
(Fabien Coelho)
- The calculation was incorrect when there were \sleep
+ The calculation was incorrect when there were \sleep
commands in the script, or when the test duration was specified in
number of transactions rather than total time.
@@ -2243,12 +2479,12 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- In pg_dump, never dump range constructor functions
+ In pg_dump, never dump range constructor functions
(Tom Lane)
- This oversight led to pg_upgrade failures with
+ This oversight led to pg_upgrade failures with
extensions containing range types, due to duplicate creation of the
constructor functions.
@@ -2256,8 +2492,8 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- In pg_xlogdump, retry opening new WAL segments when
- using option (Magnus Hagander)
@@ -2268,7 +2504,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- Fix pg_xlogdump to cope with a WAL file that begins
+ Fix pg_xlogdump to cope with a WAL file that begins
with a continuation record spanning more than one page (Pavan
Deolasee)
@@ -2276,15 +2512,15 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- Fix contrib/pg_buffercache to work
- when shared_buffers exceeds 256GB (KaiGai Kohei)
+ Fix contrib/pg_buffercache to work
+ when shared_buffers exceeds 256GB (KaiGai Kohei)
- Fix contrib/intarray/bench/bench.pl to print the results
- of the EXPLAIN it does when given the option
(Daniel Gustafsson)
@@ -2296,17 +2532,17 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- When PostgreSQL has been configured
- with
- In MSVC builds, include pg_recvlogical in a
+ In MSVC builds, include pg_recvlogical in a
client-only installation (MauMau)
@@ -2327,17 +2563,17 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
If a dynamic time zone abbreviation does not match any entry in the
referenced time zone, treat it as equivalent to the time zone name.
This avoids unexpected failures when IANA removes abbreviations from
- their time zone database, as they did in tzdata
+ their time zone database, as they did in tzdata
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 pg_timezone_abbrevs view to fail altogether.
+ the pg_timezone_abbrevs view to fail altogether.
- Update time zone data files to tzdata release 2016h
+ Update time zone data files to tzdata release 2016h
for DST law changes in Palestine and Turkey, plus historical
corrections for Turkey and some regions of Russia.
Switch to numeric abbreviations for some time zones in Antarctica,
@@ -2350,15 +2586,15 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
or no currency among the local population. They are in process of
reversing that policy in favor of using numeric UTC offsets in zones
where there is no evidence of real-world use of an English
- abbreviation. At least for the time being, PostgreSQL
+ abbreviation. At least for the time being, PostgreSQL
will continue to accept such removed abbreviations for timestamp input.
- But they will not be shown in the pg_timezone_names
+ But they will not be shown in the pg_timezone_names
view nor used for output.
- In this update, AMT is no longer shown as being in use to
- mean Armenia Time. Therefore, we have changed the Default
+ In this update, AMT is no longer shown as being in use to
+ mean Armenia Time. Therefore, we have changed the Default
abbreviation set to interpret it as Amazon Time, thus UTC-4 not UTC+4.
@@ -2403,17 +2639,17 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
Fix possible mis-evaluation of
- nested CASE-WHEN expressions (Heikki
+ nested CASE-WHEN expressions (Heikki
Linnakangas, Michael Paquier, Tom Lane)
- A CASE expression appearing within the test value
- subexpression of another CASE could become confused about
+ A CASE expression appearing within the test value
+ subexpression of another CASE 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 CASE expression could result in passing the wrong test
- value to functions called within a CASE expression in the
+ a CASE expression could result in passing the wrong test
+ value to functions called within a CASE expression in the
SQL function's body. If the test values were of different data
types, a crash might result; moreover such situations could be abused
to allow disclosure of portions of server memory. (CVE-2016-5423)
@@ -2427,7 +2663,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- Numerous places in vacuumdb and other client programs
+ Numerous places in vacuumdb and other client programs
could become confused by database and role names containing double
quotes or backslashes. Tighten up quoting rules to make that safe.
Also, ensure that when a conninfo string is used as a database name
@@ -2436,22 +2672,22 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
Fix handling of paired double quotes
- in psql's \connect
- and \password commands to match the documentation.
+ in psql's \connect
+ and \password commands to match the documentation.
- Introduce a new
- pg_dumpall now refuses to deal with database and role
+ pg_dumpall now refuses to deal with database and role
names containing carriage returns or newlines, as it seems impractical
to quote those characters safely on Windows. In future we may reject
such names on the server side, but that step has not been taken yet.
@@ -2461,40 +2697,40 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
These are considered security fixes because crafted object names
containing special characters could have been used to execute
commands with superuser privileges the next time a superuser
- executes pg_dumpall or other routine maintenance
+ executes pg_dumpall or other routine maintenance
operations. (CVE-2016-5424)
- Fix corner-case misbehaviors for IS NULL/IS NOT
- NULL applied to nested composite values (Andrew Gierth, Tom Lane)
+ Fix corner-case misbehaviors for IS NULL/IS NOT
+ NULL applied to nested composite values (Andrew Gierth, Tom Lane)
- The SQL standard specifies that IS NULL should return
+ The SQL standard specifies that IS NULL should return
TRUE for a row of all null values (thus ROW(NULL,NULL) IS
- NULL yields TRUE), but this is not meant to apply recursively
- (thus ROW(NULL, ROW(NULL,NULL)) IS NULL yields FALSE).
+ NULL yields TRUE), but this is not meant to apply recursively
+ (thus ROW(NULL, ROW(NULL,NULL)) IS NULL yields FALSE).
The core executor got this right, but certain planner optimizations
treated the test as recursive (thus producing TRUE in both cases),
- and contrib/postgres_fdw could produce remote queries
+ and contrib/postgres_fdw could produce remote queries
that misbehaved similarly.
- Make the inet and cidr data types properly reject
+ Make the inet and cidr data types properly reject
IPv6 addresses with too many colon-separated fields (Tom Lane)
- Prevent crash in close_ps()
- (the point ## lseg operator)
+ Prevent crash in close_ps()
+ (the point##lseg operator)
for NaN input coordinates (Tom Lane)
@@ -2505,19 +2741,19 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- Avoid possible crash in pg_get_expr() when inconsistent
+ Avoid possible crash in pg_get_expr() when inconsistent
values are passed to it (Michael Paquier, Thomas Munro)
- Fix several one-byte buffer over-reads in to_number()
+ Fix several one-byte buffer over-reads in to_number()
(Peter Eisentraut)
- In several cases the to_number() function would read one
+ In several cases the to_number() function would read one
more character than it should from the input string. There is a
small chance of a crash, if the input happens to be adjacent to the
end of memory.
@@ -2527,8 +2763,8 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
Do not run the planner on the query contained in CREATE
- MATERIALIZED VIEW or CREATE TABLE AS
- when WITH NO DATA is specified (Michael Paquier,
+ MATERIALIZED VIEW or CREATE TABLE AS
+ when WITH NO DATA is specified (Michael Paquier,
Tom Lane)
@@ -2542,7 +2778,7 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
Avoid unsafe intermediate state during expensive paths
- through heap_update() (Masahiko Sawada, Andres Freund)
+ through heap_update() (Masahiko Sawada, Andres Freund)
@@ -2568,15 +2804,15 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- Avoid unnecessary could not serialize access errors when
- acquiring FOR KEY SHARE row locks in serializable mode
+ Avoid unnecessary could not serialize access errors when
+ acquiring FOR KEY SHARE row locks in serializable mode
(Álvaro Herrera)
- Avoid crash in postgres -C when the specified variable
+ Avoid crash in postgres -C when the specified variable
has a null string value (Michael Paquier)
@@ -2619,12 +2855,12 @@ Branch: REL9_4_STABLE [10ad15f48] 2016-09-01 11:45:16 -0400
- Avoid consuming a transaction ID during VACUUM
+ Avoid consuming a transaction ID during VACUUM
(Alexander Korotkov)
- Some cases in VACUUM unnecessarily caused an XID to be
+ Some cases in VACUUM unnecessarily caused an XID to be
assigned to the current transaction. Normally this is negligible,
but if one is up against the XID wraparound limit, consuming more
XIDs during anti-wraparound vacuums is a very bad thing.
@@ -2640,12 +2876,12 @@ Branch: REL9_2_STABLE [294509ea9] 2016-05-25 19:39:49 -0400
Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
-->
- Avoid canceling hot-standby queries during VACUUM FREEZE
+ Avoid canceling hot-standby queries during VACUUM FREEZE
(Simon Riggs, Álvaro Herrera)
- VACUUM FREEZE on an otherwise-idle master server could
+ VACUUM FREEZE on an otherwise-idle master server could
result in unnecessary cancellations of queries on its standby
servers.
@@ -2660,15 +2896,15 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
The usual symptom of this bug is errors
- like MultiXactId NNN has not been created
+ like MultiXactId NNN has not been created
yet -- apparent wraparound.
- When a manual ANALYZE specifies a column list, don't
- reset the table's changes_since_analyze counter
+ When a manual ANALYZE specifies a column list, don't
+ reset the table's changes_since_analyze counter
(Tom Lane)
@@ -2680,7 +2916,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Fix ANALYZE's overestimation of n_distinct
+ Fix ANALYZE's overestimation of n_distinct
for a unique or nearly-unique column with many null entries (Tom
Lane)
@@ -2713,7 +2949,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- This mistake prevented VACUUM from completing in some
+ This mistake prevented VACUUM from completing in some
cases involving corrupt b-tree indexes.
@@ -2727,8 +2963,8 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Fix contrib/btree_gin to handle the smallest
- possible bigint value correctly (Peter Eisentraut)
+ Fix contrib/btree_gin to handle the smallest
+ possible bigint value correctly (Peter Eisentraut)
@@ -2741,53 +2977,53 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
It's planned to switch to two-part instead of three-part server
version numbers for releases after 9.6. Make sure
- that PQserverVersion() returns the correct value for
+ that PQserverVersion() returns the correct value for
such cases.
- Fix ecpg's code for unsigned long long
+ Fix ecpg's code for unsigned long long
array elements (Michael Meskes)
- In pg_dump with both
- Improve handling of SIGTERM/control-C in
- parallel pg_dump and pg_restore (Tom
+ Improve handling of SIGTERM/control-C in
+ parallel pg_dump and pg_restore (Tom
Lane)
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 CREATE INDEX.
+ are doing something long-running such as a CREATE INDEX.
- Fix error reporting in parallel pg_dump
- and pg_restore (Tom Lane)
+ Fix error reporting in parallel pg_dump
+ and pg_restore (Tom Lane)
- Previously, errors reported by pg_dump
- or pg_restore worker processes might never make it to
+ Previously, errors reported by pg_dump
+ or pg_restore 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 stderr. In some cases this will result in
+ everything to stderr. 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.
@@ -2795,8 +3031,8 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Ensure that parallel pg_dump
- or pg_restore on Windows will shut down properly
+ Ensure that parallel pg_dump
+ or pg_restore on Windows will shut down properly
after an error (Kyotaro Horiguchi)
@@ -2808,7 +3044,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Make pg_dump behave better when built without zlib
+ Make pg_dump behave better when built without zlib
support (Kyotaro Horiguchi)
@@ -2820,7 +3056,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Make pg_basebackup accept -Z 0 as
+ Make pg_basebackup accept -Z 0 as
specifying no compression (Fujii Masao)
@@ -2841,13 +3077,13 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Be more predictable about reporting statement timeout
- versus lock timeout (Tom Lane)
+ Be more predictable about reporting statement timeout
+ versus lock timeout (Tom Lane)
On heavily loaded machines, the regression tests sometimes failed due
- to reporting lock timeout even though the statement timeout
+ to reporting lock timeout even though the statement timeout
should have occurred first.
@@ -2867,7 +3103,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
Update our copy of the timezone code to match
- IANA's tzcode release 2016c (Tom Lane)
+ IANA's tzcode release 2016c (Tom Lane)
@@ -2879,7 +3115,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Update time zone data files to tzdata release 2016f
+ Update time zone data files to tzdata release 2016f
for DST law changes in Kemerovo and Novosibirsk, plus historical
corrections for Azerbaijan, Belarus, and Morocco.
@@ -2934,7 +3170,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
using OpenSSL within a single process and not all the code involved
follows the same rules for when to clear the error queue.
Failures have been reported specifically when a client application
- uses SSL connections in libpq concurrently with
+ uses SSL connections in libpq concurrently with
SSL connections using the PHP, Python, or Ruby wrappers for OpenSSL.
It's possible for similar problems to arise within the server as well,
if an extension module establishes an outgoing SSL connection.
@@ -2943,7 +3179,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Fix failed to build any N-way joins
+ Fix failed to build any N-way joins
planner error with a full join enclosed in the right-hand side of a
left join (Tom Lane)
@@ -2957,10 +3193,10 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
Given a three-or-more-way equivalence class of variables, such
- as X.X = Y.Y = Z.Z, it was possible for the planner to omit
+ as X.X = Y.Y = Z.Z, 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 WHERE clauses. For various reasons, erroneous plans
+ the WHERE clauses. For various reasons, erroneous plans
were seldom selected in practice, so that this bug has gone undetected
for a long time.
@@ -2981,14 +3217,14 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
The memory leak would typically not amount to much in simple queries,
but it could be very substantial during a large GIN index build with
- high maintenance_work_mem.
+ high maintenance_work_mem.
- Fix possible misbehavior of TH, th,
- and Y,YYY format codes in to_timestamp()
+ Fix possible misbehavior of TH, th,
+ and Y,YYY format codes in to_timestamp()
(Tom Lane)
@@ -3000,29 +3236,29 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Fix dumping of rules and views in which the array
- argument of a value operator
- ANY (array) construct is a sub-SELECT
+ Fix dumping of rules and views in which the array
+ argument of a valueoperator
+ ANY (array) construct is a sub-SELECT
(Tom Lane)
- Disallow newlines in ALTER SYSTEM parameter values
+ Disallow newlines in ALTER SYSTEM parameter values
(Tom Lane)
The configuration-file parser doesn't support embedded newlines in
string literals, so we mustn't allow them in values to be inserted
- by ALTER SYSTEM.
+ by ALTER SYSTEM.
- Fix ALTER TABLE ... REPLICA IDENTITY USING INDEX to
+ Fix ALTER TABLE ... REPLICA IDENTITY USING INDEX to
work properly if an index on OID is selected (David Rowley)
@@ -3048,19 +3284,19 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Make pg_regress use a startup timeout from the
- PGCTLTIMEOUT environment variable, if that's set (Tom Lane)
+ Make pg_regress use a startup timeout from the
+ PGCTLTIMEOUT environment variable, if that's set (Tom Lane)
This is for consistency with a behavior recently added
- to pg_ctl; it eases automated testing on slow machines.
+ to pg_ctl; it eases automated testing on slow machines.
- Fix pg_upgrade to correctly restore extension
+ Fix pg_upgrade to correctly restore extension
membership for operator families containing only one operator class
(Tom Lane)
@@ -3068,20 +3304,20 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
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 pg_dump
+ immediate ill effects, but would cause later pg_dump
runs to emit output that would cause (harmless) errors on restore.
- Fix pg_upgrade to not fail when new-cluster TOAST rules
+ Fix pg_upgrade to not fail when new-cluster TOAST rules
differ from old (Tom Lane)
- pg_upgrade had special-case code to handle the
- situation where the new PostgreSQL version thinks that
+ pg_upgrade had special-case code to handle the
+ situation where the new PostgreSQL version thinks that
a table should have a TOAST table while the old version did not. That
code was broken, so remove it, and instead do nothing in such cases;
there seems no reason to believe that we can't get along fine without
@@ -3092,22 +3328,22 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
Reduce the number of SysV semaphores used by a build configured with
- (Tom Lane)
- Rename internal function strtoi()
- to strtoint() to avoid conflict with a NetBSD library
+ Rename internal function strtoi()
+ to strtoint() to avoid conflict with a NetBSD library
function (Thomas Munro)
- Fix reporting of errors from bind()
- and listen() system calls on Windows (Tom Lane)
+ Fix reporting of errors from bind()
+ and listen() system calls on Windows (Tom Lane)
@@ -3120,19 +3356,19 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Fix putenv() to work properly with Visual Studio 2013
+ Fix putenv() to work properly with Visual Studio 2013
(Michael Paquier)
- Avoid possibly-unsafe use of Windows' FormatMessage()
+ Avoid possibly-unsafe use of Windows' FormatMessage()
function (Christian Ullrich)
- Use the FORMAT_MESSAGE_IGNORE_INSERTS flag where
+ Use the FORMAT_MESSAGE_IGNORE_INSERTS flag where
appropriate. No live bug is known to exist here, but it seems like a
good idea to be careful.
@@ -3140,9 +3376,9 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Update time zone data files to tzdata release 2016d
+ Update time zone data files to tzdata release 2016d
for DST law changes in Russia and Venezuela. There are new zone
- names Europe/Kirov and Asia/Tomsk to reflect
+ names Europe/Kirov and Asia/Tomsk to reflect
the fact that these regions now have different time zone histories from
adjacent regions.
@@ -3188,29 +3424,29 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
Fix incorrect handling of NULL index entries in
- indexed ROW() comparisons (Tom Lane)
+ indexed ROW() comparisons (Tom Lane)
An index search using a row comparison such as ROW(a, b) >
- ROW('x', 'y') would stop upon reaching a NULL entry in
- the b column, ignoring the fact that there might be
- non-NULL b values associated with later values
- of a.
+ ROW('x', 'y') would stop upon reaching a NULL entry in
+ the b column, ignoring the fact that there might be
+ non-NULL b values associated with later values
+ of a.
Avoid unlikely data-loss scenarios due to renaming files without
- adequate fsync() calls before and after (Michael Paquier,
+ adequate fsync() calls before and after (Michael Paquier,
Tomas Vondra, Andres Freund)
- Fix bug in json_to_record() when a field of its input
+ Fix bug in json_to_record() when a field of its input
object contains a sub-object with a field name matching one of the
requested output column names (Tom Lane)
@@ -3219,7 +3455,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
Fix misformatting of negative time zone offsets
- by to_char()'s OF format code
+ by to_char()'s OF format code
(Thomas Munro, Tom Lane)
@@ -3232,7 +3468,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
Previously, standby servers would delay application of WAL records in
- response to recovery_min_apply_delay even while replaying
+ response to recovery_min_apply_delay even while replaying
the initial portion of WAL needed to make their database state valid.
Since the standby is useless until it's reached a consistent database
state, this was deemed unhelpful.
@@ -3241,7 +3477,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Correctly handle cases where pg_subtrans is close to XID
+ Correctly handle cases where pg_subtrans is close to XID
wraparound during server startup (Jeff Janes)
@@ -3253,44 +3489,44 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
Trouble cases included tuples larger than one page when replica
- identity is FULL, UPDATEs that change a
+ identity is FULL, UPDATEs that change a
primary key within a transaction large enough to be spooled to disk,
incorrect reports of subxact logged without previous toplevel
- record, and incorrect reporting of a transaction's commit time.
+ record, and incorrect reporting of a transaction's commit time.
Fix planner error with nested security barrier views when the outer
- view has a WHERE clause containing a correlated subquery
+ view has a WHERE clause containing a correlated subquery
(Dean Rasheed)
- Fix corner-case crash due to trying to free localeconv()
+ Fix corner-case crash due to trying to free localeconv()
output strings more than once (Tom Lane)
- Fix parsing of affix files for ispell dictionaries
+ Fix parsing of affix files for ispell dictionaries
(Tom Lane)
The code could go wrong if the affix file contained any characters
whose byte length changes during case-folding, for
- example I in Turkish UTF8 locales.
+ example I in Turkish UTF8 locales.
- Avoid use of sscanf() to parse ispell
+ Avoid use of sscanf() to parse ispell
dictionary files (Artur Zakirov)
@@ -3316,27 +3552,27 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
- Fix psql's tab completion logic to handle multibyte
+ Fix psql's tab completion logic to handle multibyte
characters properly (Kyotaro Horiguchi, Robert Haas)
- Fix psql's tab completion for
- SECURITY LABEL (Tom Lane)
+ Fix psql's tab completion for
+ SECURITY LABEL (Tom Lane)
- Pressing TAB after SECURITY LABEL might cause a crash
+ Pressing TAB after SECURITY LABEL might cause a crash
or offering of inappropriate keywords.
- Make pg_ctl accept a wait timeout from the
- PGCTLTIMEOUT environment variable, if none is specified on
+ Make pg_ctl accept a wait timeout from the
+ PGCTLTIMEOUT environment variable, if none is specified on
the command line (Noah Misch)
@@ -3350,26 +3586,26 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
Fix incorrect test for Windows service status
- in pg_ctl (Manuel Mathar)
+ in pg_ctl (Manuel Mathar)
The previous set of minor releases attempted to
- fix pg_ctl to properly determine whether to send log
+ fix pg_ctl to properly determine whether to send log
messages to Window's Event Log, but got the test backwards.
- Fix pgbench to correctly handle the combination
- of -C and -M prepared options (Tom Lane)
+ Fix pgbench to correctly handle the combination
+ of -C and -M prepared options (Tom Lane)
- In pg_upgrade, skip creating a deletion script when
+ In pg_upgrade, skip creating a deletion script when
the new data directory is inside the old data directory (Bruce
Momjian)
@@ -3397,21 +3633,21 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
Fix multiple mistakes in the statistics returned
- by contrib/pgstattuple's pgstatindex()
+ by contrib/pgstattuple's pgstatindex()
function (Tom Lane)
- Remove dependency on psed in MSVC builds, since it's no
+ Remove dependency on psed in MSVC builds, since it's no
longer provided by core Perl (Michael Paquier, Andrew Dunstan)
- Update time zone data files to tzdata release 2016c
+ Update time zone data files to tzdata release 2016c
for DST law changes in Azerbaijan, Chile, Haiti, Palestine, and Russia
(Altai, Astrakhan, Kirov, Sakhalin, Ulyanovsk regions), plus
historical corrections for Lithuania, Moldova, and Russia
@@ -3447,7 +3683,7 @@ Branch: REL9_1_STABLE [de887cc8a] 2016-05-25 19:39:49 -0400
However, if you are upgrading an installation that contains any GIN
- indexes that use the (non-default) jsonb_path_ops operator
+ indexes that use the (non-default) jsonb_path_ops operator
class, see the first changelog entry below.
@@ -3471,19 +3707,19 @@ Branch: REL9_4_STABLE [788e35ac0] 2015-11-05 18:15:48 -0500
- Fix inconsistent hash calculations in jsonb_path_ops GIN
+ Fix inconsistent hash calculations in jsonb_path_ops GIN
indexes (Tom Lane)
- When processing jsonb values that contain both scalars and
+ When processing jsonb values that contain both scalars and
sub-objects at the same nesting level, for example an array containing
both scalars and sub-arrays, key hash values could be calculated
differently than they would be for the same key in a different context.
This could result in queries not finding entries that they should find.
Fixing this means that existing indexes may now be inconsistent with the
new hash calculation code. Users
- should REINDEX jsonb_path_ops GIN indexes after
+ should REINDEXjsonb_path_ops GIN indexes after
installing this update to make sure that all searches work as expected.
@@ -3513,18 +3749,18 @@ Branch: REL9_1_STABLE [dea6da132] 2015-10-06 17:15:27 -0400
- Perform an immediate shutdown if the postmaster.pid file
+ Perform an immediate shutdown if the postmaster.pid file
is removed (Tom Lane)
The postmaster now checks every minute or so
- that postmaster.pid is still there and still contains its
+ that postmaster.pid is still there and still contains its
own PID. If not, it performs an immediate shutdown, as though it had
- received SIGQUIT. The main motivation for this change
+ received SIGQUIT. 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 postmaster.pid and then starts a new
+ DBA forcibly removes postmaster.pid and then starts a new
postmaster.
@@ -3541,7 +3777,7 @@ Branch: REL9_1_STABLE [08322daed] 2015-10-31 14:36:58 -0500
- In SERIALIZABLE transaction isolation mode, serialization
+ In SERIALIZABLE transaction isolation mode, serialization
anomalies could be missed due to race conditions during insertions
(Kevin Grittner, Thomas Munro)
@@ -3560,7 +3796,7 @@ Branch: REL9_1_STABLE [5f9a86b35] 2015-12-12 14:19:29 +0100
Fix failure to emit appropriate WAL records when doing ALTER
- TABLE ... SET TABLESPACE for unlogged relations (Michael Paquier,
+ TABLE ... SET TABLESPACE for unlogged relations (Michael Paquier,
Andres Freund)
@@ -3614,7 +3850,7 @@ Branch: REL9_1_STABLE [60ba32cb5] 2015-11-20 14:55:29 -0500
- Fix ALTER COLUMN TYPE to reconstruct inherited check
+ Fix ALTER COLUMN TYPE to reconstruct inherited check
constraints properly (Tom Lane)
@@ -3629,7 +3865,7 @@ Branch: REL9_1_STABLE [7e29e7f55] 2015-12-21 19:49:15 -0300
- Fix REASSIGN OWNED to change ownership of composite types
+ Fix REASSIGN OWNED to change ownership of composite types
properly (Álvaro Herrera)
@@ -3644,7 +3880,7 @@ Branch: REL9_1_STABLE [ab14c1383] 2015-12-21 19:16:15 -0300
- Fix REASSIGN OWNED and ALTER OWNER to correctly
+ Fix REASSIGN OWNED and ALTER OWNER to correctly
update granted-permissions lists when changing owners of data types,
foreign data wrappers, or foreign servers (Bruce Momjian,
Álvaro Herrera)
@@ -3663,7 +3899,7 @@ Branch: REL9_1_STABLE [f44c5203b] 2015-12-11 18:39:09 -0300
- Fix REASSIGN OWNED to ignore foreign user mappings,
+ Fix REASSIGN OWNED to ignore foreign user mappings,
rather than fail (Álvaro Herrera)
@@ -3697,13 +3933,13 @@ Branch: REL9_3_STABLE [0a34ff7e9] 2015-12-07 17:41:45 -0500
- Fix planner's handling of LATERAL references (Tom
+ Fix planner's handling of LATERAL references (Tom
Lane)
This fixes some corner cases that led to failed to build any
- N-way joins or could not devise a query plan planner
+ N-way joins or could not devise a query plan planner
failures.
@@ -3753,9 +3989,9 @@ Branch: REL9_3_STABLE [faf18a905] 2015-11-16 13:45:17 -0500
- Speed up generation of unique table aliases in EXPLAIN and
+ Speed up generation of unique table aliases in EXPLAIN and
rule dumping, and ensure that generated aliases do not
- exceed NAMEDATALEN (Tom Lane)
+ exceed NAMEDATALEN (Tom Lane)
@@ -3771,8 +4007,8 @@ Branch: REL9_1_STABLE [7b21d1bca] 2015-11-15 14:41:09 -0500
- Fix dumping of whole-row Vars in ROW()
- and VALUES() lists (Tom Lane)
+ Fix dumping of whole-row Vars in ROW()
+ and VALUES() lists (Tom Lane)
@@ -3785,8 +4021,8 @@ Branch: REL9_4_STABLE [4f33572ee] 2015-10-20 11:06:24 -0700
- Translation of minus-infinity dates and timestamps to json
- or jsonb incorrectly rendered them as plus-infinity (Tom Lane)
+ Translation of minus-infinity dates and timestamps to json
+ or jsonb incorrectly rendered them as plus-infinity (Tom Lane)
@@ -3802,7 +4038,7 @@ Branch: REL9_1_STABLE [728a2ac21] 2015-11-17 15:47:12 -0500
- Fix possible internal overflow in numeric division
+ Fix possible internal overflow in numeric division
(Dean Rasheed)
@@ -3894,7 +4130,7 @@ Branch: REL9_1_STABLE [b94c2b6a6] 2015-10-16 15:36:17 -0400
This causes the code to emit regular expression is too
- complex errors in some cases that previously used unreasonable
+ complex errors in some cases that previously used unreasonable
amounts of time and memory.
@@ -3929,14 +4165,14 @@ Branch: REL9_1_STABLE [b00c79b5b] 2015-10-16 14:43:18 -0400
- Make %h and %r escapes
- in log_line_prefix work for messages emitted due
- to log_connections (Tom Lane)
+ Make %h and %r escapes
+ in log_line_prefix work for messages emitted due
+ to log_connections (Tom Lane)
- Previously, %h/%r started to work just after a
- new session had emitted the connection received log message;
+ Previously, %h/%r started to work just after a
+ new session had emitted the connection received log message;
now they work for that message too.
@@ -3959,7 +4195,7 @@ Branch: REL9_1_STABLE [b0d858359] 2015-10-13 11:21:33 -0400
This oversight resulted in failure to recover from crashes
- whenever logging_collector is turned on.
+ whenever logging_collector is turned on.
@@ -4009,13 +4245,13 @@ Branch: REL9_1_STABLE [db462a44e] 2015-12-17 16:55:51 -0500
- In psql, ensure that libreadline's idea
+ In psql, ensure that libreadline's idea
of the screen size is updated when the terminal window size changes
(Merlin Moncure)
- Previously, libreadline did not notice if the window
+ Previously, libreadline did not notice if the window
was resized during query output, leading to strange behavior during
later input of multiline queries.
@@ -4023,8 +4259,8 @@ Branch: REL9_1_STABLE [db462a44e] 2015-12-17 16:55:51 -0500
- Fix psql's \det command to interpret its
- pattern argument the same way as other \d commands with
+ Fix psql's \det command to interpret its
+ pattern argument the same way as other \d commands with
potentially schema-qualified patterns do (Reece Hart)
@@ -4041,7 +4277,7 @@ Branch: REL9_1_STABLE [6430a11fa] 2015-11-25 17:31:54 -0500
- Avoid possible crash in psql's \c command
+ Avoid possible crash in psql's \c command
when previous connection was via Unix socket and command specifies a
new hostname and same username (Tom Lane)
@@ -4059,21 +4295,21 @@ Branch: REL9_1_STABLE [c869a7d5b] 2015-10-12 18:30:37 -0400
- In pg_ctl start -w, test child process status directly
+ In pg_ctl start -w, test child process status directly
rather than relying on heuristics (Tom Lane, Michael Paquier)
- Previously, pg_ctl relied on an assumption that the new
- postmaster would always create postmaster.pid within five
+ Previously, pg_ctl relied on an assumption that the new
+ postmaster would always create postmaster.pid within five
seconds. But that can fail on heavily-loaded systems,
- causing pg_ctl to report incorrectly that the
+ causing pg_ctl to report incorrectly that the
postmaster failed to start.
Except on Windows, this change also means that a pg_ctl start
- -w done immediately after another such command will now reliably
+ -w 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.
@@ -4091,23 +4327,23 @@ Branch: REL9_1_STABLE [87deb55a4] 2015-11-08 17:31:24 -0500
- In pg_ctl start -w, don't attempt to use a wildcard listen
+ In pg_ctl start -w, don't attempt to use a wildcard listen
address to connect to the postmaster (Kondo Yuta)
- On Windows, pg_ctl would fail to detect postmaster
- startup if listen_addresses is set to 0.0.0.0
- or ::, because it would try to use that value verbatim as
+ On Windows, pg_ctl would fail to detect postmaster
+ startup if listen_addresses is set to 0.0.0.0
+ or ::, because it would try to use that value verbatim as
the address to connect to, which doesn't work. Instead assume
- that 127.0.0.1 or ::1, respectively, is the
+ that 127.0.0.1 or ::1, respectively, is the
right thing to use.
- In pg_ctl on Windows, check service status to decide
+ In pg_ctl on Windows, check service status to decide
where to send output, rather than checking if standard output is a
terminal (Michael Paquier)
@@ -4127,18 +4363,18 @@ Branch: REL9_1_STABLE [6df62ef43] 2015-11-23 00:32:01 -0500
- In pg_dump and pg_basebackup, adopt
+ In pg_dump and pg_basebackup, adopt
the GNU convention for handling tar-archive members exceeding 8GB
(Tom Lane)
- The POSIX standard for tar file format does not allow
+ The POSIX standard for tar file format does not allow
archive member files to exceed 8GB, but most modern implementations
- of tar support an extension that fixes that. Adopt
- this extension so that pg_dump with no
longer fails on tables with more than 8GB of data, and so
- that pg_basebackup can handle files larger than 8GB.
+ that pg_basebackup can handle files larger than 8GB.
In addition, fix some portability issues that could cause failures for
members between 4GB and 8GB on some platforms. Potentially these
problems could cause unrecoverable data loss due to unreadable backup
@@ -4148,16 +4384,16 @@ Branch: REL9_1_STABLE [6df62ef43] 2015-11-23 00:32:01 -0500
- Fix assorted corner-case bugs in pg_dump's processing
+ Fix assorted corner-case bugs in pg_dump's processing
of extension member objects (Tom Lane)
- Make pg_dump mark a view's triggers as needing to be
+ Make pg_dump mark a view's triggers as needing to be
processed after its rule, to prevent possible failure during
- parallel pg_restore (Tom Lane)
+ parallel pg_restore (Tom Lane)
@@ -4180,14 +4416,14 @@ Branch: REL9_1_STABLE [e4959fb5c] 2016-01-02 19:04:45 -0500
Ensure that relation option values are properly quoted
- in pg_dump (Kouhei Sutou, Tom Lane)
+ in pg_dump (Kouhei Sutou, Tom Lane)
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 pg_dump. This is not an issue with any
- reloption currently supported by core PostgreSQL, but
+ issued by pg_dump. This is not an issue with any
+ reloption currently supported by core PostgreSQL, but
extensions could allow reloptions that cause the problem.
@@ -4202,7 +4438,7 @@ Branch: REL9_3_STABLE [534a4159c] 2015-12-23 14:25:31 -0500
- Avoid repeated password prompts during parallel pg_dump
+ Avoid repeated password prompts during parallel pg_dump
(Zeus Kronion)
@@ -4225,14 +4461,14 @@ Branch: REL9_1_STABLE [c36064e43] 2015-11-24 17:18:27 -0500
- Fix pg_upgrade's file-copying code to handle errors
+ Fix pg_upgrade's file-copying code to handle errors
properly on Windows (Bruce Momjian)
- Install guards in pgbench against corner-case overflow
+ Install guards in pgbench against corner-case overflow
conditions during evaluation of script-specified division or modulo
operators (Fabien Coelho, Michael Paquier)
@@ -4250,22 +4486,22 @@ Branch: REL9_2_STABLE [4fb9e6109] 2015-12-28 10:50:35 -0300
Fix failure to localize messages emitted
- by pg_receivexlog and pg_recvlogical
+ by pg_receivexlog and pg_recvlogical
(Ioseph Kim)
- Avoid dump/reload problems when using both plpython2
- and plpython3 (Tom Lane)
+ Avoid dump/reload problems when using both plpython2
+ and plpython3 (Tom Lane)
- In principle, both versions of PL/Python can be used in
+ In principle, both versions of PL/Python can be used in
the same database, though not in the same session (because the two
- versions of libpython cannot safely be used concurrently).
- However, pg_restore and pg_upgrade both
+ versions of libpython cannot safely be used concurrently).
+ However, pg_restore and pg_upgrade both
do things that can fall foul of the same-session restriction. Work
around that by changing the timing of the check.
@@ -4273,7 +4509,7 @@ Branch: REL9_2_STABLE [4fb9e6109] 2015-12-28 10:50:35 -0300
- Fix PL/Python regression tests to pass with Python 3.5
+ Fix PL/Python regression tests to pass with Python 3.5
(Peter Eisentraut)
@@ -4288,29 +4524,29 @@ Branch: REL9_3_STABLE [db6e8e162] 2015-11-12 13:03:53 -0500
- Fix premature clearing of libpq's input buffer when
+ Fix premature clearing of libpq's input buffer when
socket EOF is seen (Tom Lane)
- This mistake caused libpq to sometimes not report the
+ This mistake caused libpq to sometimes not report the
backend's final error message before reporting server closed the
- connection unexpectedly.
+ connection unexpectedly.
- Prevent certain PL/Java parameters from being set by
+ Prevent certain PL/Java parameters from being set by
non-superusers (Noah Misch)
- This change mitigates a PL/Java security bug
- (CVE-2016-0766), which was fixed in PL/Java by marking
+ This change mitigates a PL/Java security bug
+ (CVE-2016-0766), which was fixed in PL/Java by marking
these parameters as superuser-only. To fix the security hazard for
- sites that update PostgreSQL more frequently
- than PL/Java, make the core code aware of them also.
+ sites that update PostgreSQL more frequently
+ than PL/Java, make the core code aware of them also.
@@ -4326,7 +4562,7 @@ Branch: REL9_1_STABLE [4b58ded74] 2015-12-14 18:48:49 +0200
- Improve libpq's handling of out-of-memory situations
+ Improve libpq's handling of out-of-memory situations
(Michael Paquier, Amit Kapila, Heikki Linnakangas)
@@ -4343,7 +4579,7 @@ Branch: REL9_1_STABLE [a9bcd8370] 2015-10-18 10:17:12 +0200
Fix order of arguments
- in ecpg-generated typedef statements
+ in ecpg-generated typedef statements
(Michael Meskes)
@@ -4360,29 +4596,29 @@ Branch: REL9_1_STABLE [84387496f] 2015-12-01 11:42:52 -0500
- Use %g not %f format
- in ecpg's PGTYPESnumeric_from_double()
+ Use %g not %f format
+ in ecpg's PGTYPESnumeric_from_double()
(Tom Lane)
- Fix ecpg-supplied header files to not contain comments
+ Fix ecpg-supplied header files to not contain comments
continued from a preprocessor directive line onto the next line
(Michael Meskes)
- Such a comment is rejected by ecpg. It's not yet clear
- whether ecpg itself should be changed.
+ Such a comment is rejected by ecpg. It's not yet clear
+ whether ecpg itself should be changed.
- Fix hstore_to_json_loose()'s test for whether
- an hstore value can be converted to a JSON number (Tom Lane)
+ Fix hstore_to_json_loose()'s test for whether
+ an hstore value can be converted to a JSON number (Tom Lane)
@@ -4403,15 +4639,15 @@ Branch: REL9_1_STABLE [1b6102eb7] 2015-12-27 13:03:19 -0300
- Ensure that contrib/pgcrypto's crypt()
+ Ensure that contrib/pgcrypto's crypt()
function can be interrupted by query cancel (Andreas Karlsson)
- In contrib/postgres_fdw, fix bugs triggered by use
- of tableoid in data-modifying commands (Etsuro Fujita,
+ In contrib/postgres_fdw, fix bugs triggered by use
+ of tableoid in data-modifying commands (Etsuro Fujita,
Robert Haas)
@@ -4433,7 +4669,7 @@ Branch: REL9_2_STABLE [7f94a5c10] 2015-12-10 10:19:31 -0500
- Accept flex versions later than 2.5.x
+ Accept flex versions later than 2.5.x
(Tom Lane, Michael Paquier)
@@ -4467,19 +4703,19 @@ Branch: REL9_1_STABLE [2a37a103b] 2015-12-11 16:14:48 -0500
- Install our missing script where PGXS builds can find it
+ Install our missing script where PGXS builds can find it
(Jim Nasby)
This allows sane behavior in a PGXS build done on a machine where build
- tools such as bison are missing.
+ tools such as bison are missing.
- Ensure that dynloader.h is included in the installed
+ Ensure that dynloader.h is included in the installed
header files in MSVC builds (Bruce Momjian, Michael Paquier)
@@ -4497,11 +4733,11 @@ Branch: REL9_1_STABLE [386dcd539] 2015-12-11 19:08:40 -0500
Add variant regression test expected-output file to match behavior of
- current libxml2 (Tom Lane)
+ current libxml2 (Tom Lane)
- The fix for libxml2's CVE-2015-7499 causes it not to
+ The fix for libxml2's CVE-2015-7499 causes it not to
output error context reports in some cases where it used to do so.
This seems to be a bug, but we'll probably have to live with it for
some time, so work around it.
@@ -4510,7 +4746,7 @@ Branch: REL9_1_STABLE [386dcd539] 2015-12-11 19:08:40 -0500
- Update time zone data files to tzdata release 2016a for
+ Update time zone data files to tzdata release 2016a for
DST law changes in Cayman Islands, Metlakatla, and Trans-Baikal
Territory (Zabaykalsky Krai), plus historical corrections for Pakistan.
@@ -4563,13 +4799,13 @@ Branch: REL9_3_STABLE [f8862172e] 2015-10-05 10:06:34 -0400
- Guard against stack overflows in json parsing
+ Guard against stack overflows in json parsing
(Oskari Saarenmaa)
- If an application constructs PostgreSQL json
- or jsonb values from arbitrary user input, the application's
+ If an application constructs PostgreSQL json
+ or jsonb values from arbitrary user input, the application's
users can reliably crash the PostgreSQL server, causing momentary
denial of service. (CVE-2015-5289)
@@ -4588,8 +4824,8 @@ Branch: REL9_0_STABLE [188e081ef] 2015-10-05 10:06:36 -0400
- Fix contrib/pgcrypto to detect and report
- too-short crypt() salts (Josh Kupershmidt)
+ Fix contrib/pgcrypto to detect and report
+ too-short crypt() salts (Josh Kupershmidt)
@@ -4634,7 +4870,7 @@ Branch: REL9_4_STABLE [bab959906] 2015-08-02 20:09:05 +0300
Fix possible deadlock during WAL insertion
- when commit_delay is set (Heikki Linnakangas)
+ when commit_delay is set (Heikki Linnakangas)
@@ -4665,13 +4901,13 @@ Branch: REL9_0_STABLE [45c69178b] 2015-06-25 14:39:06 -0400
- Fix insertion of relations into the relation cache init file
+ Fix insertion of relations into the relation cache init file
(Tom Lane)
An oversight in a patch in the most recent minor releases
- caused pg_trigger_tgrelid_tgname_index to be omitted
+ caused pg_trigger_tgrelid_tgname_index to be omitted
from the init file. Subsequent sessions detected this, then deemed the
init file to be broken and silently ignored it, resulting in a
significant degradation in session startup time. In addition to fixing
@@ -4711,7 +4947,7 @@ Branch: REL9_0_STABLE [2d4336cf8] 2015-09-30 23:32:23 -0400
- Improve LISTEN startup time when there are many unread
+ Improve LISTEN startup time when there are many unread
notifications (Matt Newell)
@@ -4731,7 +4967,7 @@ Branch: REL9_3_STABLE [1bcc9e60a] 2015-09-25 13:16:31 -0400
- This was seen primarily when restoring pg_dump output
+ This was seen primarily when restoring pg_dump output
for databases with many thousands of tables.
@@ -4755,7 +4991,7 @@ Branch: REL9_0_STABLE [444b2ebee] 2015-07-28 22:06:32 +0200
too many bugs in practice, both in the underlying OpenSSL library and
in our usage of it. Renegotiation will be removed entirely in 9.5 and
later. In the older branches, just change the default value
- of ssl_renegotiation_limit to zero (disabled).
+ of ssl_renegotiation_limit to zero (disabled).
@@ -4779,7 +5015,7 @@ Branch: REL9_0_STABLE [eeb0b7830] 2015-10-05 11:57:25 +0200
- Lower the minimum values of the *_freeze_max_age parameters
+ Lower the minimum values of the *_freeze_max_age parameters
(Andres Freund)
@@ -4802,7 +5038,7 @@ Branch: REL9_0_STABLE [b09446ed7] 2015-08-04 13:12:03 -0400
- Limit the maximum value of wal_buffers to 2GB to avoid
+ Limit the maximum value of wal_buffers to 2GB to avoid
server crashes (Josh Berkus)
@@ -4816,8 +5052,8 @@ Branch: REL9_3_STABLE [5a56c2545] 2015-06-28 18:38:06 -0400
Avoid logging complaints when a parameter that can only be set at
- server start appears multiple times in postgresql.conf,
- and fix counting of line numbers after an include_dir
+ server start appears multiple times in postgresql.conf,
+ and fix counting of line numbers after an include_dir
directive (Tom Lane)
@@ -4835,7 +5071,7 @@ Branch: REL9_0_STABLE [a89781e34] 2015-09-21 12:12:16 -0400
- Fix rare internal overflow in multiplication of numeric values
+ Fix rare internal overflow in multiplication of numeric values
(Dean Rasheed)
@@ -4862,8 +5098,8 @@ Branch: REL9_2_STABLE [8dacb29ca] 2015-10-05 10:06:35 -0400
Guard against hard-to-reach stack overflows involving record types,
- range types, json, jsonb, tsquery,
- ltxtquery and query_int (Noah Misch)
+ range types, json, jsonb, tsquery,
+ ltxtquery and query_int (Noah Misch)
@@ -4887,14 +5123,14 @@ Branch: REL9_0_STABLE [92d956f51] 2015-09-07 20:47:06 +0100
- Fix handling of DOW and DOY in datetime input
+ Fix handling of DOW and DOY in datetime input
(Greg Stark)
These tokens aren't meant to be used in datetime values, but previously
they resulted in opaque internal error messages rather
- than invalid input syntax.
+ than invalid input syntax.
@@ -4936,7 +5172,7 @@ Branch: REL9_0_STABLE [b875ca09f] 2015-10-02 15:00:52 -0400
Add recursion depth protections to regular expression, SIMILAR
- TO, and LIKE matching (Tom Lane)
+ TO, and LIKE matching (Tom Lane)
@@ -5052,8 +5288,8 @@ Branch: REL9_0_STABLE [bd327627f] 2015-08-04 18:18:47 -0400
- Fix unexpected out-of-memory situation during sort errors
- when using tuplestores with small work_mem settings (Tom
+ Fix unexpected out-of-memory situation during sort errors
+ when using tuplestores with small work_mem settings (Tom
Lane)
@@ -5071,7 +5307,7 @@ Branch: REL9_0_STABLE [36522d627] 2015-07-16 22:57:46 -0400
- Fix very-low-probability stack overrun in qsort (Tom Lane)
+ Fix very-low-probability stack overrun in qsort (Tom Lane)
@@ -5093,8 +5329,8 @@ Branch: REL9_0_STABLE [d637a899c] 2015-10-04 15:55:07 -0400
- Fix invalid memory alloc request size failure in hash joins
- with large work_mem settings (Tomas Vondra, Tom Lane)
+ Fix invalid memory alloc request size failure in hash joins
+ with large work_mem settings (Tomas Vondra, Tom Lane)
@@ -5172,9 +5408,9 @@ Branch: REL9_0_STABLE [7b4b57fc4] 2015-08-12 21:19:10 -0400
These mistakes could lead to incorrect query plans that would give wrong
answers, or to assertion failures in assert-enabled builds, or to odd
planner errors such as could not devise a query plan for the
- given query, could not find pathkey item to
- sort, plan should not reference subplan's variable,
- or failed to assign all NestLoopParams to plan nodes.
+ given query, could not find pathkey item to
+ sort, plan should not reference subplan's variable,
+ or failed to assign all NestLoopParams to plan nodes.
Thanks are due to Andreas Seltenreich and Piotr Stefaniak for fuzz
testing that exposed these problems.
@@ -5190,7 +5426,7 @@ Branch: REL9_2_STABLE [e538e510e] 2015-06-22 18:53:27 -0400
- Improve planner's performance for UPDATE/DELETE
+ Improve planner's performance for UPDATE/DELETE
on large inheritance sets (Tom Lane, Dean Rasheed)
@@ -5232,12 +5468,12 @@ Branch: REL9_0_STABLE [8b53c087d] 2015-08-02 14:54:44 -0400
During postmaster shutdown, ensure that per-socket lock files are
removed and listen sockets are closed before we remove
- the postmaster.pid file (Tom Lane)
+ the postmaster.pid file (Tom Lane)
This avoids race-condition failures if an external script attempts to
- start a new postmaster as soon as pg_ctl stop returns.
+ start a new postmaster as soon as pg_ctl stop returns.
@@ -5311,7 +5547,7 @@ Branch: REL9_0_STABLE [f527c0a2a] 2015-07-28 17:34:00 -0400
- Do not print a WARNING when an autovacuum worker is already
+ Do not print a WARNING when an autovacuum worker is already
gone when we attempt to signal it, and reduce log verbosity for such
signals (Tom Lane)
@@ -5389,7 +5625,7 @@ Branch: REL9_2_STABLE [f4297f8c5] 2015-07-27 12:32:48 +0300
- VACUUM attempted to recycle such pages, but did so in a
+ VACUUM attempted to recycle such pages, but did so in a
way that wasn't crash-safe.
@@ -5408,7 +5644,7 @@ Branch: REL9_0_STABLE [40ad78220] 2015-07-23 01:30:19 +0300
Fix off-by-one error that led to otherwise-harmless warnings
- about apparent wraparound in subtrans/multixact truncation
+ about apparent wraparound in subtrans/multixact truncation
(Thomas Munro)
@@ -5426,8 +5662,8 @@ Branch: REL9_0_STABLE [e41718fa1] 2015-08-18 19:22:38 -0400
- Fix misreporting of CONTINUE and MOVE statement
- types in PL/pgSQL's error context messages
+ Fix misreporting of CONTINUE and MOVE statement
+ types in PL/pgSQL's error context messages
(Pavel Stehule, Tom Lane)
@@ -5444,7 +5680,7 @@ Branch: REL9_1_STABLE [ca6c2f863] 2015-09-29 10:52:22 -0400
- Fix PL/Perl to handle non-ASCII error
+ Fix PL/Perl to handle non-ASCII error
message texts correctly (Alex Hunsaker)
@@ -5467,8 +5703,8 @@ Branch: REL9_1_STABLE [1d190d095] 2015-08-21 12:21:37 -0400
- Fix PL/Python crash when returning the string
- representation of a record result (Tom Lane)
+ Fix PL/Python crash when returning the string
+ representation of a record result (Tom Lane)
@@ -5485,8 +5721,8 @@ Branch: REL9_0_STABLE [4c11967e7] 2015-07-20 14:18:08 +0200
- Fix some places in PL/Tcl that neglected to check for
- failure of malloc() calls (Michael Paquier, Álvaro
+ Fix some places in PL/Tcl that neglected to check for
+ failure of malloc() calls (Michael Paquier, Álvaro
Herrera)
@@ -5503,7 +5739,7 @@ Branch: REL9_1_STABLE [2d19a0e97] 2015-08-02 22:12:51 +0300
- In contrib/isn, fix output of ISBN-13 numbers that begin
+ In contrib/isn, fix output of ISBN-13 numbers that begin
with 979 (Fabien Coelho)
@@ -5522,7 +5758,7 @@ Branch: REL9_4_STABLE [93840f96c] 2015-10-04 17:58:30 -0400
- Improve contrib/pg_stat_statements' handling of
+ Improve contrib/pg_stat_statements' handling of
query-text garbage collection (Peter Geoghegan)
@@ -5543,13 +5779,13 @@ Branch: REL9_3_STABLE [b7dcb2dd4] 2015-09-24 12:47:30 -0400
- Improve contrib/postgres_fdw's handling of
+ Improve contrib/postgres_fdw's handling of
collation-related decisions (Tom Lane)
The main user-visible effect is expected to be that comparisons
- involving varchar columns will be sent to the remote server
+ involving varchar columns will be sent to the remote server
for execution in more cases than before.
@@ -5567,7 +5803,7 @@ Branch: REL9_0_STABLE [2b189c7ec] 2015-07-07 18:45:31 +0300
- Improve libpq's handling of out-of-memory conditions
+ Improve libpq's handling of out-of-memory conditions
(Michael Paquier, Heikki Linnakangas)
@@ -5603,7 +5839,7 @@ Branch: REL9_0_STABLE [d278ff3b2] 2015-06-15 14:27:39 +0200
Fix memory leaks and missing out-of-memory checks
- in ecpg (Michael Paquier)
+ in ecpg (Michael Paquier)
@@ -5634,15 +5870,15 @@ Branch: REL9_0_STABLE [98d8c75f9] 2015-09-25 12:20:46 -0400
- Fix psql's code for locale-aware formatting of numeric
+ Fix psql's code for locale-aware formatting of numeric
output (Tom Lane)
- The formatting code invoked by \pset numericlocale on
+ The formatting code invoked by \pset numericlocale on
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 money data type.
+ output from the money data type.
@@ -5659,7 +5895,7 @@ Branch: REL9_0_STABLE [6087bf1a1] 2015-07-08 20:44:27 -0400
- Prevent crash in psql's \c command when
+ Prevent crash in psql's \c command when
there is no current connection (Noah Misch)
@@ -5675,7 +5911,7 @@ Branch: REL9_2_STABLE [3756c65a0] 2015-10-01 16:19:49 -0400
- Make pg_dump handle inherited NOT VALID
+ Make pg_dump handle inherited NOT VALID
check constraints correctly (Tom Lane)
@@ -5692,8 +5928,8 @@ Branch: REL9_1_STABLE [af225551e] 2015-07-25 17:16:39 -0400
- Fix selection of default zlib compression level
- in pg_dump's directory output format (Andrew Dunstan)
+ Fix selection of default zlib compression level
+ in pg_dump's directory output format (Andrew Dunstan)
@@ -5710,8 +5946,8 @@ Branch: REL9_0_STABLE [24aed2124] 2015-09-20 20:44:34 -0400
- Ensure that temporary files created during a pg_dump
- run with tar-format output are not world-readable (Michael
+ Ensure that temporary files created during a pg_dump
+ run with tar-format output are not world-readable (Michael
Paquier)
@@ -5729,8 +5965,8 @@ Branch: REL9_0_STABLE [52b07779d] 2015-09-11 15:51:10 -0400
- Fix pg_dump and pg_upgrade to support
- cases where the postgres or template1 database
+ Fix pg_dump and pg_upgrade to support
+ cases where the postgres or template1 database
is in a non-default tablespace (Marti Raudsepp, Bruce Momjian)
@@ -5748,7 +5984,7 @@ Branch: REL9_0_STABLE [298d1f808] 2015-08-10 20:10:16 -0400
- Fix pg_dump to handle object privileges sanely when
+ Fix pg_dump to handle object privileges sanely when
dumping from a server too old to have a particular privilege type
(Tom Lane)
@@ -5756,11 +5992,11 @@ Branch: REL9_0_STABLE [298d1f808] 2015-08-10 20:10:16 -0400
When dumping data types from pre-9.2 servers, and when dumping
functions or procedural languages from pre-7.3
- servers, pg_dump would
- produce GRANT/REVOKE commands that revoked the
+ servers, pg_dump would
+ produce GRANT/REVOKE commands that revoked the
owner's grantable privileges and instead granted all privileges
- to PUBLIC. Since the privileges involved are
- just USAGE and EXECUTE, this isn't a security
+ to PUBLIC. Since the privileges involved are
+ just USAGE and EXECUTE, this isn't a security
problem, but it's certainly a surprising representation of the older
systems' behavior. Fix it to leave the default privilege state alone
in these cases.
@@ -5780,12 +6016,12 @@ Branch: REL9_0_STABLE [5d175be17] 2015-08-04 19:34:12 -0400
- Fix pg_dump to dump shell types (Tom Lane)
+ Fix pg_dump to dump shell types (Tom Lane)
Shell types (that is, not-yet-fully-defined types) aren't useful for
- much, but nonetheless pg_dump should dump them.
+ much, but nonetheless pg_dump should dump them.
@@ -5801,7 +6037,7 @@ Branch: REL9_1_STABLE [e9a859b54] 2015-07-12 16:25:52 -0400
- Fix assorted minor memory leaks in pg_dump and other
+ Fix assorted minor memory leaks in pg_dump and other
client-side programs (Michael Paquier)
@@ -5815,8 +6051,8 @@ Branch: REL9_4_STABLE [9d6352aaa] 2015-07-03 11:15:27 +0300
- Fix pgbench's progress-report behavior when a query,
- or pgbench itself, gets stuck (Fabien Coelho)
+ Fix pgbench's progress-report behavior when a query,
+ or pgbench itself, gets stuck (Fabien Coelho)
@@ -5845,11 +6081,11 @@ Branch: REL9_0_STABLE [b5a22d8bb] 2015-08-29 16:09:25 -0400
Fix spinlock assembly code for PPC hardware to be compatible
- with AIX's native assembler (Tom Lane)
+ with AIX's native assembler (Tom Lane)
- Building with gcc didn't work if gcc
+ Building with gcc didn't work if gcc
had been configured to use the native assembler, which is becoming more
common.
@@ -5868,7 +6104,7 @@ Branch: REL9_0_STABLE [cdf596b1c] 2015-07-17 03:02:46 -0400
- On AIX, test the -qlonglong compiler option
+ On AIX, test the -qlonglong compiler option
rather than just assuming it's safe to use (Noah Misch)
@@ -5886,7 +6122,7 @@ Branch: REL9_0_STABLE [7803d5720] 2015-07-15 21:00:31 -0400
- On AIX, use -Wl,-brtllib link option to allow
+ On AIX, use -Wl,-brtllib link option to allow
symbols to be resolved at runtime (Noah Misch)
@@ -5909,7 +6145,7 @@ Branch: REL9_0_STABLE [2d8c136e7] 2015-07-29 22:54:08 -0400
Avoid use of inline functions when compiling with
- 32-bit xlc, due to compiler bugs (Noah Misch)
+ 32-bit xlc, due to compiler bugs (Noah Misch)
@@ -5925,7 +6161,7 @@ Branch: REL9_0_STABLE [b185c42c1] 2015-06-30 14:20:37 -0300
- Use librt for sched_yield() when necessary,
+ Use librt for sched_yield() when necessary,
which it is on some Solaris versions (Oskari Saarenmaa)
@@ -5939,7 +6175,7 @@ Branch: REL9_4_STABLE [a0104e080] 2015-08-14 20:23:42 -0400
- Translate encoding UHC as Windows code page 949
+ Translate encoding UHC as Windows code page 949
(Noah Misch)
@@ -5972,12 +6208,12 @@ Branch: REL9_4_STABLE [b2ed1682d] 2015-06-20 12:10:56 -0400
Fix postmaster startup failure due to not
- copying setlocale()'s return value (Noah Misch)
+ copying setlocale()'s return value (Noah Misch)
This has been reported on Windows systems with the ANSI code page set
- to CP936 (Chinese (Simplified, PRC)), and may occur with
+ to CP936 (Chinese (Simplified, PRC)), and may occur with
other multibyte code pages.
@@ -5995,7 +6231,7 @@ Branch: REL9_0_STABLE [341b877d3] 2015-07-07 16:39:25 +0300
- Fix Windows install.bat script to handle target directory
+ Fix Windows install.bat script to handle target directory
names that contain spaces (Heikki Linnakangas)
@@ -6013,9 +6249,9 @@ Branch: REL9_0_STABLE [29ff43adf] 2015-07-05 12:01:02 -0400
- Make the numeric form of the PostgreSQL version number
- (e.g., 90405) readily available to extension Makefiles,
- as a variable named VERSION_NUM (Michael Paquier)
+ Make the numeric form of the PostgreSQL version number
+ (e.g., 90405) readily available to extension Makefiles,
+ as a variable named VERSION_NUM (Michael Paquier)
@@ -6032,10 +6268,10 @@ Branch: REL9_0_STABLE [47ac95f37] 2015-10-02 19:16:37 -0400
- Update time zone data files to tzdata release 2015g for
+ Update time zone data files to tzdata 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
- America/Fort_Nelson for the Canadian Northern Rockies.
+ America/Fort_Nelson for the Canadian Northern Rockies.
@@ -6067,7 +6303,7 @@ Branch: REL9_0_STABLE [47ac95f37] 2015-10-02 19:16:37 -0400
However, if you are upgrading an installation that was previously
- upgraded using a pg_upgrade version between 9.3.0 and
+ upgraded using a pg_upgrade version between 9.3.0 and
9.3.4 inclusive, see the first changelog entry below.
@@ -6096,46 +6332,46 @@ Branch: REL9_3_STABLE [2a9b01928] 2015-06-05 09:34:15 -0400
- Recent PostgreSQL releases introduced mechanisms to
+ Recent PostgreSQL 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 pg_upgrade could also cause such a failure, in
- installations that had used pg_upgrade versions
+ bug in pg_upgrade could also cause such a failure, in
+ installations that had used pg_upgrade versions
between 9.3.0 and 9.3.4.
- The pg_upgrade bug in question was that it would
- set oldestMultiXid to 1 in pg_control even
+ The pg_upgrade bug in question was that it would
+ set oldestMultiXid to 1 in pg_control 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 oldestMultiXid value can
+ autovacuuming until a correct oldestMultiXid value can
be determined. If that would pose a hardship, users can avoid it by
- doing manual vacuuming before upgrading to this release.
+ doing manual vacuuming before upgrading to this release.
In detail:
- Check whether pg_controldata reports Latest
- checkpoint's oldestMultiXid to be 1. If not, there's nothing
+ Check whether pg_controldata reports Latest
+ checkpoint's oldestMultiXid to be 1. If not, there's nothing
to do.
- Look in PGDATA/pg_multixact/offsets to see if there's a
- file named 0000. If there is, there's nothing to do.
+ Look in PGDATA/pg_multixact/offsets to see if there's a
+ file named 0000. If there is, there's nothing to do.
Otherwise, for each table that has
- pg_class.relminmxid equal to 1,
- VACUUM that table with
+ pg_class.relminmxid equal to 1,
+ VACUUM that table with
both
and set to
zero. (You can use the vacuum cost delay parameters described
@@ -6164,7 +6400,7 @@ Branch: REL9_0_STABLE [2fe1939b0] 2015-06-07 15:32:09 -0400
With just the wrong timing of concurrent activity, a VACUUM
- FULL on a system catalog might fail to update the init file
+ FULL on a system catalog might fail to update the init file
that's used to avoid cache-loading work for new sessions. This would
result in later sessions being unable to access that catalog at all.
This is a very ancient bug, but it's so hard to trigger that no
@@ -6185,13 +6421,13 @@ Branch: REL9_0_STABLE [dbd99c7f0] 2015-06-05 13:22:27 -0400
Avoid deadlock between incoming sessions and CREATE/DROP
- DATABASE (Tom Lane)
+ DATABASE (Tom Lane)
A new session starting in a database that is the target of
- a DROP DATABASE command, or is the template for
- a CREATE DATABASE command, could cause the command to wait
+ a DROP DATABASE command, or is the template for
+ a CREATE DATABASE command, could cause the command to wait
for five seconds and then fail, even if the new session would have
exited before that.
@@ -6284,12 +6520,12 @@ Branch: REL9_3_STABLE [c2b68b1f7] 2015-05-29 17:02:58 -0400
- Avoid failures while fsync'ing data directory during
+ Avoid failures while fsync'ing data directory during
crash restart (Abhijit Menon-Sen, Tom Lane)
- In the previous minor releases we added a patch to fsync
+ In the previous minor releases we added a patch to fsync
everything in the data directory after a crash. Unfortunately its
response to any error condition was to fail, thereby preventing the
server from starting up, even when the problem was quite harmless.
@@ -6301,7 +6537,7 @@ Branch: REL9_3_STABLE [c2b68b1f7] 2015-05-29 17:02:58 -0400
- Also apply the same rules in initdb --sync-only.
+ Also apply the same rules in initdb --sync-only.
This case is less critical but it should act similarly.
@@ -6316,8 +6552,8 @@ Branch: REL9_2_STABLE [f3c67aad4] 2015-05-28 11:24:37 -0400
- Fix pg_get_functiondef() to show
- functions' LEAKPROOF property, if set (Jeevan Chalke)
+ Fix pg_get_functiondef() to show
+ functions' LEAKPROOF property, if set (Jeevan Chalke)
@@ -6329,7 +6565,7 @@ Branch: REL9_4_STABLE [9b74f32cd] 2015-05-22 10:31:29 -0400
- Fix pushJsonbValue() to unpack jbvBinary
+ Fix pushJsonbValue() to unpack jbvBinary
objects (Andrew Dunstan)
@@ -6351,14 +6587,14 @@ Branch: REL9_0_STABLE [b06649b7f] 2015-05-26 22:15:00 -0400
- Remove configure's check prohibiting linking to a
- threaded libpython
- on OpenBSD (Tom Lane)
+ Remove configure's check prohibiting linking to a
+ threaded libpython
+ on OpenBSD (Tom Lane)
The failure this restriction was meant to prevent seems to not be a
- problem anymore on current OpenBSD
+ problem anymore on current OpenBSD
versions.
@@ -6390,8 +6626,8 @@ Branch: REL9_0_STABLE [b06649b7f] 2015-05-26 22:15:00 -0400
- However, if you use contrib/citext's
- regexp_matches() functions, see the changelog entry below
+ However, if you use contrib/citext's
+ regexp_matches() functions, see the changelog entry below
about that.
@@ -6469,7 +6705,7 @@ Branch: REL9_0_STABLE [cf893530a] 2015-05-19 18:18:56 -0400
- Our replacement implementation of snprintf() failed to
+ Our replacement implementation of snprintf() failed to
check for errors reported by the underlying system library calls;
the main case that might be missed is out-of-memory situations.
In the worst case this might lead to information exposure, due to our
@@ -6479,7 +6715,7 @@ Branch: REL9_0_STABLE [cf893530a] 2015-05-19 18:18:56 -0400
- It remains possible that some calls of the *printf()
+ It remains possible that some calls of the *printf()
family of functions are vulnerable to information disclosure if an
out-of-memory error occurs at just the wrong time. We judge the risk
to not be large, but will continue analysis in this area.
@@ -6499,15 +6735,15 @@ Branch: REL9_0_STABLE [b84e5c017] 2015-05-18 10:02:39 -0400
- In contrib/pgcrypto, uniformly report decryption failures
- as Wrong key or corrupt data (Noah Misch)
+ In contrib/pgcrypto, uniformly report decryption failures
+ as Wrong key or corrupt data (Noah Misch)
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 pgcrypto's specific behaviors
+ While it's unknown whether pgcrypto's specific behaviors
are likewise exploitable, it seems better to avoid the risk by using a
one-size-fits-all message.
(CVE-2015-3167)
@@ -6557,7 +6793,7 @@ Branch: REL9_3_STABLE [ddebd2119] 2015-05-11 12:16:51 -0400
Under certain usage patterns, the existing defenses against this might
- be insufficient, allowing pg_multixact/members files to be
+ be insufficient, allowing pg_multixact/members files to be
removed too early, resulting in data loss.
The fix for this includes modifying the server to fail transactions
that would result in overwriting old multixact member ID data, and
@@ -6578,16 +6814,16 @@ Branch: REL9_1_STABLE [801e250a8] 2015-05-05 15:50:53 -0400
- Fix incorrect declaration of contrib/citext's
- regexp_matches() functions (Tom Lane)
+ Fix incorrect declaration of contrib/citext's
+ regexp_matches() functions (Tom Lane)
- These functions should return setof text[], like the core
+ These functions should return setof text[], like the core
functions they are wrappers for; but they were incorrectly declared as
- returning just text[]. This mistake had two results: first,
+ returning just text[]. 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 g flag
+ should get is an empty set (zero rows). Second, the g flag
was effectively ignored, since you would get only one result array even
if there were multiple matches.
@@ -6595,16 +6831,16 @@ Branch: REL9_1_STABLE [801e250a8] 2015-05-05 15:50:53 -0400
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 PostgreSQL 9.5.
+ will not be changed by default until PostgreSQL 9.5.
In pre-9.5 branches, the old behavior exists in version 1.0 of
- the citext extension, while we have provided corrected
- declarations in version 1.1 (which is not installed by
+ the citext extension, while we have provided corrected
+ declarations in version 1.1 (which is not installed by
default). To adopt the fix in pre-9.5 branches, execute
- ALTER EXTENSION citext UPDATE TO '1.1' in each database in
- which citext is installed. (You can also update
+ ALTER EXTENSION citext UPDATE TO '1.1' in each database in
+ which citext is installed. (You can also update
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 citext's regexp_matches() functions.
+ use citext's regexp_matches() functions.
@@ -6616,8 +6852,8 @@ Branch: REL9_4_STABLE [79afe6e66] 2015-02-26 12:34:43 -0500
- Render infinite dates and timestamps as infinity when
- converting to json, rather than throwing an error
+ Render infinite dates and timestamps as infinity when
+ converting to json, rather than throwing an error
(Andrew Dunstan)
@@ -6630,8 +6866,8 @@ Branch: REL9_4_STABLE [997066f44] 2015-05-04 12:43:16 -0400
- Fix json/jsonb's populate_record()
- and to_record() functions to handle empty input properly
+ Fix json/jsonb's populate_record()
+ and to_record() functions to handle empty input properly
(Andrew Dunstan)
@@ -6671,7 +6907,7 @@ Branch: REL9_4_STABLE [79edb2981] 2015-05-03 11:30:24 -0400
Fix behavior when changing foreign key constraint deferrability status
- with ALTER TABLE ... ALTER CONSTRAINT (Tom Lane)
+ with ALTER TABLE ... ALTER CONSTRAINT (Tom Lane)
@@ -6720,7 +6956,7 @@ Branch: REL9_0_STABLE [985da346e] 2015-04-25 16:44:27 -0400
This oversight in the planner has been observed to cause could
- not find RelOptInfo for given relids errors, but it seems possible
+ not find RelOptInfo for given relids errors, but it seems possible
that sometimes an incorrect query plan might get past that consistency
check and result in silently-wrong query output.
@@ -6768,7 +7004,7 @@ Branch: REL9_0_STABLE [72bbca27e] 2015-02-10 20:37:31 -0500
This oversight has been seen to lead to failed to join all
- relations together errors in queries involving LATERAL,
+ relations together errors in queries involving LATERAL,
and that might happen in other cases as well.
@@ -6782,7 +7018,7 @@ Branch: REL9_4_STABLE [f16270ade] 2015-02-25 21:36:40 -0500
Ensure that row locking occurs properly when the target of
- an UPDATE or DELETE is a security-barrier view
+ an UPDATE or DELETE is a security-barrier view
(Stephen Frost)
@@ -6801,7 +7037,7 @@ Branch: REL9_4_STABLE [fd3dfc236] 2015-04-28 00:18:04 +0200
On some platforms, the previous coding could result in errors like
- could not fsync file "pg_replslot/...": Bad file descriptor.
+ could not fsync file "pg_replslot/...": Bad file descriptor.
@@ -6818,7 +7054,7 @@ Branch: REL9_0_STABLE [223a94680] 2015-04-23 21:37:09 +0300
Fix possible deadlock at startup
- when max_prepared_transactions is too small
+ when max_prepared_transactions is too small
(Heikki Linnakangas)
@@ -6859,7 +7095,7 @@ Branch: REL9_0_STABLE [262fbcb9d] 2015-05-05 09:30:07 -0400
- Recursively fsync() the data directory after a crash
+ Recursively fsync() the data directory after a crash
(Abhijit Menon-Sen, Robert Haas)
@@ -6901,7 +7137,7 @@ Branch: REL9_4_STABLE [ee0d06c0b] 2015-04-03 00:07:29 -0400
This oversight could result in failures in sessions that start
- concurrently with a VACUUM FULL on a system catalog.
+ concurrently with a VACUUM FULL on a system catalog.
@@ -6913,7 +7149,7 @@ Branch: REL9_4_STABLE [2897e069c] 2015-03-30 13:05:35 -0400
- Fix crash in BackendIdGetTransactionIds() when trying
+ Fix crash in BackendIdGetTransactionIds() when trying
to get status for a backend process that just exited (Tom Lane)
@@ -6930,13 +7166,13 @@ Branch: REL9_0_STABLE [87b7fcc87] 2015-02-23 16:14:16 +0100
- Cope with unexpected signals in LockBufferForCleanup()
+ Cope with unexpected signals in LockBufferForCleanup()
(Andres Freund)
This oversight could result in spurious errors about multiple
- backends attempting to wait for pincount 1.
+ backends attempting to wait for pincount 1.
@@ -6950,7 +7186,7 @@ Branch: REL9_2_STABLE [effcaa4c2] 2015-02-15 23:26:46 -0500
- Fix crash when doing COPY IN to a table with check
+ Fix crash when doing COPY IN to a table with check
constraints that contain whole-row references (Tom Lane)
@@ -6995,7 +7231,7 @@ Branch: REL9_4_STABLE [16be9737c] 2015-03-23 16:52:17 +0100
- Avoid busy-waiting with short recovery_min_apply_delay
+ Avoid busy-waiting with short recovery_min_apply_delay
values (Andres Freund)
@@ -7061,9 +7297,9 @@ Branch: REL9_0_STABLE [152c94632] 2015-03-29 15:04:38 -0400
- ANALYZE executes index expressions many times; if there are
+ ANALYZE executes index expressions many times; if there are
slow functions in such an expression, it's desirable to be able to
- cancel the ANALYZE before that loop finishes.
+ cancel the ANALYZE before that loop finishes.
@@ -7078,10 +7314,10 @@ Branch: REL9_1_STABLE [4a4fd2b0c] 2015-03-12 13:38:49 -0400
- Ensure tableoid of a foreign table is reported
- correctly when a READ COMMITTED recheck occurs after
- locking rows in SELECT FOR UPDATE, UPDATE,
- or DELETE (Etsuro Fujita)
+ Ensure tableoid of a foreign table is reported
+ correctly when a READ COMMITTED recheck occurs after
+ locking rows in SELECT FOR UPDATE, UPDATE,
+ or DELETE (Etsuro Fujita)
@@ -7127,14 +7363,14 @@ Branch: REL9_0_STABLE [c981e5999] 2015-05-08 19:40:15 -0400
- Recommend setting include_realm to 1 when using
+ Recommend setting include_realm to 1 when using
Kerberos/GSSAPI/SSPI authentication (Stephen Frost)
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 PostgreSQL 9.5.
+ it will become the default setting in PostgreSQL 9.5.
@@ -7157,7 +7393,7 @@ Branch: REL9_0_STABLE [e48ce4f33] 2015-02-17 12:49:18 -0500
- Remove code for matching IPv4 pg_hba.conf entries to
+ Remove code for matching IPv4 pg_hba.conf entries to
IPv4-in-IPv6 addresses (Tom Lane)
@@ -7170,7 +7406,7 @@ Branch: REL9_0_STABLE [e48ce4f33] 2015-02-17 12:49:18 -0500
crashes on some systems, so let's just remove it rather than fix it.
(Had we chosen to fix it, that would make for a subtle and potentially
security-sensitive change in the effective meaning of
- IPv4 pg_hba.conf entries, which does not seem like a good
+ IPv4 pg_hba.conf entries, which does not seem like a good
thing to do in minor releases.)
@@ -7197,7 +7433,7 @@ Branch: REL9_4_STABLE [a1f4ade01] 2015-04-02 14:39:18 -0400
After a database crash, don't restart background workers that are
- marked BGW_NEVER_RESTART (Amit Khandekar)
+ marked BGW_NEVER_RESTART (Amit Khandekar)
@@ -7212,13 +7448,13 @@ Branch: REL9_1_STABLE [0d36d9f2b] 2015-02-06 11:32:42 +0200
- Report WAL flush, not insert, position in IDENTIFY_SYSTEM
+ Report WAL flush, not insert, position in IDENTIFY_SYSTEM
replication command (Heikki Linnakangas)
This avoids a possible startup failure
- in pg_receivexlog.
+ in pg_receivexlog.
@@ -7236,7 +7472,7 @@ Branch: REL9_0_STABLE [78ce2dc8e] 2015-05-07 15:10:01 +0200
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 pg_ctl will wait for
+ service too soon; and ensure that pg_ctl will wait for
shutdown (Krystian Bigaj)
@@ -7253,7 +7489,7 @@ Branch: REL9_0_STABLE [8878eaaa8] 2015-02-23 13:32:53 +0200
- Reduce risk of network deadlock when using libpq's
+ Reduce risk of network deadlock when using libpq's
non-blocking mode (Heikki Linnakangas)
@@ -7262,12 +7498,12 @@ Branch: REL9_0_STABLE [8878eaaa8] 2015-02-23 13:32:53 +0200
buffer every so often, in case the server has sent enough response data
to cause it to block on output. (A typical scenario is that the server
is sending a stream of NOTICE messages during COPY FROM
- STDIN.) This worked properly in the normal blocking mode, but not
- so much in non-blocking mode. We've modified libpq
+ STDIN.) This worked properly in the normal blocking mode, but not
+ so much in non-blocking mode. We've modified libpq
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 PQconsumeInput() upon read-ready.
+ and be sure to call PQconsumeInput() upon read-ready.
@@ -7281,7 +7517,7 @@ Branch: REL9_2_STABLE [83c3115dd] 2015-02-21 12:59:43 -0500
- In libpq, fix misparsing of empty values in URI
+ In libpq, fix misparsing of empty values in URI
connection strings (Thomas Fanghaenel)
@@ -7298,7 +7534,7 @@ Branch: REL9_0_STABLE [ce2fcc58e] 2015-02-11 11:30:11 +0100
- Fix array handling in ecpg (Michael Meskes)
+ Fix array handling in ecpg (Michael Meskes)
@@ -7314,8 +7550,8 @@ Branch: REL9_0_STABLE [557fcfae3] 2015-04-01 20:00:07 -0300
- Fix psql to sanely handle URIs and conninfo strings as
- the first parameter to \connect
+ Fix psql to sanely handle URIs and conninfo strings as
+ the first parameter to \connect
(David Fetter, Andrew Dunstan, Álvaro Herrera)
@@ -7338,17 +7574,17 @@ Branch: REL9_0_STABLE [396ef6fd8] 2015-03-14 13:43:26 -0400
- Suppress incorrect complaints from psql on some
- platforms that it failed to write ~/.psql_history at exit
+ Suppress incorrect complaints from psql on some
+ platforms that it failed to write ~/.psql_history at exit
(Tom Lane)
This misbehavior was caused by a workaround for a bug in very old
- (pre-2006) versions of libedit. We fixed it by
+ (pre-2006) versions of libedit. We fixed it by
removing the workaround, which will cause a similar failure to appear
- for anyone still using such versions of libedit.
- Recommendation: upgrade that library, or use libreadline.
+ for anyone still using such versions of libedit.
+ Recommendation: upgrade that library, or use libreadline.
@@ -7364,7 +7600,7 @@ Branch: REL9_0_STABLE [8e70f3c40] 2015-02-10 22:38:29 -0500
- Fix pg_dump's rule for deciding which casts are
+ Fix pg_dump's rule for deciding which casts are
system-provided casts that should not be dumped (Tom Lane)
@@ -7380,8 +7616,8 @@ Branch: REL9_1_STABLE [b0d53b2e3] 2015-02-18 11:43:00 -0500
- In pg_dump, fix failure to honor -Z
- compression level option together with -Fd
+ In pg_dump, fix failure to honor -Z
+ compression level option together with -Fd
(Michael Paquier)
@@ -7397,7 +7633,7 @@ Branch: REL9_1_STABLE [dcb467b8e] 2015-03-02 14:12:43 -0500
- Make pg_dump consider foreign key relationships
+ Make pg_dump consider foreign key relationships
between extension configuration tables while choosing dump order
(Gilles Darold, Michael Paquier, Stephen Frost)
@@ -7417,7 +7653,7 @@ Branch: REL9_3_STABLE [d645273cf] 2015-03-06 13:27:46 -0500
- Avoid possible pg_dump failure when concurrent sessions
+ Avoid possible pg_dump failure when concurrent sessions
are creating and dropping temporary functions (Tom Lane)
@@ -7434,7 +7670,7 @@ Branch: REL9_0_STABLE [7a501bcbf] 2015-02-25 12:01:12 -0500
- Fix dumping of views that are just VALUES(...) but have
+ Fix dumping of views that are just VALUES(...) but have
column aliases (Tom Lane)
@@ -7448,7 +7684,7 @@ Branch: REL9_4_STABLE [70fac4844] 2015-05-01 13:03:23 -0400
Ensure that a view's replication identity is correctly set
- to nothing during dump/restore (Marko Tiikkaja)
+ to nothing during dump/restore (Marko Tiikkaja)
@@ -7472,7 +7708,7 @@ Branch: REL9_3_STABLE [4e9935979] 2015-05-16 15:16:28 -0400
- In pg_upgrade, force timeline 1 in the new cluster
+ In pg_upgrade, force timeline 1 in the new cluster
(Bruce Momjian)
@@ -7494,7 +7730,7 @@ Branch: REL9_0_STABLE [2194aa92b] 2015-05-16 00:10:03 -0400
- In pg_upgrade, check for improperly non-connectable
+ In pg_upgrade, check for improperly non-connectable
databases before proceeding
(Bruce Momjian)
@@ -7512,8 +7748,8 @@ Branch: REL9_0_STABLE [4ae178f60] 2015-02-11 22:06:04 -0500
- In pg_upgrade, quote directory paths
- properly in the generated delete_old_cluster script
+ In pg_upgrade, quote directory paths
+ properly in the generated delete_old_cluster script
(Bruce Momjian)
@@ -7530,14 +7766,14 @@ Branch: REL9_0_STABLE [85dac37ee] 2015-02-11 21:02:06 -0500
- In pg_upgrade, preserve database-level freezing info
+ In pg_upgrade, preserve database-level freezing info
properly
(Bruce Momjian)
This oversight could cause missing-clog-file errors for tables within
- the postgres and template1 databases.
+ the postgres and template1 databases.
@@ -7553,7 +7789,7 @@ Branch: REL9_0_STABLE [bf22a8e58] 2015-03-30 17:18:10 -0400
- Run pg_upgrade and pg_resetxlog with
+ Run pg_upgrade and pg_resetxlog with
restricted privileges on Windows, so that they don't fail when run by
an administrator (Muhammad Asif Naeem)
@@ -7571,8 +7807,8 @@ Branch: REL9_1_STABLE [d7d294f59] 2015-02-17 11:08:40 -0500
- Improve handling of readdir() failures when scanning
- directories in initdb and pg_basebackup
+ Improve handling of readdir() failures when scanning
+ directories in initdb and pg_basebackup
(Marco Nenciarini)
@@ -7589,7 +7825,7 @@ Branch: REL9_0_STABLE [40b0c10b7] 2015-03-15 23:22:03 -0400
- Fix slow sorting algorithm in contrib/intarray (Tom Lane)
+ Fix slow sorting algorithm in contrib/intarray (Tom Lane)
@@ -7637,7 +7873,7 @@ Branch: REL9_0_STABLE [3c3749a3b] 2015-05-15 19:36:20 -0400
- Update time zone data files to tzdata release 2015d
+ Update time zone data files to tzdata release 2015d
for DST law changes in Egypt, Mongolia, and Palestine, plus historical
changes in Canada and Chile. Also adopt revised zone abbreviations for
the America/Adak zone (HST/HDT not HAST/HADT).
@@ -7672,12 +7908,12 @@ Branch: REL9_0_STABLE [3c3749a3b] 2015-05-15 19:36:20 -0400
However, if you are a Windows user and are using the Norwegian
- (Bokmål) locale, manual action is needed after the upgrade to
- replace any Norwegian (Bokmål)_Norway
- or norwegian-bokmal locale names stored
- in PostgreSQL system catalogs with the plain-ASCII
- alias Norwegian_Norway. For details see
-
+ (Bokmål) locale, manual action is needed after the upgrade to
+ replace any Norwegian (Bokmål)_Norway
+ or norwegian-bokmal locale names stored
+ in PostgreSQL system catalogs with the plain-ASCII
+ alias Norwegian_Norway. For details see
+
@@ -7705,15 +7941,15 @@ Branch: REL9_0_STABLE [56b970f2e] 2015-02-02 10:00:52 -0500
- Fix buffer overruns in to_char()
+ Fix buffer overruns in to_char()
(Bruce Momjian)
- When to_char() processes a numeric formatting template
- calling for a large number of digits, PostgreSQL
+ When to_char() processes a numeric formatting template
+ calling for a large number of digits, PostgreSQL
would read past the end of a buffer. When processing a crafted
- timestamp formatting template, PostgreSQL would write
+ timestamp formatting template, PostgreSQL would write
past the end of a buffer. Either case could crash the server.
We have not ruled out the possibility of attacks that lead to
privilege escalation, though they seem unlikely.
@@ -7733,27 +7969,27 @@ Branch: REL9_0_STABLE [9e05c5063] 2015-02-02 10:00:52 -0500
- Fix buffer overrun in replacement *printf() functions
+ Fix buffer overrun in replacement *printf() functions
(Tom Lane)
- PostgreSQL includes a replacement implementation
- of printf and related functions. This code will overrun
+ PostgreSQL includes a replacement implementation
+ of printf and related functions. This code will overrun
a stack buffer when formatting a floating point number (conversion
- specifiers e, E, f, F,
- g or G) with requested precision greater than
+ specifiers e, E, f, F,
+ g or G) 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 to_char() SQL function. While that is the only
- affected core PostgreSQL functionality, extension
+ the to_char() SQL function. While that is the only
+ affected core PostgreSQL functionality, extension
modules that use printf-family functions may be at risk as well.
- This issue primarily affects PostgreSQL on Windows.
- PostgreSQL uses the system implementation of these
+ This issue primarily affects PostgreSQL on Windows.
+ PostgreSQL uses the system implementation of these
functions where adequate, which it is on other modern platforms.
(CVE-2015-0242)
@@ -7778,12 +8014,12 @@ Branch: REL9_0_STABLE [0a3ee8a5f] 2015-02-02 10:00:52 -0500
- Fix buffer overruns in contrib/pgcrypto
+ Fix buffer overruns in contrib/pgcrypto
(Marko Tiikkaja, Noah Misch)
- Errors in memory size tracking within the pgcrypto
+ Errors in memory size tracking within the pgcrypto
module permitted stack buffer overruns and improper dependence on the
contents of uninitialized memory. The buffer overrun cases can
crash the server, and we have not ruled out the possibility of
@@ -7844,7 +8080,7 @@ Branch: REL9_0_STABLE [3a2063369] 2015-01-28 12:33:29 -0500
Some server error messages show the values of columns that violate
a constraint, such as a unique constraint. If the user does not have
- SELECT privilege on all columns of the table, this could
+ SELECT privilege on all columns of the table, this could
mean exposing values that the user should not be able to see. Adjust
the code so that values are displayed only when they came from the SQL
command or could be selected by the user.
@@ -7893,20 +8129,20 @@ Branch: REL9_2_STABLE [6bf343c6e] 2015-01-16 13:10:23 +0200
- Cope with the Windows locale named Norwegian (Bokmål)
+ Cope with the Windows locale named Norwegian (Bokmål)
(Heikki Linnakangas)
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, Norwegian_Norway.
+ name to a plain-ASCII alias, Norwegian_Norway.
- 9.4.0 mapped the troublesome name to norwegian-bokmal,
+ 9.4.0 mapped the troublesome name to norwegian-bokmal,
but that turns out not to work on all Windows configurations.
- Norwegian_Norway is now recommended instead.
+ Norwegian_Norway is now recommended instead.
@@ -7927,7 +8163,7 @@ Branch: REL9_0_STABLE [5308e085b] 2015-01-15 18:52:38 -0500
- In READ COMMITTED mode, queries that lock or update
+ In READ COMMITTED mode, queries that lock or update
recently-updated rows could crash as a result of this bug.
@@ -7956,8 +8192,8 @@ Branch: REL9_3_STABLE [54a8abc2b] 2015-01-04 15:48:29 -0300
Fix failure to wait when a transaction tries to acquire a FOR
- NO KEY EXCLUSIVE tuple lock, while multiple other transactions
- currently hold FOR SHARE locks (Álvaro Herrera)
+ NO KEY EXCLUSIVE tuple lock, while multiple other transactions
+ currently hold FOR SHARE locks (Álvaro Herrera)
@@ -7970,7 +8206,7 @@ Branch: REL9_3_STABLE [939f0fb67] 2015-01-15 13:18:19 -0500
- Improve performance of EXPLAIN with large range tables
+ Improve performance of EXPLAIN with large range tables
(Tom Lane)
@@ -7983,41 +8219,41 @@ Branch: REL9_4_STABLE [4cbf390d5] 2015-01-30 14:44:49 -0500
- Fix jsonb Unicode escape processing, and in consequence
- disallow \u0000 (Tom Lane)
+ Fix jsonb Unicode escape processing, and in consequence
+ disallow \u0000 (Tom Lane)
- Previously, the JSON Unicode escape \u0000 was accepted
+ Previously, the JSON Unicode escape \u0000 was accepted
and was stored as those six characters; but that is indistinguishable
- from what is stored for the input \\u0000, resulting in
+ from what is stored for the input \\u0000, resulting in
ambiguity. Moreover, in cases where de-escaped textual output is
- expected, such as the ->> operator, the sequence was
- printed as \u0000, which does not meet the expectation
+ expected, such as the ->> operator, the sequence was
+ printed as \u0000, which does not meet the expectation
that JSON escaping would be removed. (Consistent behavior would
- require emitting a zero byte, but PostgreSQL does not
+ require emitting a zero byte, but PostgreSQL does not
support zero bytes embedded in text strings.) 9.4.0 included an
ill-advised attempt to improve this situation by adjusting JSON output
conversion rules; but of course that could not fix the fundamental
ambiguity, and it turned out to break other usages of Unicode escape
sequences. Revert that, and to avoid the core problem,
- reject \u0000 in jsonb input.
+ reject \u0000 in jsonb input.
- If a jsonb column contains a \u0000 value stored
+ If a jsonb column contains a \u0000 value stored
with 9.4.0, it will henceforth read out as though it
- were \\u0000, which is the other valid interpretation of
+ were \\u0000, which is the other valid interpretation of
the data stored by 9.4.0 for this case.
- The json type did not have the storage-ambiguity problem, but
+ The json type did not have the storage-ambiguity problem, but
it did have the problem of inconsistent de-escaped textual output.
- Therefore \u0000 will now also be rejected
- in json values when conversion to de-escaped form is
+ Therefore \u0000 will now also be rejected
+ in json values when conversion to de-escaped form is
required. This change does not break the ability to
- store \u0000 in json columns so long as no
+ store \u0000 in json columns so long as no
processing is done on the values. This is exactly parallel to the
cases in which non-ASCII Unicode escapes are allowed when the database
encoding is not UTF8.
@@ -8036,14 +8272,14 @@ Branch: REL9_0_STABLE [cebb3f032] 2015-01-17 22:37:32 -0500
- Fix namespace handling in xpath() (Ali Akbar)
+ Fix namespace handling in xpath() (Ali Akbar)
- Previously, the xml value resulting from
- an xpath() call would not have namespace declarations if
+ Previously, the xml value resulting from
+ an xpath() call would not have namespace declarations if
the namespace declarations were attached to an ancestor element in the
- input xml value, rather than to the specific element being
+ input xml value, rather than to the specific element being
returned. Propagate the ancestral declaration so that the result is
correct when considered in isolation.
@@ -8063,7 +8299,7 @@ Branch: REL9_3_STABLE [527ff8baf] 2015-01-30 12:30:43 -0500
- This patch fixes corner-case unexpected operator NNNN planner
+ This patch fixes corner-case unexpected operator NNNN planner
errors, and improves the selectivity estimates for some other cases.
@@ -8081,7 +8317,7 @@ Branch: REL9_4_STABLE [4e241f7cd] 2014-12-30 14:53:03 +0200
- 9.4.0 could fail with index row size exceeds maximum errors
+ 9.4.0 could fail with index row size exceeds maximum errors
for data that previous versions would accept.
@@ -8111,7 +8347,7 @@ Branch: REL9_1_STABLE [37e0f13f2] 2015-01-29 19:37:22 +0200
Fix possible crash when using
- nonzero gin_fuzzy_search_limit (Heikki Linnakangas)
+ nonzero gin_fuzzy_search_limit (Heikki Linnakangas)
@@ -8139,7 +8375,7 @@ Branch: REL9_4_STABLE [b337d9657] 2015-01-15 20:52:18 +0200
Fix incorrect replay of WAL parameter change records that report
- changes in the wal_log_hints setting (Petr Jelinek)
+ changes in the wal_log_hints setting (Petr Jelinek)
@@ -8155,7 +8391,7 @@ Branch: REL9_0_STABLE [a1a8d0249] 2015-01-19 23:01:46 -0500
- Change pgstat wait timeout warning message to be LOG level,
+ Change pgstat wait timeout warning message to be LOG level,
and rephrase it to be more understandable (Tom Lane)
@@ -8164,7 +8400,7 @@ Branch: REL9_0_STABLE [a1a8d0249] 2015-01-19 23:01:46 -0500
case, but it occurs often enough on our slower buildfarm members to be
a nuisance. Reduce it to LOG level, and expend a bit more effort on
the wording: it now reads using stale statistics instead of
- current ones because stats collector is not responding.
+ current ones because stats collector is not responding.
@@ -8180,7 +8416,7 @@ Branch: REL9_0_STABLE [2e4946169] 2015-01-07 22:46:20 -0500
- Warn if macOS's setlocale() starts an unwanted extra
+ Warn if macOS's setlocale() starts an unwanted extra
thread inside the postmaster (Noah Misch)
@@ -8193,18 +8429,18 @@ Branch: REL9_4_STABLE [733728ff3] 2015-01-11 12:35:47 -0500
- Fix libpq's behavior when /etc/passwd
+ Fix libpq's behavior when /etc/passwd
isn't readable (Tom Lane)
- While doing PQsetdbLogin(), libpq
+ While doing PQsetdbLogin(), libpq
attempts to ascertain the user's operating system name, which on most
- Unix platforms involves reading /etc/passwd. As of 9.4,
+ Unix platforms involves reading /etc/passwd. As of 9.4,
failure to do that was treated as a hard error. Restore the previous
behavior, which was to fail only if the application does not provide a
database role name to connect as. This supports operation in chroot
- environments that lack an /etc/passwd file.
+ environments that lack an /etc/passwd file.
@@ -8220,17 +8456,17 @@ Branch: REL9_0_STABLE [2600e4436] 2014-12-31 12:17:12 -0500
- Improve consistency of parsing of psql's special
+ Improve consistency of parsing of psql's special
variables (Tom Lane)
- Allow variant spellings of on and off (such
- as 1/0) for ECHO_HIDDEN
- and ON_ERROR_ROLLBACK. Report a warning for unrecognized
- values for COMP_KEYWORD_CASE, ECHO,
- ECHO_HIDDEN, HISTCONTROL,
- ON_ERROR_ROLLBACK, and VERBOSITY. Recognize
+ Allow variant spellings of on and off (such
+ as 1/0) for ECHO_HIDDEN
+ and ON_ERROR_ROLLBACK. Report a warning for unrecognized
+ values for COMP_KEYWORD_CASE, ECHO,
+ ECHO_HIDDEN, HISTCONTROL,
+ ON_ERROR_ROLLBACK, and VERBOSITY. Recognize
all values for all these variables case-insensitively; previously
there was a mishmash of case-sensitive and case-insensitive behaviors.
@@ -8245,7 +8481,7 @@ Branch: REL9_3_STABLE [bb1e2426b] 2015-01-05 19:27:09 -0500
- Fix pg_dump to handle comments on event triggers
+ Fix pg_dump to handle comments on event triggers
without failing (Tom Lane)
@@ -8259,8 +8495,8 @@ Branch: REL9_3_STABLE [cc609c46f] 2015-01-30 09:01:36 -0600
- Allow parallel pg_dump to
- use (Kevin Grittner)
@@ -8275,7 +8511,7 @@ Branch: REL9_1_STABLE [2a0bfa4d6] 2015-01-03 20:54:13 +0100
- Prevent WAL files created by pg_basebackup -x/-X from
+ Prevent WAL files created by pg_basebackup -x/-X from
being archived again when the standby is promoted (Andres Freund)
@@ -8293,12 +8529,12 @@ Branch: REL9_0_STABLE [dc9a506e6] 2015-01-29 20:18:46 -0500
Handle unexpected query results, especially NULLs, safely in
- contrib/tablefunc's connectby()
+ contrib/tablefunc's connectby()
(Michael Paquier)
- connectby() previously crashed if it encountered a NULL
+ connectby() previously crashed if it encountered a NULL
key value. It now prints that row but doesn't recurse further.
@@ -8392,14 +8628,14 @@ Branch: REL9_4_STABLE [adb355106] 2015-01-14 11:08:17 -0500
- Allow CFLAGS from configure's environment
- to override automatically-supplied CFLAGS (Tom Lane)
+ Allow CFLAGS from configure's environment
+ to override automatically-supplied CFLAGS (Tom Lane)
- Previously, configure would add any switches that it
+ Previously, configure would add any switches that it
chose of its own accord to the end of the
- user-specified CFLAGS string. Since most compilers
+ user-specified CFLAGS string. Since most compilers
process switches left-to-right, this meant that configure's choices
would override the user-specified flags in case of conflicts. That
should work the other way around, so adjust the logic to put the
@@ -8419,13 +8655,13 @@ Branch: REL9_0_STABLE [338ff75fc] 2015-01-19 23:44:33 -0500
- Make pg_regress remove any temporary installation it
+ Make pg_regress remove any temporary installation it
created upon successful exit (Tom Lane)
This results in a very substantial reduction in disk space usage
- during make check-world, since that sequence involves
+ during make check-world, since that sequence involves
creation of numerous temporary installations.
@@ -8451,7 +8687,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Update time zone data files to tzdata release 2015a
+ Update time zone data files to tzdata release 2015a
for DST law changes in Chile and Mexico, plus historical changes in
Iceland.
@@ -8474,7 +8710,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Overview
- Major enhancements in PostgreSQL 9.4 include:
+ Major enhancements in PostgreSQL 9.4 include:
@@ -8483,35 +8719,35 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add jsonb, a more
- capable and efficient data type for storing JSON data
+ Add jsonb, a more
+ capable and efficient data type for storing JSON data
- Add new SQL command
- for changing postgresql.conf configuration file entries
+ Add new SQL command
+ for changing postgresql.conf configuration file entries
- Reduce lock strength for some
+ Reduce lock strength for some
commands
- Allow materialized views
+ Allow materialized views
to be refreshed without blocking concurrent reads
- Add support for logical decoding
+ Add support for logical decoding
of WAL data, to allow database changes to be streamed out in a
customizable format
@@ -8519,7 +8755,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Allow background worker processes
+ Allow background worker processes
to be dynamically registered, started and terminated
@@ -8558,14 +8794,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Previously, an input array string that started with a single-element
sub-array could later contain multi-element sub-arrays,
- e.g. '{{1}, {2,3}}'::int[] would be accepted.
+ e.g. '{{1}, {2,3}}'::int[] would be accepted.
- When converting values of type date, timestamp
- or timestamptz
+ When converting values of type date, timestamp
+ or timestamptz
to JSON, render the
values in a format compliant with ISO 8601 (Andrew Dunstan)
@@ -8575,7 +8811,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
setting; but many JSON processors
require timestamps to be in ISO 8601 format. If necessary, the
previous behavior can be obtained by explicitly casting the datetime
- value to text before passing it to the JSON conversion
+ value to text before passing it to the JSON conversion
function.
@@ -8583,15 +8819,15 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
The json
- #> text[] path extraction operator now
+ #>text[] path extraction operator now
returns its lefthand input, not NULL, if the array is empty (Tom Lane)
This is consistent with the notion that this represents zero
applications of the simple field/element extraction
- operator ->. Similarly, json
- #>> text[] with an empty array merely
+ operator ->. Similarly, json
+ #>>text[] with an empty array merely
coerces its lefthand input to text.
@@ -8616,26 +8852,26 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Cause consecutive whitespace in to_timestamp()
- and to_date() format strings to consume a corresponding
+ linkend="functions-formatting-table">to_timestamp()
+ and to_date() format strings to consume a corresponding
number of characters in the input string (whitespace or not), then
- conditionally consume adjacent whitespace, if not in FX
+ conditionally consume adjacent whitespace, if not in FX
mode (Jeevan Chalke)
- Previously, consecutive whitespace characters in a non-FX
+ Previously, consecutive whitespace characters in a non-FX
format string behaved like a single whitespace character and consumed
all adjacent whitespace in the input string. For example, previously
a format string of three spaces would consume only the first space in
- ' 12', but it will now consume all three characters.
+ ' 12', but it will now consume all three characters.
Fix ts_rank_cd()
+ linkend="textsearch-functions-table">ts_rank_cd()
to ignore stripped lexemes (Alex Hill)
@@ -8649,15 +8885,15 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
For functions declared to
take VARIADIC
- "any", an actual parameter marked as VARIADIC
+ "any", an actual parameter marked as VARIADIC
must be of a determinable array type (Pavel Stehule)
Such parameters can no longer be written as an undecorated string
- literal or NULL; a cast to an appropriate array data type
+ literal or NULL; a cast to an appropriate array data type
will now be required. Note that this does not affect parameters not
- marked VARIADIC.
+ marked VARIADIC.
@@ -8669,8 +8905,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Constructs like row_to_json(tab.*) now always emit column
- names that match the column aliases visible for table tab
+ Constructs like row_to_json(tab.*) now always emit column
+ names that match the column aliases visible for table tab
at the point of the call. In previous releases the emitted column
names would sometimes be the table's actual column names regardless
of any aliases assigned in the query.
@@ -8686,8 +8922,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Rename EXPLAIN
- ANALYZE's total runtime output
+ Rename EXPLAIN
+ ANALYZE's total runtime output
to execution time (Tom Lane)
@@ -8699,15 +8935,15 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- SHOW TIME ZONE now
- outputs simple numeric UTC offsets in POSIX timezone
+ SHOW TIME ZONE now
+ outputs simple numeric UTC offsets in POSIX timezone
format (Tom Lane)
Previously, such timezone settings were displayed as interval values.
- The new output is properly interpreted by SET TIME ZONE
+ linkend="datatype-interval-output">interval values.
+ The new output is properly interpreted by SET TIME ZONE
when passed as a simple string, whereas the old output required
special treatment to be re-parsed correctly.
@@ -8716,25 +8952,25 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Foreign data wrappers that support updating foreign tables must
- consider the possible presence of AFTER ROW triggers
+ consider the possible presence of AFTER ROW triggers
(Noah Misch)
- When an AFTER ROW trigger is present, all columns of the
+ When an AFTER ROW trigger is present, all columns of the
table must be returned by updating actions, since the trigger might
inspect any or all of them. Previously, foreign tables never had
triggers, so the FDW might optimize away fetching columns not mentioned
- in the RETURNING clause (if any).
+ in the RETURNING clause (if any).
Prevent CHECK
+ linkend="ddl-constraints-check-constraints">CHECK
constraints from referencing system columns, except
- tableoid (Amit Kapila)
+ tableoid (Amit Kapila)
@@ -8752,7 +8988,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Previously, there was an undocumented precedence order among
- the recovery_target_xxx parameters.
+ the recovery_target_xxx parameters.
@@ -8766,14 +9002,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
User commands that did their own quote preservation might need
adjustment. This is likely to be an issue for commands used in
, ,
- and COPY TO/FROM PROGRAM.
+ and COPY TO/FROM PROGRAM.
Remove catalog column pg_class.reltoastidxid
+ linkend="catalog-pg-class">pg_class.reltoastidxid
(Michael Paquier)
@@ -8781,33 +9017,33 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Remove catalog column pg_rewrite.ev_attr
+ linkend="catalog-pg-rewrite">pg_rewrite.ev_attr
(Kevin Grittner)
Per-column rules have not been supported since
- PostgreSQL 7.3.
+ PostgreSQL 7.3.
- Remove native support for Kerberos authentication
- (, etc)
(Magnus Hagander)
- The supported way to use Kerberos authentication is
- with GSSAPI. The native code has been deprecated since
- PostgreSQL 8.3.
+ The supported way to use Kerberos authentication is
+ with GSSAPI. The native code has been deprecated since
+ PostgreSQL 8.3.
- In PL/Python, handle domains over arrays like the
+ In PL/Python, handle domains over arrays like the
underlying array type (Rodolfo Campero)
@@ -8819,9 +9055,9 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Make libpq's PQconnectdbParams()
+ linkend="libpq-pqconnectdbparams">PQconnectdbParams()
and PQpingParams()
+ linkend="libpq-pqpingparams">PQpingParams()
functions process zero-length strings as defaults (Adrian
Vondendriesch)
@@ -8841,20 +9077,20 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Previously, empty arrays were returned as zero-length one-dimensional
arrays, whose text representation looked the same as zero-dimensional
- arrays ({}), but they acted differently in array
- operations. intarray's behavior in this area now
+ arrays ({}), but they acted differently in array
+ operations. intarray's behavior in this area now
matches the built-in array operators.
- now uses
- Previously this option was spelled or ,
but that was inconsistent with other tools.
@@ -8884,7 +9120,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- The new worker_spi module shows an example of use
+ The new worker_spi module shows an example of use
of this feature.
@@ -8904,7 +9140,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
During crash recovery or immediate shutdown, send uncatchable
- termination signals (SIGKILL) to child processes
+ termination signals (SIGKILL) to child processes
that do not shut down promptly (MauMau, Álvaro Herrera)
@@ -8912,7 +9148,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
This reduces the likelihood of leaving orphaned child processes
behind after shutdown, as well
as ensuring that crash recovery can proceed if some child processes
- have become stuck.
+ have become stuck.
@@ -8924,7 +9160,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Make properly report dead but
+ Make properly report dead but
not-yet-removable rows to the statistics collector (Hari Babu)
@@ -8942,14 +9178,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Reduce GIN index size
+ Reduce GIN index size
(Alexander Korotkov, Heikki Linnakangas)
Indexes upgraded via will work fine
- but will still be in the old, larger GIN format.
- Use to recreate old GIN indexes in the
+ but will still be in the old, larger GIN format.
+ Use to recreate old GIN indexes in the
new format.
@@ -8957,16 +9193,16 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Improve speed of multi-key GIN lookups (Alexander Korotkov,
+ linkend="gin">GIN lookups (Alexander Korotkov,
Heikki Linnakangas)
- Add GiST index support
- for inet and
- cidr data types
+ Add GiST index support
+ for inet and
+ cidr data types
(Emre Hasegeli)
@@ -9002,7 +9238,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Allow multiple backends to insert
- into WAL buffers
+ into WAL buffers
concurrently (Heikki Linnakangas)
@@ -9014,7 +9250,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Conditionally write only the modified portion of updated rows to
- WAL (Amit Kapila)
+ WAL (Amit Kapila)
@@ -9029,7 +9265,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Improve speed of aggregates that
- use numeric state
+ use numeric state
values (Hadi Moshayedi)
@@ -9038,8 +9274,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Attempt to freeze
tuples when tables are rewritten with or VACUUM FULL (Robert Haas,
+ linkend="sql-cluster"> or VACUUM FULL (Robert Haas,
Andres Freund)
@@ -9050,8 +9286,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Improve speed of with default nextval()
+ Improve speed of with default nextval()
columns (Simon Riggs)
@@ -9059,7 +9295,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Improve speed of accessing many different sequences in the same session
+ linkend="sql-createsequence">sequences in the same session
(David Rowley)
@@ -9073,26 +9309,26 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Reduce memory allocated by PL/pgSQL
- blocks (Tom Lane)
+ Reduce memory allocated by PL/pgSQL
+ blocks (Tom Lane)
Make the planner more aggressive about extracting restriction clauses
- from mixed AND/OR clauses (Tom Lane)
+ from mixed AND/OR clauses (Tom Lane)
- Disallow pushing volatile WHERE clauses down
- into DISTINCT subqueries (Tom Lane)
+ Disallow pushing volatile WHERE clauses down
+ into DISTINCT subqueries (Tom Lane)
- Pushing down a WHERE clause can produce a more
+ Pushing down a WHERE clause can produce a more
efficient plan overall, but at the cost of evaluating the clause
more often than is implied by the text of the query; so don't do it
if the clause contains any volatile functions.
@@ -9122,14 +9358,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add system view to
- report WAL archiver activity
+ report WAL archiver activity
(Gabriele Bartolini)
- Add n_mod_since_analyze columns to
+ Add n_mod_since_analyze columns to
and related system views
(Mark Kirkwood)
@@ -9143,9 +9379,9 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add backend_xid and backend_xmin
+ Add backend_xid and backend_xmin
columns to the system view ,
- and a backend_xmin column to
+ and a backend_xmin column to
(Christian Kruse)
@@ -9155,22 +9391,22 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- <acronym>SSL</>
+ <acronym>SSL</acronym>
- Add support for SSL ECDH key exchange
+ Add support for SSL ECDH key exchange
(Marko Kreen)
This allows use of Elliptic Curve keys for server authentication.
- Such keys are faster and have better security than RSA
+ Such keys are faster and have better security than RSA
keys. The new configuration parameter
- controls which curve is used for ECDH.
+ controls which curve is used for ECDH.
@@ -9184,14 +9420,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
By default, the server not the client now controls the preference
- order of SSL ciphers
+ order of SSL ciphers
(Marko Kreen)
Previously, the order specified by
was usually ignored in favor of client-side defaults, which are not
- configurable in most PostgreSQL clients. If
+ configurable in most PostgreSQL clients. If
desired, the old behavior can be restored via the new configuration
parameter .
@@ -9199,14 +9435,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Make show SSL
+ Make show SSL
encryption information (Andreas Kunert)
- Improve SSL renegotiation handling (Álvaro
+ Improve SSL renegotiation handling (Álvaro
Herrera)
@@ -9222,14 +9458,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add new SQL command
- for changing postgresql.conf configuration file entries
+ Add new SQL command
+ for changing postgresql.conf configuration file entries
(Amit Kapila)
Previously such settings could only be changed by manually
- editing postgresql.conf.
+ editing postgresql.conf.
@@ -9274,7 +9510,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
In contrast to , this
parameter can load any shared library, not just those in
- the $libdir/plugins directory.
+ the $libdir/plugins directory.
@@ -9287,7 +9523,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Hint bit changes are not normally logged, except when checksums are
enabled. This is useful for external tools
- like pg_rewind.
+ like pg_rewind.
@@ -9320,14 +9556,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Allow terabyte units (TB) to be used when specifying
+ Allow terabyte units (TB) to be used when specifying
configuration variable values (Simon Riggs)
- Show PIDs of lock holders and waiters and improve
+ Show PIDs of lock holders and waiters and improve
information about relations in
log messages (Christian Kruse)
@@ -9340,14 +9576,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- The previous level was LOG, which was too verbose
+ The previous level was LOG, which was too verbose
for libraries loaded per-session.
- On Windows, make SQL_ASCII-encoded databases and server
+ On Windows, make SQL_ASCII-encoded databases and server
processes (e.g., ) emit messages in
the character encoding of the server's Windows user locale
(Alexander Law, Noah Misch)
@@ -9355,7 +9591,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Previously these messages were output in the Windows
- ANSI code page.
+ ANSI code page.
@@ -9379,7 +9615,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Replication slots allow preservation of resources like
- WAL files on the primary until they are no longer
+ WAL files on the primary until they are no longer
needed by standby servers.
@@ -9400,8 +9636,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add
- option
@@ -9413,7 +9649,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
The timestamp reported
- by pg_last_xact_replay_timestamp()
+ by pg_last_xact_replay_timestamp()
now reflects already-committed records, not transactions about to
be committed. Recovering to a restore point now replays the restore
point, rather than stopping just before the restore point.
@@ -9423,34 +9659,34 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
pg_switch_xlog()
- now clears any unused trailing space in the old WAL file
+ linkend="functions-admin-backup-table">pg_switch_xlog()
+ now clears any unused trailing space in the old WAL file
(Heikki Linnakangas)
- This improves the compression ratio for WAL files.
+ This improves the compression ratio for WAL files.
Report failure return codes from external recovery commands
+ linkend="archive-recovery-settings">external recovery commands
(Peter Eisentraut)
- Reduce spinlock contention during WAL replay (Heikki
+ Reduce spinlock contention during WAL replay (Heikki
Linnakangas)
- Write WAL records of running transactions more
+ Write WAL records of running transactions more
frequently (Andres Freund)
@@ -9463,12 +9699,12 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- <link linkend="logicaldecoding">Logical Decoding</>
+ <link linkend="logicaldecoding">Logical Decoding</link>
Logical decoding allows database changes to be streamed in a
configurable format. The data is read from
- the WAL and transformed into the
+ the WAL and transformed into the
desired target format. To implement this feature, the following changes
were made:
@@ -9477,7 +9713,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add support for logical decoding
+ Add support for logical decoding
of WAL data, to allow database changes to be streamed out in a
customizable format
(Andres Freund)
@@ -9486,8 +9722,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add new setting
@@ -9495,7 +9731,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add table-level parameter REPLICA IDENTITY
+ linkend="catalog-pg-class">REPLICA IDENTITY
to control logical replication (Andres Freund)
@@ -9503,7 +9739,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add relation option
to identify user-created tables involved in logical change-set
encoding (Andres Freund)
@@ -9519,7 +9755,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add module to illustrate logical
- decoding at the SQL level (Andres Freund)
+ decoding at the SQL level (Andres Freund)
@@ -9537,28 +9773,28 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add WITH
- ORDINALITY syntax to number the rows returned from a
- set-returning function in the FROM clause
+ ORDINALITY syntax to number the rows returned from a
+ set-returning function in the FROM clause
(Andrew Gierth, David Fetter)
This is particularly useful for functions like
- unnest().
+ unnest().
Add ROWS
- FROM() syntax to allow horizontal concatenation of
- set-returning functions in the FROM clause (Andrew Gierth)
+ FROM() syntax to allow horizontal concatenation of
+ set-returning functions in the FROM clause (Andrew Gierth)
- Allow to have
+ Allow to have
an empty target list (Tom Lane)
@@ -9570,8 +9806,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Ensure that SELECT ... FOR UPDATE
- NOWAIT does not wait in corner cases involving
+ Ensure that SELECT ... FOR UPDATE
+ NOWAIT does not wait in corner cases involving
already-concurrently-updated tuples (Craig Ringer and Thomas Munro)
@@ -9587,22 +9823,22 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add DISCARD
- SEQUENCES command to discard cached sequence-related state
+ Add DISCARD
+ SEQUENCES command to discard cached sequence-related state
(Fabrízio de Royes Mello, Robert Haas)
- DISCARD ALL will now also discard such information.
+ DISCARD ALL will now also discard such information.
- Add FORCE NULL option
- to COPY FROM, which
+ Add FORCE NULL option
+ to COPY FROM, which
causes quoted strings matching the specified null string to be
- converted to NULLs in CSV mode (Ian Barwick, Michael
+ converted to NULLs in CSV mode (Ian Barwick, Michael
Paquier)
@@ -9620,35 +9856,35 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
New warnings are issued for SET
- LOCAL, SET CONSTRAINTS, SET TRANSACTION and
- ABORT when used outside a transaction block.
+ LOCAL, SET CONSTRAINTS, SET TRANSACTION and
+ ABORT when used outside a transaction block.
- <xref linkend="SQL-EXPLAIN">
+ <xref linkend="sql-explain">
- Make EXPLAIN ANALYZE show planning time (Andreas
+ Make EXPLAIN ANALYZE show planning time (Andreas
Karlsson)
- Make EXPLAIN show the grouping columns in Agg and
+ Make EXPLAIN show the grouping columns in Agg and
Group nodes (Tom Lane)
- Make EXPLAIN ANALYZE show exact and lossy
+ Make EXPLAIN ANALYZE show exact and lossy
block counts in bitmap heap scans (Etsuro Fujita)
@@ -9664,22 +9900,22 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Allow a materialized view
+ Allow a materialized view
to be refreshed without blocking other sessions from reading the view
meanwhile (Kevin Grittner)
This is done with REFRESH MATERIALIZED
- VIEW CONCURRENTLY.
+ linkend="sql-refreshmaterializedview">REFRESH MATERIALIZED
+ VIEW CONCURRENTLY.
Allow views to be automatically
+ linkend="sql-createview-updatable-views">automatically
updated even if they contain some non-updatable columns
(Dean Rasheed)
@@ -9687,28 +9923,28 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Previously the presence of non-updatable output columns such as
expressions, literals, and function calls prevented automatic
- updates. Now INSERTs, UPDATEs and
- DELETEs are supported, provided that they do not
+ updates. Now INSERTs, UPDATEs and
+ DELETEs are supported, provided that they do not
attempt to assign new values to any of the non-updatable columns.
- Allow control over whether INSERTs and
- UPDATEs can add rows to an auto-updatable view that
+ Allow control over whether INSERTs and
+ UPDATEs can add rows to an auto-updatable view that
would not appear in the view (Dean Rasheed)
- This is controlled with the new
- clause WITH CHECK OPTION.
+ This is controlled with the new
+ clause WITH CHECK OPTION.
- Allow security barrier views
+ Allow security barrier views
to be automatically updatable (Dean Rasheed)
@@ -9726,60 +9962,60 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Support triggers on foreign
- tables (Ronan Dunklau)
+ Support triggers on foreign
+ tables (Ronan Dunklau)
Allow moving groups of objects from one tablespace to another
- using the ALL IN TABLESPACE ... SET TABLESPACE form of
- , , or
- (Stephen Frost)
+ using the ALL IN TABLESPACE ... SET TABLESPACE form of
+ , , or
+ (Stephen Frost)
Allow changing foreign key constraint deferrability
- via ... ALTER
- CONSTRAINT (Simon Riggs)
+ via ... ALTER
+ CONSTRAINT (Simon Riggs)
- Reduce lock strength for some
+ Reduce lock strength for some
commands
(Simon Riggs, Noah Misch, Robert Haas)
- Specifically, VALIDATE CONSTRAINT, CLUSTER
- ON, SET WITHOUT CLUSTER, ALTER COLUMN
- SET STATISTICS, ALTER COLUMN SET
-
Allow tablespace options to be set
- in (Vik Fearing)
+ in (Vik Fearing)
Formerly these options could only be set
- via .
+ via .
- Allow to define the estimated
+ Allow to define the estimated
size of the aggregate's transition state data (Hadi Moshayedi)
@@ -9791,7 +10027,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Fix DROP IF EXISTS to avoid errors for non-existent
+ Fix DROP IF EXISTS to avoid errors for non-existent
objects in more cases (Pavel Stehule, Dean Rasheed)
@@ -9803,7 +10039,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Previously, relations once moved into the pg_catalog
+ Previously, relations once moved into the pg_catalog
schema could no longer be modified or dropped.
@@ -9820,14 +10056,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Fully implement the line data type (Peter
+ linkend="datatype-line">line data type (Peter
Eisentraut)
- The line segment data type (lseg) has always been
- fully supported. The previous line data type (which was
+ The line segment data type (lseg) has always been
+ fully supported. The previous line data type (which was
enabled only via a compile-time option) is not binary or
dump-compatible with the new implementation.
@@ -9835,17 +10071,17 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add pg_lsn
- data type to represent a WAL log sequence number
- (LSN) (Robert Haas, Michael Paquier)
+ Add pg_lsn
+ data type to represent a WAL log sequence number
+ (LSN) (Robert Haas, Michael Paquier)
Allow single-point polygons to be converted
- to circles
+ linkend="datatype-polygon">polygons to be converted
+ to circles
(Bruce Momjian)
@@ -9857,31 +10093,31 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Previously, PostgreSQL assumed that the UTC offset
- associated with a time zone abbreviation (such as EST)
+ Previously, PostgreSQL assumed that the UTC offset
+ associated with a time zone abbreviation (such as EST)
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, PostgreSQL will now associate the
+ In such timezones, PostgreSQL will now associate the
correct UTC offset with the abbreviation depending on the given date.
- Allow 5+ digit years for non-ISO timestamp and
- date strings, where appropriate (Bruce Momjian)
+ Allow 5+ digit years for non-ISO timestamp and
+ date strings, where appropriate (Bruce Momjian)
Add checks for overflow/underflow of interval values
+ linkend="datatype-datetime">interval values
(Bruce Momjian)
@@ -9889,14 +10125,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- <link linkend="datatype-json"><acronym>JSON</></link>
+ <link linkend="datatype-json"><acronym>JSON</acronym></link>
- Add jsonb, a more
- capable and efficient data type for storing JSON data
+ Add jsonb, a more
+ capable and efficient data type for storing JSON data
(Oleg Bartunov, Teodor Sigaev, Alexander
Korotkov, Peter Geoghegan, Andrew Dunstan)
@@ -9904,9 +10140,9 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
This new type allows faster access to values within a JSON
document, and faster and more useful indexing of JSON columns.
- Scalar values in jsonb documents are stored as appropriate
+ Scalar values in jsonb documents are stored as appropriate
scalar SQL types, and the JSON document structure is pre-parsed
- rather than being stored as text as in the original json
+ rather than being stored as text as in the original json
data type.
@@ -9919,18 +10155,18 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
New functions include json_array_elements_text(),
- json_build_array(), json_object(),
- json_object_agg(), json_to_record(),
- and json_to_recordset().
+ linkend="functions-json-processing-table">json_array_elements_text(),
+ json_build_array(), json_object(),
+ json_object_agg(), json_to_record(),
+ and json_to_recordset().
Add json_typeof()
- to return the data type of a json value (Andrew Tipton)
+ linkend="functions-json-processing-table">json_typeof()
+ to return the data type of a json value (Andrew Tipton)
@@ -9948,13 +10184,13 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add pg_sleep_for(interval)
- and pg_sleep_until(timestamp) to specify
+ linkend="functions-datetime-delay">pg_sleep_for(interval)
+ and pg_sleep_until(timestamp) to specify
delays more flexibly (Vik Fearing, Julien Rouhaud)
- The existing pg_sleep() function only supports delays
+ The existing pg_sleep() function only supports delays
specified in seconds.
@@ -9962,7 +10198,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add cardinality()
+ linkend="array-functions-table">cardinality()
function for arrays (Marko Tiikkaja)
@@ -9974,7 +10210,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add SQL functions to allow large
+ Add SQL functions to allow large
object reads/writes at arbitrary offsets (Pavel Stehule)
@@ -9982,7 +10218,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Allow unnest()
+ linkend="array-functions-table">unnest()
to take multiple arguments, which are individually unnested then
horizontally concatenated (Andrew Gierth)
@@ -9990,36 +10226,36 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add functions to construct times, dates,
- timestamps, timestamptzs, and intervals
+ Add functions to construct times, dates,
+ timestamps, timestamptzs, and intervals
from individual values, rather than strings (Pavel Stehule)
- These functions' names are prefixed with make_,
- e.g. make_date().
+ These functions' names are prefixed with make_,
+ e.g. make_date().
Make to_char()'s
- TZ format specifier return a useful value for simple
+ linkend="functions-formatting-table">to_char()'s
+ TZ format specifier return a useful value for simple
numeric time zone offsets (Tom Lane)
- Previously, to_char(CURRENT_TIMESTAMP, 'TZ') returned
- an empty string if the timezone was set to a constant
- like -4.
+ Previously, to_char(CURRENT_TIMESTAMP, 'TZ') returned
+ an empty string if the timezone was set to a constant
+ like -4.
- Add timezone offset format specifier OF to to_char()
+ Add timezone offset format specifier OF to to_char()
(Bruce Momjian)
@@ -10027,7 +10263,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Improve the random seed used for random()
+ linkend="functions-math-random-table">random()
(Honza Horak)
@@ -10035,7 +10271,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Tighten validity checking for Unicode code points in chr(int)
+ linkend="functions-string-other">chr(int)
(Tom Lane)
@@ -10054,18 +10290,18 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add functions for looking up objects in pg_class,
- pg_proc, pg_type, and
- pg_operator that do not generate errors for
+ Add functions for looking up objects in pg_class,
+ pg_proc, pg_type, and
+ pg_operator that do not generate errors for
non-existent objects (Yugo Nagata, Nozomi Anzai,
Robert Haas)
For example, to_regclass()
- does a lookup in pg_class similarly to
- the regclass input function, but it returns NULL for a
+ linkend="functions-info-catalog-table">to_regclass()
+ does a lookup in pg_class similarly to
+ the regclass input function, but it returns NULL for a
non-existent object instead of failing.
@@ -10073,7 +10309,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add function pg_filenode_relation()
+ linkend="functions-admin-dblocation">pg_filenode_relation()
to allow for more efficient lookup of relation names from filenodes
(Andres Freund)
@@ -10081,8 +10317,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add parameter_default column to information_schema.parameters
+ Add parameter_default column to information_schema.parameters
view (Peter Eisentraut)
@@ -10090,7 +10326,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Make information_schema.schemata
+ linkend="infoschema-schemata">information_schema.schemata
show all accessible schemas (Peter Eisentraut)
@@ -10112,7 +10348,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add control over which rows are passed
into aggregate functions via the FILTER clause
+ linkend="syntax-aggregates">FILTER clause
(David Fetter)
@@ -10120,7 +10356,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Support ordered-set (WITHIN GROUP)
+ linkend="syntax-aggregates">WITHIN GROUP)
aggregates (Atri Sharma, Andrew Gierth, Tom Lane)
@@ -10128,11 +10364,11 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add standard ordered-set aggregates percentile_cont(),
- percentile_disc(), mode(), rank(),
- dense_rank(), percent_rank(), and
- cume_dist()
+ linkend="functions-orderedset-table">percentile_cont(),
+ percentile_disc(), mode(), rank(),
+ dense_rank(), percent_rank(), and
+ cume_dist()
(Atri Sharma, Andrew Gierth)
@@ -10140,7 +10376,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Support VARIADIC
+ linkend="xfunc-sql-variadic-functions">VARIADIC
aggregate functions (Tom Lane)
@@ -10152,7 +10388,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
This allows proper declaration in SQL of aggregates like the built-in
- aggregate array_agg().
+ aggregate array_agg().
@@ -10169,20 +10405,20 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add event trigger support to PL/Perl
- and PL/Tcl (Dimitri Fontaine)
+ Add event trigger support to PL/Perl
+ and PL/Tcl (Dimitri Fontaine)
- Convert numeric
- values to decimal in PL/Python
+ Convert numeric
+ values to decimal in PL/Python
(Szymon Guz, Ronan Dunklau)
- Previously such values were converted to Python float values,
+ Previously such values were converted to Python float values,
risking loss of precision.
@@ -10198,7 +10434,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add ability to retrieve the current PL/pgSQL call stack
using GET
- DIAGNOSTICS
+ DIAGNOSTICS
(Pavel Stehule, Stephen Frost)
@@ -10206,17 +10442,17 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Add option
to display the parameters passed to a query that violated a
- STRICT constraint (Marko Tiikkaja)
+ STRICT constraint (Marko Tiikkaja)
Add variables plpgsql.extra_warnings
- and plpgsql.extra_errors to enable additional PL/pgSQL
+ linkend="plpgsql-extra-checks">plpgsql.extra_warnings
+ and plpgsql.extra_errors to enable additional PL/pgSQL
warnings and errors (Marko Tiikkaja, Petr Jelinek)
@@ -10232,13 +10468,13 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- <link linkend="libpq"><application>libpq</></link>
+ <link linkend="libpq"><application>libpq</application></link>
Make libpq's PQconndefaults()
+ linkend="libpq-pqconndefaults">PQconndefaults()
function ignore invalid service files (Steve Singer, Bruce Momjian)
@@ -10250,7 +10486,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Accept TLS protocol versions beyond TLSv1
+ Accept TLS protocol versions beyond TLSv1
in libpq (Marko Kreen)
@@ -10266,15 +10502,15 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add option
- Add
- option
@@ -10285,8 +10521,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Make pg_resetxlog
- with option output current and potentially changed
values (Rajeev Rastogi)
@@ -10301,19 +10537,19 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Make return exit code 4 for
+ Make return exit code 4 for
an inaccessible data directory (Amit Kapila, Bruce Momjian)
This behavior more closely matches the Linux Standard Base
- (LSB) Core Specification.
+ (LSB) Core Specification.
- On Windows, ensure that a non-absolute path
specification is interpreted relative
to 's current directory
(Kumar Rajeev Rastogi)
@@ -10327,7 +10563,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Allow sizeof() in ECPG
+ Allow sizeof() in ECPG
C array definitions (Michael Meskes)
@@ -10335,7 +10571,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Make ECPG properly handle nesting
- of C-style comments in both C and SQL text
+ of C-style comments in both C and SQL text
(Michael Meskes)
@@ -10343,21 +10579,21 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- <xref linkend="APP-PSQL">
+ <xref linkend="app-psql">
- Suppress No rows output in psql
mode when the footer is disabled (Bruce Momjian)
- Allow Control-C to abort psql when it's hung at
+ Allow Control-C to abort psql when it's hung at
connection startup (Peter Eisentraut)
@@ -10365,28 +10601,28 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- <link linkend="APP-PSQL-meta-commands">Backslash Commands</link>
+ <link linkend="app-psql-meta-commands">Backslash Commands</link>
- Make psql's \db+ show tablespace options
+ Make psql's \db+ show tablespace options
(Magnus Hagander)
- Make \do+ display the functions
+ Make \do+ display the functions
that implement the operators (Marko Tiikkaja)
- Make \d+ output an
- OID line only if an oid column
+ Make \d+ output an
+ OID line only if an oid column
exists in the table (Bruce Momjian)
@@ -10398,7 +10634,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Make \d show disabled system triggers (Bruce
+ Make \d show disabled system triggers (Bruce
Momjian)
@@ -10410,55 +10646,55 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Fix \copy to no longer require
- a space between stdin and a semicolon (Etsuro Fujita)
+ Fix \copy to no longer require
+ a space between stdin and a semicolon (Etsuro Fujita)
- Output the row count at the end of \copy, just
- like COPY already did (Kumar Rajeev Rastogi)
+ Output the row count at the end of \copy, just
+ like COPY already did (Kumar Rajeev Rastogi)
- Fix \conninfo to display the
- server's IP address for connections using
- hostaddr (Fujii Masao)
+ Fix \conninfo to display the
+ server's IP address for connections using
+ hostaddr (Fujii Masao)
- Previously \conninfo could not display the server's
- IP address in such cases.
+ Previously \conninfo could not display the server's
+ IP address in such cases.
- Show the SSL protocol version in
- \conninfo (Marko Kreen)
+ Show the SSL protocol version in
+ \conninfo (Marko Kreen)
- Add tab completion for \pset
+ Add tab completion for \pset
(Pavel Stehule)
- Allow \pset with no arguments
+ Allow \pset with no arguments
to show all settings (Gilles Darold)
- Make \s display the name of the history file it wrote
+ Make \s display the name of the history file it wrote
without converting it to an absolute path (Tom Lane)
@@ -10475,14 +10711,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- <xref linkend="APP-PGDUMP">
+ <xref linkend="app-pgdump">
- Allow options
-
@@ -10493,17 +10729,17 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Optionally add IF EXISTS clauses to the DROP
+ Optionally add IF EXISTS clauses to the DROP
commands emitted when removing old objects during a restore (Pavel
Stehule)
This change prevents unnecessary errors when removing old objects.
- The new
@@ -10518,20 +10754,20 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add pg_basebackup option
- Allow pg_basebackup to relocate tablespaces in
+ Allow pg_basebackup to relocate tablespaces in
the backup copy (Steeve Lennmark)
- This is particularly useful for using pg_basebackup
+ This is particularly useful for using pg_basebackup
on the same machine as the primary.
@@ -10542,8 +10778,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- This can be controlled with the pg_basebackup
- parameter.
@@ -10574,13 +10810,13 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
No longer require function prototypes for functions marked with the
- PG_FUNCTION_INFO_V1
+ PG_FUNCTION_INFO_V1
macro (Peter Eisentraut)
This change eliminates the need to write boilerplate prototypes.
- Note that the PG_FUNCTION_INFO_V1 macro must appear
+ Note that the PG_FUNCTION_INFO_V1 macro must appear
before the corresponding function definition to avoid compiler
warnings.
@@ -10588,41 +10824,41 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Remove SnapshotNow and
- HeapTupleSatisfiesNow() (Robert Haas)
+ Remove SnapshotNow and
+ HeapTupleSatisfiesNow() (Robert Haas)
All existing uses have been switched to more appropriate snapshot
- types. Catalog scans now use MVCC snapshots.
+ types. Catalog scans now use MVCC snapshots.
- Add an API to allow memory allocations over one gigabyte
+ Add an API to allow memory allocations over one gigabyte
(Noah Misch)
- Add psprintf() to simplify memory allocation during
+ Add psprintf() to simplify memory allocation during
string composition (Peter Eisentraut, Tom Lane)
- Support printf() size modifier z to
- print size_t values (Andres Freund)
+ Support printf() size modifier z to
+ print size_t values (Andres Freund)
- Change API of appendStringInfoVA()
- to better use vsnprintf() (David Rowley, Tom Lane)
+ Change API of appendStringInfoVA()
+ to better use vsnprintf() (David Rowley, Tom Lane)
@@ -10642,7 +10878,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Improve spinlock speed on x86_64 CPUs (Heikki
+ Improve spinlock speed on x86_64 CPUs (Heikki
Linnakangas)
@@ -10650,56 +10886,56 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Remove spinlock support for unsupported platforms
- SINIX, Sun3, and
- NS32K (Robert Haas)
+ SINIX, Sun3, and
+ NS32K (Robert Haas)
- Remove IRIX port (Robert Haas)
+ Remove IRIX port (Robert Haas)
Reduce the number of semaphores required by
- builds (Robert Haas)
- Rewrite duplicate_oids Unix shell script in
- Perl (Andrew Dunstan)
+ Rewrite duplicate_oids Unix shell script in
+ Perl (Andrew Dunstan)
- Add Test Anything Protocol (TAP) tests for client
+ Add Test Anything Protocol (TAP) tests for client
programs (Peter Eisentraut)
- Currently, these tests are run by make check-world
- only if the
- Add make targets and
+ , which allow selection of individual
tests to be run (Andrew Dunstan)
- Remove makefile rule (Peter Eisentraut)
@@ -10709,7 +10945,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Improve support for VPATH builds of PGXS
+ Improve support for VPATH builds of PGXS
modules (Cédric Villemain, Andrew Dunstan, Peter Eisentraut)
@@ -10722,8 +10958,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add a configure flag that appends custom text to the
- PG_VERSION string (Oskari Saarenmaa)
+ Add a configure flag that appends custom text to the
+ PG_VERSION string (Oskari Saarenmaa)
@@ -10733,46 +10969,46 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Improve DocBook XML validity (Peter Eisentraut)
+ Improve DocBook XML validity (Peter Eisentraut)
Fix various minor security and sanity issues reported by the
- Coverity scanner (Stephen Frost)
+ Coverity scanner (Stephen Frost)
Improve detection of invalid memory usage when testing
- PostgreSQL with Valgrind
+ PostgreSQL with Valgrind
(Noah Misch)
- Improve sample Emacs configuration file
- emacs.samples (Peter Eisentraut)
+ Improve sample Emacs configuration file
+ emacs.samples (Peter Eisentraut)
- Also add .dir-locals.el to the top of the source tree.
+ Also add .dir-locals.el to the top of the source tree.
- Allow pgindent to accept a command-line list
+ Allow pgindent to accept a command-line list
of typedefs (Bruce Momjian)
- Make pgindent smarter about blank lines
+ Make pgindent smarter about blank lines
around preprocessor conditionals (Bruce Momjian)
@@ -10780,14 +11016,14 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Avoid most uses of dlltool
- in Cygwin and
- Mingw builds (Marco Atzeri, Hiroshi Inoue)
+ in Cygwin and
+ Mingw builds (Marco Atzeri, Hiroshi Inoue)
- Support client-only installs in MSVC (Windows) builds
+ Support client-only installs in MSVC (Windows) builds
(MauMau)
@@ -10814,13 +11050,13 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add UUID random number generator
- gen_random_uuid() to
+ Add UUID random number generator
+ gen_random_uuid() to
(Oskari Saarenmaa)
- This allows creation of version 4 UUIDs without
+ This allows creation of version 4 UUIDs without
requiring installation of .
@@ -10828,12 +11064,12 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
Allow to work with
- the BSD or e2fsprogs UUID libraries,
- not only the OSSP UUID library (Matteo Beccati)
+ the BSD or e2fsprogs UUID libraries,
+ not only the OSSP UUID library (Matteo Beccati)
- This improves the uuid-ossp module's portability
+ This improves the uuid-ossp module's portability
since it no longer has to have the increasingly-obsolete OSSP
library. The module's name is now rather a misnomer, but we won't
change it.
@@ -10887,8 +11123,8 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Allow pg_xlogdump
- to report a live log stream with
(Heikki Linnakangas)
@@ -10920,7 +11156,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Pass 's user name (
@@ -10934,31 +11170,31 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Remove line length limit for pgbench scripts (Sawada
+ Remove line length limit for pgbench scripts (Sawada
Masahiko)
- The previous line limit was BUFSIZ.
+ The previous line limit was BUFSIZ.
- Add long option names to pgbench (Fabien Coelho)
+ Add long option names to pgbench (Fabien Coelho)
- Add pgbench option to control
the transaction rate (Fabien Coelho)
- Add pgbench option to
print periodic progress reports
(Fabien Coelho)
@@ -10975,7 +11211,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Make pg_stat_statements use a file, rather than
+ Make pg_stat_statements use a file, rather than
shared memory, for query text storage (Peter Geoghegan)
@@ -10987,7 +11223,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Allow reporting of pg_stat_statements's internal
+ Allow reporting of pg_stat_statements's internal
query hash identifier (Daniel Farina, Sameer Thakur, Peter
Geoghegan)
@@ -10995,7 +11231,7 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Add the ability to retrieve all pg_stat_statements
+ Add the ability to retrieve all pg_stat_statements
information except the query text (Peter Geoghegan)
@@ -11008,20 +11244,20 @@ Branch: REL9_4_STABLE [c2b06ab17] 2015-01-30 22:45:58 -0500
- Make pg_stat_statements ignore DEALLOCATE
+ Make pg_stat_statements ignore DEALLOCATE
commands (Fabien Coelho)
- It already ignored PREPARE, as well as planning time in
+ It already ignored PREPARE, as well as planning time in
general, so this seems more consistent.
- Save the statistics file into $PGDATA/pg_stat at server
- shutdown, rather than $PGDATA/global (Fujii Masao)
+ Save the statistics file into $PGDATA/pg_stat at server
+ shutdown, rather than $PGDATA/global (Fujii Masao)
diff --git a/doc/src/sgml/release-9.5.sgml b/doc/src/sgml/release-9.5.sgml
index 0f700dd5d31..3ab5df7a5f4 100644
--- a/doc/src/sgml/release-9.5.sgml
+++ b/doc/src/sgml/release-9.5.sgml
@@ -1,6 +1,294 @@
+
+ Release 9.5.10
+
+
+ Release date:
+ 2017-11-09
+
+
+
+ This release contains a variety of fixes from 9.5.9.
+ For information about new features in the 9.5 major release, see
+ .
+
+
+
+ Migration to Version 9.5.10
+
+
+ A dump/restore is not required for those running 9.5.X.
+
+
+
+ However, if you use BRIN indexes, see the first changelog entry below.
+
+
+
+ Also, if you are upgrading from a version earlier than 9.5.8,
+ see .
+
+
+
+
+ Changes
+
+
+
+
+
+ Fix BRIN index summarization to handle concurrent table extension
+ correctly (Álvaro Herrera)
+
+
+
+ Previously, a race condition allowed some table rows to be omitted from
+ the index. It may be necessary to reindex existing BRIN indexes to
+ recover from past occurrences of this problem.
+
+
+
+
+
+ Fix possible failures during concurrent updates of a BRIN index
+ (Tom Lane)
+
+
+
+ These race conditions could result in errors like invalid index
+ offnum or inconsistent range map.
+
+
+
+
+
+ Fix crash when logical decoding is invoked from a SPI-using function,
+ in particular any function written in a PL language
+ (Tom Lane)
+
+
+
+
+
+ Fix json_build_array(),
+ json_build_object(), and their jsonb
+ equivalents to handle explicit VARIADIC arguments
+ correctly (Michael Paquier)
+
+
+
+
+
+ Properly reject attempts to convert infinite float values to
+ type numeric (Tom Lane, KaiGai Kohei)
+
+
+
+ Previously the behavior was platform-dependent.
+
+
+
+
+
+ Fix corner-case crashes when columns have been added to the end of a
+ view (Tom Lane)
+
+
+
+
+
+ Record proper dependencies when a view or rule
+ contains FieldSelect
+ or FieldStore expression nodes (Tom Lane)
+
+
+
+ Lack of these dependencies could allow a column or data
+ type DROP 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.
+
+
+
+
+
+ Correctly detect hashability of range data types (Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+ Correctly ignore RelabelType expression nodes
+ when determining relation distinctness (David Rowley)
+
+
+
+ This allows the intended optimization to occur when a subquery has
+ a result column of type varchar.
+
+
+
+
+
+ Fix low-probability loss of NOTIFY messages due to
+ XID wraparound (Marko Tiikkaja, Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+ Avoid SIGBUS crash on Linux when a DSM memory
+ request exceeds the space available in tmpfs
+ (Thomas Munro)
+
+
+
+
+
+ Prevent low-probability crash in processing of nested trigger firings
+ (Tom Lane)
+
+
+
+
+
+ Allow COPY's FREEZE option to
+ work when the transaction isolation level is REPEATABLE
+ READ or higher (Noah Misch)
+
+
+
+ This case was unintentionally broken by a previous bug fix.
+
+
+
+
+
+ Correctly restore the umask setting when file creation fails
+ in COPY or lo_export()
+ (Peter Eisentraut)
+
+
+
+
+
+ Give a better error message for duplicate column names
+ in ANALYZE (Nathan Bossart)
+
+
+
+
+
+ Fix mis-parsing of the last line in a
+ non-newline-terminated pg_hba.conf file
+ (Tom Lane)
+
+
+
+
+
+ Fix pg_basebackup's matching of tablespace
+ paths to canonicalize both paths before comparing (Michael Paquier)
+
+
+
+ This is particularly helpful on Windows.
+
+
+
+
+
+ Fix libpq to not require user's home
+ directory to exist (Tom Lane)
+
+
+
+ In v10, failure to find the home directory while trying to
+ read ~/.pgpass 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 ~/.pg_service.conf, though this was less
+ obvious since that file is not sought unless a service name is
+ specified.
+
+
+
+
+
+ Fix libpq to guard against integer
+ overflow in the row count of a PGresult
+ (Michael Paquier)
+
+
+
+
+
+ Fix ecpg's handling of out-of-scope cursor
+ declarations with pointer or array variables (Michael Meskes)
+
+
+
+
+
+ In ecpglib, correctly handle backslashes in string literals depending
+ on whether standard_conforming_strings is set
+ (Tsunakawa Takayuki)
+
+
+
+
+
+ Make ecpglib's Informix-compatibility mode ignore fractional digits in
+ integer input strings, as expected (Gao Zengqi, Michael Meskes)
+
+
+
+
+
+ Sync our copy of the timezone library with IANA release tzcode2017c
+ (Tom Lane)
+
+
+
+ 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 posixrules file exists in the timezone data
+ directory, now match current US law rather than what it was a dozen
+ years ago.
+
+
+
+
+
+ Update time zone data files to tzdata
+ 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.
+
+
+
+
+
+
+
+
Release 9.5.9
@@ -36,20 +324,20 @@
Show foreign tables
- in information_schema.table_privileges
+ in information_schema.table_privileges
view (Peter Eisentraut)
- All other relevant information_schema views include
+ All other relevant information_schema views include
foreign tables, but this one ignored them.
- Since this view definition is installed by initdb,
+ Since this view definition is installed by initdb,
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 psql:
+ in psql:
SET search_path TO information_schema;
CREATE OR REPLACE VIEW table_privileges AS
@@ -88,21 +376,21 @@ CREATE OR REPLACE VIEW table_privileges AS
OR grantee.rolname = 'PUBLIC');
This must be repeated in each database to be fixed,
- including template0.
+ including template0.
Clean up handling of a fatal exit (e.g., due to receipt
- of SIGTERM) that occurs while trying to execute
- a ROLLBACK of a failed transaction (Tom Lane)
+ of SIGTERM) that occurs while trying to execute
+ a ROLLBACK of a failed transaction (Tom Lane)
This situation could result in an assertion failure. In production
builds, the exit would still occur, but it would log an unexpected
- message about cannot drop active portal.
+ message about cannot drop active portal.
@@ -119,7 +407,7 @@ CREATE OR REPLACE VIEW table_privileges AS
- Certain ALTER commands that change the definition of a
+ Certain ALTER 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,
@@ -131,7 +419,7 @@ CREATE OR REPLACE VIEW table_privileges AS
- Fix crash in pg_restore when using parallel mode and
+ Fix crash in pg_restore when using parallel mode and
using a list file to select a subset of items to restore
(Fabrízio de Royes Mello)
@@ -139,13 +427,13 @@ CREATE OR REPLACE VIEW table_privileges AS
- Change ecpg's parser to allow RETURNING
+ Change ecpg's parser to allow RETURNING
clauses without attached C variables (Michael Meskes)
- This allows ecpg programs to contain SQL constructs
- that use RETURNING internally (for example, inside a CTE)
+ This allows ecpg programs to contain SQL constructs
+ that use RETURNING internally (for example, inside a CTE)
rather than using it to define values to be returned to the client.
@@ -157,18 +445,18 @@ CREATE OR REPLACE VIEW table_privileges AS
This fix avoids possible crashes of PL/Perl due to inconsistent
- assumptions about the width of time_t values.
+ assumptions about the width of time_t values.
A side-effect that may be visible to extension developers is
- that _USE_32BIT_TIME_T is no longer defined globally
- in PostgreSQL Windows builds. This is not expected
- to cause problems, because type time_t is not used
- in any PostgreSQL API definitions.
+ that _USE_32BIT_TIME_T is no longer defined globally
+ in PostgreSQL Windows builds. This is not expected
+ to cause problems, because type time_t is not used
+ in any PostgreSQL API definitions.
- Fix make check to behave correctly when invoked via a
+ Fix make check to behave correctly when invoked via a
non-GNU make program (Thomas Munro)
@@ -218,7 +506,7 @@ CREATE OR REPLACE VIEW table_privileges AS
Further restrict visibility
- of pg_user_mappings.umoptions, to
+ of pg_user_mappings.umoptions, to
protect passwords stored as user mapping options
(Noah Misch)
@@ -226,11 +514,11 @@ CREATE OR REPLACE VIEW table_privileges AS
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 USAGE permission on the associated foreign server.
+ have USAGE 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 information_schema.user_mapping_options does not
- show the options in such cases, pg_user_mappings
+ Since information_schema.user_mapping_options does not
+ show the options in such cases, pg_user_mappings
should not either.
(CVE-2017-7547)
@@ -245,15 +533,15 @@ CREATE OR REPLACE VIEW table_privileges AS
Restart the postmaster after adding allow_system_table_mods
- = true to postgresql.conf. (In versions
- supporting ALTER SYSTEM, you can use that to make the
+ = true to postgresql.conf. (In versions
+ supporting ALTER SYSTEM, you can use that to make the
configuration change, but you'll still need a restart.)
- In each database of the cluster,
+ In each database of the cluster,
run the following commands as superuser:
SET search_path = pg_catalog;
@@ -284,15 +572,15 @@ CREATE OR REPLACE VIEW pg_user_mappings AS
- Do not forget to include the template0
- and template1 databases, or the vulnerability will still
- exist in databases you create later. To fix template0,
+ Do not forget to include the template0
+ and template1 databases, or the vulnerability will still
+ exist in databases you create later. To fix template0,
you'll need to temporarily make it accept connections.
- In PostgreSQL 9.5 and later, you can use
+ In PostgreSQL 9.5 and later, you can use
ALTER DATABASE template0 WITH ALLOW_CONNECTIONS true;
- and then after fixing template0, undo that with
+ and then after fixing template0, undo that with
ALTER DATABASE template0 WITH ALLOW_CONNECTIONS false;
@@ -306,7 +594,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Finally, remove the allow_system_table_mods configuration
+ Finally, remove the allow_system_table_mods configuration
setting, and again restart the postmaster.
@@ -320,16 +608,16 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- libpq ignores empty password specifications, and does
+ libpq 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 psql or other libpq-based
+ via psql or other libpq-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-libpq-based client,
+ However, with a modified or non-libpq-based client,
logging in could be possible, depending on which authentication
method is configured. In particular the most common
- method, md5, accepted empty passwords.
+ method, md5, accepted empty passwords.
Change the server to reject empty passwords in all cases.
(CVE-2017-7546)
@@ -337,13 +625,13 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Make lo_put() check for UPDATE privilege on
+ Make lo_put() check for UPDATE privilege on
the target large object (Tom Lane, Michael Paquier)
- lo_put() should surely require the same permissions
- as lowrite(), but the check was missing, allowing any
+ lo_put() should surely require the same permissions
+ as lowrite(), but the check was missing, allowing any
user to change the data in a large object.
(CVE-2017-7548)
@@ -352,12 +640,12 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Correct the documentation about the process for upgrading standby
- servers with pg_upgrade (Bruce Momjian)
+ servers with pg_upgrade (Bruce Momjian)
The previous documentation instructed users to start/stop the primary
- server after running pg_upgrade but before syncing
+ server after running pg_upgrade but before syncing
the standby servers. This sequence is unsafe.
@@ -463,21 +751,21 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Fix possible creation of an invalid WAL segment when a standby is
- promoted just after it processes an XLOG_SWITCH WAL
+ promoted just after it processes an XLOG_SWITCH WAL
record (Andres Freund)
- Fix walsender to exit promptly when client requests
+ Fix walsender to exit promptly when client requests
shutdown (Tom Lane)
- Fix SIGHUP and SIGUSR1 handling in
+ Fix SIGHUP and SIGUSR1 handling in
walsender processes (Petr Jelinek, Andres Freund)
@@ -491,7 +779,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix unnecessarily slow restarts of walreceiver
+ Fix unnecessarily slow restarts of walreceiver
processes due to race condition in postmaster (Tom Lane)
@@ -539,7 +827,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix cases where an INSERT or UPDATE assigns
+ Fix cases where an INSERT or UPDATE assigns
to more than one element of a column that is of domain-over-array
type (Tom Lane)
@@ -547,7 +835,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Allow window functions to be used in sub-SELECTs that
+ Allow window functions to be used in sub-SELECTs that
are within the arguments of an aggregate function (Tom Lane)
@@ -555,19 +843,19 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Move autogenerated array types out of the way during
- ALTER ... RENAME (Vik Fearing)
+ ALTER ... RENAME (Vik Fearing)
Previously, we would rename a conflicting autogenerated array type
- out of the way during CREATE; this fix extends that
+ out of the way during CREATE; this fix extends that
behavior to renaming operations.
- Fix dangling pointer in ALTER TABLE when there is a
+ Fix dangling pointer in ALTER TABLE when there is a
comment on a constraint belonging to the table (David Rowley)
@@ -579,44 +867,44 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Ensure that ALTER USER ... SET accepts all the syntax
- variants that ALTER ROLE ... SET does (Peter Eisentraut)
+ Ensure that ALTER USER ... SET accepts all the syntax
+ variants that ALTER ROLE ... SET does (Peter Eisentraut)
Properly update dependency info when changing a datatype I/O
- function's argument or return type from opaque to the
+ function's argument or return type from opaque to the
correct type (Heikki Linnakangas)
- CREATE TYPE updates I/O functions declared in this
+ CREATE TYPE updates I/O functions declared in this
long-obsolete style, but it forgot to record a dependency on the
- type, allowing a subsequent DROP TYPE to leave broken
+ type, allowing a subsequent DROP TYPE to leave broken
function definitions behind.
- Reduce memory usage when ANALYZE processes
- a tsvector column (Heikki Linnakangas)
+ Reduce memory usage when ANALYZE processes
+ a tsvector column (Heikki Linnakangas)
Fix unnecessary precision loss and sloppy rounding when multiplying
- or dividing money values by integers or floats (Tom Lane)
+ or dividing money values by integers or floats (Tom Lane)
Tighten checks for whitespace in functions that parse identifiers,
- such as regprocedurein() (Tom Lane)
+ such as regprocedurein() (Tom Lane)
@@ -627,20 +915,20 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Use relevant #define symbols from Perl while
- compiling PL/Perl (Ashutosh Sharma, Tom Lane)
+ Use relevant #define symbols from Perl while
+ compiling PL/Perl (Ashutosh Sharma, Tom Lane)
This avoids portability problems, typically manifesting as
- a handshake mismatch during library load, when working with
+ a handshake mismatch during library load, when working with
recent Perl versions.
- In libpq, reset GSS/SASL and SSPI authentication
+ In libpq, reset GSS/SASL and SSPI authentication
state properly after a failed connection attempt (Michael Paquier)
@@ -653,9 +941,9 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- In psql, fix failure when COPY FROM STDIN
+ In psql, fix failure when COPY FROM STDIN
is ended with a keyboard EOF signal and then another COPY
- FROM STDIN is attempted (Thomas Munro)
+ FROM STDIN is attempted (Thomas Munro)
@@ -666,8 +954,8 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_dump and pg_restore to
- emit REFRESH MATERIALIZED VIEW commands last (Tom Lane)
+ Fix pg_dump and pg_restore to
+ emit REFRESH MATERIALIZED VIEW commands last (Tom Lane)
@@ -678,15 +966,15 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Improve pg_dump/pg_restore's
- reporting of error conditions originating in zlib
+ Improve pg_dump/pg_restore's
+ reporting of error conditions originating in zlib
(Vladimir Kunschikov, Álvaro Herrera)
- Fix pg_dump with the option to
drop event triggers as expected (Tom Lane)
@@ -699,14 +987,14 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_dump to not emit invalid SQL for an empty
+ Fix pg_dump to not emit invalid SQL for an empty
operator class (Daniel Gustafsson)
- Fix pg_dump output to stdout on Windows (Kuntal Ghosh)
+ Fix pg_dump output to stdout on Windows (Kuntal Ghosh)
@@ -717,14 +1005,14 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_get_ruledef() to print correct output for
- the ON SELECT rule of a view whose columns have been
+ Fix pg_get_ruledef() to print correct output for
+ the ON SELECT rule of a view whose columns have been
renamed (Tom Lane)
- In some corner cases, pg_dump relies
- on pg_get_ruledef() to dump views, so that this error
+ In some corner cases, pg_dump relies
+ on pg_get_ruledef() to dump views, so that this error
could result in dump/reload failures.
@@ -732,13 +1020,13 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
Fix dumping of outer joins with empty constraints, such as the result
- of a NATURAL LEFT JOIN with no common columns (Tom Lane)
+ of a NATURAL LEFT JOIN with no common columns (Tom Lane)
- Fix dumping of function expressions in the FROM clause in
+ Fix dumping of function expressions in the FROM clause in
cases where the expression does not deparse into something that looks
like a function call (Tom Lane)
@@ -746,7 +1034,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_basebackup output to stdout on Windows
+ Fix pg_basebackup output to stdout on Windows
(Haribabu Kommi)
@@ -758,20 +1046,20 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_rewind to correctly handle files exceeding 2GB
+ Fix pg_rewind to correctly handle files exceeding 2GB
(Kuntal Ghosh, Michael Paquier)
- Ordinarily such files won't appear in PostgreSQL data
+ Ordinarily such files won't appear in PostgreSQL data
directories, but they could be present in some cases.
- Fix pg_upgrade to ensure that the ending WAL record
- does not have = minimum
+ Fix pg_upgrade to ensure that the ending WAL record
+ does not have = minimum
(Bruce Momjian)
@@ -783,16 +1071,16 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Fix pg_xlogdump's computation of WAL record length
+ Fix pg_xlogdump's computation of WAL record length
(Andres Freund)
- In postgres_fdw, re-establish connections to remote
- servers after ALTER SERVER or ALTER USER
- MAPPING commands (Kyotaro Horiguchi)
+ In postgres_fdw, re-establish connections to remote
+ servers after ALTER SERVER or ALTER USER
+ MAPPING commands (Kyotaro Horiguchi)
@@ -803,7 +1091,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- In postgres_fdw, allow cancellation of remote
+ In postgres_fdw, allow cancellation of remote
transaction control commands (Robert Haas, Rafia Sabih)
@@ -815,14 +1103,14 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Increase MAX_SYSCACHE_CALLBACKS to provide more room for
+ Increase MAX_SYSCACHE_CALLBACKS to provide more room for
extensions (Tom Lane)
- Always use , not , when building
shared libraries with gcc (Tom Lane)
@@ -849,34 +1137,34 @@ Branch: REL9_2_STABLE [1188b9b2c] 2017-08-02 15:07:21 -0400
- In MSVC builds, handle the case where the openssl
- library is not within a VC subdirectory (Andrew Dunstan)
+ In MSVC builds, handle the case where the openssl
+ library is not within a VC subdirectory (Andrew Dunstan)
- In MSVC builds, add proper include path for libxml2
+ In MSVC builds, add proper include path for libxml2
header files (Andrew Dunstan)
This fixes a former need to move things around in standard Windows
- installations of libxml2.
+ installations of libxml2.
In MSVC builds, recognize a Tcl library that is
- named tcl86.lib (Noah Misch)
+ named tcl86.lib (Noah Misch)
- In MSVC builds, honor PROVE_FLAGS settings
- on vcregress.pl's command line (Andrew Dunstan)
+ In MSVC builds, honor PROVE_FLAGS settings
+ on vcregress.pl's command line (Andrew Dunstan)
@@ -913,7 +1201,7 @@ Branch: REL9_2_STABLE [1188b9b2c] 2017-08-02 15:07:21 -0400
Also, if you are using third-party replication tools that depend
- on logical decoding, see the fourth changelog entry below.
+ on logical decoding, see the fourth changelog entry below.
@@ -930,18 +1218,18 @@ Branch: REL9_2_STABLE [1188b9b2c] 2017-08-02 15:07:21 -0400
Restrict visibility
- of pg_user_mappings.umoptions, to
+ of pg_user_mappings.umoptions, to
protect passwords stored as user mapping options
(Michael Paquier, Feike Steenbergen)
The previous coding allowed the owner of a foreign server object,
- or anyone he has granted server USAGE permission to,
+ or anyone he has granted server USAGE 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
- information_schema.user_mapping_options, namely that
+ information_schema.user_mapping_options, namely that
these options are visible to the user being mapped, or if the mapping
is for PUBLIC and the current user is the server
owner, or if the current user is a superuser.
@@ -965,7 +1253,7 @@ Branch: REL9_2_STABLE [1188b9b2c] 2017-08-02 15:07:21 -0400
Some selectivity estimation functions in the planner will apply
user-defined operators to values obtained
- from pg_statistic, such as most common values and
+ from pg_statistic, 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,
@@ -979,17 +1267,17 @@ Branch: REL9_2_STABLE [1188b9b2c] 2017-08-02 15:07:21 -0400
- Restore libpq's recognition of
- the PGREQUIRESSL environment variable (Daniel Gustafsson)
+ Restore libpq's recognition of
+ the PGREQUIRESSL environment variable (Daniel Gustafsson)
Processing of this environment variable was unintentionally dropped
- in PostgreSQL 9.3, but its documentation remained.
+ in PostgreSQL 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 PGSSLMODE, to avoid
+ but give it lower priority than PGSSLMODE, to avoid
breaking configurations that work correctly with post-9.3 code.
(CVE-2017-7485)
@@ -1020,7 +1308,7 @@ Branch: REL9_2_STABLE [1188b9b2c] 2017-08-02 15:07:21 -0400
- Fix possible corruption of init forks of unlogged indexes
+ Fix possible corruption of init forks of unlogged indexes
(Robert Haas, Michael Paquier)
@@ -1033,7 +1321,7 @@ Branch: REL9_2_STABLE [1188b9b2c] 2017-08-02 15:07:21 -0400
- Fix incorrect reconstruction of pg_subtrans entries
+ Fix incorrect reconstruction of pg_subtrans entries
when a standby server replays a prepared but uncommitted two-phase
transaction (Tom Lane)
@@ -1041,14 +1329,14 @@ Branch: REL9_2_STABLE [1188b9b2c] 2017-08-02 15:07:21 -0400
In most cases this turned out to have no visible ill effects, but in
corner cases it could result in circular references
- in pg_subtrans, potentially causing infinite loops
+ in pg_subtrans, potentially causing infinite loops
in queries that examine rows modified by the two-phase transaction.
- Avoid possible crash in walsender due to failure
+ Avoid possible crash in walsender due to failure
to initialize a string buffer (Stas Kelvich, Fujii Masao)
@@ -1062,7 +1350,7 @@ Branch: REL9_2_STABLE [1188b9b2c] 2017-08-02 15:07:21 -0400
- Fix postmaster's handling of fork() failure for a
+ Fix postmaster's handling of fork() failure for a
background worker process (Tom Lane)
@@ -1079,14 +1367,14 @@ Author: Andrew Gierth
Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
-->
- Fix crash or wrong answers when a GROUPING SETS column's
+ Fix crash or wrong answers when a GROUPING SETS column's
data type is hashable but not sortable (Pavan Deolasee)
- Avoid applying physical targetlist optimization to custom
+ Avoid applying physical targetlist optimization to custom
scans (Dmitry Ivanov, Tom Lane)
@@ -1099,13 +1387,13 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
- Use the correct sub-expression when applying a FOR ALL
+ Use the correct sub-expression when applying a FOR ALL
row-level-security policy (Stephen Frost)
- In some cases the WITH CHECK restriction would be applied
- when the USING restriction is more appropriate.
+ In some cases the WITH CHECK restriction would be applied
+ when the USING restriction is more appropriate.
@@ -1119,19 +1407,19 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
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 ALTER TABLE
- ... RENAME.
+ ... RENAME.
Skip tablespace privilege checks when ALTER TABLE ... ALTER
- COLUMN TYPE rebuilds an existing index (Noah Misch)
+ COLUMN TYPE rebuilds an existing index (Noah Misch)
The command failed if the calling user did not currently have
- CREATE privilege for the tablespace containing the index.
+ CREATE privilege for the tablespace containing the index.
That behavior seems unhelpful, so skip the check, allowing the
index to be rebuilt where it is.
@@ -1139,20 +1427,20 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
- Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse
- to child tables when the constraint is marked NO INHERIT
+ Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse
+ to child tables when the constraint is marked NO INHERIT
(Amit Langote)
- This fix prevents unwanted constraint does not exist failures
+ This fix prevents unwanted constraint does not exist failures
when no matching constraint is present in the child tables.
- Avoid dangling pointer in COPY ... TO when row-level
+ Avoid dangling pointer in COPY ... TO when row-level
security is active for the source table (Tom Lane)
@@ -1164,8 +1452,8 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
- Avoid accessing an already-closed relcache entry in CLUSTER
- and VACUUM FULL (Tom Lane)
+ Avoid accessing an already-closed relcache entry in CLUSTER
+ and VACUUM FULL (Tom Lane)
@@ -1176,14 +1464,14 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
- Fix VACUUM to account properly for pages that could not
+ Fix VACUUM to account properly for pages that could not
be scanned due to conflicting page pins (Andrew Gierth)
This tended to lead to underestimation of the number of tuples in
the table. In the worst case of a small heavily-contended
- table, VACUUM could incorrectly report that the table
+ table, VACUUM could incorrectly report that the table
contained no tuples, leading to very bad planning choices.
@@ -1197,12 +1485,12 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
- Fix integer-overflow problems in interval comparison (Kyotaro
+ Fix integer-overflow problems in interval comparison (Kyotaro
Horiguchi, Tom Lane)
- The comparison operators for type interval could yield wrong
+ The comparison operators for type interval could yield wrong
answers for intervals larger than about 296000 years. Indexes on
columns containing such large values should be reindexed, since they
may be corrupt.
@@ -1211,21 +1499,21 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
- Fix cursor_to_xml() to produce valid output
- with tableforest = false
+ Fix cursor_to_xml() to produce valid output
+ with tableforest = false
(Thomas Munro, Peter Eisentraut)
- Previously it failed to produce a wrapping <table>
+ Previously it failed to produce a wrapping <table>
element.
- Fix roundoff problems in float8_timestamptz()
- and make_interval() (Tom Lane)
+ Fix roundoff problems in float8_timestamptz()
+ and make_interval() (Tom Lane)
@@ -1237,14 +1525,14 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
- Fix pg_get_object_address() to handle members of operator
+ Fix pg_get_object_address() to handle members of operator
families correctly (Álvaro Herrera)
- Improve performance of pg_timezone_names view
+ Improve performance of pg_timezone_names view
(Tom Lane, David Rowley)
@@ -1258,13 +1546,13 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
- Fix sloppy handling of corner-case errors from lseek()
- and close() (Tom Lane)
+ Fix sloppy handling of corner-case errors from lseek()
+ and close() (Tom Lane)
Neither of these system calls are likely to fail in typical situations,
- but if they did, fd.c could get quite confused.
+ but if they did, fd.c could get quite confused.
@@ -1282,21 +1570,21 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
- Fix ecpg to support COMMIT PREPARED
- and ROLLBACK PREPARED (Masahiko Sawada)
+ Fix ecpg to support COMMIT PREPARED
+ and ROLLBACK PREPARED (Masahiko Sawada)
Fix a double-free error when processing dollar-quoted string literals
- in ecpg (Michael Meskes)
+ in ecpg (Michael Meskes)
- In pg_dump, fix incorrect schema and owner marking for
+ In pg_dump, fix incorrect schema and owner marking for
comments and security labels of some types of database objects
(Giuseppe Broccolo, Tom Lane)
@@ -1311,20 +1599,20 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
- Avoid emitting an invalid list file in pg_restore -l
+ Avoid emitting an invalid list file in pg_restore -l
when SQL object names contain newlines (Tom Lane)
Replace newlines by spaces, which is sufficient to make the output
- valid for pg_restore -L's purposes.
+ valid for pg_restore -L's purposes.
- Fix pg_upgrade to transfer comments and security labels
- attached to large objects (blobs) (Stephen Frost)
+ Fix pg_upgrade to transfer comments and security labels
+ attached to large objects (blobs) (Stephen Frost)
@@ -1336,26 +1624,26 @@ Branch: REL9_5_STABLE [7be3678a8] 2017-04-24 07:53:05 +0100
Improve error handling
- in contrib/adminpack's pg_file_write()
+ in contrib/adminpack's pg_file_write()
function (Noah Misch)
Notably, it failed to detect errors reported
- by fclose().
+ by fclose().
- In contrib/dblink, avoid leaking the previous unnamed
+ In contrib/dblink, avoid leaking the previous unnamed
connection when establishing a new unnamed connection (Joe Conway)
- Fix contrib/pg_trgm's extraction of trigrams from regular
+ Fix contrib/pg_trgm's extraction of trigrams from regular
expressions (Tom Lane)
@@ -1374,7 +1662,7 @@ Branch: REL9_4_STABLE [f14bf0a8f] 2017-05-06 22:19:56 -0400
Branch: REL9_3_STABLE [3aa16b117] 2017-05-06 22:17:35 -0400
-->
- In contrib/postgres_fdw,
+ In contrib/postgres_fdw,
transmit query cancellation requests to the remote server
(Michael Paquier, Etsuro Fujita)
@@ -1405,7 +1693,7 @@ Branch: REL9_3_STABLE [3aa16b117] 2017-05-06 22:17:35 -0400
- Update time zone data files to tzdata release 2017b
+ Update time zone data files to tzdata 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
@@ -1419,9 +1707,9 @@ Branch: REL9_3_STABLE [3aa16b117] 2017-05-06 22:17:35 -0400
or no currency among the local population. They are in process of
reversing that policy in favor of using numeric UTC offsets in zones
where there is no evidence of real-world use of an English
- abbreviation. At least for the time being, PostgreSQL
+ abbreviation. At least for the time being, PostgreSQL
will continue to accept such removed abbreviations for timestamp input.
- But they will not be shown in the pg_timezone_names
+ But they will not be shown in the pg_timezone_names
view nor used for output.
@@ -1434,15 +1722,15 @@ Branch: REL9_3_STABLE [3aa16b117] 2017-05-06 22:17:35 -0400
The Microsoft MSVC build scripts neglected to install
- the posixrules file in the timezone directory tree.
+ the posixrules 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 US/Eastern zone. If you don't want that, remove
- the posixrules file, or replace it with a copy of some
+ the US/Eastern zone. If you don't want that, remove
+ the posixrules file, or replace it with a copy of some
other zone file (see ). Note that
due to caching, you may need to restart the server to get such changes
to take effect.
@@ -1495,15 +1783,15 @@ Branch: REL9_3_STABLE [3aa16b117] 2017-05-06 22:17:35 -0400
Fix a race condition that could cause indexes built
- with CREATE INDEX CONCURRENTLY to be corrupt
+ with CREATE INDEX CONCURRENTLY to be corrupt
(Pavan Deolasee, Tom Lane)
- If CREATE INDEX CONCURRENTLY was used to build an index
+ If CREATE INDEX CONCURRENTLY was used to build an index
that depends on a column not previously indexed, then rows
updated by transactions that ran concurrently with
- the CREATE INDEX command could have received incorrect
+ the CREATE INDEX 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.
@@ -1520,7 +1808,7 @@ Branch: REL9_3_STABLE [3aa16b117] 2017-05-06 22:17:35 -0400
Backends failed to account for this snapshot when advertising their
oldest xmin, potentially allowing concurrent vacuuming operations to
remove data that was still needed. This led to transient failures
- along the lines of cache lookup failed for relation 1255.
+ along the lines of cache lookup failed for relation 1255.
@@ -1530,7 +1818,7 @@ Branch: REL9_3_STABLE [3aa16b117] 2017-05-06 22:17:35 -0400
- The WAL record emitted for a BRIN revmap page when moving an
+ The WAL record emitted for a BRIN revmap page when moving an
index tuple to a different page was incorrect. Replay would make the
related portion of the index useless, forcing it to be recomputed.
@@ -1538,13 +1826,13 @@ Branch: REL9_3_STABLE [3aa16b117] 2017-05-06 22:17:35 -0400
- Unconditionally WAL-log creation of the init fork for an
+ Unconditionally WAL-log creation of the init fork for an
unlogged table (Michael Paquier)
Previously, this was skipped when
- = minimal, but actually it's necessary even in that case
+ = minimal, but actually it's necessary even in that case
to ensure that the unlogged table is properly reset to empty after a
crash.
@@ -1615,7 +1903,7 @@ Branch: REL9_4_STABLE [30e3cb307] 2016-11-17 13:31:30 -0300
- Make sure ALTER TABLE preserves index tablespace
+ Make sure ALTER TABLE preserves index tablespace
assignments when rebuilding indexes (Tom Lane, Michael Paquier)
@@ -1630,7 +1918,7 @@ Branch: REL9_4_STABLE [30e3cb307] 2016-11-17 13:31:30 -0300
Fix incorrect updating of trigger function properties when changing a
foreign-key constraint's deferrability properties with ALTER
- TABLE ... ALTER CONSTRAINT (Tom Lane)
+ TABLE ... ALTER CONSTRAINT (Tom Lane)
@@ -1646,29 +1934,29 @@ Branch: REL9_4_STABLE [30e3cb307] 2016-11-17 13:31:30 -0300
- This avoids could not find trigger NNN
- or relation NNN has no triggers errors.
+ This avoids could not find trigger NNN
+ or relation NNN has no triggers errors.
- Fix ALTER TABLE ... SET DATA TYPE ... USING when child
+ Fix ALTER TABLE ... SET DATA TYPE ... USING when child
table has different column ordering than the parent
(Álvaro Herrera)
- Failure to adjust the column numbering in the USING
+ Failure to adjust the column numbering in the USING
expression led to errors,
- typically attribute N has wrong type.
+ typically attribute N has wrong type.
Fix processing of OID column when a table with OIDs is associated to
- a parent with OIDs via ALTER TABLE ... INHERIT (Amit
+ a parent with OIDs via ALTER TABLE ... INHERIT (Amit
Langote)
@@ -1681,7 +1969,7 @@ Branch: REL9_4_STABLE [30e3cb307] 2016-11-17 13:31:30 -0300
- Fix CREATE OR REPLACE VIEW to update the view query
+ Fix CREATE OR REPLACE VIEW to update the view query
before attempting to apply the new view options (Dean Rasheed)
@@ -1694,7 +1982,7 @@ Branch: REL9_4_STABLE [30e3cb307] 2016-11-17 13:31:30 -0300
Report correct object identity during ALTER TEXT SEARCH
- CONFIGURATION (Artur Zakirov)
+ CONFIGURATION (Artur Zakirov)
@@ -1706,8 +1994,8 @@ Branch: REL9_4_STABLE [30e3cb307] 2016-11-17 13:31:30 -0300
Fix commit timestamp mechanism to not fail when queried about
- the special XIDs FrozenTransactionId
- and BootstrapTransactionId (Craig Ringer)
+ the special XIDs FrozenTransactionId
+ and BootstrapTransactionId (Craig Ringer)
@@ -1745,28 +2033,28 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
The symptom was spurious ON CONFLICT is not supported on table
- ... used as a catalog table errors when the target
- of INSERT ... ON CONFLICT is a view with cascade option.
+ ... used as a catalog table errors when the target
+ of INSERT ... ON CONFLICT is a view with cascade option.
- Fix incorrect target lists can have at most N
- entries complaint when using ON CONFLICT with
+ Fix incorrect target lists can have at most N
+ entries complaint when using ON CONFLICT with
wide tables (Tom Lane)
- Prevent multicolumn expansion of foo.* in
- an UPDATE source expression (Tom Lane)
+ Prevent multicolumn expansion of foo.* in
+ an UPDATE source expression (Tom Lane)
This led to UPDATE target count mismatch --- internal
- error. Now the syntax is understood as a whole-row variable,
+ error. Now the syntax is understood as a whole-row variable,
as it would be in other contexts.
@@ -1774,12 +2062,12 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
Ensure that column typmods are determined accurately for
- multi-row VALUES constructs (Tom Lane)
+ multi-row VALUES constructs (Tom Lane)
This fixes problems occurring when the first value in a column has a
- determinable typmod (e.g., length for a varchar value) but
+ determinable typmod (e.g., length for a varchar value) but
later values don't share the same limit.
@@ -1794,15 +2082,15 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
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 (U&'...') or Unicode identifier
- (U&"...").
+ string literal (U&'...') or Unicode identifier
+ (U&"...").
Ensure that a purely negative text search query, such
- as !foo, matches empty tsvectors (Tom Dunstan)
+ as !foo, matches empty tsvectors (Tom Dunstan)
@@ -1813,20 +2101,20 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
- Prevent crash when ts_rewrite() replaces a non-top-level
+ Prevent crash when ts_rewrite() replaces a non-top-level
subtree with an empty query (Artur Zakirov)
- Fix performance problems in ts_rewrite() (Tom Lane)
+ Fix performance problems in ts_rewrite() (Tom Lane)
- Fix ts_rewrite()'s handling of nested NOT operators
+ Fix ts_rewrite()'s handling of nested NOT operators
(Tom Lane)
@@ -1834,27 +2122,27 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
Improve speed of user-defined aggregates that
- use array_append() as transition function (Tom Lane)
+ use array_append() as transition function (Tom Lane)
- Fix array_fill() to handle empty arrays properly (Tom Lane)
+ Fix array_fill() to handle empty arrays properly (Tom Lane)
- Fix possible crash in array_position()
- or array_positions() when processing arrays of records
+ Fix possible crash in array_position()
+ or array_positions() when processing arrays of records
(Junseok Yang)
- Fix one-byte buffer overrun in quote_literal_cstr()
+ Fix one-byte buffer overrun in quote_literal_cstr()
(Heikki Linnakangas)
@@ -1866,8 +2154,8 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
- Prevent multiple calls of pg_start_backup()
- and pg_stop_backup() from running concurrently (Michael
+ Prevent multiple calls of pg_start_backup()
+ and pg_stop_backup() from running concurrently (Michael
Paquier)
@@ -1880,7 +2168,7 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
Disable transform that attempted to remove no-op AT TIME
- ZONE conversions (Tom Lane)
+ ZONE conversions (Tom Lane)
@@ -1891,15 +2179,15 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
- Avoid discarding interval-to-interval casts
+ Avoid discarding interval-to-interval casts
that aren't really no-ops (Tom Lane)
In some cases, a cast that should result in zeroing out
- low-order interval fields was mistakenly deemed to be a
+ low-order interval fields was mistakenly deemed to be a
no-op and discarded. An example is that casting from INTERVAL
- MONTH to INTERVAL YEAR failed to clear the months field.
+ MONTH to INTERVAL YEAR failed to clear the months field.
@@ -1919,28 +2207,28 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
- Fix pg_dump to dump user-defined casts and transforms
+ Fix pg_dump to dump user-defined casts and transforms
that use built-in functions (Stephen Frost)
- Fix pg_restore with
to behave more sanely if an archive contains
- unrecognized DROP commands (Tom Lane)
+ unrecognized DROP commands (Tom Lane)
This doesn't fix any live bug, but it may improve the behavior in
- future if pg_restore is used with an archive
- generated by a later pg_dump version.
+ future if pg_restore is used with an archive
+ generated by a later pg_dump version.
- Fix pg_basebackup's rate limiting in the presence of
+ Fix pg_basebackup's rate limiting in the presence of
slow I/O (Antonin Houska)
@@ -1953,15 +2241,15 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
- Fix pg_basebackup's handling of
- symlinked pg_stat_tmp and pg_replslot
+ Fix pg_basebackup's handling of
+ symlinked pg_stat_tmp and pg_replslot
subdirectories (Magnus Hagander, Michael Paquier)
- Fix possible pg_basebackup failure on standby
+ Fix possible pg_basebackup failure on standby
server when including WAL files (Amit Kapila, Robert Haas)
@@ -1969,7 +2257,7 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
Fix possible mishandling of expanded arrays in domain check
- constraints and CASE execution (Tom Lane)
+ constraints and CASE execution (Tom Lane)
@@ -2001,21 +2289,21 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
- Fix PL/Tcl to support triggers on tables that have .tupno
+ Fix PL/Tcl to support triggers on tables that have .tupno
as a column name (Tom Lane)
This matches the (previously undocumented) behavior of
- PL/Tcl's spi_exec and spi_execp commands,
- namely that a magic .tupno column is inserted only if
+ PL/Tcl's spi_exec and spi_execp commands,
+ namely that a magic .tupno column is inserted only if
there isn't a real column named that.
- Allow DOS-style line endings in ~/.pgpass files,
+ Allow DOS-style line endings in ~/.pgpass files,
even on Unix (Vik Fearing)
@@ -2027,23 +2315,23 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
- Fix one-byte buffer overrun if ecpg is given a file
+ Fix one-byte buffer overrun if ecpg is given a file
name that ends with a dot (Takayuki Tsunakawa)
- Fix psql's tab completion for ALTER DEFAULT
- PRIVILEGES (Gilles Darold, Stephen Frost)
+ Fix psql's tab completion for ALTER DEFAULT
+ PRIVILEGES (Gilles Darold, Stephen Frost)
- In psql, treat an empty or all-blank setting of
- the PAGER environment variable as meaning no
- pager (Tom Lane)
+ In psql, treat an empty or all-blank setting of
+ the PAGER environment variable as meaning no
+ pager (Tom Lane)
@@ -2054,28 +2342,28 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
- Improve contrib/dblink's reporting of
- low-level libpq errors, such as out-of-memory
+ Improve contrib/dblink's reporting of
+ low-level libpq errors, such as out-of-memory
(Joe Conway)
- Teach contrib/dblink to ignore irrelevant server options
- when it uses a contrib/postgres_fdw foreign server as
+ Teach contrib/dblink to ignore irrelevant server options
+ when it uses a contrib/postgres_fdw foreign server as
the source of connection options (Corey Huinker)
Previously, if the foreign server object had options that were not
- also libpq connection options, an error occurred.
+ also libpq connection options, an error occurred.
- Fix portability problems in contrib/pageinspect's
+ Fix portability problems in contrib/pageinspect's
functions for GIN indexes (Peter Eisentraut, Tom Lane)
@@ -2102,7 +2390,7 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
- Update time zone data files to tzdata release 2016j
+ Update time zone data files to tzdata 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.
@@ -2165,7 +2453,7 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
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 could not read block XXX:
+ producing errors like could not read block XXX:
read only 0 of 8192 bytes. Checksum failures in the
visibility map are also possible, if checksumming is enabled.
@@ -2173,7 +2461,7 @@ Branch: REL9_2_STABLE [60314e28e] 2016-12-13 19:08:09 -0600
Procedures for determining whether there is a problem and repairing it
if so are discussed at
- .
+ .
@@ -2191,7 +2479,7 @@ Branch: REL9_4_STABLE [a69443564] 2016-09-03 13:28:53 -0400
- The typical symptom was unexpected GIN leaf action errors
+ The typical symptom was unexpected GIN leaf action errors
during WAL replay.
@@ -2206,13 +2494,13 @@ Branch: REL9_4_STABLE [8778da2af] 2016-09-09 15:54:29 -0300
Branch: REL9_3_STABLE [dfe7121df] 2016-09-09 15:54:29 -0300
-->
- Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that
+ Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that
have been updated by a subsequently-aborted transaction
(Álvaro Herrera)
- In 9.5 and later, the SELECT would sometimes fail to
+ In 9.5 and later, the SELECT 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.
@@ -2248,13 +2536,13 @@ Branch: REL9_5_STABLE [94bc30725] 2016-08-17 17:03:36 -0700
-->
Fix deletion of speculatively inserted TOAST tuples when backing out
- of INSERT ... ON CONFLICT (Oskari Saarenmaa)
+ of INSERT ... ON CONFLICT (Oskari Saarenmaa)
In the race condition where two transactions try to insert conflicting
tuples at about the same time, the loser would fail with
- an attempted to delete invisible tuple error if its
+ an attempted to delete invisible tuple error if its
insertion included any TOAST'ed fields.
@@ -2262,7 +2550,7 @@ Branch: REL9_5_STABLE [94bc30725] 2016-08-17 17:03:36 -0700
Don't throw serialization errors for self-conflicting insertions
- in INSERT ... ON CONFLICT (Thomas Munro, Peter Geoghegan)
+ in INSERT ... ON CONFLICT (Thomas Munro, Peter Geoghegan)
@@ -2300,29 +2588,29 @@ Branch: REL9_5_STABLE [46bd14a10] 2016-08-24 22:20:01 -0400
Branch: REL9_4_STABLE [566afa15c] 2016-08-24 22:20:01 -0400
-->
- Fix query-lifespan memory leak in a bulk UPDATE on a table
- with a PRIMARY KEY or REPLICA IDENTITY index
+ Fix query-lifespan memory leak in a bulk UPDATE on a table
+ with a PRIMARY KEY or REPLICA IDENTITY index
(Tom Lane)
- Fix COPY with a column name list from a table that has
+ Fix COPY with a column name list from a table that has
row-level security enabled (Adam Brightwell)
- Fix EXPLAIN to emit valid XML when
+ Fix EXPLAIN to emit valid XML when
is on (Markus Winand)
Previously the XML output-format option produced syntactically invalid
- tags such as <I/O-Read-Time>. That is now
- rendered as <I-O-Read-Time>.
+ tags such as <I/O-Read-Time>. That is now
+ rendered as <I-O-Read-Time>.
@@ -2337,20 +2625,20 @@ Branch: REL9_2_STABLE [ceb005319] 2016-08-12 12:13:04 -0400
-->
Suppress printing of zeroes for unmeasured times
- in EXPLAIN (Maksim Milyutin)
+ in EXPLAIN (Maksim Milyutin)
Certain option combinations resulted in printing zero values for times
that actually aren't ever measured in that combination. Our general
- policy in EXPLAIN is not to print such fields at all, so
+ policy in EXPLAIN is not to print such fields at all, so
do that consistently in all cases.
- Fix statistics update for TRUNCATE in a prepared
+ Fix statistics update for TRUNCATE in a prepared
transaction (Stas Kelvich)
@@ -2367,37 +2655,37 @@ Branch: REL9_2_STABLE [eaf6fe7fa] 2016-09-09 11:45:40 +0100
Branch: REL9_1_STABLE [3ed7f54bc] 2016-09-09 11:46:03 +0100
-->
- Fix timeout length when VACUUM is waiting for exclusive
+ Fix timeout length when VACUUM is waiting for exclusive
table lock so that it can truncate the table (Simon Riggs)
The timeout was meant to be 50 milliseconds, but it was actually only
- 50 microseconds, causing VACUUM to give up on truncation
+ 50 microseconds, causing VACUUM to give up on truncation
much more easily than intended. Set it to the intended value.
- Fix bugs in merging inherited CHECK constraints while
+ Fix bugs in merging inherited CHECK constraints while
creating or altering a table (Tom Lane, Amit Langote)
- Allow identical CHECK constraints to be added to a parent
+ Allow identical CHECK 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 NOT VALID
+ constraint from the parent table with a NOT VALID
constraint on the child. Likewise, prevent merging of a NO
- INHERIT child constraint with an inherited constraint.
+ INHERIT child constraint with an inherited constraint.
Show a sensible value
- in pg_settings.unit
- for min_wal_size and max_wal_size (Tom Lane)
+ in pg_settings.unit
+ for min_wal_size and max_wal_size (Tom Lane)
@@ -2413,15 +2701,15 @@ Branch: REL9_1_STABLE [7e01c8ef3] 2016-08-14 15:06:02 -0400
-->
Remove artificial restrictions on the values accepted
- by numeric_in() and numeric_recv()
+ by numeric_in() and numeric_recv()
(Tom Lane)
We allow numeric values up to the limit of the storage format (more
- than 1e100000), so it seems fairly pointless
- that numeric_in() rejected scientific-notation exponents
- above 1000. Likewise, it was silly for numeric_recv() to
+ than 1e100000), so it seems fairly pointless
+ that numeric_in() rejected scientific-notation exponents
+ above 1000. Likewise, it was silly for numeric_recv() to
reject more than 1000 digits in an input value.
@@ -2467,7 +2755,7 @@ Branch: REL9_5_STABLE [da9659f87] 2016-08-22 15:30:37 -0400
In the worst case, this could result in a corrupt btree index, which
- would need to be rebuilt using REINDEX. However, the
+ would need to be rebuilt using REINDEX. However, the
situation is believed to be rare.
@@ -2501,7 +2789,7 @@ Branch: REL9_2_STABLE [823df401d] 2016-08-31 08:52:13 -0400
Branch: REL9_1_STABLE [e3439a455] 2016-08-31 08:52:13 -0400
-->
- Disallow starting a standalone backend with standby_mode
+ Disallow starting a standalone backend with standby_mode
turned on (Michael Paquier)
@@ -2527,7 +2815,7 @@ Branch: REL9_4_STABLE [690a2fb90] 2016-08-17 13:15:04 -0700
This failure to reset all of the fields of the slot could
- prevent VACUUM from removing dead tuples.
+ prevent VACUUM from removing dead tuples.
@@ -2538,7 +2826,7 @@ Branch: REL9_4_STABLE [690a2fb90] 2016-08-17 13:15:04 -0700
- This avoids possible failures during munmap() on systems
+ This avoids possible failures during munmap() on systems
with atypical default huge page sizes. Except in crash-recovery
cases, there were no ill effects other than a log message.
@@ -2564,7 +2852,7 @@ Branch: REL9_4_STABLE [32cdf680f] 2016-09-23 09:54:11 -0400
Previously, the same value would be chosen every time, because it was
- derived from random() but srandom() had not
+ derived from random() but srandom() had not
yet been called. While relatively harmless, this was not the intended
behavior.
@@ -2584,8 +2872,8 @@ Branch: REL9_4_STABLE [c23b2523d] 2016-09-20 12:12:36 -0400
- Windows sometimes returns ERROR_ACCESS_DENIED rather
- than ERROR_ALREADY_EXISTS when there is an existing
+ Windows sometimes returns ERROR_ACCESS_DENIED rather
+ than ERROR_ALREADY_EXISTS when there is an existing
segment. This led to postmaster startup failure due to believing that
the former was an unrecoverable error.
@@ -2599,8 +2887,8 @@ Branch: REL9_6_STABLE Release: REL9_6_0 [c81c71d88] 2016-08-18 14:48:51 -0400
Branch: REL9_5_STABLE [a8fc19505] 2016-08-18 14:48:51 -0400
-->
- Fix PL/pgSQL to not misbehave with parameters and
- local variables of type int2vector or oidvector
+ Fix PL/pgSQL to not misbehave with parameters and
+ local variables of type int2vector or oidvector
(Tom Lane)
@@ -2608,7 +2896,7 @@ Branch: REL9_5_STABLE [a8fc19505] 2016-08-18 14:48:51 -0400
Don't try to share SSL contexts across multiple connections
- in libpq (Heikki Linnakangas)
+ in libpq (Heikki Linnakangas)
@@ -2619,12 +2907,12 @@ Branch: REL9_5_STABLE [a8fc19505] 2016-08-18 14:48:51 -0400
- Avoid corner-case memory leak in libpq (Tom Lane)
+ Avoid corner-case memory leak in libpq (Tom Lane)
The reported problem involved leaking an error report
- during PQreset(), but there might be related cases.
+ during PQreset(), but there might be related cases.
@@ -2640,7 +2928,7 @@ Branch: REL9_2_STABLE [a4a3fac16] 2016-09-18 14:00:13 +0300
Branch: REL9_1_STABLE [ed29d2de2] 2016-09-18 14:07:30 +0300
-->
- Make ecpg's and
options work consistently with our other executables (Haribabu Kommi)
@@ -2658,12 +2946,12 @@ Branch: REL9_5_STABLE [b93d37474] 2016-09-21 13:16:20 +0300
Branch: REL9_4_STABLE [f16d4a241] 2016-09-21 13:16:24 +0300
-->
- Fix pgbench's calculation of average latency
+ Fix pgbench's calculation of average latency
(Fabien Coelho)
- The calculation was incorrect when there were \sleep
+ The calculation was incorrect when there were \sleep
commands in the script, or when the test duration was specified in
number of transactions rather than total time.
@@ -2671,7 +2959,7 @@ Branch: REL9_4_STABLE [f16d4a241] 2016-09-21 13:16:24 +0300
- In pg_upgrade, check library loadability in name order
+ In pg_upgrade, check library loadability in name order
(Tom Lane)
@@ -2693,12 +2981,12 @@ Branch: REL9_3_STABLE [f39bb487d] 2016-09-23 13:49:27 -0400
Branch: REL9_2_STABLE [53b29d986] 2016-09-23 13:49:27 -0400
-->
- In pg_dump, never dump range constructor functions
+ In pg_dump, never dump range constructor functions
(Tom Lane)
- This oversight led to pg_upgrade failures with
+ This oversight led to pg_upgrade failures with
extensions containing range types, due to duplicate creation of the
constructor functions.
@@ -2712,9 +3000,9 @@ Branch: REL9_6_STABLE Release: REL9_6_0 [a88cee90f] 2016-09-08 10:48:03 -0400
Branch: REL9_5_STABLE [142a110b3] 2016-09-08 10:48:03 -0400
-->
- In pg_dump with
@@ -2727,27 +3015,27 @@ Branch: REL9_5_STABLE [9050e5c89] 2016-08-29 12:18:57 +0100
Branch: REL9_5_STABLE [3aa233f82] 2016-08-29 18:12:04 -0300
-->
- Make pg_receivexlog work correctly
- with without slots (Gabriele Bartolini)
- Disallow specifying both
- Make pg_rewind turn off synchronous_commit
+ Make pg_rewind turn off synchronous_commit
in its session on the source server (Michael Banck, Michael Paquier)
- This allows pg_rewind to work even when the source
+ This allows pg_rewind to work even when the source
server is using synchronous replication that is not working for some
reason.
@@ -2755,8 +3043,8 @@ Branch: REL9_5_STABLE [3aa233f82] 2016-08-29 18:12:04 -0300
- In pg_xlogdump, retry opening new WAL segments when
- using option (Magnus Hagander)
@@ -2775,7 +3063,7 @@ Branch: REL9_4_STABLE [314a25fb3] 2016-08-29 14:38:17 +0900
Branch: REL9_3_STABLE [5833306dd] 2016-08-29 15:51:30 +0900
-->
- Fix pg_xlogdump to cope with a WAL file that begins
+ Fix pg_xlogdump to cope with a WAL file that begins
with a continuation record spanning more than one page (Pavan
Deolasee)
@@ -2790,8 +3078,8 @@ Branch: REL9_5_STABLE [60b6d99da] 2016-09-15 09:30:36 -0400
Branch: REL9_4_STABLE [1336bd986] 2016-09-15 09:22:52 -0400
-->
- Fix contrib/pg_buffercache to work
- when shared_buffers exceeds 256GB (KaiGai Kohei)
+ Fix contrib/pg_buffercache to work
+ when shared_buffers exceeds 256GB (KaiGai Kohei)
@@ -2807,8 +3095,8 @@ Branch: REL9_2_STABLE [60bb1bb12] 2016-08-17 15:51:11 -0400
Branch: REL9_1_STABLE [9942376a5] 2016-08-17 15:51:11 -0400
-->
- Fix contrib/intarray/bench/bench.pl to print the results
- of the EXPLAIN it does when given the option
(Daniel Gustafsson)
@@ -2842,11 +3130,11 @@ Branch: REL9_4_STABLE [5d41f27a9] 2016-09-23 15:50:00 -0400
- When PostgreSQL has been configured
- with
@@ -2859,7 +3147,7 @@ Branch: REL9_5_STABLE [52acf020a] 2016-09-19 14:27:08 -0400
Branch: REL9_4_STABLE [ca93b816f] 2016-09-19 14:27:13 -0400
-->
- In MSVC builds, include pg_recvlogical in a
+ In MSVC builds, include pg_recvlogical in a
client-only installation (MauMau)
@@ -2899,17 +3187,17 @@ Branch: REL9_1_STABLE [380dad29d] 2016-09-02 17:29:32 -0400
If a dynamic time zone abbreviation does not match any entry in the
referenced time zone, treat it as equivalent to the time zone name.
This avoids unexpected failures when IANA removes abbreviations from
- their time zone database, as they did in tzdata
+ their time zone database, as they did in tzdata
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 pg_timezone_abbrevs view to fail altogether.
+ the pg_timezone_abbrevs view to fail altogether.
- Update time zone data files to tzdata release 2016h
+ Update time zone data files to tzdata 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,
@@ -2922,15 +3210,15 @@ Branch: REL9_1_STABLE [380dad29d] 2016-09-02 17:29:32 -0400
or no currency among the local population. They are in process of
reversing that policy in favor of using numeric UTC offsets in zones
where there is no evidence of real-world use of an English
- abbreviation. At least for the time being, PostgreSQL
+ abbreviation. At least for the time being, PostgreSQL
will continue to accept such removed abbreviations for timestamp input.
- But they will not be shown in the pg_timezone_names
+ But they will not be shown in the pg_timezone_names
view nor used for output.
- In this update, AMT is no longer shown as being in use to
- mean Armenia Time. Therefore, we have changed the Default
+ In this update, AMT is no longer shown as being in use to
+ mean Armenia Time. Therefore, we have changed the Default
abbreviation set to interpret it as Amazon Time, thus UTC-4 not UTC+4.
@@ -2984,17 +3272,17 @@ Branch: REL9_1_STABLE [5327b764a] 2016-08-08 10:33:47 -0400
-->
Fix possible mis-evaluation of
- nested CASE-WHEN expressions (Heikki
+ nested CASE-WHEN expressions (Heikki
Linnakangas, Michael Paquier, Tom Lane)
- A CASE expression appearing within the test value
- subexpression of another CASE could become confused about
+ A CASE expression appearing within the test value
+ subexpression of another CASE 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 CASE expression could result in passing the wrong test
- value to functions called within a CASE expression in the
+ a CASE expression could result in passing the wrong test
+ value to functions called within a CASE 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)
@@ -3055,7 +3343,7 @@ Branch: REL9_1_STABLE [aed766ab5] 2016-08-08 10:07:53 -0400
- Numerous places in vacuumdb and other client programs
+ Numerous places in vacuumdb 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
@@ -3064,22 +3352,22 @@ Branch: REL9_1_STABLE [aed766ab5] 2016-08-08 10:07:53 -0400
Fix handling of paired double quotes
- in psql's \connect
- and \password commands to match the documentation.
+ in psql's \connect
+ and \password commands to match the documentation.
- Introduce a new
- pg_dumpall now refuses to deal with database and role
+ pg_dumpall 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.
@@ -3089,7 +3377,7 @@ Branch: REL9_1_STABLE [aed766ab5] 2016-08-08 10:07:53 -0400
These are considered security fixes because crafted object names
containing special characters could have been used to execute
commands with superuser privileges the next time a superuser
- executes pg_dumpall or other routine maintenance
+ executes pg_dumpall or other routine maintenance
operations. (CVE-2016-5424)
@@ -3111,18 +3399,18 @@ Branch: REL9_2_STABLE [7b8526e5d] 2016-07-28 16:09:15 -0400
Branch: REL9_1_STABLE [c0e5096fc] 2016-07-28 16:09:15 -0400
-->
- Fix corner-case misbehaviors for IS NULL/IS NOT
- NULL applied to nested composite values (Andrew Gierth, Tom Lane)
+ Fix corner-case misbehaviors for IS NULL/IS NOT
+ NULL applied to nested composite values (Andrew Gierth, Tom Lane)
- The SQL standard specifies that IS NULL should return
+ The SQL standard specifies that IS NULL should return
TRUE for a row of all null values (thus ROW(NULL,NULL) IS
- NULL yields TRUE), but this is not meant to apply recursively
- (thus ROW(NULL, ROW(NULL,NULL)) IS NULL yields FALSE).
+ NULL yields TRUE), but this is not meant to apply recursively
+ (thus ROW(NULL, ROW(NULL,NULL)) IS NULL yields FALSE).
The core executor got this right, but certain planner optimizations
treated the test as recursive (thus producing TRUE in both cases),
- and contrib/postgres_fdw could produce remote queries
+ and contrib/postgres_fdw could produce remote queries
that misbehaved similarly.
@@ -3134,8 +3422,8 @@ Branch: master [eae1ad9b6] 2016-05-23 19:23:36 -0400
Branch: REL9_5_STABLE [e504d915b] 2016-05-23 19:23:36 -0400
-->
- Fix unrecognized node type error for INSERT ... ON
- CONFLICT within a recursive CTE (a WITH item) (Peter
+ Fix unrecognized node type error for INSERT ... ON
+ CONFLICT within a recursive CTE (a WITH item) (Peter
Geoghegan)
@@ -3147,7 +3435,7 @@ Branch: master [26e66184d] 2016-05-11 16:20:23 -0400
Branch: REL9_5_STABLE [58d802410] 2016-05-11 16:20:03 -0400
-->
- Fix INSERT ... ON CONFLICT to successfully match index
+ Fix INSERT ... ON CONFLICT to successfully match index
expressions or index predicates that are simplified during the
planner's expression preprocessing phase (Tom Lane)
@@ -3161,7 +3449,7 @@ Branch: REL9_5_STABLE [31ce32ade] 2016-07-04 16:09:11 -0400
-->
Correctly handle violations of exclusion constraints that apply to
- the target table of an INSERT ... ON CONFLICT command,
+ the target table of an INSERT ... ON CONFLICT command,
but are not one of the selected arbiter indexes (Tom Lane)
@@ -3178,7 +3466,7 @@ Branch: master [8a13d5e6d] 2016-05-11 17:06:53 -0400
Branch: REL9_5_STABLE [428484ce1] 2016-05-11 17:06:53 -0400
-->
- Fix INSERT ... ON CONFLICT to not fail if the target
+ Fix INSERT ... ON CONFLICT to not fail if the target
table has a unique index on OID (Tom Lane)
@@ -3194,7 +3482,7 @@ Branch: REL9_2_STABLE [f66e0fec3] 2016-06-16 17:16:53 -0400
Branch: REL9_1_STABLE [7b97dafa2] 2016-06-16 17:16:58 -0400
-->
- Make the inet and cidr data types properly reject
+ Make the inet and cidr data types properly reject
IPv6 addresses with too many colon-separated fields (Tom Lane)
@@ -3210,8 +3498,8 @@ Branch: REL9_2_STABLE [89b301104] 2016-07-16 14:42:37 -0400
Branch: REL9_1_STABLE [608cc0c41] 2016-07-16 14:42:37 -0400
-->
- Prevent crash in close_ps()
- (the point ## lseg operator)
+ Prevent crash in close_ps()
+ (the point##lseg operator)
for NaN input coordinates (Tom Lane)
@@ -3229,7 +3517,7 @@ Branch: REL9_4_STABLE [b25d87f91] 2016-07-01 11:40:22 -0400
Branch: REL9_3_STABLE [b0f20c2ea] 2016-07-01 11:40:22 -0400
-->
- Avoid possible crash in pg_get_expr() when inconsistent
+ Avoid possible crash in pg_get_expr() when inconsistent
values are passed to it (Michael Paquier, Thomas Munro)
@@ -3245,12 +3533,12 @@ Branch: REL9_2_STABLE [b0134fe84] 2016-08-08 11:13:45 -0400
Branch: REL9_1_STABLE [d555d2642] 2016-08-08 11:13:51 -0400
-->
- Fix several one-byte buffer over-reads in to_number()
+ Fix several one-byte buffer over-reads in to_number()
(Peter Eisentraut)
- In several cases the to_number() function would read one
+ In several cases the to_number() 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.
@@ -3267,8 +3555,8 @@ Branch: REL9_3_STABLE [17bfef80e] 2016-06-27 15:57:21 -0400
-->
Do not run the planner on the query contained in CREATE
- MATERIALIZED VIEW or CREATE TABLE AS
- when WITH NO DATA is specified (Michael Paquier,
+ MATERIALIZED VIEW or CREATE TABLE AS
+ when WITH NO DATA is specified (Michael Paquier,
Tom Lane)
@@ -3291,7 +3579,7 @@ Branch: REL9_1_STABLE [37276017f] 2016-07-15 17:49:49 -0700
-->
Avoid unsafe intermediate state during expensive paths
- through heap_update() (Masahiko Sawada, Andres Freund)
+ through heap_update() (Masahiko Sawada, Andres Freund)
@@ -3331,8 +3619,8 @@ Branch: REL9_4_STABLE [166873dd0] 2016-07-15 14:17:20 -0400
Branch: REL9_3_STABLE [6c243f90a] 2016-07-15 14:17:20 -0400
-->
- Avoid unnecessary could not serialize access errors when
- acquiring FOR KEY SHARE row locks in serializable mode
+ Avoid unnecessary could not serialize access errors when
+ acquiring FOR KEY SHARE row locks in serializable mode
(Álvaro Herrera)
@@ -3346,14 +3634,14 @@ Branch: master [9eaf5be50] 2016-06-03 18:07:14 -0400
Branch: REL9_5_STABLE [8355897ff] 2016-06-03 18:07:14 -0400
-->
- Make sure expanded datums returned by a plan node are
+ Make sure expanded datums returned by a plan node are
read-only (Tom Lane)
This avoids failures in some cases where the result of a lower plan
node is referenced in multiple places in upper nodes. So far as
- core PostgreSQL is concerned, only array values
+ core PostgreSQL is concerned, only array values
returned by PL/pgSQL functions are at risk; but extensions might
use expanded datums for other things.
@@ -3374,7 +3662,7 @@ Branch: REL9_3_STABLE [dafdcbb6c] 2016-06-22 11:55:32 -0400
Branch: REL9_2_STABLE [dd41661d2] 2016-06-22 11:55:35 -0400
-->
- Avoid crash in postgres -C when the specified variable
+ Avoid crash in postgres -C when the specified variable
has a null string value (Michael Paquier)
@@ -3470,12 +3758,12 @@ Branch: REL9_2_STABLE [4cf0978ea] 2016-05-24 15:47:51 -0400
Branch: REL9_1_STABLE [5551dac59] 2016-05-24 15:47:51 -0400
-->
- Avoid consuming a transaction ID during VACUUM
+ Avoid consuming a transaction ID during VACUUM
(Alexander Korotkov)
- Some cases in VACUUM unnecessarily caused an XID to be
+ Some cases in VACUUM 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.
@@ -3498,7 +3786,7 @@ Branch: REL9_3_STABLE [28f294afd] 2016-06-24 18:29:28 -0400
The usual symptom of this bug is errors
- like MultiXactId NNN has not been created
+ like MultiXactId NNN has not been created
yet -- apparent wraparound.
@@ -3514,8 +3802,8 @@ Branch: REL9_2_STABLE [3201709de] 2016-06-06 17:44:18 -0400
Branch: REL9_1_STABLE [32ceb8dfb] 2016-06-06 17:44:18 -0400
-->
- When a manual ANALYZE specifies a column list, don't
- reset the table's changes_since_analyze counter
+ When a manual ANALYZE specifies a column list, don't
+ reset the table's changes_since_analyze counter
(Tom Lane)
@@ -3536,7 +3824,7 @@ Branch: REL9_2_STABLE [127d73009] 2016-08-07 18:52:02 -0400
Branch: REL9_1_STABLE [a449ad095] 2016-08-07 18:52:02 -0400
-->
- Fix ANALYZE's overestimation of n_distinct
+ Fix ANALYZE's overestimation of n_distinct
for a unique or nearly-unique column with many null entries (Tom
Lane)
@@ -3600,7 +3888,7 @@ Branch: REL9_4_STABLE [98d5f366b] 2016-08-06 14:28:38 -0400
- This mistake prevented VACUUM from completing in some
+ This mistake prevented VACUUM from completing in some
cases involving corrupt b-tree indexes.
@@ -3612,7 +3900,7 @@ Branch: master [8cf739de8] 2016-06-24 16:57:36 -0400
Branch: REL9_5_STABLE [07f69137b] 2016-06-24 16:57:36 -0400
-->
- Fix building of large (bigger than shared_buffers)
+ Fix building of large (bigger than shared_buffers)
hash indexes (Tom Lane)
@@ -3646,9 +3934,9 @@ Branch: master [8a859691d] 2016-06-05 11:53:06 -0400
Branch: REL9_5_STABLE [a7aa61ffe] 2016-06-05 11:53:06 -0400
-->
- Fix possible crash during a nearest-neighbor (ORDER BY
- distance) indexscan on a contrib/btree_gist index on
- an interval column (Peter Geoghegan)
+ Fix possible crash during a nearest-neighbor (ORDER BY
+ distance) indexscan on a contrib/btree_gist index on
+ an interval column (Peter Geoghegan)
@@ -3659,7 +3947,7 @@ Branch: master [975ad4e60] 2016-05-30 14:47:22 -0400
Branch: REL9_5_STABLE [2973d7d02] 2016-05-30 14:47:22 -0400
-->
- Fix PANIC: failed to add BRIN tuple error when attempting
+ Fix PANIC: failed to add BRIN tuple error when attempting
to update a BRIN index entry (Álvaro Herrera)
@@ -3682,8 +3970,8 @@ Branch: master [baebab3ac] 2016-07-12 18:07:03 -0400
Branch: REL9_5_STABLE [a0943dbbe] 2016-07-12 18:06:50 -0400
-->
- Fix PL/pgSQL's handling of the INTO clause
- within IMPORT FOREIGN SCHEMA commands (Tom Lane)
+ Fix PL/pgSQL's handling of the INTO clause
+ within IMPORT FOREIGN SCHEMA commands (Tom Lane)
@@ -3698,8 +3986,8 @@ Branch: REL9_2_STABLE [6c0be49b2] 2016-07-17 09:39:51 -0400
Branch: REL9_1_STABLE [84d679204] 2016-07-17 09:41:08 -0400
-->
- Fix contrib/btree_gin to handle the smallest
- possible bigint value correctly (Peter Eisentraut)
+ Fix contrib/btree_gin to handle the smallest
+ possible bigint value correctly (Peter Eisentraut)
@@ -3721,7 +4009,7 @@ Branch: REL9_1_STABLE [1f63b0e09] 2016-08-05 18:58:36 -0400
It's planned to switch to two-part instead of three-part server
version numbers for releases after 9.6. Make sure
- that PQserverVersion() returns the correct value for
+ that PQserverVersion() returns the correct value for
such cases.
@@ -3737,7 +4025,7 @@ Branch: REL9_2_STABLE [295edbecf] 2016-08-01 15:08:48 +0200
Branch: REL9_1_STABLE [c15f502b6] 2016-08-01 15:08:36 +0200
-->
- Fix ecpg's code for unsigned long long
+ Fix ecpg's code for unsigned long long
array elements (Michael Meskes)
@@ -3752,8 +4040,8 @@ Branch: REL9_3_STABLE [6693c9d7b] 2016-08-02 12:49:09 -0400
Branch: REL9_2_STABLE [a5a7caaa1] 2016-08-02 12:49:15 -0400
-->
- In pg_dump with both
@@ -3771,15 +4059,15 @@ Branch: REL9_4_STABLE [53c2601a5] 2016-06-03 11:29:20 -0400
Branch: REL9_3_STABLE [4a21c6fd7] 2016-06-03 11:29:20 -0400
-->
- Improve handling of SIGTERM/control-C in
- parallel pg_dump and pg_restore (Tom
+ Improve handling of SIGTERM/control-C in
+ parallel pg_dump and pg_restore (Tom
Lane)
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 CREATE INDEX.
+ are doing something long-running such as a CREATE INDEX.
@@ -3792,17 +4080,17 @@ Branch: REL9_4_STABLE [ea274b2f4] 2016-05-25 12:39:57 -0400
Branch: REL9_3_STABLE [1c8205159] 2016-05-25 12:39:57 -0400
-->
- Fix error reporting in parallel pg_dump
- and pg_restore (Tom Lane)
+ Fix error reporting in parallel pg_dump
+ and pg_restore (Tom Lane)
- Previously, errors reported by pg_dump
- or pg_restore worker processes might never make it to
+ Previously, errors reported by pg_dump
+ or pg_restore 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 stderr. In some cases this will result in
+ everything to stderr. 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.
@@ -3817,8 +4105,8 @@ Branch: REL9_4_STABLE [d32bc204c] 2016-05-26 10:50:42 -0400
Branch: REL9_3_STABLE [b9784e1f7] 2016-05-26 10:50:46 -0400
-->
- Ensure that parallel pg_dump
- or pg_restore on Windows will shut down properly
+ Ensure that parallel pg_dump
+ or pg_restore on Windows will shut down properly
after an error (Kyotaro Horiguchi)
@@ -3835,13 +4123,13 @@ Branch: master [d74048def] 2016-05-26 22:14:23 +0200
Branch: REL9_5_STABLE [47e596976] 2016-05-26 22:18:04 +0200
-->
- Make parallel pg_dump fail cleanly when run against a
+ Make parallel pg_dump fail cleanly when run against a
standby server (Magnus Hagander)
This usage is not supported
- unless is specified, but the
error was not handled very well.
@@ -3855,7 +4143,7 @@ Branch: REL9_4_STABLE [f2f18a37c] 2016-05-26 11:51:16 -0400
Branch: REL9_3_STABLE [99565a1ef] 2016-05-26 11:51:20 -0400
-->
- Make pg_dump behave better when built without zlib
+ Make pg_dump behave better when built without zlib
support (Kyotaro Horiguchi)
@@ -3876,7 +4164,7 @@ Branch: REL9_2_STABLE [a21617759] 2016-08-01 17:38:00 +0900
Branch: REL9_1_STABLE [366f4a962] 2016-08-01 17:38:05 +0900
-->
- Make pg_basebackup accept -Z 0 as
+ Make pg_basebackup accept -Z 0 as
specifying no compression (Fujii Masao)
@@ -3922,13 +4210,13 @@ Branch: REL9_4_STABLE [c2651cd24] 2016-05-27 10:40:20 -0400
Branch: REL9_3_STABLE [1f1e70a87] 2016-05-27 10:40:20 -0400
-->
- Be more predictable about reporting statement timeout
- versus lock timeout (Tom Lane)
+ Be more predictable about reporting statement timeout
+ versus lock timeout (Tom Lane)
On heavily loaded machines, the regression tests sometimes failed due
- to reporting lock timeout even though the statement timeout
+ to reporting lock timeout even though the statement timeout
should have occurred first.
@@ -3981,7 +4269,7 @@ Branch: REL9_1_STABLE [d70df7867] 2016-07-19 17:53:31 -0400
-->
Update our copy of the timezone code to match
- IANA's tzcode release 2016c (Tom Lane)
+ IANA's tzcode release 2016c (Tom Lane)
@@ -4002,7 +4290,7 @@ Branch: REL9_2_STABLE [7822792f7] 2016-08-05 12:58:58 -0400
Branch: REL9_1_STABLE [a44388ffe] 2016-08-05 12:59:02 -0400
-->
- Update time zone data files to tzdata release 2016f
+ Update time zone data files to tzdata release 2016f
for DST law changes in Kemerovo and Novosibirsk, plus historical
corrections for Azerbaijan, Belarus, and Morocco.
@@ -4066,7 +4354,7 @@ Branch: REL9_1_STABLE [9b676fd49] 2016-05-07 00:09:37 -0400
using OpenSSL within a single process and not all the code involved
follows the same rules for when to clear the error queue.
Failures have been reported specifically when a client application
- uses SSL connections in libpq concurrently with
+ uses SSL connections in libpq 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.
@@ -4084,7 +4372,7 @@ Branch: REL9_2_STABLE [ad2d32b57] 2016-04-21 20:05:58 -0400
Branch: REL9_1_STABLE [6882dbd34] 2016-04-21 20:05:58 -0400
-->
- Fix failed to build any N-way joins
+ Fix failed to build any N-way joins
planner error with a full join enclosed in the right-hand side of a
left join (Tom Lane)
@@ -4106,10 +4394,10 @@ Branch: REL9_2_STABLE [f02cb8c9a] 2016-04-29 20:19:38 -0400
Given a three-or-more-way equivalence class of variables, such
- as X.X = Y.Y = Z.Z, it was possible for the planner to omit
+ as X.X = Y.Y = Z.Z, 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 WHERE clauses. For various reasons, erroneous plans
+ the WHERE clauses. For various reasons, erroneous plans
were seldom selected in practice, so that this bug has gone undetected
for a long time.
@@ -4128,7 +4416,7 @@ Branch: REL9_5_STABLE [81deadd31] 2016-04-21 23:17:36 -0400
- An example is that SELECT (ARRAY[])::text[] gave an error,
+ An example is that SELECT (ARRAY[])::text[] gave an error,
though it worked without the parentheses.
@@ -4160,7 +4448,7 @@ Branch: REL9_4_STABLE [ef35afa35] 2016-04-20 14:25:15 -0400
The memory leak would typically not amount to much in simple queries,
but it could be very substantial during a large GIN index build with
- high maintenance_work_mem.
+ high maintenance_work_mem.
@@ -4175,8 +4463,8 @@ Branch: REL9_2_STABLE [11247dd99] 2016-05-06 12:09:20 -0400
Branch: REL9_1_STABLE [7bad282c3] 2016-05-06 12:09:20 -0400
-->
- Fix possible misbehavior of TH, th,
- and Y,YYY format codes in to_timestamp()
+ Fix possible misbehavior of TH, th,
+ and Y,YYY format codes in to_timestamp()
(Tom Lane)
@@ -4197,9 +4485,9 @@ Branch: REL9_2_STABLE [c7c145e4f] 2016-04-21 14:20:18 -0400
Branch: REL9_1_STABLE [663624e60] 2016-04-21 14:20:18 -0400
-->
- Fix dumping of rules and views in which the array
- argument of a value operator
- ANY (array) construct is a sub-SELECT
+ Fix dumping of rules and views in which the array
+ argument of a valueoperator
+ ANY (array) construct is a sub-SELECT
(Tom Lane)
@@ -4212,14 +4500,14 @@ Branch: REL9_5_STABLE [f3d17491c] 2016-04-04 18:05:23 -0400
Branch: REL9_4_STABLE [28148e258] 2016-04-04 18:05:24 -0400
-->
- Disallow newlines in ALTER SYSTEM parameter values
+ Disallow newlines in ALTER SYSTEM parameter values
(Tom Lane)
The configuration-file parser doesn't support embedded newlines in
string literals, so we mustn't allow them in values to be inserted
- by ALTER SYSTEM.
+ by ALTER SYSTEM.
@@ -4231,7 +4519,7 @@ Branch: REL9_5_STABLE [8f8e65d34] 2016-04-15 12:11:27 -0400
Branch: REL9_4_STABLE [8eed31ffb] 2016-04-15 12:11:27 -0400
-->
- Fix ALTER TABLE ... REPLICA IDENTITY USING INDEX to
+ Fix ALTER TABLE ... REPLICA IDENTITY USING INDEX to
work properly if an index on OID is selected (David Rowley)
@@ -4290,13 +4578,13 @@ Branch: REL9_2_STABLE [1b22368ff] 2016-04-20 23:48:13 -0400
Branch: REL9_1_STABLE [4c1c9f80b] 2016-04-20 23:48:13 -0400
-->
- Make pg_regress use a startup timeout from the
- PGCTLTIMEOUT environment variable, if that's set (Tom Lane)
+ Make pg_regress use a startup timeout from the
+ PGCTLTIMEOUT environment variable, if that's set (Tom Lane)
This is for consistency with a behavior recently added
- to pg_ctl; it eases automated testing on slow machines.
+ to pg_ctl; it eases automated testing on slow machines.
@@ -4311,7 +4599,7 @@ Branch: REL9_2_STABLE [6bb42d520] 2016-04-13 18:57:52 -0400
Branch: REL9_1_STABLE [3ef1f3a3e] 2016-04-13 18:57:52 -0400
-->
- Fix pg_upgrade to correctly restore extension
+ Fix pg_upgrade to correctly restore extension
membership for operator families containing only one operator class
(Tom Lane)
@@ -4319,7 +4607,7 @@ Branch: REL9_1_STABLE [3ef1f3a3e] 2016-04-13 18:57:52 -0400
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 pg_dump
+ immediate ill effects, but would cause later pg_dump
runs to emit output that would cause (harmless) errors on restore.
@@ -4333,13 +4621,13 @@ Branch: REL9_4_STABLE [e1aecebc0] 2016-05-06 22:05:51 -0400
Branch: REL9_3_STABLE [e1d88f983] 2016-05-06 22:05:51 -0400
-->
- Fix pg_upgrade to not fail when new-cluster TOAST rules
+ Fix pg_upgrade to not fail when new-cluster TOAST rules
differ from old (Tom Lane)
- pg_upgrade had special-case code to handle the
- situation where the new PostgreSQL version thinks that
+ pg_upgrade had special-case code to handle the
+ situation where the new PostgreSQL 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
@@ -4369,7 +4657,7 @@ Branch: REL9_2_STABLE [b24f7e280] 2016-04-18 13:33:07 -0400
-->
Reduce the number of SysV semaphores used by a build configured with
- (Tom Lane)
@@ -4384,8 +4672,8 @@ Branch: REL9_2_STABLE [0f5491283] 2016-04-23 16:53:15 -0400
Branch: REL9_1_STABLE [cbff4b708] 2016-04-23 16:53:15 -0400
-->
- Rename internal function strtoi()
- to strtoint() to avoid conflict with a NetBSD library
+ Rename internal function strtoi()
+ to strtoint() to avoid conflict with a NetBSD library
function (Thomas Munro)
@@ -4407,8 +4695,8 @@ Branch: REL9_2_STABLE [b5ebc513d] 2016-04-21 16:59:13 -0400
Branch: REL9_1_STABLE [9028f404e] 2016-04-21 16:59:17 -0400
-->
- Fix reporting of errors from bind()
- and listen() system calls on Windows (Tom Lane)
+ Fix reporting of errors from bind()
+ and listen() system calls on Windows (Tom Lane)
@@ -4463,7 +4751,7 @@ Branch: REL9_4_STABLE [c238a4101] 2016-04-22 05:20:07 -0400
Branch: REL9_3_STABLE [ab5c6d01f] 2016-04-22 05:20:18 -0400
-->
- Fix putenv() to work properly with Visual Studio 2013
+ Fix putenv() to work properly with Visual Studio 2013
(Michael Paquier)
@@ -4479,12 +4767,12 @@ Branch: REL9_2_STABLE [b4b06931e] 2016-03-29 11:54:58 -0400
Branch: REL9_1_STABLE [6cd30292b] 2016-03-29 11:54:58 -0400
-->
- Avoid possibly-unsafe use of Windows' FormatMessage()
+ Avoid possibly-unsafe use of Windows' FormatMessage()
function (Christian Ullrich)
- Use the FORMAT_MESSAGE_IGNORE_INSERTS flag where
+ Use the FORMAT_MESSAGE_IGNORE_INSERTS flag where
appropriate. No live bug is known to exist here, but it seems like a
good idea to be careful.
@@ -4501,9 +4789,9 @@ Branch: REL9_2_STABLE [29d154e36] 2016-05-05 20:09:27 -0400
Branch: REL9_1_STABLE [bfc39da64] 2016-05-05 20:09:32 -0400
-->
- Update time zone data files to tzdata release 2016d
+ Update time zone data files to tzdata release 2016d
for DST law changes in Russia and Venezuela. There are new zone
- names Europe/Kirov and Asia/Tomsk to reflect
+ names Europe/Kirov and Asia/Tomsk to reflect
the fact that these regions now have different time zone histories from
adjacent regions.
@@ -4536,7 +4824,7 @@ Branch: REL9_1_STABLE [bfc39da64] 2016-05-05 20:09:32 -0400
- However, you may need to REINDEX some indexes after applying
+ However, you may need to REINDEX some indexes after applying
the update, as per the first changelog entry below.
@@ -4554,39 +4842,39 @@ Branch: REL9_5_STABLE [8aa6e9780] 2016-03-23 16:04:35 -0400
- Disable abbreviated keys for string sorting in non-C
+ Disable abbreviated keys for string sorting in non-C
locales (Robert Haas)
- PostgreSQL 9.5 introduced logic for speeding up
+ PostgreSQL 9.5 introduced logic for speeding up
comparisons of string data types by using the standard C library
- function strxfrm() as a substitute
- for strcoll(). It now emerges that most versions of
+ function strxfrm() as a substitute
+ for strcoll(). It now emerges that most versions of
glibc (Linux's implementation of the C library) have buggy
- implementations of strxfrm() that, in some locales,
+ implementations of strxfrm() that, in some locales,
can produce string comparison results that do not
- match strcoll(). Until this problem can be better
- characterized, disable the optimization in all non-C
- locales. (C locale is safe since it uses
- neither strcoll() nor strxfrm().)
+ match strcoll(). Until this problem can be better
+ characterized, disable the optimization in all non-C
+ locales. (C locale is safe since it uses
+ neither strcoll() nor strxfrm().)
Unfortunately, this problem affects not only sorting but also entry
ordering in B-tree indexes, which means that B-tree indexes
- on text, varchar, or char columns may now
+ on text, varchar, or char columns may now
be corrupt if they sort according to an affected locale and were
- built or modified under PostgreSQL 9.5.0 or 9.5.1.
- Users should REINDEX indexes that might be affected.
+ built or modified under PostgreSQL 9.5.0 or 9.5.1.
+ Users should REINDEX indexes that might be affected.
It is not possible at this time to give an exhaustive list of
- known-affected locales. C locale is known safe, and
+ known-affected locales. C locale is known safe, and
there is no evidence of trouble in English-based locales such
- as en_US, but some other popular locales such
- as de_DE are affected in most glibc versions.
+ as en_US, but some other popular locales such
+ as de_DE are affected in most glibc versions.
@@ -4619,14 +4907,14 @@ Branch: REL9_5_STABLE [bf78a6f10] 2016-03-28 10:57:46 -0300
Add must-be-superuser checks to some
- new contrib/pageinspect functions (Andreas Seltenreich)
+ new contrib/pageinspect functions (Andreas Seltenreich)
- Most functions in the pageinspect extension that
- inspect bytea values disallow calls by non-superusers,
- but brin_page_type() and brin_metapage_info()
- failed to do so. Passing contrived bytea values to them might
+ Most functions in the pageinspect extension that
+ inspect bytea values disallow calls by non-superusers,
+ but brin_page_type() and brin_metapage_info()
+ failed to do so. Passing contrived bytea values to them might
crash the server or disclose a few bytes of server memory. Add the
missing permissions checks to prevent misuse.
(CVE-2016-3065)
@@ -4641,15 +4929,15 @@ Branch: REL9_5_STABLE [bf7ced5e2] 2016-03-03 09:50:38 +0000
- Fix incorrect handling of indexed ROW() comparisons
+ Fix incorrect handling of indexed ROW() comparisons
(Simon Riggs)
Flaws in a minor optimization introduced in 9.5 caused incorrect
- results if the ROW() comparison matches the index ordering
+ results if the ROW() comparison matches the index ordering
partially but not exactly (for example, differing column order, or the
- index contains both ASC and DESC columns).
+ index contains both ASC and DESC columns).
Pending a better solution, the optimization has been removed.
@@ -4667,15 +4955,15 @@ Branch: REL9_1_STABLE [d485d9581] 2016-03-09 14:51:02 -0500
Fix incorrect handling of NULL index entries in
- indexed ROW() comparisons (Tom Lane)
+ indexed ROW() comparisons (Tom Lane)
An index search using a row comparison such as ROW(a, b) >
- ROW('x', 'y') would stop upon reaching a NULL entry in
- the b column, ignoring the fact that there might be
- non-NULL b values associated with later values
- of a.
+ ROW('x', 'y') would stop upon reaching a NULL entry in
+ the b column, ignoring the fact that there might be
+ non-NULL b values associated with later values
+ of a.
@@ -4698,7 +4986,7 @@ Branch: REL9_1_STABLE [d0e47bcd4] 2016-03-09 18:53:54 -0800
Avoid unlikely data-loss scenarios due to renaming files without
- adequate fsync() calls before and after (Michael Paquier,
+ adequate fsync() calls before and after (Michael Paquier,
Tomas Vondra, Andres Freund)
@@ -4712,14 +5000,14 @@ Branch: REL9_5_STABLE [d8d5a00b1] 2016-03-22 17:56:06 -0400
Fix incorrect behavior when rechecking a just-modified row in a query
- that does SELECT FOR UPDATE/SHARE and contains some
+ that does SELECT FOR UPDATE/SHARE and contains some
relations that need not be locked (Tom Lane)
Rows from non-locked relations were incorrectly treated as containing
all NULLs during the recheck, which could result in incorrectly
- deciding that the updated row no longer passes the WHERE
+ deciding that the updated row no longer passes the WHERE
condition, or in incorrectly outputting NULLs.
@@ -4733,7 +5021,7 @@ Branch: REL9_4_STABLE [597e41e45] 2016-03-02 23:31:39 -0500
- Fix bug in json_to_record() when a field of its input
+ Fix bug in json_to_record() when a field of its input
object contains a sub-object with a field name matching one of the
requested output column names (Tom Lane)
@@ -4748,7 +5036,7 @@ Branch: REL9_5_STABLE [68d68ff83] 2016-02-21 10:40:39 -0500
Fix nonsense result from two-argument form
- of jsonb_object() when called with empty arrays
+ of jsonb_object() when called with empty arrays
(Michael Paquier, Andrew Dunstan)
@@ -4761,7 +5049,7 @@ Branch: REL9_5_STABLE [5f95521b3] 2016-03-23 10:43:24 -0400
- Fix misbehavior in jsonb_set() when converting a path
+ Fix misbehavior in jsonb_set() when converting a path
array element into an integer for use as an array subscript
(Michael Paquier)
@@ -4777,7 +5065,7 @@ Branch: REL9_4_STABLE [17a250b18] 2016-03-17 15:50:33 -0400
Fix misformatting of negative time zone offsets
- by to_char()'s OF format code
+ by to_char()'s OF format code
(Thomas Munro, Tom Lane)
@@ -4791,7 +5079,7 @@ Branch: REL9_5_STABLE [3f14d8d59] 2016-03-15 18:04:48 -0400
Fix possible incorrect logging of waits done by
- INSERT ... ON CONFLICT (Peter Geoghegan)
+ INSERT ... ON CONFLICT (Peter Geoghegan)
@@ -4815,7 +5103,7 @@ Branch: REL9_4_STABLE [a9613ee69] 2016-03-06 02:43:26 +0900
Previously, standby servers would delay application of WAL records in
- response to recovery_min_apply_delay even while replaying
+ response to recovery_min_apply_delay even while replaying
the initial portion of WAL needed to make their database state valid.
Since the standby is useless until it's reached a consistent database
state, this was deemed unhelpful.
@@ -4834,7 +5122,7 @@ Branch: REL9_1_STABLE [ca32f125b] 2016-02-19 08:35:02 +0000
- Correctly handle cases where pg_subtrans is close to XID
+ Correctly handle cases where pg_subtrans is close to XID
wraparound during server startup (Jeff Janes)
@@ -4870,10 +5158,10 @@ Branch: REL9_5_STABLE [f8a75881f] 2016-03-02 23:43:42 -0800
Trouble cases included tuples larger than one page when replica
- identity is FULL, UPDATEs that change a
+ identity is FULL, UPDATEs that change a
primary key within a transaction large enough to be spooled to disk,
incorrect reports of subxact logged without previous toplevel
- record, and incorrect reporting of a transaction's commit time.
+ record, and incorrect reporting of a transaction's commit time.
@@ -4887,7 +5175,7 @@ Branch: REL9_4_STABLE [9b69d5c1d] 2016-02-29 12:34:33 +0000
Fix planner error with nested security barrier views when the outer
- view has a WHERE clause containing a correlated subquery
+ view has a WHERE clause containing a correlated subquery
(Dean Rasheed)
@@ -4916,7 +5204,7 @@ Branch: REL9_1_STABLE [7d6c58aa1] 2016-02-28 23:40:35 -0500
- Fix corner-case crash due to trying to free localeconv()
+ Fix corner-case crash due to trying to free localeconv()
output strings more than once (Tom Lane)
@@ -4933,14 +5221,14 @@ Branch: REL9_1_STABLE [fe747b741] 2016-03-06 19:21:03 -0500
- Fix parsing of affix files for ispell dictionaries
+ Fix parsing of affix files for ispell dictionaries
(Tom Lane)
The code could go wrong if the affix file contained any characters
whose byte length changes during case-folding, for
- example I in Turkish UTF8 locales.
+ example I in Turkish UTF8 locales.
@@ -4956,7 +5244,7 @@ Branch: REL9_1_STABLE [e56acbe2a] 2016-02-10 19:30:12 -0500
- Avoid use of sscanf() to parse ispell
+ Avoid use of sscanf() to parse ispell
dictionary files (Artur Zakirov)
@@ -5020,7 +5308,7 @@ Branch: REL9_1_STABLE [b4895bf79] 2016-03-04 11:57:40 -0500
- Fix psql's tab completion logic to handle multibyte
+ Fix psql's tab completion logic to handle multibyte
characters properly (Kyotaro Horiguchi, Robert Haas)
@@ -5036,12 +5324,12 @@ Branch: REL9_1_STABLE [2d61d88d8] 2016-03-14 11:31:49 -0400
- Fix psql's tab completion for
- SECURITY LABEL (Tom Lane)
+ Fix psql's tab completion for
+ SECURITY LABEL (Tom Lane)
- Pressing TAB after SECURITY LABEL might cause a crash
+ Pressing TAB after SECURITY LABEL might cause a crash
or offering of inappropriate keywords.
@@ -5058,8 +5346,8 @@ Branch: REL9_1_STABLE [f97664cf5] 2016-02-10 20:34:48 -0500
- Make pg_ctl accept a wait timeout from the
- PGCTLTIMEOUT environment variable, if none is specified on
+ Make pg_ctl accept a wait timeout from the
+ PGCTLTIMEOUT environment variable, if none is specified on
the command line (Noah Misch)
@@ -5083,12 +5371,12 @@ Branch: REL9_1_STABLE [5a39c7395] 2016-03-07 10:41:11 -0500
Fix incorrect test for Windows service status
- in pg_ctl (Manuel Mathar)
+ in pg_ctl (Manuel Mathar)
The previous set of minor releases attempted to
- fix pg_ctl to properly determine whether to send log
+ fix pg_ctl to properly determine whether to send log
messages to Window's Event Log, but got the test backwards.
@@ -5105,8 +5393,8 @@ Branch: REL9_1_STABLE [1965a8ce1] 2016-03-16 23:18:08 -0400
- Fix pgbench to correctly handle the combination
- of -C and -M prepared options (Tom Lane)
+ Fix pgbench to correctly handle the combination
+ of -C and -M prepared options (Tom Lane)
@@ -5120,7 +5408,7 @@ Branch: REL9_3_STABLE [bf26c4f44] 2016-02-18 18:32:26 -0500
- In pg_upgrade, skip creating a deletion script when
+ In pg_upgrade, skip creating a deletion script when
the new data directory is inside the old data directory (Bruce
Momjian)
@@ -5178,7 +5466,7 @@ Branch: REL9_1_STABLE [0f359c7de] 2016-02-18 15:40:36 -0500
Fix multiple mistakes in the statistics returned
- by contrib/pgstattuple's pgstatindex()
+ by contrib/pgstattuple's pgstatindex()
function (Tom Lane)
@@ -5195,7 +5483,7 @@ Branch: REL9_1_STABLE [2aa9fd963] 2016-03-19 18:59:41 -0400
- Remove dependency on psed in MSVC builds, since it's no
+ Remove dependency on psed in MSVC builds, since it's no
longer provided by core Perl (Michael Paquier, Andrew Dunstan)
@@ -5212,7 +5500,7 @@ Branch: REL9_1_STABLE [e5fd35cc5] 2016-03-25 19:03:54 -0400
- Update time zone data files to tzdata release 2016c
+ Update time zone data files to tzdata 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
@@ -5296,7 +5584,7 @@ Branch: REL9_5_STABLE [87dbc72a7] 2016-02-08 11:03:37 +0100
- Avoid pushdown of HAVING clauses when grouping sets are
+ Avoid pushdown of HAVING clauses when grouping sets are
used (Andrew Gierth)
@@ -5309,7 +5597,7 @@ Branch: REL9_5_STABLE [82406d6ff] 2016-02-07 14:57:24 -0500
- Fix deparsing of ON CONFLICT arbiter WHERE
+ Fix deparsing of ON CONFLICT arbiter WHERE
clauses (Peter Geoghegan)
@@ -5326,14 +5614,14 @@ Branch: REL9_1_STABLE [b043df093] 2016-01-26 15:38:33 -0500
- Make %h and %r escapes
- in log_line_prefix work for messages emitted due
- to log_connections (Tom Lane)
+ Make %h and %r escapes
+ in log_line_prefix work for messages emitted due
+ to log_connections (Tom Lane)
- Previously, %h/%r started to work just after a
- new session had emitted the connection received log message;
+ Previously, %h/%r started to work just after a
+ new session had emitted the connection received log message;
now they work for that message too.
@@ -5367,8 +5655,8 @@ Branch: REL9_1_STABLE [ed5f57218] 2016-01-29 10:28:03 +0100
- Fix psql's \det command to interpret its
- pattern argument the same way as other \d commands with
+ Fix psql's \det command to interpret its
+ pattern argument the same way as other \d commands with
potentially schema-qualified patterns do (Reece Hart)
@@ -5385,7 +5673,7 @@ Branch: REL9_1_STABLE [b96f6f444] 2016-01-07 11:59:08 -0300
- In pg_ctl on Windows, check service status to decide
+ In pg_ctl on Windows, check service status to decide
where to send output, rather than checking if standard output is a
terminal (Michael Paquier)
@@ -5403,7 +5691,7 @@ Branch: REL9_1_STABLE [5108013db] 2016-01-13 18:55:27 -0500
- Fix assorted corner-case bugs in pg_dump's processing
+ Fix assorted corner-case bugs in pg_dump's processing
of extension member objects (Tom Lane)
@@ -5417,7 +5705,7 @@ Branch: REL9_5_STABLE [1e910cf5b] 2016-01-22 20:04:35 -0300
Fix improper quoting of domain constraint names
- in pg_dump (Elvis Pranskevichus)
+ in pg_dump (Elvis Pranskevichus)
@@ -5433,9 +5721,9 @@ Branch: REL9_1_STABLE [9c704632c] 2016-02-04 00:26:10 -0500
- Make pg_dump mark a view's triggers as needing to be
+ Make pg_dump mark a view's triggers as needing to be
processed after its rule, to prevent possible failure during
- parallel pg_restore (Tom Lane)
+ parallel pg_restore (Tom Lane)
@@ -5451,7 +5739,7 @@ Branch: REL9_1_STABLE [4c8b07d3c] 2016-02-03 09:25:34 -0500
- Install guards in pgbench against corner-case overflow
+ Install guards in pgbench against corner-case overflow
conditions during evaluation of script-specified division or modulo
operators (Fabien Coelho, Michael Paquier)
@@ -5465,7 +5753,7 @@ Branch: REL9_5_STABLE [7ef311eb4] 2016-01-05 17:25:12 -0300
- Suppress useless warning message when pg_receivexlog
+ Suppress useless warning message when pg_receivexlog
connects to a pre-9.4 server (Marco Nenciarini)
@@ -5483,15 +5771,15 @@ Branch: REL9_5_STABLE [5ef26b8de] 2016-01-11 20:06:47 -0500
- Avoid dump/reload problems when using both plpython2
- and plpython3 (Tom Lane)
+ Avoid dump/reload problems when using both plpython2
+ and plpython3 (Tom Lane)
- In principle, both versions of PL/Python can be used in
+ In principle, both versions of PL/Python can be used in
the same database, though not in the same session (because the two
- versions of libpython cannot safely be used concurrently).
- However, pg_restore and pg_upgrade both
+ versions of libpython cannot safely be used concurrently).
+ However, pg_restore and pg_upgrade both
do things that can fall foul of the same-session restriction. Work
around that by changing the timing of the check.
@@ -5508,7 +5796,7 @@ Branch: REL9_5_STABLE [a66c1fcdd] 2016-01-08 11:39:28 -0500
- Fix PL/Python regression tests to pass with Python 3.5
+ Fix PL/Python regression tests to pass with Python 3.5
(Peter Eisentraut)
@@ -5525,16 +5813,16 @@ Branch: REL9_1_STABLE [b1f591c50] 2016-02-05 20:23:19 -0500
- Prevent certain PL/Java parameters from being set by
+ Prevent certain PL/Java parameters from being set by
non-superusers (Noah Misch)
- This change mitigates a PL/Java security bug
- (CVE-2016-0766), which was fixed in PL/Java by marking
+ This change mitigates a PL/Java security bug
+ (CVE-2016-0766), which was fixed in PL/Java by marking
these parameters as superuser-only. To fix the security hazard for
- sites that update PostgreSQL more frequently
- than PL/Java, make the core code aware of them also.
+ sites that update PostgreSQL more frequently
+ than PL/Java, make the core code aware of them also.
@@ -5551,14 +5839,14 @@ Branch: REL9_4_STABLE [33b26426e] 2016-02-08 11:10:14 +0100
- Fix ecpg-supplied header files to not contain comments
+ Fix ecpg-supplied header files to not contain comments
continued from a preprocessor directive line onto the next line
(Michael Meskes)
- Such a comment is rejected by ecpg. It's not yet clear
- whether ecpg itself should be changed.
+ Such a comment is rejected by ecpg. It's not yet clear
+ whether ecpg itself should be changed.
@@ -5572,8 +5860,8 @@ Branch: REL9_3_STABLE [1f2b195eb] 2016-02-03 01:39:08 -0500
- Fix hstore_to_json_loose()'s test for whether
- an hstore value can be converted to a JSON number (Tom Lane)
+ Fix hstore_to_json_loose()'s test for whether
+ an hstore value can be converted to a JSON number (Tom Lane)
@@ -5594,8 +5882,8 @@ Branch: REL9_4_STABLE [2099b911d] 2016-02-04 22:27:47 -0500
- In contrib/postgres_fdw, fix bugs triggered by use
- of tableoid in data-modifying commands (Etsuro Fujita,
+ In contrib/postgres_fdw, fix bugs triggered by use
+ of tableoid in data-modifying commands (Etsuro Fujita,
Robert Haas)
@@ -5608,7 +5896,7 @@ Branch: REL9_5_STABLE [47acf3add] 2016-01-22 11:53:06 -0500
- Fix ill-advised restriction of NAMEDATALEN to be less
+ Fix ill-advised restriction of NAMEDATALEN to be less
than 256 (Robert Haas, Tom Lane)
@@ -5645,7 +5933,7 @@ Branch: REL9_1_STABLE [b1bc38144] 2016-01-19 23:30:28 -0500
- Ensure that dynloader.h is included in the installed
+ Ensure that dynloader.h is included in the installed
header files in MSVC builds (Bruce Momjian, Michael Paquier)
@@ -5662,7 +5950,7 @@ Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
- Update time zone data files to tzdata release 2016a for
+ Update time zone data files to tzdata release 2016a for
DST law changes in Cayman Islands, Metlakatla, and Trans-Baikal
Territory (Zabaykalsky Krai), plus historical corrections for Pakistan.
@@ -5685,7 +5973,7 @@ Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
Overview
- Major enhancements in PostgreSQL 9.5 include:
+ Major enhancements in PostgreSQL 9.5 include:
@@ -5694,31 +5982,31 @@ Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
- Allow INSERTs
+ Allow INSERTs
that would generate constraint conflicts to be turned into
- UPDATEs or ignored
+ UPDATEs or ignored
- Add GROUP BY analysis features GROUPING SETS,
- CUBE and
- ROLLUP
+ Add GROUP BY analysis features GROUPING SETS,
+ CUBE and
+ ROLLUP
- Add row-level security control
+ Add row-level security control
Create mechanisms for tracking
- the progress of replication,
+ the progress of replication,
including methods for identifying the origin of individual changes
during logical replication
@@ -5726,7 +6014,7 @@ Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
- Add Block Range Indexes (BRIN)
+ Add Block Range Indexes (BRIN)
@@ -5772,21 +6060,21 @@ Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
2015-03-11 [c6b3c93] Tom Lane: Make operator precedence follow the SQL standar..
-->
- Adjust operator precedence
- to match the SQL standard (Tom Lane)
+ Adjust operator precedence
+ to match the SQL standard (Tom Lane)
The precedence of <=, >=
and <> has been reduced to match that of
<, >
- and =. The precedence of IS tests
- (e.g., x IS NULL) has been reduced to be
+ and =. The precedence of IS tests
+ (e.g., xIS NULL) has been reduced to be
just below these six comparison operators.
- Also, multi-keyword operators beginning with NOT now have
+ Also, multi-keyword operators beginning with NOT now have
the precedence of their base operator (for example, NOT
- BETWEEN now has the same precedence as BETWEEN) whereas
- before they had inconsistent precedence, behaving like NOT
+ BETWEEN now has the same precedence as BETWEEN) whereas
+ before they had inconsistent precedence, behaving like NOT
with respect to their left operand but like their base operator with
respect to their right operand. The new configuration
parameter can be
@@ -5801,7 +6089,7 @@ Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
-->
Change 's default shutdown mode from
- smart to fast (Bruce Momjian)
+ smart to fast (Bruce Momjian)
@@ -5816,18 +6104,18 @@ Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
-->
Use assignment cast behavior for data type conversions
- in PL/pgSQL assignments, rather than converting to and
+ in PL/pgSQL assignments, rather than converting to and
from text (Tom Lane)
This change causes conversions of Booleans to strings to
- produce true or false, not t
- or f. Other type conversions may succeed in more cases
- than before; for example, assigning a numeric value 3.9 to
+ produce true or false, not t
+ or f. Other type conversions may succeed in more cases
+ than before; for example, assigning a numeric value 3.9 to
an integer variable will now assign 4 rather than failing. If no
assignment-grade cast is defined for the particular source and
- destination types, PL/pgSQL will fall back to its old
+ destination types, PL/pgSQL will fall back to its old
I/O conversion behavior.
@@ -5838,13 +6126,13 @@ Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
-->
Allow characters in server
- command-line options to be escaped with a backslash (Andres Freund)
+ command-line options to be escaped with a backslash (Andres Freund)
Formerly, spaces in the options string always separated options, so
there was no way to include a space in an option value. Including
- a backslash in an option value now requires writing \\.
+ a backslash in an option value now requires writing \\.
@@ -5854,9 +6142,9 @@ Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
-->
Change the default value of the GSSAPI include_realm parameter to 1, so
- that by default the realm is not removed from a GSS
- or SSPI principal name (Stephen Frost)
+ linkend="gssapi-auth">include_realm parameter to 1, so
+ that by default the realm is not removed from a GSS
+ or SSPI principal name (Stephen Frost)
@@ -5867,7 +6155,7 @@ Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
2015-06-29 [d661532] Heikki..: Also trigger restartpoints based on max_wal_siz..
-->
- Replace configuration parameter checkpoint_segments
+ Replace configuration parameter checkpoint_segments
with
and (Heikki Linnakangas)
@@ -5889,13 +6177,13 @@ max_wal_size = (3 * checkpoint_segments) * 16MB
2014-06-18 [df8b7bc] Tom Lane: Improve our mechanism for controlling the Linux..
-->
- Control the Linux OOM killer via new environment
+ Control the Linux OOM killer via new environment
variables PG_OOM_ADJUST_FILE
+ linkend="linux-memory-overcommit">PG_OOM_ADJUST_FILE
and PG_OOM_ADJUST_VALUE,
- instead of compile-time options LINUX_OOM_SCORE_ADJ and
- LINUX_OOM_ADJ
+ linkend="linux-memory-overcommit">PG_OOM_ADJUST_VALUE,
+ instead of compile-time options LINUX_OOM_SCORE_ADJ and
+ LINUX_OOM_ADJ
(Gurjeet Singh)
@@ -5907,7 +6195,7 @@ max_wal_size = (3 * checkpoint_segments) * 16MB
-->
Decommission server configuration
- parameter ssl_renegotiation_limit, which was deprecated
+ parameter ssl_renegotiation_limit, which was deprecated
in earlier releases (Andres Freund)
@@ -5915,8 +6203,8 @@ max_wal_size = (3 * checkpoint_segments) * 16MB
While SSL renegotiation is a good idea in theory, it has caused enough
bugs to be considered a net negative in practice, and it is due to be
removed from future versions of the relevant standards. We have
- therefore removed support for it from PostgreSQL.
- The ssl_renegotiation_limit parameter still exists, but
+ therefore removed support for it from PostgreSQL.
+ The ssl_renegotiation_limit parameter still exists, but
cannot be set to anything but zero (disabled). It's not documented
anymore, either.
@@ -5927,7 +6215,7 @@ max_wal_size = (3 * checkpoint_segments) * 16MB
2014-11-05 [525a489] Tom Lane: Remove the last vestige of server-side autocomm..
-->
- Remove server configuration parameter autocommit, which
+ Remove server configuration parameter autocommit, which
was already deprecated and non-operational (Tom Lane)
@@ -5937,8 +6225,8 @@ max_wal_size = (3 * checkpoint_segments) * 16MB
2015-03-06 [bb8582a] Peter ..: Remove rolcatupdate
-->
- Remove the pg_authid
- catalog's rolcatupdate field, as it had no usefulness
+ Remove the pg_authid
+ catalog's rolcatupdate field, as it had no usefulness
(Adam Brightwell)
@@ -5949,8 +6237,8 @@ max_wal_size = (3 * checkpoint_segments) * 16MB
-->
The pg_stat_replication
- system view's sent field is now NULL, not zero, when
+ linkend="monitoring-stats-views-table">pg_stat_replication
+ system view's sent field is now NULL, not zero, when
it has no valid value (Magnus Hagander)
@@ -5960,13 +6248,13 @@ max_wal_size = (3 * checkpoint_segments) * 16MB
2015-07-17 [89ddd29] Andrew..: Support JSON negative array subscripts everywh..
-->
- Allow json and jsonb array extraction operators to
+ Allow json and jsonb array extraction operators to
accept negative subscripts, which count from the end of JSON arrays
(Peter Geoghegan, Andrew Dunstan)
- Previously, these operators returned NULL for negative
+ Previously, these operators returned NULL for negative
subscripts.
@@ -5999,12 +6287,12 @@ max_wal_size = (3 * checkpoint_segments) * 16MB
2015-05-15 [b0b7be6] Alvaro..: Add BRIN infrastructure for "inclusion" opclasses
-->
- Add Block Range Indexes (BRIN)
+ Add Block Range Indexes (BRIN)
(Álvaro Herrera)
- BRIN indexes store only summary data (such as minimum
+ BRIN indexes store only summary data (such as minimum
and maximum values) for ranges of heap blocks. They are therefore
very compact and cheap to update; but if the data is naturally
clustered, they can still provide substantial speedup of searches.
@@ -6018,7 +6306,7 @@ max_wal_size = (3 * checkpoint_segments) * 16MB
Allow queries to perform accurate distance filtering of
bounding-box-indexed objects (polygons, circles) using GiST indexes (Alexander Korotkov, Heikki
+ linkend="gist">GiST indexes (Alexander Korotkov, Heikki
Linnakangas)
@@ -6038,7 +6326,7 @@ max_wal_size = (3 * checkpoint_segments) * 16MB
2015-03-30 [0633a60] Heikki..: Add index-only scan support to range type GiST ..
-->
- Allow GiST indexes to perform index-only
+ Allow GiST indexes to perform index-only
scans (Anastasia Lubennikova, Heikki Linnakangas, Andreas Karlsson)
@@ -6049,14 +6337,14 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add configuration parameter
- to control the size of GIN pending lists (Fujii Masao)
+ to control the size of GIN pending lists (Fujii Masao)
This value can also be set on a per-index basis as an index storage
parameter. Previously the pending-list size was controlled
by , which was awkward because
- appropriate values for work_mem are often much too large
+ appropriate values for work_mem are often much too large
for this purpose.
@@ -6067,7 +6355,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Issue a warning during the creation of hash indexes because they are not
+ linkend="indexes-types">hash indexes because they are not
crash-safe (Bruce Momjian)
@@ -6088,8 +6376,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-13 [78efd5c] Robert..: Extend abbreviated key infrastructure to datum ..
-->
- Improve the speed of sorting of varchar, text,
- and numeric fields via abbreviated keys
+ Improve the speed of sorting of varchar, text,
+ and numeric fields via abbreviated keys
(Peter Geoghegan, Andrew Gierth, Robert Haas)
@@ -6101,8 +6389,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
Extend the infrastructure that allows sorting to be performed by
inlined, non-SQL-callable comparison functions to
- cover CREATE INDEX, REINDEX, and
- CLUSTER (Peter Geoghegan)
+ cover CREATE INDEX, REINDEX, and
+ CLUSTER (Peter Geoghegan)
@@ -6163,7 +6451,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
This particularly addresses scalability problems when running on
- systems with multiple CPU sockets.
+ systems with multiple CPU sockets.
@@ -6183,7 +6471,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow pushdown of query restrictions into subqueries with window functions, where appropriate
+ linkend="tutorial-window">window functions, where appropriate
(David Rowley)
@@ -6206,7 +6494,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
Teach the planner to use statistics obtained from an expression
index on a boolean-returning function, when a matching function call
- appears in WHERE (Tom Lane)
+ appears in WHERE (Tom Lane)
@@ -6215,7 +6503,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-09-23 [cfb2024] Tom Lane: Make ANALYZE compute basic statistics even for..
-->
- Make ANALYZE compute basic statistics (null fraction and
+ Make ANALYZE compute basic statistics (null fraction and
average column width) even for columns whose data type lacks an
equality function (Oleksandr Shulgin)
@@ -6229,7 +6517,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
- Speed up CRC (cyclic redundancy check) computations
+ Speed up CRC (cyclic redundancy check) computations
and switch to CRC-32C (Abhijit Menon-Sen, Heikki Linnakangas)
@@ -6249,7 +6537,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-07-01 [9f03ca9] Robert..: Avoid copying index tuples when building an ind..
-->
- Speed up CREATE INDEX by avoiding unnecessary memory
+ Speed up CREATE INDEX by avoiding unnecessary memory
copies (Robert Haas)
@@ -6283,7 +6571,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add per-table autovacuum logging control via new
- log_autovacuum_min_duration storage parameter
+ log_autovacuum_min_duration storage parameter
(Michael Paquier)
@@ -6299,7 +6587,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
This string, typically set in postgresql.conf,
+ linkend="config-setting-configuration-file">postgresql.conf,
allows clients to identify the cluster. This name also appears
in the process title of all server processes, allowing for easier
identification of processes belonging to the same cluster.
@@ -6321,7 +6609,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
- <acronym>SSL</>
+ <acronym>SSL</acronym>
@@ -6331,13 +6619,13 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Check Subject Alternative
- Names in SSL server certificates, if present
+ Names in SSL server certificates, if present
(Alexey Klyukin)
When they are present, this replaces checks against the certificate's
- Common Name.
+ Common Name.
@@ -6347,8 +6635,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add system view pg_stat_ssl to report
- SSL connection information (Magnus Hagander)
+ linkend="pg-stat-ssl-view">pg_stat_ssl to report
+ SSL connection information (Magnus Hagander)
@@ -6357,22 +6645,22 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-02-03 [91fa7b4] Heikki..: Add API functions to libpq to interrogate SSL ..
-->
- Add libpq functions to return SSL
+ Add libpq functions to return SSL
information in an implementation-independent way (Heikki Linnakangas)
- While PQgetssl() can
- still be used to call OpenSSL functions, it is now
+ While PQgetssl() can
+ still be used to call OpenSSL functions, it is now
considered deprecated because future versions
- of libpq might support other SSL
+ of libpq might support other SSL
implementations. When possible, use the new
functions PQsslAttribute(), PQsslAttributeNames(),
- and PQsslInUse()
- to obtain SSL information in
- an SSL-implementation-independent way.
+ linkend="libpq-pqsslattribute">PQsslAttribute(), PQsslAttributeNames(),
+ and PQsslInUse()
+ to obtain SSL information in
+ an SSL-implementation-independent way.
@@ -6381,7 +6669,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-04-09 [8a0d34e4] Peter ..: libpq: Don't overwrite existing OpenSSL thread..
-->
- Make libpq honor any OpenSSL
+ Make libpq honor any OpenSSL
thread callbacks (Jan Urbanski)
@@ -6406,20 +6694,20 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-06-29 [d661532] Heikki..: Also trigger restartpoints based on max_wal_siz..
-->
- Replace configuration parameter checkpoint_segments
+ Replace configuration parameter checkpoint_segments
with
and (Heikki Linnakangas)
- This change allows the allocation of a large number of WAL
+ This change allows the allocation of a large number of WAL
files without keeping them after they are no longer needed.
- Therefore the default for max_wal_size has been set
- to 1GB, much larger than the old default
- for checkpoint_segments.
+ Therefore the default for max_wal_size has been set
+ to 1GB, much larger than the old default
+ for checkpoint_segments.
Also note that standby servers perform restartpoints to try to limit
- their WAL space consumption to max_wal_size; previously
- they did not pay any attention to checkpoint_segments.
+ their WAL space consumption to max_wal_size; previously
+ they did not pay any attention to checkpoint_segments.
@@ -6428,18 +6716,18 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-06-18 [df8b7bc] Tom Lane: Improve our mechanism for controlling the Linux..
-->
- Control the Linux OOM killer via new environment
+ Control the Linux OOM killer via new environment
variables PG_OOM_ADJUST_FILE
+ linkend="linux-memory-overcommit">PG_OOM_ADJUST_FILE
and PG_OOM_ADJUST_VALUE
+ linkend="linux-memory-overcommit">PG_OOM_ADJUST_VALUE
(Gurjeet Singh)
- The previous OOM control infrastructure involved
- compile-time options LINUX_OOM_SCORE_ADJ and
- LINUX_OOM_ADJ, which are no longer supported.
+ The previous OOM control infrastructure involved
+ compile-time options LINUX_OOM_SCORE_ADJ and
+ LINUX_OOM_ADJ, which are no longer supported.
The new behavior is available in all builds.
@@ -6457,8 +6745,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
Time stamp information can be accessed using functions pg_xact_commit_timestamp()
- and pg_last_committed_xact().
+ linkend="functions-commit-timestamp">pg_xact_commit_timestamp()
+ and pg_last_committed_xact().
@@ -6468,7 +6756,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow to be set
- by ALTER ROLE SET (Peter Eisentraut, Kyotaro Horiguchi)
+ by ALTER ROLE SET (Peter Eisentraut, Kyotaro Horiguchi)
@@ -6477,7 +6765,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-04-03 [a75fb9b] Alvaro..: Have autovacuum workers listen to SIGHUP, too
-->
- Allow autovacuum workers
+ Allow autovacuum workers
to respond to configuration parameter changes during a run
(Michael Paquier)
@@ -6496,7 +6784,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
This means that assertions can no longer be turned
off if they were enabled at compile time, allowing for more
efficient code optimization. This change also removes the postgres option.
@@ -6517,7 +6805,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add system view pg_file_settings
+ linkend="view-pg-file-settings">pg_file_settings
to show the contents of the server's configuration files
(Sawada Masahiko)
@@ -6528,8 +6816,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-14 [a486e35] Peter ..: Add pg_settings.pending_restart column
-->
- Add pending_restart to the system view pg_settings to
+ Add pending_restart to the system view pg_settings to
indicate a change has been made but will not take effect until a
database restart (Peter Eisentraut)
@@ -6540,14 +6828,14 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-09-02 [bd3b7a9] Fujii ..: Support ALTER SYSTEM RESET command.
-->
- Allow ALTER SYSTEM
- values to be reset with ALTER SYSTEM RESET (Vik
+ Allow ALTER SYSTEM
+ values to be reset with ALTER SYSTEM RESET (Vik
Fearing)
This command removes the specified setting
- from postgresql.auto.conf.
+ from postgresql.auto.conf.
@@ -6568,7 +6856,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Create mechanisms for tracking
- the progress of replication,
+ the progress of replication,
including methods for identifying the origin of individual changes
during logical replication (Andres Freund)
@@ -6600,14 +6888,14 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-15 [51c11a7] Andres..: Remove pause_at_recovery_target recovery.conf s..
-->
- Add recovery.conf
+ Add recovery.conf
parameter recovery_target_action
+ linkend="recovery-target-action">recovery_target_action
to control post-recovery activity (Petr Jelínek)
- This replaces the old parameter pause_at_recovery_target.
+ This replaces the old parameter pause_at_recovery_target.
@@ -6617,8 +6905,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add new value
- always to allow standbys to always archive received
- WAL files (Fujii Masao)
+ always to allow standbys to always archive received
+ WAL files (Fujii Masao)
@@ -6629,7 +6917,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
Add configuration
parameter to
- control WAL read retry after failure
+ control WAL read retry after failure
(Alexey Vasiliev, Michael Paquier)
@@ -6643,7 +6931,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-11 [57aa5b2] Fujii ..: Add GUC to enable compression of full page imag..
-->
- Allow compression of full-page images stored in WAL
+ Allow compression of full-page images stored in WAL
(Rahila Syed, Michael Paquier)
@@ -6660,7 +6948,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-08 [de76884] Heikki..: At promotion, archive last segment from old tim..
-->
- Archive WAL files with suffix .partial
+ Archive WAL files with suffix .partial
during standby promotion (Heikki Linnakangas)
@@ -6677,9 +6965,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
By default, replication commands, e.g. IDENTIFY_SYSTEM,
+ linkend="protocol-replication">IDENTIFY_SYSTEM,
are not logged, even when is set
- to all.
+ to all.
@@ -6689,12 +6977,12 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Report the processes holding replication slots in pg_replication_slots
+ linkend="view-pg-replication-slots">pg_replication_slots
(Craig Ringer)
- The new output column is active_pid.
+ The new output column is active_pid.
@@ -6703,9 +6991,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-11-25 [b3fc672] Heikki..: Allow using connection URI in primary_conninfo.
-->
- Allow recovery.conf's primary_conninfo setting to
- use connection URIs, e.g. postgres://
+ Allow recovery.conf's primary_conninfo setting to
+ use connection URIs, e.g. postgres://
(Alexander Shulgin)
@@ -6725,16 +7013,16 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-08 [2c8f483] Andres..: Represent columns requiring insert and update p..
-->
- Allow INSERTs
+ Allow INSERTs
that would generate constraint conflicts to be turned into
- UPDATEs or ignored (Peter Geoghegan, Heikki
+ UPDATEs or ignored (Peter Geoghegan, Heikki
Linnakangas, Andres Freund)
- The syntax is INSERT ... ON CONFLICT DO NOTHING/UPDATE.
+ The syntax is INSERT ... ON CONFLICT DO NOTHING/UPDATE.
This is the Postgres implementation of the popular
- UPSERT command.
+ UPSERT command.
@@ -6743,10 +7031,10 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-16 [f3d3118] Andres..: Support GROUPING SETS, CUBE and ROLLUP.
-->
- Add GROUP BY analysis features GROUPING SETS,
- CUBE and
- ROLLUP
+ Add GROUP BY analysis features GROUPING SETS,
+ CUBE and
+ ROLLUP
(Andrew Gierth, Atri Sharma)
@@ -6757,13 +7045,13 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow setting multiple target columns in
- an UPDATE from the result of
+ an UPDATE from the result of
a single sub-SELECT (Tom Lane)
This is accomplished using the syntax UPDATE tab SET
- (col1, col2, ...) = (SELECT ...).
+ (col1, col2, ...) = (SELECT ...).
@@ -6772,13 +7060,13 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-10-07 [df630b0] Alvaro..: Implement SKIP LOCKED for row-level locks
-->
- Add SELECT option
- SKIP LOCKED to skip locked rows (Thomas Munro)
+ Add SELECT option
+ SKIP LOCKED to skip locked rows (Thomas Munro)
This does not throw an error for locked rows like
- NOWAIT does.
+ NOWAIT does.
@@ -6787,8 +7075,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-15 [f6d208d] Simon ..: TABLESAMPLE, SQL Standard and extensible
-->
- Add SELECT option
- TABLESAMPLE to return a subset of a table (Petr
+ Add SELECT option
+ TABLESAMPLE to return a subset of a table (Petr
Jelínek)
@@ -6796,7 +7084,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
This feature supports the SQL-standard table sampling methods.
In addition, there are provisions
for user-defined
- table sampling methods.
+ table sampling methods.
@@ -6825,13 +7113,13 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add more details about sort ordering in EXPLAIN output (Marius Timmer,
+ linkend="sql-explain">EXPLAIN output (Marius Timmer,
Lukas Kreft, Arne Scheffer)
- Details include COLLATE, DESC,
- USING, and NULLS FIRST/LAST.
+ Details include COLLATE, DESC,
+ USING, and NULLS FIRST/LAST.
@@ -6840,7 +7128,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-12-18 [35192f0] Alvaro..: Have VACUUM log number of skipped pages due to ..
-->
- Make VACUUM log the
+ Make VACUUM log the
number of pages skipped due to pins (Jim Nasby)
@@ -6850,15 +7138,15 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-02-20 [d42358e] Alvaro..: Have TRUNCATE update pgstat tuple counters
-->
- Make TRUNCATE properly
- update the pg_stat* tuple counters (Alexander Shulgin)
+ Make TRUNCATE properly
+ update the pg_stat* tuple counters (Alexander Shulgin)
- <xref linkend="SQL-REINDEX">
+ <xref linkend="sql-reindex">
@@ -6867,8 +7155,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-12-09 [fe263d1] Simon ..: REINDEX SCHEMA
-->
- Allow REINDEX to reindex an entire schema using the
- SCHEMA option (Sawada Masahiko)
+ Allow REINDEX to reindex an entire schema using the
+ SCHEMA option (Sawada Masahiko)
@@ -6877,7 +7165,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-15 [ecd222e] Fujii ..: Support VERBOSE option in REINDEX command.
-->
- Add VERBOSE option to REINDEX (Sawada
+ Add VERBOSE option to REINDEX (Sawada
Masahiko)
@@ -6887,8 +7175,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-12-09 [ae4e688] Simon ..: Silence REINDEX
-->
- Prevent REINDEX DATABASE and SCHEMA
- from outputting object names, unless VERBOSE is used
+ Prevent REINDEX DATABASE and SCHEMA
+ from outputting object names, unless VERBOSE is used
(Simon Riggs)
@@ -6898,7 +7186,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-04-09 [17d436d] Fujii ..: Remove obsolete FORCE option from REINDEX.
-->
- Remove obsolete FORCE option from REINDEX
+ Remove obsolete FORCE option from REINDEX
(Fujii Masao)
@@ -6918,7 +7206,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-09-19 [491c029] Stephe..: Row-Level Security Policies (RLS)
-->
- Add row-level security control
+ Add row-level security control
(Craig Ringer, KaiGai Kohei, Adam Brightwell, Dean Rasheed,
Stephen Frost)
@@ -6926,11 +7214,11 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
This feature allows row-by-row control over which users can add,
modify, or even see rows in a table. This is controlled by new
- commands CREATE/ALTER/DROP POLICY and ALTER TABLE ... ENABLE/DISABLE
- ROW SECURITY.
+ commands CREATE/ALTER/DROP POLICY and ALTER TABLE ... ENABLE/DISABLE
+ ROW SECURITY.
@@ -6941,8 +7229,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
Allow changing of the WAL
logging status of a table after creation with ALTER TABLE ... SET LOGGED /
- UNLOGGED (Fabrízio de Royes Mello)
+ linkend="sql-altertable">ALTER TABLE ... SET LOGGED /
+ UNLOGGED (Fabrízio de Royes Mello)
@@ -6953,12 +7241,12 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-12-13 [e39b6f9] Andrew..: Add CINE option for CREATE TABLE AS and CREATE ..
-->
- Add IF NOT EXISTS clause to CREATE TABLE AS,
- CREATE INDEX,
- CREATE SEQUENCE,
- and CREATE
- MATERIALIZED VIEW (Fabrízio de Royes Mello)
+ Add IF NOT EXISTS clause to CREATE TABLE AS,
+ CREATE INDEX,
+ CREATE SEQUENCE,
+ and CREATE
+ MATERIALIZED VIEW (Fabrízio de Royes Mello)
@@ -6967,9 +7255,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-24 [1d8198b] Bruce ..: Add support for ALTER TABLE IF EXISTS ... RENAM..
-->
- Add support for IF EXISTS to ALTER TABLE ... RENAME
- CONSTRAINT (Bruce Momjian)
+ Add support for IF EXISTS to ALTER TABLE ... RENAME
+ CONSTRAINT (Bruce Momjian)
@@ -6978,17 +7266,17 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-09 [31eae60] Alvaro..: Allow CURRENT/SESSION_USER to be used in certai..
-->
- Allow some DDL commands to accept CURRENT_USER
- or SESSION_USER, meaning the current user or session
+ Allow some DDL commands to accept CURRENT_USER
+ or SESSION_USER, meaning the current user or session
user, in place of a specific user name (Kyotaro Horiguchi,
Álvaro Herrera)
This feature is now supported in
- , ,
- , ,
- and ALTER object OWNER TO commands.
+ , ,
+ , ,
+ and ALTER object OWNER TO commands.
@@ -6997,8 +7285,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-12-23 [7eca575] Alvaro..: get_object_address: separate domain constraints..
-->
- Support comments on domain
- constraints (Álvaro Herrera)
+ Support comments on domain
+ constraints (Álvaro Herrera)
@@ -7017,14 +7305,14 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-11 [fa26424] Stephe..: Allow LOCK TABLE .. ROW EXCLUSIVE MODE with IN..
-->
- Allow LOCK TABLE ... ROW EXCLUSIVE
- MODE for those with INSERT privileges on the
+ Allow LOCK TABLE ... ROW EXCLUSIVE
+ MODE for those with INSERT privileges on the
target table (Stephen Frost)
- Previously this command required UPDATE, DELETE,
- or TRUNCATE privileges.
+ Previously this command required UPDATE, DELETE,
+ or TRUNCATE privileges.
@@ -7033,7 +7321,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-23 [e5f455f] Tom Lane: Apply table and domain CHECK constraints in nam.
-->
- Apply table and domain CHECK constraints in order by name
+ Apply table and domain CHECK constraints in order by name
(Tom Lane)
@@ -7049,16 +7337,16 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow CREATE/ALTER DATABASE
- to manipulate datistemplate and
- datallowconn (Vik Fearing)
+ linkend="sql-createdatabase">CREATE/ALTER DATABASE
+ to manipulate datistemplate and
+ datallowconn (Vik Fearing)
This allows these per-database settings to be
changed without manually modifying the pg_database
+ linkend="catalog-pg-database">pg_database
system catalog.
@@ -7075,7 +7363,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-07-10 [59efda3] Tom Lane: Implement IMPORT FOREIGN SCHEMA.
-->
- Add support for
+ Add support for
(Ronan Dunklau, Michael Paquier, Tom Lane)
@@ -7090,7 +7378,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-12-17 [fc2ac1f] Tom Lane: Allow CHECK constraints to be placed on foreign..
-->
- Allow CHECK constraints to be placed on foreign tables
+ Allow CHECK constraints to be placed on foreign tables
(Shigeru Hanada, Etsuro Fujita)
@@ -7099,7 +7387,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
and are not enforced locally. However, they are assumed to hold for
purposes of query optimization, such
as constraint
- exclusion.
+ exclusion.
@@ -7115,7 +7403,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
To let this work naturally, foreign tables are now allowed to have
check constraints marked as not valid, and to set storage
- and OID characteristics, even though these operations are
+ and OID characteristics, even though these operations are
effectively no-ops for a foreign table.
@@ -7145,14 +7433,14 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-11 [b488c58] Alvaro..: Allow on-the-fly capture of DDL event details
-->
- Whenever a ddl_command_end event trigger is installed,
- capture details of DDL activity for it to inspect
+ Whenever a ddl_command_end event trigger is installed,
+ capture details of DDL activity for it to inspect
(Álvaro Herrera)
This information is available through a set-returning function pg_event_trigger_ddl_commands(),
+ linkend="pg-event-trigger-ddl-command-end-functions">pg_event_trigger_ddl_commands(),
or by inspection of C data structures if that function doesn't
provide enough detail.
@@ -7164,7 +7452,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow event triggers on table rewrites caused by ALTER TABLE (Dimitri
+ linkend="sql-altertable">ALTER TABLE (Dimitri
Fontaine)
@@ -7175,10 +7463,10 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add event trigger support for database-level COMMENT, SECURITY LABEL,
- and GRANT/REVOKE (Álvaro Herrera)
+ linkend="sql-comment">COMMENT, SECURITY LABEL,
+ and GRANT/REVOKE (Álvaro Herrera)
@@ -7189,7 +7477,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add columns to the output of pg_event_trigger_dropped_objects
+ linkend="pg-event-trigger-sql-drop-functions">pg_event_trigger_dropped_objects
(Álvaro Herrera)
@@ -7214,12 +7502,12 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-09-09 [57b1085] Peter ..: Allow empty content in xml type
-->
- Allow the xml data type
+ Allow the xml data type
to accept empty or all-whitespace content values (Peter Eisentraut)
- This is required by the SQL/XML
+ This is required by the SQL/XML
specification.
@@ -7229,8 +7517,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-10-21 [6f04368] Peter ..: Allow input format xxxx-xxxx-xxxx for macaddr ..
-->
- Allow macaddr input
- using the format xxxx-xxxx-xxxx (Herwin Weststrate)
+ Allow macaddr input
+ using the format xxxx-xxxx-xxxx (Herwin Weststrate)
@@ -7240,15 +7528,15 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Disallow non-SQL-standard syntax for interval with
+ linkend="datatype-interval-input">interval with
both precision and field specifications (Bruce Momjian)
Per the standard, such type specifications should be written as,
- for example, INTERVAL MINUTE TO SECOND(2).
- PostgreSQL formerly allowed this to be written as
- INTERVAL(2) MINUTE TO SECOND, but it must now be
+ for example, INTERVAL MINUTE TO SECOND(2).
+ PostgreSQL formerly allowed this to be written as
+ INTERVAL(2) MINUTE TO SECOND, but it must now be
written in the standard way.
@@ -7259,8 +7547,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add selectivity estimators for inet/cidr operators and improve
+ linkend="datatype-inet">inet/cidr operators and improve
estimators for text search functions (Emre Hasegeli, Tom Lane)
@@ -7272,9 +7560,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add data
- types regrole
- and regnamespace
- to simplify entering and pretty-printing the OID of a role
+ types regrole
+ and regnamespace
+ to simplify entering and pretty-printing the OID of a role
or namespace (Kyotaro Horiguchi)
@@ -7282,7 +7570,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
- <link linkend="datatype-json"><acronym>JSON</></link>
+ <link linkend="datatype-json"><acronym>JSON</acronym></link>
@@ -7292,10 +7580,10 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-31 [37def42] Andrew..: Rename jsonb_replace to jsonb_set and allow it ..
-->
- Add jsonb functions jsonb_set()
+ Add jsonb functions jsonb_set()
and jsonb_pretty()
+ linkend="functions-json-processing-table">jsonb_pretty()
(Dmitry Dolgov, Andrew Dunstan, Petr Jelínek)
@@ -7305,23 +7593,23 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-12-12 [7e354ab] Andrew..: Add several generator functions for jsonb that ..
-->
- Add jsonb generator functions to_jsonb(),
+ Add jsonb generator functions to_jsonb(),
jsonb_object(),
+ linkend="functions-json-creation-table">jsonb_object(),
jsonb_build_object(),
+ linkend="functions-json-creation-table">jsonb_build_object(),
jsonb_build_array(),
+ linkend="functions-json-creation-table">jsonb_build_array(),
jsonb_agg(),
+ linkend="functions-aggregate-table">jsonb_agg(),
and jsonb_object_agg()
+ linkend="functions-aggregate-table">jsonb_object_agg()
(Andrew Dunstan)
- Equivalent functions already existed for type json.
+ Equivalent functions already existed for type json.
@@ -7331,8 +7619,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Reduce casting requirements to/from json and jsonb (Tom Lane)
+ linkend="datatype-json">json and jsonb (Tom Lane)
@@ -7341,9 +7629,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-06-11 [908e234] Andrew..: Rename jsonb - text[] operator to #- to avoid a..
-->
- Allow text, text array, and integer
- values to be subtracted
- from jsonb documents (Dmitry Dolgov, Andrew Dunstan)
+ Allow text, text array, and integer
+ values to be subtracted
+ from jsonb documents (Dmitry Dolgov, Andrew Dunstan)
@@ -7352,8 +7640,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-12 [c694701] Andrew..: Additional functions and operators for jsonb
-->
- Add jsonb || operator
+ Add jsonb|| operator
(Dmitry Dolgov, Andrew Dunstan)
@@ -7364,9 +7652,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add json_strip_nulls()
+ linkend="functions-json-processing-table">json_strip_nulls()
and jsonb_strip_nulls()
+ linkend="functions-json-processing-table">jsonb_strip_nulls()
functions to remove JSON null values from documents
(Andrew Dunstan)
@@ -7388,8 +7676,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-11-11 [1871c89] Fujii ..: Add generate_series(numeric, numeric).
-->
- Add generate_series()
- for numeric values (Plato Malugin)
+ Add generate_series()
+ for numeric values (Plato Malugin)
@@ -7399,8 +7687,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow array_agg() and
- ARRAY() to take arrays as inputs (Ali Akbar, Tom Lane)
+ linkend="functions-aggregate-table">array_agg() and
+ ARRAY() to take arrays as inputs (Ali Akbar, Tom Lane)
@@ -7411,9 +7699,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add functions array_position()
+ linkend="array-functions-table">array_position()
and array_positions()
+ linkend="array-functions-table">array_positions()
to return subscripts of array values (Pavel Stehule)
@@ -7423,8 +7711,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-12-15 [4520ba6] Heikki..: Add point <-> polygon distance operator.
-->
- Add a point-to-polygon distance operator
- <->
+ Add a point-to-polygon distance operator
+ <->
(Alexander Korotkov)
@@ -7435,8 +7723,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow multibyte characters as escapes in SIMILAR TO
- and SUBSTRING
+ linkend="functions-similarto-regexp">SIMILAR TO
+ and SUBSTRING
(Jeff Davis)
@@ -7451,7 +7739,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add a width_bucket()
+ linkend="functions-math-func-table">width_bucket()
variant that supports any sortable data type and non-uniform bucket
widths (Petr Jelínek)
@@ -7462,8 +7750,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-06-28 [cb2acb1] Heikki..: Add missing_ok option to the SQL functions for..
-->
- Add an optional missing_ok argument to pg_read_file()
+ Add an optional missing_ok argument to pg_read_file()
and related functions (Michael Paquier, Heikki Linnakangas)
@@ -7473,14 +7761,14 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-10 [865f14a] Robert..: Allow named parameters to be specified using =>..
-->
- Allow =>
+ Allow =>
to specify named parameters in function calls (Pavel Stehule)
- Previously only := could be used. This requires removing
- the possibility for => to be a user-defined operator.
- Creation of user-defined => operators has been issuing
+ Previously only := could be used. This requires removing
+ the possibility for => to be a user-defined operator.
+ Creation of user-defined => operators has been issuing
warnings since PostgreSQL 9.0.
@@ -7490,7 +7778,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-25 [06bf0dd] Tom Lane: Upgrade src/port/rint.c to be POSIX-compliant.
-->
- Add POSIX-compliant rounding for platforms that use
+ Add POSIX-compliant rounding for platforms that use
PostgreSQL-supplied rounding functions (Pedro Gimeno Fortea)
@@ -7509,11 +7797,11 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add function pg_get_object_address()
- to return OIDs that uniquely
+ linkend="functions-info-object-table">pg_get_object_address()
+ to return OIDs that uniquely
identify an object, and function pg_identify_object_as_address()
- to return object information based on OIDs (Álvaro
+ linkend="functions-info-object-table">pg_identify_object_as_address()
+ to return object information based on OIDs (Álvaro
Herrera)
@@ -7524,11 +7812,11 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Loosen security checks for viewing queries in pg_stat_activity,
+ linkend="pg-stat-activity-view">pg_stat_activity,
executing pg_cancel_backend(),
+ linkend="functions-admin-signal-table">pg_cancel_backend(),
and executing pg_terminate_backend()
+ linkend="functions-admin-signal-table">pg_terminate_backend()
(Stephen Frost)
@@ -7544,7 +7832,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add pg_stat_get_snapshot_timestamp()
+ linkend="monitoring-stats-funcs-table">pg_stat_get_snapshot_timestamp()
to output the time stamp of the statistics snapshot (Matt Kelly)
@@ -7560,7 +7848,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add mxid_age()
+ linkend="vacuum-for-multixact-wraparound">mxid_age()
to compute multi-xid age (Bruce Momjian)
@@ -7578,9 +7866,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-08-28 [6c40f83] Tom Lane: Add min and max aggregates for inet/cidr data t..
-->
- Add min()/max() aggregates
- for inet/cidr data types (Haribabu
+ Add min()/max() aggregates
+ for inet/cidr data types (Haribabu
Kommi)
@@ -7613,12 +7901,12 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Improve support for composite types in PL/Python (Ed Behn, Ronan
+ linkend="plpython">PL/Python (Ed Behn, Ronan
Dunklau)
- This allows PL/Python functions to return arrays
+ This allows PL/Python functions to return arrays
of composite types.
@@ -7629,7 +7917,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Reduce lossiness of PL/Python floating-point value
+ linkend="plpython">PL/Python floating-point value
conversions (Marko Kreen)
@@ -7639,19 +7927,19 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-04-26 [cac7658] Peter ..: Add transforms feature
-->
- Allow specification of conversion routines between SQL
+ Allow specification of conversion routines between SQL
data types and data types of procedural languages (Peter Eisentraut)
This change adds new commands CREATE/DROP TRANSFORM.
+ linkend="sql-createtransform">CREATE/DROP TRANSFORM.
This also adds optional transformations between the hstore and ltree types to/from PL/Perl and PL/Python.
+ linkend="hstore">hstore and ltree types to/from PL/Perl and PL/Python.
@@ -7670,7 +7958,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-02-16 [9e3ad1a] Tom Lane: Use fast path in plpgsql's RETURN/RETURN NEXT i..
-->
- Improve PL/pgSQL array
+ Improve PL/pgSQL array
performance (Tom Lane)
@@ -7680,8 +7968,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-25 [a4847fc] Tom Lane: Add an ASSERT statement in plpgsql.
-->
- Add an ASSERT
- statement in PL/pgSQL (Pavel Stehule)
+ Add an ASSERT
+ statement in PL/pgSQL (Pavel Stehule)
@@ -7690,7 +7978,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-11-25 [bb1b8f6] Tom Lane: De-reserve most statement-introducing keywords ..
-->
- Allow more PL/pgSQL
+ Allow more PL/pgSQL
keywords to be used as identifiers (Tom Lane)
@@ -7715,11 +8003,11 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Move pg_archivecleanup,
- pg_test_fsync,
- pg_test_timing,
- and pg_xlogdump
- from contrib to src/bin (Peter Eisentraut)
+ linkend="pgarchivecleanup">pg_archivecleanup,
+ pg_test_fsync,
+ pg_test_timing,
+ and pg_xlogdump
+ from contrib to src/bin (Peter Eisentraut)
@@ -7733,7 +8021,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-23 [61081e7] Heikki..: Add pg_rewind, for re-synchronizing a master se..
-->
- Add pg_rewind,
+ Add pg_rewind,
which allows re-synchronizing a master server after failback
(Heikki Linnakangas)
@@ -7745,13 +8033,13 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow pg_receivexlog
+ linkend="app-pgreceivewal">pg_receivexlog
to manage physical replication slots (Michael Paquier)
- This is controlled via new and
+ options.
@@ -7761,13 +8049,13 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow pg_receivexlog
- to synchronously flush WAL to storage using new
- option (Furuya Osamu, Fujii Masao)
- Without this, WAL files are fsync'ed only on close.
+ Without this, WAL files are fsync'ed only on close.
@@ -7776,8 +8064,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-01-23 [a179232] Alvaro..: vacuumdb: enable parallel mode
-->
- Allow vacuumdb to
- vacuum in parallel using new option (Dilip Kumar)
@@ -7786,7 +8074,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-11-12 [5094da9] Alvaro..: vacuumdb: don't prompt for passwords over and ..
-->
- In vacuumdb, do not
+ In vacuumdb, do not
prompt for the same password repeatedly when multiple connections
are necessary (Haribabu Kommi, Michael Paquier)
@@ -7797,8 +8085,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-15 [458a077] Fujii ..: Support ––verbose option in reindexdb.
-->
- Add
@@ -7808,10 +8096,10 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-12 [72d422a] Andrew..: Map basebackup tablespaces using a tablespace_..
-->
- Make pg_basebackup
- use a tablespace mapping file when using tar format,
+ Make pg_basebackup
+ use a tablespace mapping file when using tar format,
to support symbolic links and file paths of 100+ characters in length
- on MS Windows (Amit Kapila)
+ on MS Windows (Amit Kapila)
@@ -7821,15 +8109,15 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-09-19 [bdd5726] Andres..: Add the capability to display summary statistic..
-->
- Add pg_xlogdump option
- to display summary statistics (Abhijit Menon-Sen)
- <xref linkend="APP-PSQL">
+ <xref linkend="app-psql">
@@ -7838,7 +8126,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-31 [9d9991c] Bruce ..: psql: add asciidoc output format
-->
- Allow psql to produce AsciiDoc output (Szymon Guz)
+ Allow psql to produce AsciiDoc output (Szymon Guz)
@@ -7847,14 +8135,14 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-07-10 [5b214c5] Fujii ..: Add new ECHO mode 'errors' that displays only ..
-->
- Add an errors mode that displays only failed commands
- to psql's ECHO variable
+ Add an errors mode that displays only failed commands
+ to psql's ECHO variable
(Pavel Stehule)
- This behavior can also be selected with psql's
- option.
@@ -7864,12 +8152,12 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Provide separate column, header, and border linestyle control
- in psql's unicode linestyle (Pavel Stehule)
+ in psql's unicode linestyle (Pavel Stehule)
Single or double lines are supported; the default is
- single.
+ single.
@@ -7878,8 +8166,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-09-02 [51bb795] Andres..: Add psql PROMPT variable showing which line of ..
-->
- Add new option %l in psql's PROMPT variables
+ Add new option %l in psql's PROMPT variables
to display the current multiline statement line number
(Sawada Masahiko)
@@ -7890,8 +8178,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-28 [7655f4c] Andrew..: Add a pager_min_lines setting to psql
-->
- Add \pset option pager_min_lines
+ Add \pset option pager_min_lines
to control pager invocation (Andrew Dunstan)
@@ -7901,7 +8189,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-11-21 [4077fb4] Andrew..: Fix an error in psql that overcounted output l..
-->
- Improve psql line counting used when deciding
+ Improve psql line counting used when deciding
to invoke the pager (Andrew Dunstan)
@@ -7912,8 +8200,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-12-08 [e90371d] Tom Lane: Make failure to open psql log-file fatal.
-->
- psql now fails if the file specified by
- an or switch cannot be
written (Tom Lane, Daniel Vérité)
@@ -7927,7 +8215,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-07-12 [bd40951] Andres..: Minimal psql tab completion support for SET se..
-->
- Add psql tab completion when setting the
+ Add psql tab completion when setting the
variable (Jeff Janes)
@@ -7941,7 +8229,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-06-23 [631e7f6] Heikki..: Improve tab-completion of DROP and ALTER ENABLE..
-->
- Improve psql's tab completion for triggers and rules
+ Improve psql's tab completion for triggers and rules
(Andreas Karlsson)
@@ -7949,7 +8237,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
- <link linkend="APP-PSQL-meta-commands">Backslash Commands</link>
+ <link linkend="app-psql-meta-commands">Backslash Commands</link>
@@ -7958,17 +8246,17 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-09-10 [07c8651] Andres..: Add new psql help topics, accessible to both..
-->
- Add psql \? help sections
- variables and options (Pavel Stehule)
+ Add psql\? help sections
+ variables and options (Pavel Stehule)
- \? variables shows psql's special
- variables and \? options shows the command-line options.
- \? commands shows the meta-commands, which is the
+ \? variables shows psql's special
+ variables and \? options shows the command-line options.
+ \? commands shows the meta-commands, which is the
traditional output and remains the default. These help displays
can also be obtained with the command-line
- option --help=section.
+ option --help=section.
@@ -7977,7 +8265,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-07-14 [ee80f04] Alvaro..: psql: Show tablespace size in \db+
-->
- Show tablespace size in psql's \db+
+ Show tablespace size in psql's \db+
(Fabrízio de Royes Mello)
@@ -7987,7 +8275,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-04-09 [a6f3c1f] Magnus..: Show owner of types in psql \dT+
-->
- Show data type owners in psql's \dT+
+ Show data type owners in psql's \dT+
(Magnus Hagander)
@@ -7997,13 +8285,13 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-09-04 [f6f654f] Fujii ..: Allow \watch to display query execution time if..
-->
- Allow psql's \watch to output
- \timing information (Fujii Masao)
+ Allow psql's \watch to output
+ \timing information (Fujii Masao)
- Also prevent
@@ -8012,8 +8300,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-11-22 [eca2b9b] Andrew..: Rework echo_hidden for \sf and \ef from commit ..
-->
- Make psql's \sf and \ef
- commands honor ECHO_HIDDEN (Andrew Dunstan)
+ Make psql's \sf and \ef
+ commands honor ECHO_HIDDEN (Andrew Dunstan)
@@ -8022,8 +8310,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-08-12 [e15c4ab] Fujii ..: Add tab-completion for \unset and valid setting..
-->
- Improve psql tab completion for \set,
- \unset, and :variable names (Pavel
+ Improve psql tab completion for \set,
+ \unset, and :variable names (Pavel
Stehule)
@@ -8034,7 +8322,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow tab completion of role names
- in psql \c commands (Ian Barwick)
+ in psql\c commands (Ian Barwick)
@@ -8045,7 +8333,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
- <xref linkend="APP-PGDUMP">
+ <xref linkend="app-pgdump">
@@ -8054,15 +8342,15 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-11-17 [be1cc8f] Simon ..: Add pg_dump ––snapshot option
-->
- Allow pg_dump to share a snapshot taken by another
- session using (Simon Riggs, Michael Paquier)
The remote snapshot must have been exported by
- pg_export_snapshot() or logical replication slot
+ pg_export_snapshot() or logical replication slot
creation. This can be used to share a consistent snapshot
- across multiple pg_dump processes.
+ across multiple pg_dump processes.
@@ -8087,13 +8375,13 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-07-07 [7700597] Tom Lane: In pg_dump, show server and pg_dump versions w..
-->
- Make pg_dump always print the server and
- pg_dump versions (Jing Wang)
+ Make pg_dump always print the server and
+ pg_dump versions (Jing Wang)
Previously, version information was only printed in
- mode.
@@ -8102,9 +8390,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-06-04 [232cd63] Fujii ..: Remove -i/-ignore-version option from pg_dump..
-->
- Remove the long-ignored
@@ -8122,7 +8410,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-08-25 [ebe30ad] Bruce ..: pg_ctl, pg_upgrade: allow multiple -o/-O opti..
-->
- Support multiple pg_ctl options,
concatenating their values (Bruce Momjian)
@@ -8132,13 +8420,13 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-07-17 [c0e4520] Magnus..: Add option to pg_ctl to choose event source for..
-->
- Allow control of pg_ctl's event source logging
- on MS Windows (MauMau)
+ Allow control of pg_ctl's event source logging
+ on MS Windows (MauMau)
- This only controls pg_ctl, not the server, which
- has separate settings in postgresql.conf.
+ This only controls pg_ctl, not the server, which
+ has separate settings in postgresql.conf.
@@ -8148,14 +8436,14 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
If the server's listen address is set to a wildcard value
- (0.0.0.0 in IPv4 or :: in IPv6), connect via
+ (0.0.0.0 in IPv4 or :: in IPv6), connect via
the loopback address rather than trying to use the wildcard address
literally (Kondo Yuta)
This fix primarily affects Windows, since on other platforms
- pg_ctl will prefer to use a Unix-domain socket.
+ pg_ctl will prefer to use a Unix-domain socket.
@@ -8173,13 +8461,13 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-04-14 [9fa8b0e] Peter ..: Move pg_upgrade from contrib/ to src/bin/
-->
- Move pg_upgrade from contrib to
- src/bin (Peter Eisentraut)
+ Move pg_upgrade from contrib to
+ src/bin (Peter Eisentraut)
In connection with this change, the functionality previously
- provided by the pg_upgrade_support module has been
+ provided by the pg_upgrade_support module has been
moved into the core server.
@@ -8189,8 +8477,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-08-25 [ebe30ad] Bruce ..: pg_ctl, pg_upgrade: allow multiple -o/-O optio..
-->
- Support multiple pg_upgrade
- / options,
concatenating their values (Bruce Momjian)
@@ -8201,7 +8489,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Improve database collation comparisons in
- pg_upgrade (Heikki Linnakangas)
+ pg_upgrade (Heikki Linnakangas)
@@ -8228,7 +8516,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-04-13 [81134af] Peter ..: Move pgbench from contrib/ to src/bin/
-->
- Move pgbench from contrib to src/bin
+ Move pgbench from contrib to src/bin
(Peter Eisentraut)
@@ -8239,7 +8527,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Fix calculation of TPS number excluding connections
- establishing (Tatsuo Ishii, Fabien Coelho)
+ establishing (Tatsuo Ishii, Fabien Coelho)
@@ -8261,7 +8549,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
- This is controlled by a new option.
@@ -8271,7 +8559,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow pgbench to generate Gaussian/exponential distributions
- using \setrandom (Kondo Mitsumasa, Fabien Coelho)
+ using \setrandom (Kondo Mitsumasa, Fabien Coelho)
@@ -8280,9 +8568,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-02 [878fdcb] Robert..: pgbench: Add a real expression syntax to \set
-->
- Allow pgbench's \set command to handle
+ Allow pgbench's \set command to handle
arithmetic expressions containing more than one operator, and add
- % (modulo) to the set of operators it supports
+ % (modulo) to the set of operators it supports
(Robert Haas, Fabien Coelho)
@@ -8303,7 +8591,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-11-20 [2c03216] Heikki..: Revamp the WAL record format.
-->
- Simplify WAL record format
+ Simplify WAL record format
(Heikki Linnakangas)
@@ -8328,7 +8616,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-09-25 [b64d92f] Andres..: Add a basic atomic ops API abstracting away pla..
-->
- Add atomic memory operations API (Andres Freund)
+ Add atomic memory operations API (Andres Freund)
@@ -8366,13 +8654,13 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Foreign tables can now take part in INSERT ... ON CONFLICT
- DO NOTHING queries (Peter Geoghegan, Heikki Linnakangas,
+ DO NOTHING queries (Peter Geoghegan, Heikki Linnakangas,
Andres Freund)
Foreign data wrappers must be modified to handle this.
- INSERT ... ON CONFLICT DO UPDATE is not supported on
+ INSERT ... ON CONFLICT DO UPDATE is not supported on
foreign tables.
@@ -8382,7 +8670,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-12-18 [4a14f13] Tom Lane: Improve hash_create's API for selecting simple-..
-->
- Improve hash_create()'s API for selecting
+ Improve hash_create()'s API for selecting
simple-binary-key hash functions (Teodor Sigaev, Tom Lane)
@@ -8403,8 +8691,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-06-28 [a6d488c] Andres..: Remove Alpha and Tru64 support.
-->
- Remove Alpha (CPU) and Tru64 (OS) ports (Andres Freund)
+ Remove Alpha (CPU) and Tru64 (OS) ports (Andres Freund)
@@ -8414,11 +8702,11 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Remove swap-byte-based spinlock implementation for
- ARMv5 and earlier CPUs (Robert Haas)
+ ARMv5 and earlier CPUs (Robert Haas)
- ARMv5's weak memory ordering made this locking
+ ARMv5's weak memory ordering made this locking
implementation unsafe. Spinlock support is still possible on
newer gcc implementations with atomics support.
@@ -8444,10 +8732,10 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Change index operator class for columns pg_seclabel.provider
+ linkend="catalog-pg-seclabel">pg_seclabel.provider
and pg_shseclabel.provider
- to be text_pattern_ops (Tom Lane)
+ linkend="catalog-pg-shseclabel">pg_shseclabel.provider
+ to be text_pattern_ops (Tom Lane)
@@ -8480,8 +8768,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow higher-precision time stamp resolution on Windows 8, Windows
- Server 2012, and later Windows systems (Craig Ringer)
+ class="osname">Windows 8, Windows
+ Server 2012, and later Windows systems (Craig Ringer)
@@ -8490,8 +8778,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-03-18 [f9dead5] Alvaro..: Install shared libraries to bin/ in Windows un..
-->
- Install shared libraries to bin in MS Windows (Peter Eisentraut, Michael Paquier)
+ Install shared libraries to bin in MS Windows (Peter Eisentraut, Michael Paquier)
@@ -8500,8 +8788,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-04-16 [22d0053] Alvaro..: MSVC: install src/test/modules together with c..
-->
- Install src/test/modules together with
- contrib on MSVC builds (Michael
+ Install src/test/modules together with
+ contrib on MSVC builds (Michael
Paquier)
@@ -8511,9 +8799,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-07-12 [8d9a0e8] Magnus..: Support ––with-extra-version equivalent functi..
-->
- Allow configure's
-
@@ -8522,7 +8810,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-07-14 [91f03ba] Noah M..: MSVC: Recognize PGFILEDESC in contrib and conv..
-->
- Pass PGFILEDESC into MSVC contrib builds
+ Pass PGFILEDESC into MSVC contrib builds
(Michael Paquier)
@@ -8532,8 +8820,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-07-14 [c4a448e] Noah M..: MSVC: Apply icons to all binaries having them ..
-->
- Add icons to all MSVC-built binaries and version
- information to all MS Windows
+ Add icons to all MSVC-built binaries and version
+ information to all MS Windows
binaries (Noah Misch)
@@ -8548,12 +8836,12 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add optional-argument support to the internal
- getopt_long() implementation (Michael Paquier,
+ getopt_long() implementation (Michael Paquier,
Andres Freund)
- This is used by the MSVC build.
+ This is used by the MSVC build.
@@ -8575,7 +8863,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
Add statistics for minimum, maximum,
mean, and standard deviation times to pg_stat_statements
+ linkend="pgstatstatements-columns">pg_stat_statements
(Mitsumasa Kondo, Andrew Dunstan)
@@ -8585,8 +8873,8 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-10-01 [32984d8] Heikki..: Add functions for dealing with PGP armor heade..
-->
- Add pgcrypto function
- pgp_armor_headers() to extract PGP
+ Add pgcrypto function
+ pgp_armor_headers() to extract PGP
armor headers (Marko Tiikkaja, Heikki Linnakangas)
@@ -8597,7 +8885,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow empty replacement strings in unaccent (Mohammad Alhashash)
+ linkend="unaccent">unaccent (Mohammad Alhashash)
@@ -8612,7 +8900,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Allow multicharacter source strings in unaccent (Tom Lane)
+ linkend="unaccent">unaccent (Tom Lane)
@@ -8628,9 +8916,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-15 [149f6f1] Simon ..: TABLESAMPLE system_time(limit)
-->
- Add contrib modules tsm_system_rows and
- tsm_system_time
+ Add contrib modules tsm_system_rows and
+ tsm_system_time
to allow additional table sampling methods (Petr Jelínek)
@@ -8640,9 +8928,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-11-21 [3a82bc6] Heikki..: Add pageinspect functions for inspecting GIN in..
-->
- Add GIN
+ Add GIN
index inspection functions to pageinspect (Heikki
+ linkend="pageinspect">pageinspect (Heikki
Linnakangas, Peter Geoghegan, Michael Paquier)
@@ -8653,7 +8941,7 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
-->
Add information about buffer pins to pg_buffercache display
+ linkend="pgbuffercache">pg_buffercache display
(Andres Freund)
@@ -8663,9 +8951,9 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2015-05-13 [5850b20] Andres..: Add pgstattuple_approx() to the pgstattuple ext..
-->
- Allow pgstattuple
+ Allow pgstattuple
to report approximate answers with less overhead using
- pgstattuple_approx() (Abhijit Menon-Sen)
+ pgstattuple_approx() (Abhijit Menon-Sen)
@@ -8675,15 +8963,15 @@ Add GUC and storage parameter to set the maximum size of GIN pending list.
2014-12-01 [df761e3] Alvaro..: Move security_label test
-->
- Move dummy_seclabel, test_shm_mq,
- test_parser, and worker_spi
- from contrib to src/test/modules
+ Move dummy_seclabel, test_shm_mq,
+ test_parser, and worker_spi
+ from contrib to src/test/modules
(Álvaro Herrera)
These modules are only meant for server testing, so they do not need
- to be built or installed when packaging PostgreSQL.
+ to be built or installed when packaging PostgreSQL.
diff --git a/doc/src/sgml/release-9.6.sgml b/doc/src/sgml/release-9.6.sgml
index dc811c4ca5d..5e358ef4b4d 100644
--- a/doc/src/sgml/release-9.6.sgml
+++ b/doc/src/sgml/release-9.6.sgml
@@ -1,6 +1,512 @@
+
+ Release 9.6.6
+
+
+ Release date:
+ 2017-11-09
+
+
+
+ This release contains a variety of fixes from 9.6.5.
+ For information about new features in the 9.6 major release, see
+ .
+
+
+
+ Migration to Version 9.6.6
+
+
+ A dump/restore is not required for those running 9.6.X.
+
+
+
+ However, if you use BRIN indexes, see the first changelog entry below.
+
+
+
+ Also, if you are upgrading from a version earlier than 9.6.4,
+ see .
+
+
+
+
+ Changes
+
+
+
+
+
+ Fix BRIN index summarization to handle concurrent table extension
+ correctly (Álvaro Herrera)
+
+
+
+ Previously, a race condition allowed some table rows to be omitted from
+ the index. It may be necessary to reindex existing BRIN indexes to
+ recover from past occurrences of this problem.
+
+
+
+
+
+ Fix possible failures during concurrent updates of a BRIN index
+ (Tom Lane)
+
+
+
+ These race conditions could result in errors like invalid index
+ offnum or inconsistent range map.
+
+
+
+
+
+ Fix crash when logical decoding is invoked from a SPI-using function,
+ in particular any function written in a PL language
+ (Tom Lane)
+
+
+
+
+
+ Fix incorrect query results when multiple GROUPING
+ SETS columns contain the same simple variable (Tom Lane)
+
+
+
+
+
+ Fix incorrect parallelization decisions for nested queries
+ (Amit Kapila, Kuntal Ghosh)
+
+
+
+
+
+ Fix parallel query handling to not fail when a recently-used role is
+ dropped (Amit Kapila)
+
+
+
+
+
+ Fix json_build_array(),
+ json_build_object(), and their jsonb
+ equivalents to handle explicit VARIADIC arguments
+ correctly (Michael Paquier)
+
+
+
+
+
+
+ Properly reject attempts to convert infinite float values to
+ type numeric (Tom Lane, KaiGai Kohei)
+
+
+
+ Previously the behavior was platform-dependent.
+
+
+
+
+
+ Fix corner-case crashes when columns have been added to the end of a
+ view (Tom Lane)
+
+
+
+
+
+ Record proper dependencies when a view or rule
+ contains FieldSelect
+ or FieldStore expression nodes (Tom Lane)
+
+
+
+ Lack of these dependencies could allow a column or data
+ type DROP 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.
+
+
+
+
+
+ Correctly detect hashability of range data types (Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+
+ Correctly ignore RelabelType expression nodes
+ when determining relation distinctness (David Rowley)
+
+
+
+ This allows the intended optimization to occur when a subquery has
+ a result column of type varchar.
+
+
+
+
+
+ Prevent sharing transition states between ordered-set aggregates
+ (David Rowley)
+
+
+
+ This causes a crash with the built-in ordered-set aggregates, and
+ probably with user-written ones as well. v11 and later will include
+ provisions for dealing with such cases safely, but in released
+ branches, just disable the optimization.
+
+
+
+
+
+ Prevent idle_in_transaction_session_timeout from
+ being ignored when a statement_timeout occurred
+ earlier (Lukas Fittl)
+
+
+
+
+
+ Fix low-probability loss of NOTIFY messages due to
+ XID wraparound (Marko Tiikkaja, Tom Lane)
+
+
+
+ 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.
+
+
+
+
+
+
+ Avoid SIGBUS crash on Linux when a DSM memory
+ request exceeds the space available in tmpfs
+ (Thomas Munro)
+
+
+
+
+
+ Reduce the frequency of data flush requests during bulk file copies to
+ avoid performance problems on macOS, particularly with its new APFS
+ file system (Tom Lane)
+
+
+
+
+
+
+ Prevent low-probability crash in processing of nested trigger firings
+ (Tom Lane)
+
+
+
+
+
+ Allow COPY's FREEZE option to
+ work when the transaction isolation level is REPEATABLE
+ READ or higher (Noah Misch)
+
+
+
+ This case was unintentionally broken by a previous bug fix.
+
+
+
+
+
+
+ Correctly restore the umask setting when file creation fails
+ in COPY or lo_export()
+ (Peter Eisentraut)
+
+
+
+
+
+
+ Give a better error message for duplicate column names
+ in ANALYZE (Nathan Bossart)
+
+
+
+
+
+
+ Add missing cases in GetCommandLogLevel(),
+ preventing errors when certain SQL commands are used while
+ log_statement is set to ddl
+ (Michael Paquier)
+
+
+
+
+
+
+ Fix mis-parsing of the last line in a
+ non-newline-terminated pg_hba.conf file
+ (Tom Lane)
+
+
+
+
+
+ Fix AggGetAggref() to return the
+ correct Aggref nodes to aggregate final
+ functions whose transition calculations have been merged (Tom Lane)
+
+
+
+
+
+
+ Fix pg_dump to ensure that it
+ emits GRANT commands in a valid order
+ (Stephen Frost)
+
+
+
+
+
+ Fix pg_basebackup's matching of tablespace
+ paths to canonicalize both paths before comparing (Michael Paquier)
+
+
+
+ This is particularly helpful on Windows.
+
+
+
+
+
+ Fix libpq to not require user's home
+ directory to exist (Tom Lane)
+
+
+
+ In v10, failure to find the home directory while trying to
+ read ~/.pgpass 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 ~/.pg_service.conf, though this was less
+ obvious since that file is not sought unless a service name is
+ specified.
+
+
+
+
+
+
+ Fix libpq to guard against integer
+ overflow in the row count of a PGresult
+ (Michael Paquier)
+
+
+
+
+
+
+ Fix ecpg's handling of out-of-scope cursor
+ declarations with pointer or array variables (Michael Meskes)
+
+
+
+
+
+ In ecpglib, correctly handle backslashes in string literals depending
+ on whether standard_conforming_strings is set
+ (Tsunakawa Takayuki)
+
+
+
+
+
+ Make ecpglib's Informix-compatibility mode ignore fractional digits in
+ integer input strings, as expected (Gao Zengqi, Michael Meskes)
+
+
+
+
+
+
+ Fix ecpg's regression tests to work reliably
+ on Windows (Christian Ullrich, Michael Meskes)
+
+
+
+
+
+
+ Sync our copy of the timezone library with IANA release tzcode2017c
+ (Tom Lane)
+
+
+
+ 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 posixrules file exists in the timezone data
+ directory, now match current US law rather than what it was a dozen
+ years ago.
+
+
+
+
+
+ Update time zone data files to tzdata
+ 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.
+
+
+
+
+
+
+
+
Release 9.6.5
@@ -46,20 +552,20 @@ Branch: REL9_2_STABLE [98e6784aa] 2017-08-15 19:33:04 -0400
-->
Show foreign tables
- in information_schema.table_privileges
+ in information_schema.table_privileges
view (Peter Eisentraut)
- All other relevant information_schema views include
+ All other relevant information_schema views include
foreign tables, but this one ignored them.
- Since this view definition is installed by initdb,
+ Since this view definition is installed by initdb,
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 psql:
+ in psql:
SET search_path TO information_schema;
CREATE OR REPLACE VIEW table_privileges AS
@@ -98,7 +604,7 @@ CREATE OR REPLACE VIEW table_privileges AS
OR grantee.rolname = 'PUBLIC');
This must be repeated in each database to be fixed,
- including template0.
+ including template0.
@@ -114,14 +620,14 @@ Branch: REL9_2_STABLE [8ae41ceae] 2017-08-14 15:43:20 -0400
-->
Clean up handling of a fatal exit (e.g., due to receipt
- of SIGTERM) that occurs while trying to execute
- a ROLLBACK of a failed transaction (Tom Lane)
+ of SIGTERM) that occurs while trying to execute
+ a ROLLBACK of a failed transaction (Tom Lane)
This situation could result in an assertion failure. In production
builds, the exit would still occur, but it would log an unexpected
- message about cannot drop active portal.
+ message about cannot drop active portal.
@@ -156,7 +662,7 @@ Branch: REL9_2_STABLE [4e704aac1] 2017-08-09 17:03:10 -0400
- Certain ALTER commands that change the definition of a
+ Certain ALTER commands that change the definition of a
composite type or domain type are supposed to fail if there are any
stored values of that type in the database, because they lack the
infrastructure needed to update or check such values. Previously,
@@ -189,7 +695,7 @@ Branch: REL9_4_STABLE [59dde9fed] 2017-08-19 13:39:38 -0400
Branch: REL9_3_STABLE [ece4bd901] 2017-08-19 13:39:38 -0400
-->
- Fix crash in pg_restore when using parallel mode and
+ Fix crash in pg_restore when using parallel mode and
using a list file to select a subset of items to restore
(Fabrízio de Royes Mello)
@@ -206,13 +712,13 @@ Branch: REL9_3_STABLE [f8bc6b2f6] 2017-08-16 13:30:09 +0200
Branch: REL9_2_STABLE [60b135c82] 2017-08-16 13:30:20 +0200
-->
- Change ecpg's parser to allow RETURNING
+ Change ecpg's parser to allow RETURNING
clauses without attached C variables (Michael Meskes)
- This allows ecpg programs to contain SQL constructs
- that use RETURNING internally (for example, inside a CTE)
+ This allows ecpg programs to contain SQL constructs
+ that use RETURNING internally (for example, inside a CTE)
rather than using it to define values to be returned to the client.
@@ -225,7 +731,7 @@ Branch: REL_10_STABLE [a6b174f55] 2017-08-16 13:27:21 +0200
Branch: REL9_6_STABLE [954490fec] 2017-08-16 13:28:10 +0200
-->
- Change ecpg's parser to recognize backslash
+ Change ecpg's parser to recognize backslash
continuation of C preprocessor command lines (Michael Meskes)
@@ -253,12 +759,12 @@ Branch: REL9_2_STABLE [f7e4783dd] 2017-08-17 13:15:46 -0400
This fix avoids possible crashes of PL/Perl due to inconsistent
- assumptions about the width of time_t values.
+ assumptions about the width of time_t values.
A side-effect that may be visible to extension developers is
- that _USE_32BIT_TIME_T is no longer defined globally
- in PostgreSQL Windows builds. This is not expected
- to cause problems, because type time_t is not used
- in any PostgreSQL API definitions.
+ that _USE_32BIT_TIME_T is no longer defined globally
+ in PostgreSQL Windows builds. This is not expected
+ to cause problems, because type time_t is not used
+ in any PostgreSQL API definitions.
@@ -270,7 +776,7 @@ Branch: REL9_6_STABLE [fc2aafe4a] 2017-08-09 12:06:08 -0400
Branch: REL9_5_STABLE [a784d5f21] 2017-08-09 12:06:14 -0400
-->
- Fix make check to behave correctly when invoked via a
+ Fix make check to behave correctly when invoked via a
non-GNU make program (Thomas Munro)
@@ -329,7 +835,7 @@ Branch: REL9_2_STABLE [e255e97a2] 2017-08-07 07:09:32 -0700
-->
Further restrict visibility
- of pg_user_mappings.umoptions, to
+ of pg_user_mappings.umoptions, to
protect passwords stored as user mapping options
(Noah Misch)
@@ -337,11 +843,11 @@ Branch: REL9_2_STABLE [e255e97a2] 2017-08-07 07:09:32 -0700
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 USAGE permission on the associated foreign server.
+ have USAGE 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 information_schema.user_mapping_options does not
- show the options in such cases, pg_user_mappings
+ Since information_schema.user_mapping_options does not
+ show the options in such cases, pg_user_mappings
should not either.
(CVE-2017-7547)
@@ -356,15 +862,15 @@ Branch: REL9_2_STABLE [e255e97a2] 2017-08-07 07:09:32 -0700
Restart the postmaster after adding allow_system_table_mods
- = true to postgresql.conf. (In versions
- supporting ALTER SYSTEM, you can use that to make the
+ = true to postgresql.conf. (In versions
+ supporting ALTER SYSTEM, you can use that to make the
configuration change, but you'll still need a restart.)
- In each database of the cluster,
+ In each database of the cluster,
run the following commands as superuser:
SET search_path = pg_catalog;
@@ -395,15 +901,15 @@ CREATE OR REPLACE VIEW pg_user_mappings AS
- Do not forget to include the template0
- and template1 databases, or the vulnerability will still
- exist in databases you create later. To fix template0,
+ Do not forget to include the template0
+ and template1 databases, or the vulnerability will still
+ exist in databases you create later. To fix template0,
you'll need to temporarily make it accept connections.
- In PostgreSQL 9.5 and later, you can use
+ In PostgreSQL 9.5 and later, you can use
ALTER DATABASE template0 WITH ALLOW_CONNECTIONS true;
- and then after fixing template0, undo that with
+ and then after fixing template0, undo that with
ALTER DATABASE template0 WITH ALLOW_CONNECTIONS false;
@@ -417,7 +923,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
- Finally, remove the allow_system_table_mods configuration
+ Finally, remove the allow_system_table_mods configuration
setting, and again restart the postmaster.
@@ -440,16 +946,16 @@ Branch: REL9_2_STABLE [06651648a] 2017-08-07 17:04:17 +0300
- libpq ignores empty password specifications, and does
+ libpq 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 psql or other libpq-based
+ via psql or other libpq-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-libpq-based client,
+ However, with a modified or non-libpq-based client,
logging in could be possible, depending on which authentication
method is configured. In particular the most common
- method, md5, accepted empty passwords.
+ method, md5, accepted empty passwords.
Change the server to reject empty passwords in all cases.
(CVE-2017-7546)
@@ -464,13 +970,13 @@ Branch: REL9_5_STABLE [873741c68] 2017-08-07 10:19:21 -0400
Branch: REL9_4_STABLE [f1cda6d6c] 2017-08-07 10:19:22 -0400
-->
- Make lo_put() check for UPDATE privilege on
+ Make lo_put() check for UPDATE privilege on
the target large object (Tom Lane, Michael Paquier)
- lo_put() should surely require the same permissions
- as lowrite(), but the check was missing, allowing any
+ lo_put() should surely require the same permissions
+ as lowrite(), but the check was missing, allowing any
user to change the data in a large object.
(CVE-2017-7548)
@@ -485,12 +991,12 @@ Branch: REL9_5_STABLE [fd376afc9] 2017-06-15 12:30:02 -0400
-->
Correct the documentation about the process for upgrading standby
- servers with pg_upgrade (Bruce Momjian)
+ servers with pg_upgrade (Bruce Momjian)
The previous documentation instructed users to start/stop the primary
- server after running pg_upgrade but before syncing
+ server after running pg_upgrade but before syncing
the standby servers. This sequence is unsafe.
@@ -697,7 +1203,7 @@ Branch: REL9_2_STABLE [81bf7b5b1] 2017-06-21 14:13:58 -0700
-->
Fix possible creation of an invalid WAL segment when a standby is
- promoted just after it processes an XLOG_SWITCH WAL
+ promoted just after it processes an XLOG_SWITCH WAL
record (Andres Freund)
@@ -711,7 +1217,7 @@ Branch: REL9_5_STABLE [446914f6b] 2017-06-30 12:00:03 -0400
Branch: REL9_4_STABLE [5aa8db014] 2017-06-30 12:00:03 -0400
-->
- Fix walsender to exit promptly when client requests
+ Fix walsender to exit promptly when client requests
shutdown (Tom Lane)
@@ -731,7 +1237,7 @@ Branch: REL9_3_STABLE [45d067d50] 2017-06-05 19:18:16 -0700
Branch: REL9_2_STABLE [133b1920c] 2017-06-05 19:18:16 -0700
-->
- Fix SIGHUP and SIGUSR1 handling in
+ Fix SIGHUP and SIGUSR1 handling in
walsender processes (Petr Jelinek, Andres Freund)
@@ -761,7 +1267,7 @@ Branch: REL9_3_STABLE [cb59949f6] 2017-06-26 17:31:56 -0400
Branch: REL9_2_STABLE [e96adaacd] 2017-06-26 17:31:56 -0400
-->
- Fix unnecessarily slow restarts of walreceiver
+ Fix unnecessarily slow restarts of walreceiver
processes due to race condition in postmaster (Tom Lane)
@@ -880,7 +1386,7 @@ Branch: REL9_3_STABLE [aea1a3f0e] 2017-07-12 18:00:04 -0400
Branch: REL9_2_STABLE [75670ec37] 2017-07-12 18:00:04 -0400
-->
- Fix cases where an INSERT or UPDATE assigns
+ Fix cases where an INSERT or UPDATE assigns
to more than one element of a column that is of domain-over-array
type (Tom Lane)
@@ -896,7 +1402,7 @@ Branch: REL9_4_STABLE [dc777f9db] 2017-06-27 17:51:11 -0400
Branch: REL9_3_STABLE [66dee28b4] 2017-06-27 17:51:11 -0400
-->
- Allow window functions to be used in sub-SELECTs that
+ Allow window functions to be used in sub-SELECTs that
are within the arguments of an aggregate function (Tom Lane)
@@ -908,7 +1414,7 @@ Branch: master [7086be6e3] 2017-07-24 15:57:24 -0400
Branch: REL9_6_STABLE [971faefc2] 2017-07-24 16:24:42 -0400
-->
- Ensure that a view's CHECK OPTIONS clause is enforced
+ Ensure that a view's CHECK OPTIONS clause is enforced
properly when the underlying table is a foreign table (Etsuro Fujita)
@@ -930,12 +1436,12 @@ Branch: REL9_2_STABLE [da9165686] 2017-05-26 15:16:59 -0400
-->
Move autogenerated array types out of the way during
- ALTER ... RENAME (Vik Fearing)
+ ALTER ... RENAME (Vik Fearing)
Previously, we would rename a conflicting autogenerated array type
- out of the way during CREATE; this fix extends that
+ out of the way during CREATE; this fix extends that
behavior to renaming operations.
@@ -948,7 +1454,7 @@ Branch: REL9_6_STABLE [b35cce914] 2017-05-15 11:33:44 -0400
Branch: REL9_5_STABLE [53a1aa9f9] 2017-05-15 11:33:45 -0400
-->
- Fix dangling pointer in ALTER TABLE when there is a
+ Fix dangling pointer in ALTER TABLE when there is a
comment on a constraint belonging to the table (David Rowley)
@@ -969,8 +1475,8 @@ Branch: REL9_3_STABLE [b7d1bc820] 2017-08-03 21:29:36 -0400
Branch: REL9_2_STABLE [22eb38caa] 2017-08-03 21:42:46 -0400
-->
- Ensure that ALTER USER ... SET accepts all the syntax
- variants that ALTER ROLE ... SET does (Peter Eisentraut)
+ Ensure that ALTER USER ... SET accepts all the syntax
+ variants that ALTER ROLE ... SET does (Peter Eisentraut)
@@ -981,18 +1487,18 @@ Branch: master [86705aa8c] 2017-08-03 13:24:48 -0400
Branch: REL9_6_STABLE [1f220c390] 2017-08-03 13:25:32 -0400
-->
- Allow a foreign table's CHECK constraints to be
- initially NOT VALID (Amit Langote)
+ Allow a foreign table's CHECK constraints to be
+ initially NOT VALID (Amit Langote)
- CREATE TABLE silently drops NOT VALID
- specifiers for CHECK constraints, reasoning that the
+ CREATE TABLE silently drops NOT VALID
+ specifiers for CHECK constraints, reasoning that the
table must be empty so the constraint can be validated immediately.
- But this is wrong for CREATE FOREIGN TABLE, where there's
+ But this is wrong for CREATE FOREIGN TABLE, where there's
no reason to suppose that the underlying table is empty, and even if
it is it's no business of ours to decide that the constraint can be
- treated as valid going forward. Skip this optimization for
+ treated as valid going forward. Skip this optimization for
foreign tables.
@@ -1009,14 +1515,14 @@ Branch: REL9_2_STABLE [ac93a78b0] 2017-06-16 11:46:26 +0300
-->
Properly update dependency info when changing a datatype I/O
- function's argument or return type from opaque to the
+ function's argument or return type from opaque to the
correct type (Heikki Linnakangas)
- CREATE TYPE updates I/O functions declared in this
+ CREATE TYPE updates I/O functions declared in this
long-obsolete style, but it forgot to record a dependency on the
- type, allowing a subsequent DROP TYPE to leave broken
+ type, allowing a subsequent DROP TYPE to leave broken
function definitions behind.
@@ -1028,7 +1534,7 @@ Branch: master [34aebcf42] 2017-06-02 19:11:15 -0700
Branch: REL9_6_STABLE [8a7cd781e] 2017-06-02 19:11:23 -0700
-->
- Allow parallelism in the query plan when COPY copies from
+ Allow parallelism in the query plan when COPY copies from
a query's result (Andres Freund)
@@ -1044,8 +1550,8 @@ Branch: REL9_3_STABLE [11854dee0] 2017-07-12 22:04:08 +0300
Branch: REL9_2_STABLE [40ba61b44] 2017-07-12 22:04:15 +0300
-->
- Reduce memory usage when ANALYZE processes
- a tsvector column (Heikki Linnakangas)
+ Reduce memory usage when ANALYZE processes
+ a tsvector column (Heikki Linnakangas)
@@ -1061,7 +1567,7 @@ Branch: REL9_2_STABLE [798d2321e] 2017-05-21 13:05:17 -0400
-->
Fix unnecessary precision loss and sloppy rounding when multiplying
- or dividing money values by integers or floats (Tom Lane)
+ or dividing money values by integers or floats (Tom Lane)
@@ -1077,7 +1583,7 @@ Branch: REL9_2_STABLE [a047270d5] 2017-05-24 15:28:35 -0400
-->
Tighten checks for whitespace in functions that parse identifiers,
- such as regprocedurein() (Tom Lane)
+ such as regprocedurein() (Tom Lane)
@@ -1103,13 +1609,13 @@ Branch: REL9_3_STABLE [0d8f015e7] 2017-07-31 12:38:35 -0400
Branch: REL9_2_STABLE [456c7dff2] 2017-07-31 12:38:35 -0400
-->
- Use relevant #define symbols from Perl while
- compiling PL/Perl (Ashutosh Sharma, Tom Lane)
+ Use relevant #define symbols from Perl while
+ compiling PL/Perl (Ashutosh Sharma, Tom Lane)
This avoids portability problems, typically manifesting as
- a handshake mismatch during library load, when working with
+ a handshake mismatch during library load, when working with
recent Perl versions.
@@ -1124,7 +1630,7 @@ Branch: REL9_4_STABLE [1fe1fc449] 2017-06-07 14:04:49 +0300
Branch: REL9_3_STABLE [f2fa0c651] 2017-06-07 14:04:44 +0300
-->
- In libpq, reset GSS/SASL and SSPI authentication
+ In libpq, reset GSS/SASL and SSPI authentication
state properly after a failed connection attempt (Michael Paquier)
@@ -1146,9 +1652,9 @@ Branch: REL9_3_STABLE [6bc710f6d] 2017-05-17 12:24:19 -0400
Branch: REL9_2_STABLE [07477130e] 2017-05-17 12:24:19 -0400
-->
- In psql, fix failure when COPY FROM STDIN
+ In psql, fix failure when COPY FROM STDIN
is ended with a keyboard EOF signal and then another COPY
- FROM STDIN is attempted (Thomas Munro)
+ FROM STDIN is attempted (Thomas Munro)
@@ -1167,8 +1673,8 @@ Branch: REL9_4_STABLE [b93217653] 2017-08-03 17:36:43 -0400
Branch: REL9_3_STABLE [035bb8222] 2017-08-03 17:36:23 -0400
-->
- Fix pg_dump and pg_restore to
- emit REFRESH MATERIALIZED VIEW commands last (Tom Lane)
+ Fix pg_dump and pg_restore to
+ emit REFRESH MATERIALIZED VIEW commands last (Tom Lane)
@@ -1190,8 +1696,8 @@ Branch: REL9_5_STABLE [12f1e523a] 2017-08-03 14:55:17 -0400
Branch: REL9_4_STABLE [69ad12b58] 2017-08-03 14:55:17 -0400
-->
- Improve pg_dump/pg_restore's
- reporting of error conditions originating in zlib
+ Improve pg_dump/pg_restore's
+ reporting of error conditions originating in zlib
(Vladimir Kunschikov, Álvaro Herrera)
@@ -1206,7 +1712,7 @@ Branch: REL9_4_STABLE [502ead3d6] 2017-07-22 20:20:10 -0400
Branch: REL9_3_STABLE [68a22bc69] 2017-07-22 20:20:10 -0400
-->
- Fix pg_dump with the option to
drop event triggers as expected (Tom Lane)
@@ -1224,8 +1730,8 @@ Branch: master [4500edc7e] 2017-06-28 10:33:57 -0400
Branch: REL9_6_STABLE [a2de017b3] 2017-06-28 10:34:01 -0400
-->
- Fix pg_dump with the
@@ -1240,7 +1746,7 @@ Branch: REL9_3_STABLE [a561254e4] 2017-05-26 12:51:05 -0400
Branch: REL9_2_STABLE [f62e1eff5] 2017-05-26 12:51:06 -0400
-->
- Fix pg_dump to not emit invalid SQL for an empty
+ Fix pg_dump to not emit invalid SQL for an empty
operator class (Daniel Gustafsson)
@@ -1256,7 +1762,7 @@ Branch: REL9_3_STABLE [2943c04f7] 2017-06-19 11:03:16 -0400
Branch: REL9_2_STABLE [c10cbf77a] 2017-06-19 11:03:21 -0400
-->
- Fix pg_dump output to stdout on Windows (Kuntal Ghosh)
+ Fix pg_dump output to stdout on Windows (Kuntal Ghosh)
@@ -1276,14 +1782,14 @@ Branch: REL9_3_STABLE [b6d640047] 2017-07-24 15:16:31 -0400
Branch: REL9_2_STABLE [d9874fde8] 2017-07-24 15:16:31 -0400
-->
- Fix pg_get_ruledef() to print correct output for
- the ON SELECT rule of a view whose columns have been
+ Fix pg_get_ruledef() to print correct output for
+ the ON SELECT rule of a view whose columns have been
renamed (Tom Lane)
- In some corner cases, pg_dump relies
- on pg_get_ruledef() to dump views, so that this error
+ In some corner cases, pg_dump relies
+ on pg_get_ruledef() to dump views, so that this error
could result in dump/reload failures.
@@ -1299,7 +1805,7 @@ Branch: REL9_3_STABLE [e947838ae] 2017-07-20 11:29:36 -0400
-->
Fix dumping of outer joins with empty constraints, such as the result
- of a NATURAL LEFT JOIN with no common columns (Tom Lane)
+ of a NATURAL LEFT JOIN with no common columns (Tom Lane)
@@ -1314,7 +1820,7 @@ Branch: REL9_3_STABLE [0ecc407d9] 2017-07-13 19:24:44 -0400
Branch: REL9_2_STABLE [bccfb1776] 2017-07-13 19:24:44 -0400
-->
- Fix dumping of function expressions in the FROM clause in
+ Fix dumping of function expressions in the FROM clause in
cases where the expression does not deparse into something that looks
like a function call (Tom Lane)
@@ -1331,7 +1837,7 @@ Branch: REL9_3_STABLE [f3633689f] 2017-07-14 16:03:23 +0300
Branch: REL9_2_STABLE [4b994a96c] 2017-07-14 16:03:27 +0300
-->
- Fix pg_basebackup output to stdout on Windows
+ Fix pg_basebackup output to stdout on Windows
(Haribabu Kommi)
@@ -1349,12 +1855,12 @@ Branch: REL9_6_STABLE [73fbf3d3d] 2017-07-21 22:04:55 -0400
Branch: REL9_5_STABLE [ed367be64] 2017-07-21 22:05:07 -0400
-->
- Fix pg_rewind to correctly handle files exceeding 2GB
+ Fix pg_rewind to correctly handle files exceeding 2GB
(Kuntal Ghosh, Michael Paquier)
- Ordinarily such files won't appear in PostgreSQL data
+ Ordinarily such files won't appear in PostgreSQL data
directories, but they could be present in some cases.
@@ -1370,8 +1876,8 @@ Branch: REL9_3_STABLE [5c890645d] 2017-06-20 13:20:02 -0400
Branch: REL9_2_STABLE [65beccae5] 2017-06-20 13:20:02 -0400
-->
- Fix pg_upgrade to ensure that the ending WAL record
- does not have = minimum
+ Fix pg_upgrade to ensure that the ending WAL record
+ does not have = minimum
(Bruce Momjian)
@@ -1389,7 +1895,7 @@ Branch: REL9_6_STABLE [d3ca4b4b4] 2017-06-05 16:10:07 -0700
Branch: REL9_5_STABLE [25653c171] 2017-06-05 16:10:07 -0700
-->
- Fix pg_xlogdump's computation of WAL record length
+ Fix pg_xlogdump's computation of WAL record length
(Andres Freund)
@@ -1409,9 +1915,9 @@ Branch: REL9_4_STABLE [a648fc70a] 2017-07-21 14:20:43 -0400
Branch: REL9_3_STABLE [6d9de660d] 2017-07-21 14:20:43 -0400
-->
- In postgres_fdw, re-establish connections to remote
- servers after ALTER SERVER or ALTER USER
- MAPPING commands (Kyotaro Horiguchi)
+ In postgres_fdw, re-establish connections to remote
+ servers after ALTER SERVER or ALTER USER
+ MAPPING commands (Kyotaro Horiguchi)
@@ -1430,7 +1936,7 @@ Branch: REL9_4_STABLE [c02c450cf] 2017-06-07 15:40:35 -0400
Branch: REL9_3_STABLE [fc267a0c3] 2017-06-07 15:41:05 -0400
-->
- In postgres_fdw, allow cancellation of remote
+ In postgres_fdw, allow cancellation of remote
transaction control commands (Robert Haas, Rafia Sabih)
@@ -1449,7 +1955,7 @@ Branch: REL9_5_STABLE [6f2fe2468] 2017-05-11 14:51:38 -0400
Branch: REL9_4_STABLE [5c633f76b] 2017-05-11 14:51:46 -0400
-->
- Increase MAX_SYSCACHE_CALLBACKS to provide more room for
+ Increase MAX_SYSCACHE_CALLBACKS to provide more room for
extensions (Tom Lane)
@@ -1465,7 +1971,7 @@ Branch: REL9_3_STABLE [cee7238de] 2017-06-01 13:32:56 -0400
Branch: REL9_2_STABLE [a378b9bc2] 2017-06-01 13:32:56 -0400
-->
- Always use , not , when building
shared libraries with gcc (Tom Lane)
@@ -1492,8 +1998,8 @@ Branch: REL9_3_STABLE [da30fa603] 2017-06-05 20:40:47 -0400
Branch: REL9_2_STABLE [f964a7c5a] 2017-06-05 20:41:01 -0400
-->
- In MSVC builds, handle the case where the openssl
- library is not within a VC subdirectory (Andrew Dunstan)
+ In MSVC builds, handle the case where the openssl
+ library is not within a VC subdirectory (Andrew Dunstan)
@@ -1508,13 +2014,13 @@ Branch: REL9_3_STABLE [2c7d2114b] 2017-05-12 10:24:16 -0400
Branch: REL9_2_STABLE [614f83c12] 2017-05-12 10:24:36 -0400
-->
- In MSVC builds, add proper include path for libxml2
+ In MSVC builds, add proper include path for libxml2
header files (Andrew Dunstan)
This fixes a former need to move things around in standard Windows
- installations of libxml2.
+ installations of libxml2.
@@ -1530,7 +2036,7 @@ Branch: REL9_2_STABLE [4885e5c88] 2017-07-23 23:53:55 -0700
-->
In MSVC builds, recognize a Tcl library that is
- named tcl86.lib (Noah Misch)
+ named tcl86.lib (Noah Misch)
@@ -1551,8 +2057,8 @@ Branch: REL9_5_STABLE [7eb4124da] 2017-07-16 11:27:07 -0400
Branch: REL9_4_STABLE [9c3f502b4] 2017-07-16 11:27:15 -0400
-->
- In MSVC builds, honor PROVE_FLAGS settings
- on vcregress.pl's command line (Andrew Dunstan)
+ In MSVC builds, honor PROVE_FLAGS settings
+ on vcregress.pl's command line (Andrew Dunstan)
@@ -1589,7 +2095,7 @@ Branch: REL9_4_STABLE [9c3f502b4] 2017-07-16 11:27:15 -0400
Also, if you are using third-party replication tools that depend
- on logical decoding, see the fourth changelog entry below.
+ on logical decoding, see the fourth changelog entry below.
@@ -1615,18 +2121,18 @@ Branch: REL9_2_STABLE [99cbb0bd9] 2017-05-08 07:24:28 -0700
-->
Restrict visibility
- of pg_user_mappings.umoptions, to
+ of pg_user_mappings.umoptions, to
protect passwords stored as user mapping options
(Michael Paquier, Feike Steenbergen)
The previous coding allowed the owner of a foreign server object,
- or anyone he has granted server USAGE permission to,
+ or anyone he has granted server USAGE 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
- information_schema.user_mapping_options, namely that
+ information_schema.user_mapping_options, namely that
these options are visible to the user being mapped, or if the mapping
is for PUBLIC and the current user is the server
owner, or if the current user is a superuser.
@@ -1665,7 +2171,7 @@ Branch: REL9_3_STABLE [703da1795] 2017-05-08 11:19:08 -0400
Some selectivity estimation functions in the planner will apply
user-defined operators to values obtained
- from pg_statistic, such as most common values and
+ from pg_statistic, such as most common values and
histogram entries. This occurs before table permissions are checked,
so a nefarious user could exploit the behavior to obtain these values
for table columns he does not have permission to read. To fix,
@@ -1687,17 +2193,17 @@ Branch: REL9_4_STABLE [ed36c1fe1] 2017-05-08 07:24:27 -0700
Branch: REL9_3_STABLE [3eab81127] 2017-05-08 07:24:28 -0700
-->
- Restore libpq's recognition of
- the PGREQUIRESSL environment variable (Daniel Gustafsson)
+ Restore libpq's recognition of
+ the PGREQUIRESSL environment variable (Daniel Gustafsson)
Processing of this environment variable was unintentionally dropped
- in PostgreSQL 9.3, but its documentation remained.
+ in PostgreSQL 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 PGSSLMODE, to avoid
+ but give it lower priority than PGSSLMODE, to avoid
breaking configurations that work correctly with post-9.3 code.
(CVE-2017-7485)
@@ -1748,7 +2254,7 @@ Branch: REL9_3_STABLE [6bd7816e7] 2017-03-14 12:08:14 -0400
Branch: REL9_2_STABLE [b2ae1d6c4] 2017-03-14 12:10:36 -0400
-->
- Fix possible corruption of init forks of unlogged indexes
+ Fix possible corruption of init forks of unlogged indexes
(Robert Haas, Michael Paquier)
@@ -1770,7 +2276,7 @@ Branch: REL9_3_STABLE [856580873] 2017-04-23 13:10:57 -0400
Branch: REL9_2_STABLE [952e33b05] 2017-04-23 13:10:58 -0400
-->
- Fix incorrect reconstruction of pg_subtrans entries
+ Fix incorrect reconstruction of pg_subtrans entries
when a standby server replays a prepared but uncommitted two-phase
transaction (Tom Lane)
@@ -1778,7 +2284,7 @@ Branch: REL9_2_STABLE [952e33b05] 2017-04-23 13:10:58 -0400
In most cases this turned out to have no visible ill effects, but in
corner cases it could result in circular references
- in pg_subtrans, potentially causing infinite loops
+ in pg_subtrans, potentially causing infinite loops
in queries that examine rows modified by the two-phase transaction.
@@ -1792,7 +2298,7 @@ Branch: REL9_5_STABLE [feb659cce] 2017-02-22 08:29:44 +0900
Branch: REL9_4_STABLE [a3eb715a3] 2017-02-22 08:29:57 +0900
-->
- Avoid possible crash in walsender due to failure
+ Avoid possible crash in walsender due to failure
to initialize a string buffer (Stas Kelvich, Fujii Masao)
@@ -1840,7 +2346,7 @@ Branch: REL9_5_STABLE [dba1f310a] 2017-04-24 12:16:58 -0400
Branch: REL9_4_STABLE [436b560b8] 2017-04-24 12:16:58 -0400
-->
- Fix postmaster's handling of fork() failure for a
+ Fix postmaster's handling of fork() failure for a
background worker process (Tom Lane)
@@ -1858,7 +2364,7 @@ Branch: master [89deca582] 2017-04-07 12:18:38 -0400
Branch: REL9_6_STABLE [c0a493e17] 2017-04-07 12:18:38 -0400
-->
- Fix possible no relation entry for relid 0 error when
+ Fix possible no relation entry for relid 0 error when
planning nested set operations (Tom Lane)
@@ -1886,7 +2392,7 @@ Branch: REL9_6_STABLE [6c73b390b] 2017-04-17 15:29:00 -0400
Branch: REL9_5_STABLE [6f0f98bb0] 2017-04-17 15:29:00 -0400
-->
- Avoid applying physical targetlist optimization to custom
+ Avoid applying physical targetlist optimization to custom
scans (Dmitry Ivanov, Tom Lane)
@@ -1905,13 +2411,13 @@ Branch: REL9_6_STABLE [92b15224b] 2017-05-06 21:46:41 -0400
Branch: REL9_5_STABLE [d617c7629] 2017-05-06 21:46:56 -0400
-->
- Use the correct sub-expression when applying a FOR ALL
+ Use the correct sub-expression when applying a FOR ALL
row-level-security policy (Stephen Frost)
- In some cases the WITH CHECK restriction would be applied
- when the USING restriction is more appropriate.
+ In some cases the WITH CHECK restriction would be applied
+ when the USING restriction is more appropriate.
@@ -1934,7 +2440,7 @@ Branch: REL9_2_STABLE [c9d6c564f] 2017-05-02 18:05:54 -0400
Due to lack of a cache flush step between commands in an extension
script file, non-utility queries might not see the effects of an
immediately preceding catalog change, such as ALTER TABLE
- ... RENAME.
+ ... RENAME.
@@ -1950,12 +2456,12 @@ Branch: REL9_2_STABLE [27a8c8033] 2017-02-12 16:05:23 -0500
-->
Skip tablespace privilege checks when ALTER TABLE ... ALTER
- COLUMN TYPE rebuilds an existing index (Noah Misch)
+ COLUMN TYPE rebuilds an existing index (Noah Misch)
The command failed if the calling user did not currently have
- CREATE privilege for the tablespace containing the index.
+ CREATE privilege for the tablespace containing the index.
That behavior seems unhelpful, so skip the check, allowing the
index to be rebuilt where it is.
@@ -1972,13 +2478,13 @@ Branch: REL9_3_STABLE [954744f7a] 2017-04-28 14:53:56 -0400
Branch: REL9_2_STABLE [f60f0c8fe] 2017-04-28 14:55:42 -0400
-->
- Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse
- to child tables when the constraint is marked NO INHERIT
+ Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse
+ to child tables when the constraint is marked NO INHERIT
(Amit Langote)
- This fix prevents unwanted constraint does not exist failures
+ This fix prevents unwanted constraint does not exist failures
when no matching constraint is present in the child tables.
@@ -1991,7 +2497,7 @@ Branch: REL9_6_STABLE [943140d57] 2017-03-06 16:50:47 -0500
Branch: REL9_5_STABLE [420d9ec0a] 2017-03-06 16:50:47 -0500
-->
- Avoid dangling pointer in COPY ... TO when row-level
+ Avoid dangling pointer in COPY ... TO when row-level
security is active for the source table (Tom Lane)
@@ -2009,8 +2515,8 @@ Branch: REL9_6_STABLE [68f7b91e5] 2017-03-04 16:09:33 -0500
Branch: REL9_5_STABLE [807df31d1] 2017-03-04 16:09:33 -0500
-->
- Avoid accessing an already-closed relcache entry in CLUSTER
- and VACUUM FULL (Tom Lane)
+ Avoid accessing an already-closed relcache entry in CLUSTER
+ and VACUUM FULL (Tom Lane)
@@ -2032,14 +2538,14 @@ Branch: master [64ae420b2] 2017-03-17 14:35:54 +0000
Branch: REL9_6_STABLE [733488dc6] 2017-03-17 14:46:15 +0000
-->
- Fix VACUUM to account properly for pages that could not
+ Fix VACUUM to account properly for pages that could not
be scanned due to conflicting page pins (Andrew Gierth)
This tended to lead to underestimation of the number of tuples in
the table. In the worst case of a small heavily-contended
- table, VACUUM could incorrectly report that the table
+ table, VACUUM could incorrectly report that the table
contained no tuples, leading to very bad planning choices.
@@ -2067,13 +2573,13 @@ Branch: master [d5286aa90] 2017-03-21 16:23:10 +0300
Branch: REL9_6_STABLE [a4d07d2e9] 2017-03-21 16:24:10 +0300
-->
- Fix incorrect support for certain box operators in SP-GiST
+ Fix incorrect support for certain box operators in SP-GiST
(Nikita Glukhov)
- SP-GiST index scans using the operators &<
- &> &<| and |&>
+ SP-GiST index scans using the operators &<
+ &>&<| and |&>
would yield incorrect answers.
@@ -2087,12 +2593,12 @@ Branch: REL9_5_STABLE [d68a2b20a] 2017-04-05 23:51:28 -0400
Branch: REL9_4_STABLE [8851bcf88] 2017-04-05 23:51:28 -0400
-->
- Fix integer-overflow problems in interval comparison (Kyotaro
+ Fix integer-overflow problems in interval comparison (Kyotaro
Horiguchi, Tom Lane)
- The comparison operators for type interval could yield wrong
+ The comparison operators for type interval could yield wrong
answers for intervals larger than about 296000 years. Indexes on
columns containing such large values should be reindexed, since they
may be corrupt.
@@ -2110,13 +2616,13 @@ Branch: REL9_3_STABLE [6e86b448f] 2017-05-04 21:31:12 -0400
Branch: REL9_2_STABLE [a48d47908] 2017-05-04 22:39:23 -0400
-->
- Fix cursor_to_xml() to produce valid output
- with tableforest = false
+ Fix cursor_to_xml() to produce valid output
+ with tableforest = false
(Thomas Munro, Peter Eisentraut)
- Previously it failed to produce a wrapping <table>
+ Previously it failed to produce a wrapping <table>
element.
@@ -2134,8 +2640,8 @@ Branch: REL9_5_STABLE [cf73c6bfc] 2017-02-09 15:49:57 -0500
Branch: REL9_4_STABLE [86ef376bb] 2017-02-09 15:49:58 -0500
-->
- Fix roundoff problems in float8_timestamptz()
- and make_interval() (Tom Lane)
+ Fix roundoff problems in float8_timestamptz()
+ and make_interval() (Tom Lane)
@@ -2155,7 +2661,7 @@ Branch: REL9_6_STABLE [1ec36a9eb] 2017-04-16 20:49:40 -0400
Branch: REL9_5_STABLE [b6e6ae1dc] 2017-04-16 20:50:31 -0400
-->
- Fix pg_get_object_address() to handle members of operator
+ Fix pg_get_object_address() to handle members of operator
families correctly (Álvaro Herrera)
@@ -2167,12 +2673,12 @@ Branch: master [78874531b] 2017-03-24 13:53:40 +0300
Branch: REL9_6_STABLE [8de6278d3] 2017-03-24 13:55:02 +0300
-->
- Fix cancelling of pg_stop_backup() when attempting to stop
+ Fix cancelling of pg_stop_backup() when attempting to stop
a non-exclusive backup (Michael Paquier, David Steele)
- If pg_stop_backup() was cancelled while waiting for a
+ If pg_stop_backup() was cancelled while waiting for a
non-exclusive backup to end, related state was left inconsistent;
a new exclusive backup could not be started, and there were other minor
problems.
@@ -2196,7 +2702,7 @@ Branch: REL9_3_STABLE [07987304d] 2017-05-07 11:35:05 -0400
Branch: REL9_2_STABLE [9061680f0] 2017-05-07 11:35:11 -0400
-->
- Improve performance of pg_timezone_names view
+ Improve performance of pg_timezone_names view
(Tom Lane, David Rowley)
@@ -2226,13 +2732,13 @@ Branch: REL9_3_STABLE [3f613c6a4] 2017-02-21 17:51:28 -0500
Branch: REL9_2_STABLE [775227590] 2017-02-21 17:51:28 -0500
-->
- Fix sloppy handling of corner-case errors from lseek()
- and close() (Tom Lane)
+ Fix sloppy handling of corner-case errors from lseek()
+ and close() (Tom Lane)
Neither of these system calls are likely to fail in typical situations,
- but if they did, fd.c could get quite confused.
+ but if they did, fd.c could get quite confused.
@@ -2273,8 +2779,8 @@ Branch: REL9_3_STABLE [04207ef76] 2017-03-13 20:52:05 +0100
Branch: REL9_2_STABLE [d8c207437] 2017-03-13 20:52:16 +0100
-->
- Fix ecpg to support COMMIT PREPARED
- and ROLLBACK PREPARED (Masahiko Sawada)
+ Fix ecpg to support COMMIT PREPARED
+ and ROLLBACK PREPARED (Masahiko Sawada)
@@ -2290,7 +2796,7 @@ Branch: REL9_2_STABLE [731afc91f] 2017-03-10 10:52:01 +0100
-->
Fix a double-free error when processing dollar-quoted string literals
- in ecpg (Michael Meskes)
+ in ecpg (Michael Meskes)
@@ -2300,8 +2806,8 @@ Author: Teodor Sigaev
Branch: REL9_6_STABLE [2ed391f95] 2017-03-24 19:23:13 +0300
-->
- Fix pgbench to handle the combination
- of and options correctly
(Fabien Coelho)
@@ -2313,8 +2819,8 @@ Branch: master [ef2662394] 2017-03-07 11:36:42 -0500
Branch: REL9_6_STABLE [0e2c85d13] 2017-03-07 11:36:35 -0500
-->
- Fix pgbench to honor the long-form option
- spelling , as per its documentation (Tom Lane)
@@ -2325,15 +2831,15 @@ Branch: master [330b84d8c] 2017-03-06 23:29:02 -0500
Branch: REL9_6_STABLE [e961341cc] 2017-03-06 23:29:08 -0500
-->
- Fix pg_dump/pg_restore to correctly
- handle privileges for the public schema when
- using option (Stephen Frost)
Other schemas start out with no privileges granted,
- but public does not; this requires special-case treatment
- when it is dropped and restored due to the option.
@@ -2348,7 +2854,7 @@ Branch: REL9_3_STABLE [783acfd4d] 2017-03-06 19:33:59 -0500
Branch: REL9_2_STABLE [0ab75448e] 2017-03-06 19:33:59 -0500
-->
- In pg_dump, fix incorrect schema and owner marking for
+ In pg_dump, fix incorrect schema and owner marking for
comments and security labels of some types of database objects
(Giuseppe Broccolo, Tom Lane)
@@ -2368,12 +2874,12 @@ Branch: master [39370e6a0] 2017-02-17 15:06:28 -0500
Branch: REL9_6_STABLE [4e8b2fd33] 2017-02-17 15:06:34 -0500
-->
- Fix typo in pg_dump's query for initial privileges
+ Fix typo in pg_dump's query for initial privileges
of a procedural language (Peter Eisentraut)
- This resulted in pg_dump always believing that the
+ This resulted in pg_dump always believing that the
language had no initial privileges. Since that's true for most
procedural languages, ill effects from this bug are probably rare.
@@ -2390,13 +2896,13 @@ Branch: REL9_3_STABLE [0c0a95c2f] 2017-03-10 14:15:09 -0500
Branch: REL9_2_STABLE [e6d2ba419] 2017-03-10 14:15:09 -0500
-->
- Avoid emitting an invalid list file in pg_restore -l
+ Avoid emitting an invalid list file in pg_restore -l
when SQL object names contain newlines (Tom Lane)
Replace newlines by spaces, which is sufficient to make the output
- valid for pg_restore -L's purposes.
+ valid for pg_restore -L's purposes.
@@ -2411,8 +2917,8 @@ Branch: REL9_3_STABLE [7f831f09b] 2017-03-06 17:04:29 -0500
Branch: REL9_2_STABLE [e864cd25b] 2017-03-06 17:04:55 -0500
-->
- Fix pg_upgrade to transfer comments and security labels
- attached to large objects (blobs) (Stephen Frost)
+ Fix pg_upgrade to transfer comments and security labels
+ attached to large objects (blobs) (Stephen Frost)
@@ -2433,13 +2939,13 @@ Branch: REL9_2_STABLE [0276da5eb] 2017-03-12 19:36:28 -0400
-->
Improve error handling
- in contrib/adminpack's pg_file_write()
+ in contrib/adminpack's pg_file_write()
function (Noah Misch)
Notably, it failed to detect errors reported
- by fclose().
+ by fclose().
@@ -2454,7 +2960,7 @@ Branch: REL9_3_STABLE [f6cfc14e5] 2017-03-11 13:33:22 -0800
Branch: REL9_2_STABLE [c4613c3f4] 2017-03-11 13:33:30 -0800
-->
- In contrib/dblink, avoid leaking the previous unnamed
+ In contrib/dblink, avoid leaking the previous unnamed
connection when establishing a new unnamed connection (Joe Conway)
@@ -2479,7 +2985,7 @@ Branch: REL9_4_STABLE [b179684c7] 2017-04-13 17:18:35 -0400
Branch: REL9_3_STABLE [5be58cc89] 2017-04-13 17:18:35 -0400
-->
- Fix contrib/pg_trgm's extraction of trigrams from regular
+ Fix contrib/pg_trgm's extraction of trigrams from regular
expressions (Tom Lane)
@@ -2497,7 +3003,7 @@ Branch: master [332bec1e6] 2017-04-24 22:50:07 -0400
Branch: REL9_6_STABLE [86e640a69] 2017-04-26 09:14:21 -0400
-->
- In contrib/postgres_fdw, allow join conditions that
+ In contrib/postgres_fdw, allow join conditions that
contain shippable extension-provided functions to be pushed to the
remote server (David Rowley, Ashutosh Bapat)
@@ -2555,7 +3061,7 @@ Branch: REL9_3_STABLE [dc93cafca] 2017-05-01 11:54:02 -0400
Branch: REL9_2_STABLE [c96ccc40e] 2017-05-01 11:54:08 -0400
-->
- Update time zone data files to tzdata release 2017b
+ Update time zone data files to tzdata release 2017b
for DST law changes in Chile, Haiti, and Mongolia, plus historical
corrections for Ecuador, Kazakhstan, Liberia, and Spain.
Switch to numeric abbreviations for numerous time zones in South
@@ -2569,9 +3075,9 @@ Branch: REL9_2_STABLE [c96ccc40e] 2017-05-01 11:54:08 -0400
or no currency among the local population. They are in process of
reversing that policy in favor of using numeric UTC offsets in zones
where there is no evidence of real-world use of an English
- abbreviation. At least for the time being, PostgreSQL
+ abbreviation. At least for the time being, PostgreSQL
will continue to accept such removed abbreviations for timestamp input.
- But they will not be shown in the pg_timezone_names
+ But they will not be shown in the pg_timezone_names
view nor used for output.
@@ -2593,15 +3099,15 @@ Branch: REL9_2_STABLE [82e7d3dfd] 2017-05-07 11:57:41 -0400
The Microsoft MSVC build scripts neglected to install
- the posixrules file in the timezone directory tree.
+ the posixrules 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 US/Eastern zone. If you don't want that, remove
- the posixrules file, or replace it with a copy of some
+ the US/Eastern zone. If you don't want that, remove
+ the posixrules file, or replace it with a copy of some
other zone file (see ). Note that
due to caching, you may need to restart the server to get such changes
to take effect.
@@ -2663,15 +3169,15 @@ Branch: REL9_2_STABLE [bcd7b47c2] 2017-02-06 13:20:25 -0500
-->
Fix a race condition that could cause indexes built
- with CREATE INDEX CONCURRENTLY to be corrupt
+ with CREATE INDEX CONCURRENTLY to be corrupt
(Pavan Deolasee, Tom Lane)
- If CREATE INDEX CONCURRENTLY was used to build an index
+ If CREATE INDEX CONCURRENTLY was used to build an index
that depends on a column not previously indexed, then rows
updated by transactions that ran concurrently with
- the CREATE INDEX command could have received incorrect
+ the CREATE INDEX command could have received incorrect
index entries. If you suspect this may have happened, the most
reliable solution is to rebuild affected indexes after installing
this update.
@@ -2695,7 +3201,7 @@ Branch: REL9_4_STABLE [3e844a34b] 2016-11-15 15:55:36 -0500
Backends failed to account for this snapshot when advertising their
oldest xmin, potentially allowing concurrent vacuuming operations to
remove data that was still needed. This led to transient failures
- along the lines of cache lookup failed for relation 1255.
+ along the lines of cache lookup failed for relation 1255.
@@ -2711,7 +3217,7 @@ Branch: REL9_5_STABLE [ed8e8b814] 2017-01-09 18:19:29 -0300
- The WAL record emitted for a BRIN revmap page when moving an
+ The WAL record emitted for a BRIN revmap page when moving an
index tuple to a different page was incorrect. Replay would make the
related portion of the index useless, forcing it to be recomputed.
@@ -2728,13 +3234,13 @@ Branch: REL9_3_STABLE [8e403f215] 2016-12-08 14:16:47 -0500
Branch: REL9_2_STABLE [a00ac6299] 2016-12-08 14:19:25 -0500
-->
- Unconditionally WAL-log creation of the init fork for an
+ Unconditionally WAL-log creation of the init fork for an
unlogged table (Michael Paquier)
Previously, this was skipped when
- = minimal, but actually it's necessary even in that case
+ = minimal, but actually it's necessary even in that case
to ensure that the unlogged table is properly reset to empty after a
crash.
@@ -2816,7 +3322,7 @@ Branch: master [93eb619cd] 2016-12-17 02:22:15 +0900
Branch: REL9_6_STABLE [6c75fb6b3] 2016-12-17 02:25:47 +0900
-->
- Disallow setting the num_sync field to zero in
+ Disallow setting the num_sync field to zero in
(Fujii Masao)
@@ -2867,7 +3373,7 @@ Branch: REL9_6_STABLE [20064c0ec] 2017-01-29 23:05:09 -0500
-->
Fix tracking of initial privileges for extension member objects so
- that it works correctly with ALTER EXTENSION ... ADD/DROP
+ that it works correctly with ALTER EXTENSION ... ADD/DROP
(Stephen Frost)
@@ -2875,7 +3381,7 @@ Branch: REL9_6_STABLE [20064c0ec] 2017-01-29 23:05:09 -0500
An object's current privileges at the time it is added to the
extension will now be considered its default privileges; only
later changes in its privileges will be dumped by
- subsequent pg_dump runs.
+ subsequent pg_dump runs.
@@ -2890,7 +3396,7 @@ Branch: REL9_3_STABLE [8f67a6c22] 2016-11-23 13:45:56 -0500
Branch: REL9_2_STABLE [05975ab0a] 2016-11-23 13:45:56 -0500
-->
- Make sure ALTER TABLE preserves index tablespace
+ Make sure ALTER TABLE preserves index tablespace
assignments when rebuilding indexes (Tom Lane, Michael Paquier)
@@ -2912,7 +3418,7 @@ Branch: REL9_4_STABLE [3a9a8c408] 2016-10-26 17:05:06 -0400
Fix incorrect updating of trigger function properties when changing a
foreign-key constraint's deferrability properties with ALTER
- TABLE ... ALTER CONSTRAINT (Tom Lane)
+ TABLE ... ALTER CONSTRAINT (Tom Lane)
@@ -2937,8 +3443,8 @@ Branch: REL9_2_STABLE [6a363a4c2] 2016-11-25 13:44:48 -0500
- This avoids could not find trigger NNN
- or relation NNN has no triggers errors.
+ This avoids could not find trigger NNN
+ or relation NNN has no triggers errors.
@@ -2950,15 +3456,15 @@ Branch: REL9_6_STABLE [4e563a1f6] 2017-01-09 19:26:58 -0300
Branch: REL9_5_STABLE [4d4ab6ccd] 2017-01-09 19:26:58 -0300
-->
- Fix ALTER TABLE ... SET DATA TYPE ... USING when child
+ Fix ALTER TABLE ... SET DATA TYPE ... USING when child
table has different column ordering than the parent
(Álvaro Herrera)
- Failure to adjust the column numbering in the USING
+ Failure to adjust the column numbering in the USING
expression led to errors,
- typically attribute N has wrong type.
+ typically attribute N has wrong type.
@@ -2974,7 +3480,7 @@ Branch: REL9_2_STABLE [6c4cf2be8] 2017-01-04 18:00:12 -0500
-->
Fix processing of OID column when a table with OIDs is associated to
- a parent with OIDs via ALTER TABLE ... INHERIT (Amit
+ a parent with OIDs via ALTER TABLE ... INHERIT (Amit
Langote)
@@ -2992,8 +3498,8 @@ Branch: master [1ead0208b] 2016-12-22 16:23:38 -0500
Branch: REL9_6_STABLE [68330c8b4] 2016-12-22 16:23:34 -0500
-->
- Ensure that CREATE TABLE ... LIKE ... WITH OIDS creates
- a table with OIDs, whether or not the LIKE-referenced
+ Ensure that CREATE TABLE ... LIKE ... WITH OIDS creates
+ a table with OIDs, whether or not the LIKE-referenced
table(s) have OIDs (Tom Lane)
@@ -3007,7 +3513,7 @@ Branch: REL9_5_STABLE [78a98b767] 2016-12-21 17:02:47 +0000
Branch: REL9_4_STABLE [cad24980e] 2016-12-21 17:03:54 +0000
-->
- Fix CREATE OR REPLACE VIEW to update the view query
+ Fix CREATE OR REPLACE VIEW to update the view query
before attempting to apply the new view options (Dean Rasheed)
@@ -3028,7 +3534,7 @@ Branch: REL9_3_STABLE [0e3aadb68] 2016-12-22 17:09:00 -0500
-->
Report correct object identity during ALTER TEXT SEARCH
- CONFIGURATION (Artur Zakirov)
+ CONFIGURATION (Artur Zakirov)
@@ -3046,8 +3552,8 @@ Branch: REL9_5_STABLE [7816d1356] 2016-11-24 15:39:55 -0300
-->
Fix commit timestamp mechanism to not fail when queried about
- the special XIDs FrozenTransactionId
- and BootstrapTransactionId (Craig Ringer)
+ the special XIDs FrozenTransactionId
+ and BootstrapTransactionId (Craig Ringer)
@@ -3068,8 +3574,8 @@ Branch: REL9_5_STABLE [6e00ba1e1] 2016-11-10 15:00:58 -0500
The symptom was spurious ON CONFLICT is not supported on table
- ... used as a catalog table errors when the target
- of INSERT ... ON CONFLICT is a view with cascade option.
+ ... used as a catalog table errors when the target
+ of INSERT ... ON CONFLICT is a view with cascade option.
@@ -3081,8 +3587,8 @@ Branch: REL9_6_STABLE [da05d0ebc] 2016-12-04 15:02:46 -0500
Branch: REL9_5_STABLE [25c06a1ed] 2016-12-04 15:02:48 -0500
-->
- Fix incorrect target lists can have at most N
- entries complaint when using ON CONFLICT with
+ Fix incorrect target lists can have at most N
+ entries complaint when using ON CONFLICT with
wide tables (Tom Lane)
@@ -3094,8 +3600,8 @@ Branch: master [da8f3ebf3] 2016-11-02 14:32:13 -0400
Branch: REL9_6_STABLE [f4d865f22] 2016-11-02 14:32:13 -0400
-->
- Fix spurious query provides a value for a dropped column
- errors during INSERT or UPDATE on a table
+ Fix spurious query provides a value for a dropped column
+ errors during INSERT or UPDATE on a table
with a dropped column (Tom Lane)
@@ -3110,13 +3616,13 @@ Branch: REL9_4_STABLE [44c8b4fcd] 2016-11-20 14:26:19 -0500
Branch: REL9_3_STABLE [71db302ec] 2016-11-20 14:26:19 -0500
-->
- Prevent multicolumn expansion of foo.* in
- an UPDATE source expression (Tom Lane)
+ Prevent multicolumn expansion of foo.* in
+ an UPDATE source expression (Tom Lane)
This led to UPDATE target count mismatch --- internal
- error. Now the syntax is understood as a whole-row variable,
+ error. Now the syntax is understood as a whole-row variable,
as it would be in other contexts.
@@ -3133,12 +3639,12 @@ Branch: REL9_2_STABLE [082d1fb9e] 2016-12-09 12:01:14 -0500
-->
Ensure that column typmods are determined accurately for
- multi-row VALUES constructs (Tom Lane)
+ multi-row VALUES constructs (Tom Lane)
This fixes problems occurring when the first value in a column has a
- determinable typmod (e.g., length for a varchar value) but
+ determinable typmod (e.g., length for a varchar value) but
later values don't share the same limit.
@@ -3162,8 +3668,8 @@ Branch: REL9_2_STABLE [6e2c21ec5] 2016-12-21 17:39:33 -0500
Normally, a Unicode surrogate leading character must be followed by a
Unicode surrogate trailing character, but the check for this was
missed if the leading character was the last character in a Unicode
- string literal (U&'...') or Unicode identifier
- (U&"...").
+ string literal (U&'...') or Unicode identifier
+ (U&"...").
@@ -3174,7 +3680,7 @@ Branch: master [db80acfc9] 2016-12-20 09:20:17 +0200
Branch: REL9_6_STABLE [ce92fc4e2] 2016-12-20 09:20:30 +0200
-->
- Fix execution of DISTINCT and ordered aggregates when
+ Fix execution of DISTINCT and ordered aggregates when
multiple such aggregates are able to share the same transition state
(Heikki Linnakangas)
@@ -3189,7 +3695,7 @@ Branch: master [260443847] 2016-12-19 13:49:50 -0500
Branch: REL9_6_STABLE [3f07eff10] 2016-12-19 13:49:45 -0500
-->
- Fix implementation of phrase search operators in tsquery
+ Fix implementation of phrase search operators in tsquery
(Tom Lane)
@@ -3218,7 +3724,7 @@ Branch: REL9_2_STABLE [fe6120f9b] 2017-01-26 12:17:47 -0500
-->
Ensure that a purely negative text search query, such
- as !foo, matches empty tsvectors (Tom Dunstan)
+ as !foo, matches empty tsvectors (Tom Dunstan)
@@ -3238,7 +3744,7 @@ Branch: REL9_3_STABLE [79e1a9efa] 2016-12-11 13:09:57 -0500
Branch: REL9_2_STABLE [f4ccee408] 2016-12-11 13:09:57 -0500
-->
- Prevent crash when ts_rewrite() replaces a non-top-level
+ Prevent crash when ts_rewrite() replaces a non-top-level
subtree with an empty query (Artur Zakirov)
@@ -3254,7 +3760,7 @@ Branch: REL9_3_STABLE [407d513df] 2016-10-30 17:35:43 -0400
Branch: REL9_2_STABLE [606e16a7f] 2016-10-30 17:35:43 -0400
-->
- Fix performance problems in ts_rewrite() (Tom Lane)
+ Fix performance problems in ts_rewrite() (Tom Lane)
@@ -3269,7 +3775,7 @@ Branch: REL9_3_STABLE [77a22f898] 2016-10-30 15:24:40 -0400
Branch: REL9_2_STABLE [b0f8a273e] 2016-10-30 15:24:40 -0400
-->
- Fix ts_rewrite()'s handling of nested NOT operators
+ Fix ts_rewrite()'s handling of nested NOT operators
(Tom Lane)
@@ -3283,7 +3789,7 @@ Branch: REL9_5_STABLE [7151e72d7] 2016-10-30 12:27:41 -0400
-->
Improve speed of user-defined aggregates that
- use array_append() as transition function (Tom Lane)
+ use array_append() as transition function (Tom Lane)
@@ -3298,7 +3804,7 @@ Branch: REL9_3_STABLE [ee9cb284a] 2017-01-05 11:33:51 -0500
Branch: REL9_2_STABLE [e0d59c6ef] 2017-01-05 11:33:51 -0500
-->
- Fix array_fill() to handle empty arrays properly (Tom Lane)
+ Fix array_fill() to handle empty arrays properly (Tom Lane)
@@ -3310,8 +3816,8 @@ Branch: REL9_6_STABLE [79c89f1f4] 2016-12-09 12:42:17 -0300
Branch: REL9_5_STABLE [581b09c72] 2016-12-09 12:42:17 -0300
-->
- Fix possible crash in array_position()
- or array_positions() when processing arrays of records
+ Fix possible crash in array_position()
+ or array_positions() when processing arrays of records
(Junseok Yang)
@@ -3327,7 +3833,7 @@ Branch: REL9_3_STABLE [e71fe8470] 2016-12-16 12:53:22 +0200
Branch: REL9_2_STABLE [c8f8ed5c2] 2016-12-16 12:53:27 +0200
-->
- Fix one-byte buffer overrun in quote_literal_cstr()
+ Fix one-byte buffer overrun in quote_literal_cstr()
(Heikki Linnakangas)
@@ -3348,8 +3854,8 @@ Branch: REL9_3_STABLE [f64b11fa0] 2017-01-17 17:32:20 +0900
Branch: REL9_2_STABLE [c73157ca0] 2017-01-17 17:32:45 +0900
-->
- Prevent multiple calls of pg_start_backup()
- and pg_stop_backup() from running concurrently (Michael
+ Prevent multiple calls of pg_start_backup()
+ and pg_stop_backup() from running concurrently (Michael
Paquier)
@@ -3368,7 +3874,7 @@ Branch: REL9_5_STABLE [74e67bbad] 2017-01-18 15:21:52 -0500
-->
Disable transform that attempted to remove no-op AT TIME
- ZONE conversions (Tom Lane)
+ ZONE conversions (Tom Lane)
@@ -3388,15 +3894,15 @@ Branch: REL9_3_STABLE [583599839] 2016-12-27 15:43:54 -0500
Branch: REL9_2_STABLE [beae7d5f0] 2016-12-27 15:43:55 -0500
-->
- Avoid discarding interval-to-interval casts
+ Avoid discarding interval-to-interval casts
that aren't really no-ops (Tom Lane)
In some cases, a cast that should result in zeroing out
- low-order interval fields was mistakenly deemed to be a
+ low-order interval fields was mistakenly deemed to be a
no-op and discarded. An example is that casting from INTERVAL
- MONTH to INTERVAL YEAR failed to clear the months field.
+ MONTH to INTERVAL YEAR failed to clear the months field.
@@ -3432,7 +3938,7 @@ Branch: master [4212cb732] 2016-12-06 11:11:54 -0500
Branch: REL9_6_STABLE [ebe5dc9e0] 2016-12-06 11:43:12 -0500
-->
- Allow statements prepared with PREPARE to be given
+ Allow statements prepared with PREPARE to be given
parallel plans (Amit Kapila, Tobias Bussmann)
@@ -3501,7 +4007,7 @@ Branch: REL9_6_STABLE [7defc3b97] 2016-11-10 11:31:56 -0500
-->
Fix the plan generated for sorted partial aggregation with a constant
- GROUP BY clause (Tom Lane)
+ GROUP BY clause (Tom Lane)
@@ -3512,8 +4018,8 @@ Branch: master [1f542a2ea] 2016-12-13 13:20:37 -0500
Branch: REL9_6_STABLE [997a2994e] 2016-12-13 13:20:16 -0500
-->
- Fix could not find plan for CTE planner error when dealing
- with a UNION ALL containing CTE references (Tom Lane)
+ Fix could not find plan for CTE planner error when dealing
+ with a UNION ALL containing CTE references (Tom Lane)
@@ -3530,7 +4036,7 @@ Branch: REL9_6_STABLE [b971a98ce] 2017-02-02 19:11:27 -0500
The typical consequence of this mistake was a plan should not
- reference subplan's variable error.
+ reference subplan's variable error.
@@ -3561,7 +4067,7 @@ Branch: master [bec96c82f] 2017-01-19 12:06:21 -0500
Branch: REL9_6_STABLE [fd081cabf] 2017-01-19 12:06:27 -0500
-->
- Fix pg_dump to emit the data of a sequence that is
+ Fix pg_dump to emit the data of a sequence that is
marked as an extension configuration table (Michael Paquier)
@@ -3573,14 +4079,14 @@ Branch: master [e2090d9d2] 2017-01-31 16:24:11 -0500
Branch: REL9_6_STABLE [eb5e9d90d] 2017-01-31 16:24:14 -0500
-->
- Fix mishandling of ALTER DEFAULT PRIVILEGES ... REVOKE
- in pg_dump (Stephen Frost)
+ Fix mishandling of ALTER DEFAULT PRIVILEGES ... REVOKE
+ in pg_dump (Stephen Frost)
- pg_dump missed issuing the
- required REVOKE commands in cases where ALTER
- DEFAULT PRIVILEGES had been used to reduce privileges to less than
+ pg_dump missed issuing the
+ required REVOKE commands in cases where ALTER
+ DEFAULT PRIVILEGES had been used to reduce privileges to less than
they would normally be.
@@ -3602,7 +4108,7 @@ Branch: REL9_3_STABLE [fc03f7dd1] 2016-12-21 13:47:28 -0500
Branch: REL9_2_STABLE [59a389891] 2016-12-21 13:47:32 -0500
-->
- Fix pg_dump to dump user-defined casts and transforms
+ Fix pg_dump to dump user-defined casts and transforms
that use built-in functions (Stephen Frost)
@@ -3616,15 +4122,15 @@ Branch: REL9_5_STABLE [a7864037d] 2016-11-17 14:59:23 -0500
Branch: REL9_4_STABLE [e69b532be] 2016-11-17 14:59:26 -0500
-->
- Fix pg_restore with
to behave more sanely if an archive contains
- unrecognized DROP commands (Tom Lane)
+ unrecognized DROP commands (Tom Lane)
This doesn't fix any live bug, but it may improve the behavior in
- future if pg_restore is used with an archive
- generated by a later pg_dump version.
+ future if pg_restore is used with an archive
+ generated by a later pg_dump version.
@@ -3637,7 +4143,7 @@ Branch: REL9_5_STABLE [bc53d7130] 2016-12-19 10:16:02 +0100
Branch: REL9_4_STABLE [f6508827a] 2016-12-19 10:16:12 +0100
-->
- Fix pg_basebackup's rate limiting in the presence of
+ Fix pg_basebackup's rate limiting in the presence of
slow I/O (Antonin Houska)
@@ -3656,8 +4162,8 @@ Branch: REL9_5_STABLE [6d779e05a] 2016-11-07 15:03:56 +0100
Branch: REL9_4_STABLE [5556420d4] 2016-11-07 15:04:23 +0100
-->
- Fix pg_basebackup's handling of
- symlinked pg_stat_tmp and pg_replslot
+ Fix pg_basebackup's handling of
+ symlinked pg_stat_tmp and pg_replslot
subdirectories (Magnus Hagander, Michael Paquier)
@@ -3673,7 +4179,7 @@ Branch: REL9_3_STABLE [92929a3e3] 2016-10-27 12:00:05 -0400
Branch: REL9_2_STABLE [629575fa2] 2016-10-27 12:14:07 -0400
-->
- Fix possible pg_basebackup failure on standby
+ Fix possible pg_basebackup failure on standby
server when including WAL files (Amit Kapila, Robert Haas)
@@ -3685,10 +4191,10 @@ Branch: master [dbdfd114f] 2016-11-25 18:36:10 -0500
Branch: REL9_6_STABLE [255bcd27f] 2016-11-25 18:36:10 -0500
-->
- Improve initdb to insert the correct
+ Improve initdb to insert the correct
platform-specific default values for
- the xxx_flush_after parameters
- into postgresql.conf (Fabien Coelho, Tom Lane)
+ the xxx_flush_after parameters
+ into postgresql.conf (Fabien Coelho, Tom Lane)
@@ -3706,7 +4212,7 @@ Branch: REL9_5_STABLE [c472f2a33] 2016-12-22 15:01:39 -0500
-->
Fix possible mishandling of expanded arrays in domain check
- constraints and CASE execution (Tom Lane)
+ constraints and CASE execution (Tom Lane)
@@ -3762,14 +4268,14 @@ Branch: REL9_3_STABLE [9c0b04f18] 2016-11-06 14:43:14 -0500
Branch: REL9_2_STABLE [92b7b1058] 2016-11-06 14:43:14 -0500
-->
- Fix PL/Tcl to support triggers on tables that have .tupno
+ Fix PL/Tcl to support triggers on tables that have .tupno
as a column name (Tom Lane)
This matches the (previously undocumented) behavior of
- PL/Tcl's spi_exec and spi_execp commands,
- namely that a magic .tupno column is inserted only if
+ PL/Tcl's spi_exec and spi_execp commands,
+ namely that a magic .tupno column is inserted only if
there isn't a real column named that.
@@ -3785,7 +4291,7 @@ Branch: REL9_3_STABLE [46b6f3fff] 2016-11-15 16:17:19 -0500
Branch: REL9_2_STABLE [13aa9af37] 2016-11-15 16:17:19 -0500
-->
- Allow DOS-style line endings in ~/.pgpass files,
+ Allow DOS-style line endings in ~/.pgpass files,
even on Unix (Vik Fearing)
@@ -3806,7 +4312,7 @@ Branch: REL9_3_STABLE [1df8b3fe8] 2016-12-22 08:32:25 +0100
Branch: REL9_2_STABLE [501c91074] 2016-12-22 08:34:07 +0100
-->
- Fix one-byte buffer overrun if ecpg is given a file
+ Fix one-byte buffer overrun if ecpg is given a file
name that ends with a dot (Takayuki Tsunakawa)
@@ -3819,11 +4325,11 @@ Branch: REL9_6_STABLE [6a8c67f50] 2016-12-25 16:04:47 -0500
-->
Fix incorrect error reporting for duplicate data
- in psql's \crosstabview (Tom Lane)
+ in psql's \crosstabview (Tom Lane)
- psql sometimes quoted the wrong row and/or column
+ psql sometimes quoted the wrong row and/or column
values when complaining about multiple entries for the same crosstab
cell.
@@ -3840,8 +4346,8 @@ Branch: REL9_3_STABLE [2022d594d] 2016-12-23 21:01:48 -0500
Branch: REL9_2_STABLE [26b55d669] 2016-12-23 21:01:51 -0500
-->
- Fix psql's tab completion for ALTER DEFAULT
- PRIVILEGES (Gilles Darold, Stephen Frost)
+ Fix psql's tab completion for ALTER DEFAULT
+ PRIVILEGES (Gilles Darold, Stephen Frost)
@@ -3852,8 +4358,8 @@ Branch: master [404e66758] 2016-11-28 11:51:30 -0500
Branch: REL9_6_STABLE [28735cc72] 2016-11-28 11:51:35 -0500
-->
- Fix psql's tab completion for ALTER TABLE t
- ALTER c DROP ... (Kyotaro Horiguchi)
+ Fix psql's tab completion for ALTER TABLE t
+ ALTER c DROP ... (Kyotaro Horiguchi)
@@ -3868,9 +4374,9 @@ Branch: REL9_3_STABLE [82eb5c514] 2016-12-07 12:19:56 -0500
Branch: REL9_2_STABLE [1ec5cc025] 2016-12-07 12:19:57 -0500
-->
- In psql, treat an empty or all-blank setting of
- the PAGER environment variable as meaning no
- pager (Tom Lane)
+ In psql, treat an empty or all-blank setting of
+ the PAGER environment variable as meaning no
+ pager (Tom Lane)
@@ -3890,8 +4396,8 @@ Branch: REL9_3_STABLE [9b8507bfa] 2016-12-22 09:47:25 -0800
Branch: REL9_2_STABLE [44de099f8] 2016-12-22 09:46:46 -0800
-->
- Improve contrib/dblink's reporting of
- low-level libpq errors, such as out-of-memory
+ Improve contrib/dblink's reporting of
+ low-level libpq errors, such as out-of-memory
(Joe Conway)
@@ -3906,14 +4412,14 @@ Branch: REL9_4_STABLE [cb687e0ac] 2016-12-22 09:19:08 -0800
Branch: REL9_3_STABLE [bd46cce21] 2016-12-22 09:18:50 -0800
-->
- Teach contrib/dblink to ignore irrelevant server options
- when it uses a contrib/postgres_fdw foreign server as
+ Teach contrib/dblink to ignore irrelevant server options
+ when it uses a contrib/postgres_fdw foreign server as
the source of connection options (Corey Huinker)
Previously, if the foreign server object had options that were not
- also libpq connection options, an error occurred.
+ also libpq connection options, an error occurred.
@@ -3927,7 +4433,7 @@ Branch: REL9_6_STABLE [2a8783e44] 2016-11-02 00:09:28 -0400
Branch: REL9_5_STABLE [af636d7b5] 2016-11-02 00:09:28 -0400
-->
- Fix portability problems in contrib/pageinspect's
+ Fix portability problems in contrib/pageinspect's
functions for GIN indexes (Peter Eisentraut, Tom Lane)
@@ -4016,7 +4522,7 @@ Branch: REL9_3_STABLE [2b133be04] 2017-01-30 11:41:02 -0500
Branch: REL9_2_STABLE [ef878cc2c] 2017-01-30 11:41:09 -0500
-->
- Update time zone data files to tzdata release 2016j
+ Update time zone data files to tzdata release 2016j
for DST law changes in northern Cyprus (adding a new zone
Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga,
and Antarctica/Casey.
@@ -4083,7 +4589,7 @@ Branch: REL9_3_STABLE [1c02ee314] 2016-10-19 15:00:34 +0300
crash recovery, or to be written incorrectly on a standby server.
Bogus entries in a free space map could lead to attempts to access
pages that have been truncated away from the relation itself, typically
- producing errors like could not read block XXX:
+ producing errors like could not read block XXX:
read only 0 of 8192 bytes. Checksum failures in the
visibility map are also possible, if checksumming is enabled.
@@ -4091,7 +4597,7 @@ Branch: REL9_3_STABLE [1c02ee314] 2016-10-19 15:00:34 +0300
Procedures for determining whether there is a problem and repairing it
if so are discussed at
- .
+ .
@@ -4102,7 +4608,7 @@ Branch: master [5afcd2aa7] 2016-09-30 20:40:55 -0400
Branch: REL9_6_STABLE [b6d906073] 2016-09-30 20:39:06 -0400
-->
- Fix possible data corruption when pg_upgrade rewrites
+ Fix possible data corruption when pg_upgrade rewrites
a relation visibility map into 9.6 format (Tom Lane)
@@ -4112,20 +4618,20 @@ Branch: REL9_6_STABLE [b6d906073] 2016-09-30 20:39:06 -0400
Windows, the old map was read using text mode, leading to incorrect
results if the map happened to contain consecutive bytes that matched
a carriage return/line feed sequence. The latter error would almost
- always lead to a pg_upgrade failure due to the map
+ always lead to a pg_upgrade failure due to the map
file appearing to be the wrong length.
If you are using a big-endian machine (many non-Intel architectures
- are big-endian) and have used pg_upgrade to upgrade
+ are big-endian) and have used pg_upgrade to upgrade
from a pre-9.6 release, you should assume that all visibility maps are
incorrect and need to be regenerated. It is sufficient to truncate
each relation's visibility map
- with contrib/pg_visibility's
- pg_truncate_visibility_map() function.
+ with contrib/pg_visibility's
+ pg_truncate_visibility_map() function.
For more information see
- .
+ .
@@ -4138,7 +4644,7 @@ Branch: REL9_5_STABLE [65d85b8f9] 2016-10-23 18:36:13 -0400
-->
Don't throw serialization errors for self-conflicting insertions
- in INSERT ... ON CONFLICT (Thomas Munro, Peter Geoghegan)
+ in INSERT ... ON CONFLICT (Thomas Munro, Peter Geoghegan)
@@ -4150,7 +4656,7 @@ Branch: REL9_6_STABLE [a5f0bd77a] 2016-10-17 12:13:35 +0300
-->
Fix use-after-free hazard in execution of aggregate functions
- using DISTINCT (Peter Geoghegan)
+ using DISTINCT (Peter Geoghegan)
@@ -4185,7 +4691,7 @@ Branch: REL9_6_STABLE [190765a05] 2016-10-03 16:23:02 -0400
Branch: REL9_5_STABLE [647a86e37] 2016-10-03 16:23:12 -0400
-->
- Fix COPY with a column name list from a table that has
+ Fix COPY with a column name list from a table that has
row-level security enabled (Adam Brightwell)
@@ -4201,14 +4707,14 @@ Branch: REL9_3_STABLE [edb514306] 2016-10-20 17:18:09 -0400
Branch: REL9_2_STABLE [f17c26dbd] 2016-10-20 17:18:14 -0400
-->
- Fix EXPLAIN to emit valid XML when
+ Fix EXPLAIN to emit valid XML when
is on (Markus Winand)
Previously the XML output-format option produced syntactically invalid
- tags such as <I/O-Read-Time>. That is now
- rendered as <I-O-Read-Time>.
+ tags such as <I/O-Read-Time>. That is now
+ rendered as <I-O-Read-Time>.
@@ -4220,7 +4726,7 @@ Branch: REL9_6_STABLE [03f2bf70a] 2016-10-13 19:46:06 -0400
Branch: REL9_5_STABLE [3cd504254] 2016-10-13 19:45:58 -0400
-->
- Fix statistics update for TRUNCATE in a prepared
+ Fix statistics update for TRUNCATE in a prepared
transaction (Stas Kelvich)
@@ -4242,16 +4748,16 @@ Branch: REL9_3_STABLE [f0bf0f233] 2016-10-13 17:05:15 -0400
Branch: REL9_2_STABLE [6f2db29ec] 2016-10-13 17:05:15 -0400
-->
- Fix bugs in merging inherited CHECK constraints while
+ Fix bugs in merging inherited CHECK constraints while
creating or altering a table (Tom Lane, Amit Langote)
- Allow identical CHECK constraints to be added to a parent
+ Allow identical CHECK 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 NOT VALID
+ constraint from the parent table with a NOT VALID
constraint on the child. Likewise, prevent merging of a NO
- INHERIT child constraint with an inherited constraint.
+ INHERIT child constraint with an inherited constraint.
@@ -4264,8 +4770,8 @@ Branch: REL9_5_STABLE [f50fa46cc] 2016-10-03 16:40:27 -0400
-->
Show a sensible value
- in pg_settings.unit
- for min_wal_size and max_wal_size (Tom Lane)
+ in pg_settings.unit
+ for min_wal_size and max_wal_size (Tom Lane)
@@ -4276,7 +4782,7 @@ Branch: master [9c4cc9e2c] 2016-10-13 00:25:48 -0400
Branch: REL9_6_STABLE [0e9e64c07] 2016-10-13 00:25:28 -0400
-->
- Fix replacement of array elements in jsonb_set()
+ Fix replacement of array elements in jsonb_set()
(Tom Lane)
@@ -4364,7 +4870,7 @@ Branch: REL9_4_STABLE [6d3cbbf59] 2016-10-13 15:07:11 -0400
- This avoids possible failures during munmap() on systems
+ This avoids possible failures during munmap() on systems
with atypical default huge page sizes. Except in crash-recovery
cases, there were no ill effects other than a log message.
@@ -4390,7 +4896,7 @@ Branch: REL9_1_STABLE [e84e4761f] 2016-10-07 12:53:51 +0300
-->
Don't try to share SSL contexts across multiple connections
- in libpq (Heikki Linnakangas)
+ in libpq (Heikki Linnakangas)
@@ -4411,12 +4917,12 @@ Branch: REL9_2_STABLE [7397f62e7] 2016-10-10 10:35:58 -0400
Branch: REL9_1_STABLE [fb6825fe5] 2016-10-10 10:35:58 -0400
-->
- Avoid corner-case memory leak in libpq (Tom Lane)
+ Avoid corner-case memory leak in libpq (Tom Lane)
The reported problem involved leaking an error report
- during PQreset(), but there might be related cases.
+ during PQreset(), but there might be related cases.
@@ -4428,7 +4934,7 @@ Branch: REL9_6_STABLE [bac56dbe0] 2016-10-03 10:07:39 -0400
Branch: REL9_5_STABLE [0f259bd17] 2016-10-03 10:07:39 -0400
-->
- In pg_upgrade, check library loadability in name order
+ In pg_upgrade, check library loadability in name order
(Tom Lane)
@@ -4446,13 +4952,13 @@ Branch: master [e8bdee277] 2016-10-02 14:31:28 -0400
Branch: REL9_6_STABLE [f40334b85] 2016-10-02 14:31:28 -0400
-->
- Fix pg_upgrade to work correctly for extensions
+ Fix pg_upgrade to work correctly for extensions
containing index access methods (Tom Lane)
To allow this, the server has been extended to support ALTER
- EXTENSION ADD/DROP ACCESS METHOD. That functionality should have
+ EXTENSION ADD/DROP ACCESS METHOD. That functionality should have
been included in the original patch to support dynamic creation of
access methods, but it was overlooked.
@@ -4465,7 +4971,7 @@ Branch: master [f002ed2b8] 2016-09-30 20:40:56 -0400
Branch: REL9_6_STABLE [53fbeed40] 2016-09-30 20:40:27 -0400
-->
- Improve error reporting in pg_upgrade's file
+ Improve error reporting in pg_upgrade's file
copying/linking/rewriting steps (Tom Lane, Álvaro Herrera)
@@ -4477,7 +4983,7 @@ Branch: master [4806f26f9] 2016-10-07 09:51:18 -0400
Branch: REL9_6_STABLE [1749332ec] 2016-10-07 09:51:28 -0400
-->
- Fix pg_dump to work against pre-7.4 servers
+ Fix pg_dump to work against pre-7.4 servers
(Amit Langote, Tom Lane)
@@ -4490,8 +4996,8 @@ Branch: REL9_6_STABLE [2933ed036] 2016-10-07 14:35:41 +0300
Branch: REL9_5_STABLE [010a1b561] 2016-10-07 14:35:45 +0300
-->
- Disallow specifying both
@@ -4504,12 +5010,12 @@ Branch: REL9_6_STABLE [aab809664] 2016-10-06 13:34:38 +0300
Branch: REL9_5_STABLE [69da71254] 2016-10-06 13:34:32 +0300
-->
- Make pg_rewind turn off synchronous_commit
+ Make pg_rewind turn off synchronous_commit
in its session on the source server (Michael Banck, Michael Paquier)
- This allows pg_rewind to work even when the source
+ This allows pg_rewind to work even when the source
server is using synchronous replication that is not working for some
reason.
@@ -4525,8 +5031,8 @@ Branch: REL9_4_STABLE [da3f71a08] 2016-09-30 11:22:49 +0200
Branch: REL9_3_STABLE [4bff35cca] 2016-09-30 11:23:25 +0200
-->
- In pg_xlogdump, retry opening new WAL segments when
- using option (Magnus Hagander)
@@ -4542,7 +5048,7 @@ Branch: master [9a109452d] 2016-10-01 16:32:54 -0400
Branch: REL9_6_STABLE [f4e787c82] 2016-10-01 16:32:55 -0400
-->
- Fix contrib/pg_visibility to report the correct TID for
+ Fix contrib/pg_visibility to report the correct TID for
a corrupt tuple that has been the subject of a rolled-back update
(Tom Lane)
@@ -4556,7 +5062,7 @@ Branch: REL9_6_STABLE [68fb75e10] 2016-10-01 13:35:20 -0400
-->
Fix makefile dependencies so that parallel make
- of PL/Python by itself will succeed reliably
+ of PL/Python by itself will succeed reliably
(Pavel Raiskup)
@@ -4594,7 +5100,7 @@ Branch: REL9_2_STABLE [a03339aef] 2016-10-19 17:57:01 -0400
Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400
-->
- Update time zone data files to tzdata release 2016h
+ Update time zone data files to tzdata release 2016h
for DST law changes in Palestine and Turkey, plus historical
corrections for Turkey and some regions of Russia.
Switch to numeric abbreviations for some time zones in Antarctica,
@@ -4607,15 +5113,15 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400
or no currency among the local population. They are in process of
reversing that policy in favor of using numeric UTC offsets in zones
where there is no evidence of real-world use of an English
- abbreviation. At least for the time being, PostgreSQL
+ abbreviation. At least for the time being, PostgreSQL
will continue to accept such removed abbreviations for timestamp input.
- But they will not be shown in the pg_timezone_names
+ But they will not be shown in the pg_timezone_names
view nor used for output.
- In this update, AMT is no longer shown as being in use to
- mean Armenia Time. Therefore, we have changed the Default
+ In this update, AMT is no longer shown as being in use to
+ mean Armenia Time. Therefore, we have changed the Default
abbreviation set to interpret it as Amazon Time, thus UTC-4 not UTC+4.
@@ -4637,7 +5143,7 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400
Overview
- Major enhancements in PostgreSQL 9.6 include:
+ Major enhancements in PostgreSQL 9.6 include:
@@ -4671,15 +5177,15 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400
- postgres_fdw now supports remote joins, sorts,
- UPDATEs, and DELETEs
+ postgres_fdw now supports remote joins, sorts,
+ UPDATEs, and DELETEs
Substantial performance improvements, especially in the area of
- scalability on multi-CPU-socket servers
+ scalability on multi-CPU-socket servers
@@ -4714,7 +5220,7 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400
-->
Improve the pg_stat_activity
+ linkend="pg-stat-activity-view">pg_stat_activity
view's information about what a process is waiting for (Amit
Kapila, Ildus Kurbangaliev)
@@ -4722,10 +5228,10 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400
Historically a process has only been shown as waiting if it was
waiting for a heavyweight lock. Now waits for lightweight locks
- and buffer pins are also shown in pg_stat_activity.
+ and buffer pins are also shown in pg_stat_activity.
Also, the type of lock being waited for is now visible.
- These changes replace the waiting column with
- wait_event_type and wait_event.
+ These changes replace the waiting column with
+ wait_event_type and wait_event.
@@ -4735,14 +5241,14 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400
-->
In to_char(),
+ linkend="functions-formatting-table">to_char(),
do not count a minus sign (when needed) as part of the field
width for time-related fields (Bruce Momjian)
- For example, to_char('-4 years'::interval, 'YY')
- now returns -04, rather than -4.
+ For example, to_char('-4 years'::interval, 'YY')
+ now returns -04, rather than -4.
@@ -4752,18 +5258,18 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400
-->
Make extract() behave
+ linkend="functions-datetime-table">extract() behave
more reasonably with infinite inputs (Vitaly Burovoy)
- Historically the extract() function just returned
+ Historically the extract() function just returned
zero given an infinite timestamp, regardless of the given
field name. Make it return infinity
or -infinity as appropriate when the
requested field is one that is monotonically increasing (e.g,
- year, epoch), or NULL when
- it is not (e.g., day, hour). Also,
+ year, epoch), or NULL when
+ it is not (e.g., day, hour). Also,
throw the expected error for bad field names.
@@ -4774,9 +5280,9 @@ Branch: REL9_1_STABLE [22cf97635] 2016-10-19 17:57:06 -0400
This commit is also listed under libpq and psql
-->
- Remove PL/pgSQL's feature that suppressed the
- innermost line of CONTEXT for messages emitted by
- RAISE commands (Pavel Stehule)
+ Remove PL/pgSQL's feature that suppressed the
+ innermost line of CONTEXT for messages emitted by
+ RAISE commands (Pavel Stehule)
@@ -4791,13 +5297,13 @@ This commit is also listed under libpq and psql
-->
Fix the default text search parser to allow leading digits
- in email and host tokens (Artur Zakirov)
+ in email and host tokens (Artur Zakirov)
In most cases this will result in few changes in the parsing of
text. But if you have data where such addresses occur frequently,
- it may be worth rebuilding dependent tsvector columns
+ it may be worth rebuilding dependent tsvector columns
and indexes so that addresses of this form will be found properly
by text searches.
@@ -4809,8 +5315,8 @@ This commit is also listed under libpq and psql
2016-03-16 [9a206d063] Improve script generating unaccent rules
-->
- Extend contrib/unaccent's
- standard unaccent.rules file to handle all diacritics
+ Extend contrib/unaccent's
+ standard unaccent.rules file to handle all diacritics
known to Unicode, and to expand ligatures correctly (Thomas Munro,
Léonard Benedetti)
@@ -4819,7 +5325,7 @@ This commit is also listed under libpq and psql
The previous version neglected to convert some less-common letters
with diacritic marks. Also, ligatures are now expanded into
separate letters. Installations that use this rules file may wish
- to rebuild tsvector columns and indexes that depend on the
+ to rebuild tsvector columns and indexes that depend on the
result.
@@ -4830,15 +5336,15 @@ This commit is also listed under libpq and psql
-->
Remove the long-deprecated
- CREATEUSER/NOCREATEUSER options from
- CREATE ROLE and allied commands (Tom Lane)
+ CREATEUSER/NOCREATEUSER options from
+ CREATE ROLE and allied commands (Tom Lane)
- CREATEUSER actually meant SUPERUSER,
+ CREATEUSER actually meant SUPERUSER,
for ancient backwards-compatibility reasons. This has been a
constant source of confusion for people who (reasonably) expect
- it to mean CREATEROLE. It has been deprecated for
+ it to mean CREATEROLE. It has been deprecated for
ten years now, so fix the problem by removing it.
@@ -4850,13 +5356,13 @@ This commit is also listed under libpq and psql
2016-05-08 [7df974ee0] Disallow superuser names starting with 'pg_' in initdb
-->
- Treat role names beginning with pg_ as reserved
+ Treat role names beginning with pg_ as reserved
(Stephen Frost)
User creation of such role names is now disallowed. This prevents
- conflicts with built-in roles created by initdb.
+ conflicts with built-in roles created by initdb.
@@ -4866,16 +5372,16 @@ This commit is also listed under libpq and psql
-->
Change a column name in the
- information_schema.routines
- view from result_cast_character_set_name
- to result_cast_char_set_name (Clément
+ information_schema.routines
+ view from result_cast_character_set_name
+ to result_cast_char_set_name (Clément
Prévost)
The SQL:2011 standard specifies the longer name, but that appears
to be a mistake, because adjacent column names use the shorter
- style, as do other information_schema views.
+ style, as do other information_schema views.
@@ -4884,7 +5390,7 @@ This commit is also listed under libpq and psql
2015-12-08 [d5563d7df] psql: Support multiple -c and -f options, and allow mixi
-->
- psql's option no longer implies
+ psql's option no longer implies
(Pavel Stehule, Catalin Iacob)
@@ -4893,7 +5399,7 @@ This commit is also listed under libpq and psql
Write (or its
abbreviation ) explicitly to obtain the old
behavior. Scripts so modified will still work with old
- versions of psql.
+ versions of psql.
@@ -4902,7 +5408,7 @@ This commit is also listed under libpq and psql
2015-07-02 [5671aaca8] Improve pg_restore's -t switch to match all types of rel
-->
- Improve pg_restore's option to
+ Improve pg_restore's option to
match all types of relations, not only plain tables (Craig Ringer)
@@ -4912,17 +5418,17 @@ This commit is also listed under libpq and psql
2016-02-12 [59a884e98] Change delimiter used for display of NextXID
-->
- Change the display format used for NextXID in
- pg_controldata and related places (Joe Conway,
+ Change the display format used for NextXID in
+ pg_controldata and related places (Joe Conway,
Bruce Momjian)
Display epoch-and-transaction-ID values in the format
- number:number.
+ number:number.
The previous format
- number/number was
- confusingly similar to that used for LSNs.
+ number/number was
+ confusingly similar to that used for LSNs.
@@ -4940,8 +5446,8 @@ and many others in the same vein
Many of the standard extensions have been updated to allow their
functions to be executed within parallel query worker processes.
These changes will not take effect in
- databases pg_upgrade'd from prior versions unless
- you apply ALTER EXTENSION UPDATE to each such extension
+ databases pg_upgrade'd from prior versions unless
+ you apply ALTER EXTENSION UPDATE to each such extension
(in each database of a cluster).
@@ -5002,7 +5508,7 @@ and many others in the same vein
- With 9.6, PostgreSQL introduces initial support
+ With 9.6, PostgreSQL introduces initial support
for parallel execution of large queries. Only strictly read-only
queries where the driving table is accessed via a sequential scan
can be parallelized. Hash joins and nested loops can be performed
@@ -5048,7 +5554,7 @@ and many others in the same vein
2015-09-02 [30bb26b5e] Allow usage of huge maintenance_work_mem for GIN build.
-->
- Allow GIN index builds to
+ Allow GIN index builds to
make effective use of
settings larger than 1 GB (Robert Abraham, Teodor Sigaev)
@@ -5076,7 +5582,7 @@ and many others in the same vein
-->
Add gin_clean_pending_list()
+ linkend="functions-admin-index">gin_clean_pending_list()
function to allow manual invocation of pending-list cleanup for a
GIN index (Jeff Janes)
@@ -5094,7 +5600,7 @@ and many others in the same vein
-->
Improve handling of dead index tuples in GiST indexes (Anastasia Lubennikova)
+ linkend="gist">GiST indexes (Anastasia Lubennikova)
@@ -5110,8 +5616,8 @@ and many others in the same vein
2016-03-30 [acdf2a8b3] Introduce SP-GiST operator class over box.
-->
- Add an SP-GiST operator class for
- type box (Alexander Lebedev)
+ Add an SP-GiST operator class for
+ type box (Alexander Lebedev)
@@ -5137,10 +5643,10 @@ and many others in the same vein
- The new approach makes better use of the CPU cache
+ The new approach makes better use of the CPU cache
for typical cache sizes and data volumes. Where necessary,
the behavior can be adjusted via the new configuration parameter
- .
+ replacement_sort_tuples.
@@ -5162,17 +5668,17 @@ and many others in the same vein
2016-02-17 [f1f5ec1ef] Reuse abbreviated keys in ordered [set] aggregates.
-->
- Speed up sorting of uuid, bytea, and
- char(n) fields by using abbreviated keys
+ Speed up sorting of uuid, bytea, and
+ char(n) fields by using abbreviated keys
(Peter Geoghegan)
Support for abbreviated keys has also been
added to the non-default operator classes text_pattern_ops,
- varchar_pattern_ops, and
- bpchar_pattern_ops. Processing of ordered-set
+ linkend="indexes-opclass">text_pattern_ops,
+ varchar_pattern_ops, and
+ bpchar_pattern_ops. Processing of ordered-set
aggregates can also now exploit abbreviated keys.
@@ -5182,8 +5688,8 @@ and many others in the same vein
2015-12-16 [b648b7034] Speed up CREATE INDEX CONCURRENTLY's TID sort.
-->
- Speed up CREATE INDEX CONCURRENTLY by treating
- TIDs as 64-bit integers during sorting (Peter
+ Speed up CREATE INDEX CONCURRENTLY by treating
+ TIDs as 64-bit integers during sorting (Peter
Geoghegan)
@@ -5203,7 +5709,7 @@ and many others in the same vein
2015-09-03 [4aec49899] Assorted code review for recent ProcArrayLock patch.
-->
- Reduce contention for the ProcArrayLock (Amit Kapila,
+ Reduce contention for the ProcArrayLock (Amit Kapila,
Robert Haas)
@@ -5234,7 +5740,7 @@ and many others in the same vein
-->
Use atomic operations, rather than a spinlock, to protect an
- LWLock's wait queue (Andres Freund)
+ LWLock's wait queue (Andres Freund)
@@ -5244,7 +5750,7 @@ and many others in the same vein
-->
Partition the shared hash table freelist to reduce contention on
- multi-CPU-socket servers (Aleksander Alekseev)
+ multi-CPU-socket servers (Aleksander Alekseev)
@@ -5280,14 +5786,14 @@ and many others in the same vein
2016-04-04 [391159e03] Partially revert commit 3d3bf62f30200500637b24fdb7b992a9
-->
- Improve ANALYZE's estimates for columns with many nulls
+ Improve ANALYZE's estimates for columns with many nulls
(Tomas Vondra, Alex Shulgin)
- Previously ANALYZE tended to underestimate the number
- of non-NULL distinct values in a column with many
- NULLs, and was also inaccurate in computing the
+ Previously ANALYZE tended to underestimate the number
+ of non-NULL distinct values in a column with many
+ NULLs, and was also inaccurate in computing the
most-common values.
@@ -5314,13 +5820,13 @@ and many others in the same vein
- If a table t has a foreign key restriction, say
- (a,b) REFERENCES r (x,y), then a WHERE
- condition such as t.a = r.x AND t.b = r.y cannot
- select more than one r row per t row.
- The planner formerly considered these AND conditions
+ If a table t has a foreign key restriction, say
+ (a,b) REFERENCES r (x,y), then a WHERE
+ condition such as t.a = r.x AND t.b = r.y cannot
+ select more than one r row per t row.
+ The planner formerly considered these AND conditions
to be independent and would often drastically misestimate
- selectivity as a result. Now it compares the WHERE
+ selectivity as a result. Now it compares the WHERE
conditions to applicable foreign key constraints and produces
better estimates.
@@ -5331,7 +5837,7 @@ and many others in the same vein
- <command>VACUUM</>
+ <command>VACUUM</command>
@@ -5361,7 +5867,7 @@ and many others in the same vein
If necessary, vacuum can be forced to process all-frozen
- pages using the new DISABLE_PAGE_SKIPPING option.
+ pages using the new DISABLE_PAGE_SKIPPING option.
Normally this should never be needed, but it might help in
recovering from visibility-map corruption.
@@ -5372,7 +5878,7 @@ and many others in the same vein
2015-12-30 [e84290823] Avoid useless truncation attempts during VACUUM.
-->
- Avoid useless heap-truncation attempts during VACUUM
+ Avoid useless heap-truncation attempts during VACUUM
(Jeff Janes, Tom Lane)
@@ -5401,19 +5907,19 @@ and many others in the same vein
2016-08-07 [9ee1cf04a] Fix TOAST access failure in RETURNING queries.
-->
- Allow old MVCC snapshots to be invalidated after a
+ Allow old MVCC snapshots to be invalidated after a
configurable timeout (Kevin Grittner)
Normally, deleted tuples cannot be physically removed by
- vacuuming until the last transaction that could see
+ vacuuming until the last transaction that could see
them is gone. A transaction that stays open for a long
time can thus cause considerable table bloat because
space cannot be recycled. This feature allows setting
a time-based limit, via the new configuration parameter
, on how long an
- MVCC snapshot is guaranteed to be valid. After that,
+ MVCC snapshot is guaranteed to be valid. After that,
dead tuples are candidates for removal. A transaction using an
outdated snapshot will get an error if it attempts to read a page
that potentially could have contained such data.
@@ -5425,12 +5931,12 @@ and many others in the same vein
2016-02-11 [d4c3a156c] Remove GROUP BY columns that are functionally dependent
-->
- Ignore GROUP BY columns that are
+ Ignore GROUP BY columns that are
functionally dependent on other columns (David Rowley)
- If a GROUP BY clause includes all columns of a
+ If a GROUP BY clause includes all columns of a
non-deferred primary key, as well as other columns of the same
table, those other columns are redundant and can be dropped
from the grouping. This saves computation in many common cases.
@@ -5443,17 +5949,17 @@ and many others in the same vein
-->
Allow use of an index-only
- scan on a partial index when the index's WHERE
+ scan on a partial index when the index's WHERE
clause references columns that are not indexed (Tomas Vondra,
Kyotaro Horiguchi)
For example, an index defined by CREATE INDEX tidx_partial
- ON t(b) WHERE a > 0 can now be used for an index-only scan by
- a query that specifies WHERE a > 0 and does not
- otherwise use a. Previously this was disallowed
- because a is not listed as an index column.
+ ON t(b) WHERE a > 0 can now be used for an index-only scan by
+ a query that specifies WHERE a > 0 and does not
+ otherwise use a. Previously this was disallowed
+ because a is not listed as an index column.
@@ -5493,7 +5999,7 @@ and many others in the same vein
- PostgreSQL writes data to the kernel's disk cache,
+ PostgreSQL writes data to the kernel's disk cache,
from where it will be flushed to physical storage in due time.
Many operating systems are not smart about managing this and allow
large amounts of dirty data to accumulate before deciding to flush
@@ -5504,11 +6010,11 @@ and many others in the same vein
- On Linux, sync_file_range() is used for this purpose,
+ On Linux, sync_file_range() is used for this purpose,
and the feature is on by default on Linux because that function has
few downsides. This flushing capability is also available on other
- platforms if they have msync()
- or posix_fadvise(), but those interfaces have some
+ platforms if they have msync()
+ or posix_fadvise(), but those interfaces have some
undesirable side-effects so the feature is disabled by default on
non-Linux platforms.
@@ -5533,7 +6039,7 @@ and many others in the same vein
- For example, SELECT AVG(x), VARIANCE(x) FROM tab can use
+ For example, SELECT AVG(x), VARIANCE(x) FROM tab can use
a single per-row computation for both aggregates.
@@ -5544,7 +6050,7 @@ and many others in the same vein
-->
Speed up visibility tests for recently-created tuples by checking
- the current transaction's snapshot, not pg_clog, to
+ the current transaction's snapshot, not pg_clog, to
decide if the source transaction should be considered committed
(Jeff Janes, Tom Lane)
@@ -5570,9 +6076,9 @@ and many others in the same vein
- Two-phase commit information is now written only to WAL
- during PREPARE TRANSACTION, and will be read back from
- WAL during COMMIT PREPARED if that happens
+ Two-phase commit information is now written only to WAL
+ during PREPARE TRANSACTION, and will be read back from
+ WAL during COMMIT PREPARED if that happens
soon thereafter. A separate state file is created only if the
pending transaction does not get committed or aborted by the time
of the next checkpoint.
@@ -5603,8 +6109,8 @@ and many others in the same vein
2016-02-06 [aa2387e2f] Improve speed of timestamp/time/date output functions.
-->
- Improve speed of the output functions for timestamp,
- time, and date data types (David Rowley,
+ Improve speed of the output functions for timestamp,
+ time, and date data types (David Rowley,
Andres Freund)
@@ -5615,7 +6121,7 @@ and many others in the same vein
-->
Avoid some unnecessary cancellations of hot-standby queries
- during replay of actions that take AccessExclusive
+ during replay of actions that take AccessExclusive
locks (Jeff Janes)
@@ -5649,8 +6155,8 @@ and many others in the same vein
2015-07-05 [6c82d8d1f] Further reduce overhead for passing plpgsql variables to
-->
- Speed up expression evaluation in PL/pgSQL by
- keeping ParamListInfo entries for simple variables
+ Speed up expression evaluation in PL/pgSQL by
+ keeping ParamListInfo entries for simple variables
valid at all times (Tom Lane)
@@ -5660,7 +6166,7 @@ and many others in the same vein
2015-07-06 [4f33621f3] Don't set SO_SNDBUF on recent Windows versions that have
-->
- Avoid reducing the SO_SNDBUF setting below its default
+ Avoid reducing the SO_SNDBUF setting below its default
on recent Windows versions (Chen Huajun)
@@ -5696,8 +6202,8 @@ and many others in the same vein
-->
Add pg_stat_progress_vacuum
- system view to provide progress reporting for VACUUM
+ linkend="pg-stat-progress-vacuum-view">pg_stat_progress_vacuum
+ system view to provide progress reporting for VACUUM
operations (Amit Langote, Robert Haas, Vinayak Pokale, Rahila Syed)
@@ -5708,11 +6214,11 @@ and many others in the same vein
-->
Add pg_control_system(),
- pg_control_checkpoint(),
- pg_control_recovery(), and
- pg_control_init() functions to expose fields of
- pg_control to SQL (Joe Conway, Michael
+ linkend="functions-controldata">pg_control_system(),
+ pg_control_checkpoint(),
+ pg_control_recovery(), and
+ pg_control_init() functions to expose fields of
+ pg_control to SQL (Joe Conway, Michael
Paquier)
@@ -5722,15 +6228,15 @@ and many others in the same vein
2016-02-17 [a5c43b886] Add new system view, pg_config
-->
- Add pg_config
+ Add pg_config
system view (Joe Conway)
This view exposes the same information available from
- the pg_config command-line utility,
+ the pg_config command-line utility,
namely assorted compile-time configuration information for
- PostgreSQL.
+ PostgreSQL.
@@ -5739,8 +6245,8 @@ and many others in the same vein
2015-08-10 [3f811c2d6] Add confirmed_flush column to pg_replication_slots.
-->
- Add a confirmed_flush_lsn column to the pg_replication_slots
+ Add a confirmed_flush_lsn column to the pg_replication_slots
system view (Marko Tiikkaja)
@@ -5753,9 +6259,9 @@ and many others in the same vein
-->
Add pg_stat_wal_receiver
+ linkend="pg-stat-wal-receiver-view">pg_stat_wal_receiver
system view to provide information about the state of a hot-standby
- server's WAL receiver process (Michael Paquier)
+ server's WAL receiver process (Michael Paquier)
@@ -5765,7 +6271,7 @@ and many others in the same vein
-->
Add pg_blocking_pids()
+ linkend="functions-info-session-table">pg_blocking_pids()
function to reliably identify which sessions block which others
(Tom Lane)
@@ -5774,7 +6280,7 @@ and many others in the same vein
This function returns an array of the process IDs of any
sessions that are blocking the session with the given process ID.
Historically users have obtained such information using a self-join
- on the pg_locks view. However, it is unreasonably
+ on the pg_locks view. However, it is unreasonably
tedious to do it that way with any modicum of correctness, and
the addition of parallel queries has made the old approach entirely
impractical, since locks might be held or awaited by child worker
@@ -5788,7 +6294,7 @@ and many others in the same vein
-->
Add function pg_current_xlog_flush_location()
+ linkend="functions-admin-backup-table">pg_current_xlog_flush_location()
to expose the current transaction log flush location (Tomas Vondra)
@@ -5799,8 +6305,8 @@ and many others in the same vein
-->
Add function pg_notification_queue_usage()
- to report how full the NOTIFY queue is (Brendan Jurd)
+ linkend="functions-info-session-table">pg_notification_queue_usage()
+ to report how full the NOTIFY queue is (Brendan Jurd)
@@ -5816,7 +6322,7 @@ and many others in the same vein
The memory usage dump that is output to the postmaster log during an
out-of-memory failure now summarizes statistics when there are a
large number of memory contexts, rather than possibly generating
- a very large report. There is also a grand total
+ a very large report. There is also a grand total
summary line now.
@@ -5826,7 +6332,7 @@ and many others in the same vein
- <acronym>Authentication</>
+ <acronym>Authentication</acronym>
@@ -5835,15 +6341,15 @@ and many others in the same vein
2016-04-08 [34c33a1f0] Add BSD authentication method.
-->
- Add a BSD authentication
+ Add a BSD authentication
method to allow use of
- the BSD Authentication service for
- PostgreSQL client authentication (Marisa Emerson)
+ the BSD Authentication service for
+ PostgreSQL client authentication (Marisa Emerson)
BSD Authentication is currently only available on OpenBSD.
+ class="osname">OpenBSD.
@@ -5852,9 +6358,9 @@ and many others in the same vein
2016-04-08 [2f1d2b7a7] Set PAM_RHOST item for PAM authentication
-->
- When using PAM
+ When using PAM
authentication, provide the client IP address or host name
- to PAM modules via the PAM_RHOST item
+ to PAM modules via the PAM_RHOST item
(Grzegorz Sampolski)
@@ -5870,7 +6376,7 @@ and many others in the same vein
All ordinarily-reachable password authentication failure cases
- should now provide specific DETAIL fields in the log.
+ should now provide specific DETAIL fields in the log.
@@ -5879,7 +6385,7 @@ and many others in the same vein
2015-09-06 [643beffe8] Support RADIUS passwords up to 128 characters
-->
- Support RADIUS passwords
+ Support RADIUS passwords
up to 128 characters long (Marko Tiikkaja)
@@ -5889,11 +6395,11 @@ and many others in the same vein
2016-04-08 [35e2e357c] Add authentication parameters compat_realm and upn_usena
-->
- Add new SSPI
+ Add new SSPI
authentication parameters
- compat_realm and upn_username to control
- whether NetBIOS or Kerberos
- realm names and user names are used during SSPI
+ compat_realm and upn_username to control
+ whether NetBIOS or Kerberos
+ realm names and user names are used during SSPI
authentication (Christian Ullrich)
@@ -5939,7 +6445,7 @@ and many others in the same vein
2015-09-08 [1aba62ec6] Allow per-tablespace effective_io_concurrency
-->
- Allow effective_io_concurrency to be set per-tablespace
+ Allow effective_io_concurrency to be set per-tablespace
to support cases where different tablespaces have different I/O
characteristics (Julien Rouhaud)
@@ -5951,7 +6457,7 @@ and many others in the same vein
2015-09-07 [b1e1862a1] Coordinate log_line_prefix options 'm' and 'n' to share
-->
- Add option %n to
+ Add option %n to
print the current time in Unix epoch form, with milliseconds (Tomas
Vondra, Jeff Davis)
@@ -5966,7 +6472,7 @@ and many others in the same vein
Add and configuration parameters
to provide more control over the message format when logging to
- syslog (Peter Eisentraut)
+ syslog (Peter Eisentraut)
@@ -5975,16 +6481,16 @@ and many others in the same vein
2016-03-18 [b555ed810] Merge wal_level "archive" and "hot_standby" into new nam
-->
- Merge the archive and hot_standby values
+ Merge the archive and hot_standby values
of the configuration parameter
- into a single new value replica (Peter Eisentraut)
+ into a single new value replica (Peter Eisentraut)
Making a distinction between these settings is no longer useful,
and merging them is a step towards a planned future simplification
of replication setup. The old names are still accepted but are
- converted to replica internally.
+ converted to replica internally.
@@ -5993,15 +6499,15 @@ and many others in the same vein
2016-02-02 [7d17e683f] Add support for systemd service notifications
-->
- Add configure option
- This allows the use of systemd service units of
- type notify, which greatly simplifies the management
- of PostgreSQL under systemd.
+ This allows the use of systemd service units of
+ type notify, which greatly simplifies the management
+ of PostgreSQL under systemd.
@@ -6010,17 +6516,17 @@ and many others in the same vein
2016-03-19 [9a83564c5] Allow SSL server key file to have group read access if o
-->
- Allow the server's SSL key file to have group read
- access if it is owned by root (Christoph Berg)
+ Allow the server's SSL key file to have group read
+ access if it is owned by root (Christoph Berg)
Formerly, we insisted the key file be owned by the
- user running the PostgreSQL server, but
+ user running the PostgreSQL server, but
that is inconvenient on some systems (such as Debian) that are configured to manage
+ class="osname">Debian) that are configured to manage
certificates centrally. Therefore, allow the case where the key
- file is owned by root and has group read access.
+ file is owned by root and has group read access.
It is up to the operating system administrator to ensure that
the group does not include any untrusted users.
@@ -6085,8 +6591,8 @@ XXX this is pending backpatch, may need to remove
2016-04-26 [c6ff84b06] Emit invalidations to standby for transactions without x
-->
- Ensure that invalidation messages are recorded in WAL
- even when issued by a transaction that has no XID
+ Ensure that invalidation messages are recorded in WAL
+ even when issued by a transaction that has no XID
assigned (Andres Freund)
@@ -6102,7 +6608,7 @@ XXX this is pending backpatch, may need to remove
2016-04-28 [e2c79e14d] Prevent multiple cleanup process for pending list in GIN
-->
- Prevent multiple processes from trying to clean a GIN
+ Prevent multiple processes from trying to clean a GIN
index's pending list concurrently (Teodor Sigaev, Jeff Janes)
@@ -6147,13 +6653,13 @@ XXX this is pending backpatch, may need to remove
2016-03-29 [314cbfc5d] Add new replication mode synchronous_commit = 'remote_ap
-->
- Add new setting remote_apply for configuration
+ Add new setting remote_apply for configuration
parameter (Thomas Munro)
In this mode, the master waits for the transaction to be
- applied on the standby server, not just written
+ applied on the standby server, not just written
to disk. That means that you can count on a transaction started
on the standby to see all commits previously acknowledged by
the master.
@@ -6168,14 +6674,14 @@ XXX this is pending backpatch, may need to remove
Add a feature to the replication
protocol, and a corresponding option to pg_create_physical_replication_slot(),
- to allow reserving WAL immediately when creating a
+ linkend="functions-replication-table">pg_create_physical_replication_slot(),
+ to allow reserving WAL immediately when creating a
replication slot (Gurjeet Singh, Michael Paquier)
This allows the creation of a replication slot to guarantee
- that all the WAL needed for a base backup will be
+ that all the WAL needed for a base backup will be
available.
@@ -6186,13 +6692,13 @@ XXX this is pending backpatch, may need to remove
-->
Add a option to
- pg_basebackup
+ pg_basebackup
(Peter Eisentraut)
- This lets pg_basebackup use a replication
- slot defined for WAL streaming. After the base
+ This lets pg_basebackup use a replication
+ slot defined for WAL streaming. After the base
backup completes, selecting the same slot for regular streaming
replication allows seamless startup of the new standby server.
@@ -6205,8 +6711,8 @@ XXX this is pending backpatch, may need to remove
-->
Extend pg_start_backup()
- and pg_stop_backup() to support non-exclusive backups
+ linkend="functions-admin-backup-table">pg_start_backup()
+ and pg_stop_backup() to support non-exclusive backups
(Magnus Hagander)
@@ -6226,14 +6732,14 @@ XXX this is pending backpatch, may need to remove
-->
Allow functions that return sets of tuples to return simple
- NULLs (Andrew Gierth, Tom Lane)
+ NULLs (Andrew Gierth, Tom Lane)
- In the context of SELECT FROM function(...), a function
+ In the context of SELECT FROM function(...), a function
that returned a set of composite values was previously not allowed
- to return a plain NULL value as part of the set.
- Now that is allowed and interpreted as a row of NULLs.
+ to return a plain NULL value as part of the set.
+ Now that is allowed and interpreted as a row of NULLs.
This avoids corner-case errors with, for example, unnesting an
array of composite values.
@@ -6245,14 +6751,14 @@ XXX this is pending backpatch, may need to remove
-->
Fully support array subscripts and field selections in the
- target column list of an INSERT with multiple
- VALUES rows (Tom Lane)
+ target column list of an INSERT with multiple
+ VALUES rows (Tom Lane)
Previously, such cases failed if the same target column was
mentioned more than once, e.g., INSERT INTO tab (x[1],
- x[2]) VALUES (...).
+ x[2]) VALUES (...).
@@ -6262,16 +6768,16 @@ XXX this is pending backpatch, may need to remove
2016-03-25 [d543170f2] Don't split up SRFs when choosing to postpone SELECT out
-->
- When appropriate, postpone evaluation of SELECT
- output expressions until after an ORDER BY sort
+ When appropriate, postpone evaluation of SELECT
+ output expressions until after an ORDER BY sort
(Konstantin Knizhnik)
This change ensures that volatile or expensive functions in the
output list are executed in the order suggested by ORDER
- BY, and that they are not evaluated more times than required
- when there is a LIMIT clause. Previously, these
+ BY, and that they are not evaluated more times than required
+ when there is a LIMIT clause. Previously, these
properties held if the ordering was performed by an index scan or
pre-merge-join sort, but not if it was performed by a top-level
sort.
@@ -6289,9 +6795,9 @@ XXX this is pending backpatch, may need to remove
- This change allows command tags, e.g. SELECT, to
+ This change allows command tags, e.g. SELECT, to
correctly report tuple counts larger than 4 billion. This also
- applies to PL/pgSQL's GET DIAGNOSTICS ... ROW_COUNT
+ applies to PL/pgSQL's GET DIAGNOSTICS ... ROW_COUNT
command.
@@ -6302,17 +6808,17 @@ XXX this is pending backpatch, may need to remove
-->
Avoid doing encoding conversions by converting through the
- MULE_INTERNAL encoding (Tom Lane)
+ MULE_INTERNAL encoding (Tom Lane)
Previously, many conversions for Cyrillic and Central
European single-byte encodings were done by converting to a
- related MULE_INTERNAL coding scheme and then to the
+ related MULE_INTERNAL coding scheme and then to the
destination encoding. Aside from being inefficient, this meant
that when the conversion encountered an untranslatable character,
the error message would confusingly complain about failure to
- convert to or from MULE_INTERNAL, rather than the
+ convert to or from MULE_INTERNAL, rather than the
user-visible encoding.
@@ -6331,7 +6837,7 @@ XXX this is pending backpatch, may need to remove
Previously, the foreign join pushdown infrastructure left the
question of security entirely up to individual foreign data
- wrappers, but that made it too easy for an FDW to
+ wrappers, but that made it too easy for an FDW to
inadvertently create subtle security holes. So, make it the core
code's job to determine which role ID will access each table,
and do not attempt join pushdown unless the role is the same for
@@ -6353,13 +6859,13 @@ XXX this is pending backpatch, may need to remove
2015-11-27 [92e38182d] COPY (INSERT/UPDATE/DELETE .. RETURNING ..)
-->
- Allow COPY to copy the output of an
- INSERT/UPDATE/DELETE
- ... RETURNING query (Marko Tiikkaja)
+ Allow COPY to copy the output of an
+ INSERT/UPDATE/DELETE
+ ... RETURNING query (Marko Tiikkaja)
- Previously, an intermediate CTE had to be written to
+ Previously, an intermediate CTE had to be written to
get this result.
@@ -6369,16 +6875,16 @@ XXX this is pending backpatch, may need to remove
2016-04-05 [f2fcad27d] Support ALTER THING .. DEPENDS ON EXTENSION
-->
- Introduce ALTER object DEPENDS ON
+ Introduce ALTER object DEPENDS ON
EXTENSION (Abhijit Menon-Sen)
This command allows a database object to be marked as depending
on an extension, so that it will be dropped automatically if
- the extension is dropped (without needing CASCADE).
+ the extension is dropped (without needing CASCADE).
However, the object is not part of the extension, and thus will
- be dumped separately by pg_dump.
+ be dumped separately by pg_dump.
@@ -6387,7 +6893,7 @@ XXX this is pending backpatch, may need to remove
2015-11-19 [bc4996e61] Make ALTER .. SET SCHEMA do nothing, instead of throwing
-->
- Make ALTER object SET SCHEMA do nothing
+ Make ALTER object SET SCHEMA do nothing
when the object is already in the requested schema, rather than
throwing an error as it historically has for most object types
(Marti Raudsepp)
@@ -6411,8 +6917,8 @@ XXX this is pending backpatch, may need to remove
2015-07-29 [2cd40adb8] Add IF NOT EXISTS processing to ALTER TABLE ADD COLUMN
-->
- Add an
@@ -6422,7 +6928,7 @@ XXX this is pending backpatch, may need to remove
2016-03-10 [fcb4bfddb] Reduce lock level for altering fillfactor
-->
- Reduce the lock strength needed by ALTER TABLE
+ Reduce the lock strength needed by ALTER TABLE
when setting fillfactor and autovacuum-related relation options
(Fabrízio de Royes Mello, Simon Riggs)
@@ -6434,7 +6940,7 @@ XXX this is pending backpatch, may need to remove
-->
Introduce CREATE
- ACCESS METHOD to allow extensions to create index access
+ ACCESS METHOD to allow extensions to create index access
methods (Alexander Korotkov, Petr Jelínek)
@@ -6444,7 +6950,7 @@ XXX this is pending backpatch, may need to remove
2015-10-03 [b67aaf21e] Add CASCADE support for CREATE EXTENSION.
-->
- Add a CASCADE option to CREATE
+ Add a CASCADE option to CREATE
EXTENSION to automatically create any extensions the
requested one depends on (Petr Jelínek)
@@ -6455,7 +6961,7 @@ XXX this is pending backpatch, may need to remove
2015-10-05 [b943f502b] Have CREATE TABLE LIKE add OID column if any LIKEd table
-->
- Make CREATE TABLE ... LIKE include an OID
+ Make CREATE TABLE ... LIKE include an OID
column if any source table has one (Bruce Momjian)
@@ -6465,14 +6971,14 @@ XXX this is pending backpatch, may need to remove
2015-12-16 [f27a6b15e] Mark CHECK constraints declared NOT VALID valid if creat
-->
- If a CHECK constraint is declared NOT VALID
+ If a CHECK constraint is declared NOT VALID
in a table creation command, automatically mark it as valid
(Amit Langote, Amul Sul)
This is safe because the table has no existing rows. This matches
- the longstanding behavior of FOREIGN KEY constraints.
+ the longstanding behavior of FOREIGN KEY constraints.
@@ -6481,16 +6987,16 @@ XXX this is pending backpatch, may need to remove
2016-03-25 [c94959d41] Fix DROP OPERATOR to reset oprcom/oprnegate links to the
-->
- Fix DROP OPERATOR to clear
- pg_operator.oprcom and
- pg_operator.oprnegate links to
+ Fix DROP OPERATOR to clear
+ pg_operator.oprcom and
+ pg_operator.oprnegate links to
the dropped operator (Roma Sokolov)
Formerly such links were left as-is, which could pose a problem
in the somewhat unlikely event that the dropped operator's
- OID was reused for another operator.
+ OID was reused for another operator.
@@ -6499,13 +7005,13 @@ XXX this is pending backpatch, may need to remove
2016-07-11 [4d042999f] Print a given subplan only once in EXPLAIN.
-->
- Do not show the same subplan twice in EXPLAIN output
+ Do not show the same subplan twice in EXPLAIN output
(Tom Lane)
In certain cases, typically involving SubPlan nodes in index
- conditions, EXPLAIN would print data for the same
+ conditions, EXPLAIN would print data for the same
subplan twice.
@@ -6516,7 +7022,7 @@ XXX this is pending backpatch, may need to remove
-->
Disallow creation of indexes on system columns, except for
- OID columns (David Rowley)
+ OID columns (David Rowley)
@@ -6550,8 +7056,8 @@ XXX this is pending backpatch, may need to remove
checks that would throw an error if they were called by a
non-superuser. This forced the use of superuser roles for
some relatively pedestrian tasks. The hard-wired error checks
- are now gone in favor of making initdb revoke the
- default public EXECUTE privilege on these functions.
+ are now gone in favor of making initdb revoke the
+ default public EXECUTE privilege on these functions.
This allows installations to choose to grant usage of such
functions to trusted roles that do not need all superuser
privileges.
@@ -6569,7 +7075,7 @@ XXX this is pending backpatch, may need to remove
- Currently the only such role is pg_signal_backend,
+ Currently the only such role is pg_signal_backend,
but more are expected to be added in future.
@@ -6591,19 +7097,19 @@ XXX this is pending backpatch, may need to remove
2016-06-27 [6734a1cac] Change predecence of phrase operator.
-->
- Improve full-text search to support
+ Improve full-text search to support
searching for phrases, that is, lexemes appearing adjacent to each
other in a specific order, or with a specified distance between
them (Teodor Sigaev, Oleg Bartunov, Dmitry Ivanov)
- A phrase-search query can be specified in tsquery
- input using the new operators <-> and
- <N>. The former means
+ A phrase-search query can be specified in tsquery
+ input using the new operators <-> and
+ <N>. The former means
that the lexemes before and after it must appear adjacent to
each other in that order. The latter means they must be exactly
- N lexemes apart.
+ N lexemes apart.
@@ -6613,7 +7119,7 @@ XXX this is pending backpatch, may need to remove
-->
Allow omitting one or both boundaries in an array slice specifier,
- e.g. array_col[3:] (Yury Zhuravlev)
+ e.g. array_col[3:] (Yury Zhuravlev)
@@ -6634,19 +7140,19 @@ XXX this is pending backpatch, may need to remove
This change prevents unexpected out-of-range errors for
- timestamp with time zone values very close to the
- implementation limits. Previously, the same value might
- be accepted or not depending on the timezone setting,
+ timestamp with time zone values very close to the
+ implementation limits. Previously, the same value might
+ be accepted or not depending on the timezone setting,
meaning that a dump and reload could fail on a value that had been
accepted when presented. Now the limits are enforced according
- to the equivalent UTC time, not local time, so as to
- be independent of timezone.
+ to the equivalent UTC time, not local time, so as to
+ be independent of timezone.
- Also, PostgreSQL is now more careful to detect
+ Also, PostgreSQL is now more careful to detect
overflow in operations that compute new date or timestamp values,
- such as date + integer.
+ such as date+integer.
@@ -6655,14 +7161,14 @@ XXX this is pending backpatch, may need to remove
2016-03-30 [50861cd68] Improve portability of I/O behavior for the geometric ty
-->
- For geometric data types, make sure infinity and
- NaN component values are treated consistently during
+ For geometric data types, make sure infinity and
+ NaN component values are treated consistently during
input and output (Tom Lane)
Such values will now always print the same as they would in
- a simple float8 column, and be accepted the same way
+ a simple float8 column, and be accepted the same way
on input. Previously the behavior was platform-dependent.
@@ -6675,8 +7181,8 @@ XXX this is pending backpatch, may need to remove
-->
Upgrade
- the ispell
- dictionary type to handle modern Hunspell files and
+ the ispell
+ dictionary type to handle modern Hunspell files and
support more languages (Artur Zakirov)
@@ -6687,7 +7193,7 @@ XXX this is pending backpatch, may need to remove
-->
Implement look-behind constraints
- in regular expressions
+ in regular expressions
(Tom Lane)
@@ -6706,12 +7212,12 @@ XXX this is pending backpatch, may need to remove
-->
In regular expressions, if an apparent three-digit octal escape
- \nnn would exceed 377 (255 decimal),
+ \nnn would exceed 377 (255 decimal),
assume it is a two-digit octal escape instead (Tom Lane)
- This makes the behavior match current Tcl releases.
+ This makes the behavior match current Tcl releases.
@@ -6720,8 +7226,8 @@ XXX this is pending backpatch, may need to remove
2015-11-07 [c5e86ea93] Add "xid <> xid" and "xid <> int4" operators.
-->
- Add transaction ID operators xid <>
- xid and xid <> int4,
+ Add transaction ID operators xid<>
+ xid and xid<>int4,
for consistency with the corresponding equality operators
(Michael Paquier)
@@ -6742,9 +7248,9 @@ XXX this is pending backpatch, may need to remove
-->
Add jsonb_insert()
- function to insert a new element into a jsonb array,
- or a not-previously-existing key into a jsonb object
+ linkend="functions-json-processing-table">jsonb_insert()
+ function to insert a new element into a jsonb array,
+ or a not-previously-existing key into a jsonb object
(Dmitry Dolgov)
@@ -6755,9 +7261,9 @@ XXX this is pending backpatch, may need to remove
2016-05-05 [18a02ad2a] Fix corner-case loss of precision in numeric pow() calcu
-->
- Improve the accuracy of the ln(), log(),
- exp(), and pow() functions for type
- numeric (Dean Rasheed)
+ Improve the accuracy of the ln(), log(),
+ exp(), and pow() functions for type
+ numeric (Dean Rasheed)
@@ -6767,8 +7273,8 @@ XXX this is pending backpatch, may need to remove
-->
Add a scale(numeric)
- function to extract the display scale of a numeric value
+ linkend="functions-math-func-table">scale(numeric)
+ function to extract the display scale of a numeric value
(Marko Tiikkaja)
@@ -6783,8 +7289,8 @@ XXX this is pending backpatch, may need to remove
For example, sind()
- measures its argument in degrees, whereas sin()
+ linkend="functions-math-trig-table">sind()
+ measures its argument in degrees, whereas sin()
measures in radians. These functions go to some lengths to
deliver exact results for values where an exact result can be
expected, for instance sind(30) = 0.5.
@@ -6796,15 +7302,15 @@ XXX this is pending backpatch, may need to remove
2016-01-22 [fd5200c3d] Improve cross-platform consistency of Inf/NaN handling i
-->
- Ensure that trigonometric functions handle infinity
- and NaN inputs per the POSIX standard
+ Ensure that trigonometric functions handle infinity
+ and NaN inputs per the POSIX standard
(Dean Rasheed)
- The POSIX standard says that these functions should
- return NaN for NaN input, and should throw
- an error for out-of-range inputs including infinity.
+ The POSIX standard says that these functions should
+ return NaN for NaN input, and should throw
+ an error for out-of-range inputs including infinity.
Previously our behavior varied across platforms.
@@ -6815,9 +7321,9 @@ XXX this is pending backpatch, may need to remove
-->
Make to_timestamp(float8)
- convert float infinity to
- timestamp infinity (Vitaly Burovoy)
+ linkend="functions-datetime-table">to_timestamp(float8)
+ convert float infinity to
+ timestamp infinity (Vitaly Burovoy)
@@ -6831,15 +7337,15 @@ XXX this is pending backpatch, may need to remove
2016-05-05 [0b9a23443] Rename tsvector delete() to ts_delete(), and filter() to
-->
- Add new functions for tsvector data (Stas Kelvich)
+ Add new functions for tsvector data (Stas Kelvich)
The new functions are ts_delete(),
- ts_filter(), unnest(),
- tsvector_to_array(), array_to_tsvector(),
- and a variant of setweight() that sets the weight
+ linkend="textsearch-functions-table">ts_delete(),
+ ts_filter(), unnest(),
+ tsvector_to_array(), array_to_tsvector(),
+ and a variant of setweight() that sets the weight
only for specified lexeme(s).
@@ -6849,11 +7355,11 @@ XXX this is pending backpatch, may need to remove
2015-09-17 [9acb9007d] Fix oversight in tsearch type check
-->
- Allow ts_stat()
- and tsvector_update_trigger()
+ Allow ts_stat()
+ and tsvector_update_trigger()
to operate on values that are of types binary-compatible with the
expected argument type, not just exactly that type; for example
- allow citext where text is expected (Teodor
+ allow citext where text is expected (Teodor
Sigaev)
@@ -6864,14 +7370,14 @@ XXX this is pending backpatch, may need to remove
-->
Add variadic functions num_nulls()
- and num_nonnulls() that count the number of their
+ linkend="functions-comparison-func-table">num_nulls()
+ and num_nonnulls() that count the number of their
arguments that are null or non-null (Marko Tiikkaja)
- An example usage is CHECK(num_nonnulls(a,b,c) = 1)
- which asserts that exactly one of a,b,c is not NULL.
+ An example usage is CHECK(num_nonnulls(a,b,c) = 1)
+ which asserts that exactly one of a,b,c is not NULL.
These functions can also be used to count the number of null or
nonnull elements in an array.
@@ -6883,8 +7389,8 @@ XXX this is pending backpatch, may need to remove
-->
Add function parse_ident()
- to split a qualified, possibly quoted SQL identifier
+ linkend="functions-string-other">parse_ident()
+ to split a qualified, possibly quoted SQL identifier
into its parts (Pavel Stehule)
@@ -6895,15 +7401,15 @@ XXX this is pending backpatch, may need to remove
-->
In to_number(),
- interpret a V format code as dividing by 10 to the
- power of the number of digits following V (Bruce
+ linkend="functions-formatting-table">to_number(),
+ interpret a V format code as dividing by 10 to the
+ power of the number of digits following V (Bruce
Momjian)
This makes it operate in an inverse fashion to
- to_char().
+ to_char().
@@ -6913,8 +7419,8 @@ XXX this is pending backpatch, may need to remove
-->
Make the to_reg*()
- functions accept type text not cstring
+ linkend="functions-info-catalog-table">to_reg*()
+ functions accept type text not cstring
(Petr Korobeinikov)
@@ -6930,16 +7436,16 @@ XXX this is pending backpatch, may need to remove
-->
Add pg_size_bytes()
+ linkend="functions-admin-dbsize">pg_size_bytes()
function to convert human-readable size strings to numbers (Pavel
Stehule, Vitaly Burovoy, Dean Rasheed)
This function converts strings like those produced by
- pg_size_pretty() into bytes. An example
+ pg_size_pretty() into bytes. An example
usage is SELECT oid::regclass FROM pg_class WHERE
- pg_total_relation_size(oid) > pg_size_bytes('10 GB').
+ pg_total_relation_size(oid) > pg_size_bytes('10 GB').
@@ -6949,7 +7455,7 @@ XXX this is pending backpatch, may need to remove
-->
In pg_size_pretty(),
+ linkend="functions-admin-dbsize">pg_size_pretty(),
format negative numbers similarly to positive ones (Adrian
Vondendriesch)
@@ -6965,14 +7471,14 @@ XXX this is pending backpatch, may need to remove
2015-07-02 [10fb48d66] Add an optional missing_ok argument to SQL function curr
-->
- Add an optional missing_ok argument to the current_setting()
+ Add an optional missing_ok argument to the current_setting()
function (David Christensen)
This allows avoiding an error for an unrecognized parameter
- name, instead returning a NULL.
+ name, instead returning a NULL.
@@ -6984,16 +7490,16 @@ XXX this is pending backpatch, may need to remove
-->
Change various catalog-inspection functions to return
- NULL for invalid input (Michael Paquier)
+ NULL for invalid input (Michael Paquier)
pg_get_viewdef()
- now returns NULL if given an invalid view OID,
- and several similar functions likewise return NULL for
+ linkend="functions-info-catalog-table">pg_get_viewdef()
+ now returns NULL if given an invalid view OID,
+ and several similar functions likewise return NULL for
bad input. Previously, such cases usually led to cache
- lookup failed errors, which are not meant to occur in
+ lookup failed errors, which are not meant to occur in
user-facing cases.
@@ -7004,13 +7510,13 @@ XXX this is pending backpatch, may need to remove
-->
Fix pg_replication_origin_xact_reset()
+ linkend="pg-replication-origin-xact-reset">pg_replication_origin_xact_reset()
to not have any arguments (Fujii Masao)
The documentation said that it has no arguments, and the C code did
- not expect any arguments, but the entry in pg_proc
+ not expect any arguments, but the entry in pg_proc
mistakenly specified two arguments.
@@ -7030,7 +7536,7 @@ XXX this is pending backpatch, may need to remove
-->
In PL/pgSQL, detect mismatched
- CONTINUE and EXIT statements while
+ CONTINUE and EXIT statements while
compiling a function, rather than at execution time
(Jim Nasby)
@@ -7043,7 +7549,7 @@ XXX this is pending backpatch, may need to remove
2016-07-02 [3a4a33ad4] PL/Python: Report argument parsing errors using exceptio
-->
- Extend PL/Python's error-reporting and
+ Extend PL/Python's error-reporting and
message-reporting functions to allow specifying additional message
fields besides the primary error message (Pavel Stehule)
@@ -7055,7 +7561,7 @@ XXX this is pending backpatch, may need to remove
-->
Allow PL/Python functions to call themselves recursively
- via SPI, and fix the behavior when multiple
+ via SPI, and fix the behavior when multiple
set-returning PL/Python functions are called within one query
(Alexey Grishchenko, Tom Lane)
@@ -7077,14 +7583,14 @@ XXX this is pending backpatch, may need to remove
2016-03-02 [e2609323e] Make PL/Tcl require Tcl 8.4 or later.
-->
- Modernize PL/Tcl to use Tcl's object
- APIs instead of simple strings (Jim Nasby, Karl
+ Modernize PL/Tcl to use Tcl's object
+ APIs instead of simple strings (Jim Nasby, Karl
Lehenbauer)
This can improve performance substantially in some cases.
- Note that PL/Tcl now requires Tcl 8.4 or later.
+ Note that PL/Tcl now requires Tcl 8.4 or later.
@@ -7094,8 +7600,8 @@ XXX this is pending backpatch, may need to remove
2016-03-25 [cd37bb785] Improve PL/Tcl errorCode facility by providing decoded n
-->
- In PL/Tcl, make database-reported errors return
- additional information in Tcl's errorCode global
+ In PL/Tcl, make database-reported errors return
+ additional information in Tcl's errorCode global
variable (Jim Nasby, Tom Lane)
@@ -7110,15 +7616,15 @@ XXX this is pending backpatch, may need to remove
2016-03-02 [c8c7c93de] Fix PL/Tcl's encoding conversion logic.
-->
- Fix PL/Tcl to perform encoding conversion between
- the database encoding and UTF-8, which is what Tcl
+ Fix PL/Tcl to perform encoding conversion between
+ the database encoding and UTF-8, which is what Tcl
expects (Tom Lane)
Previously, strings were passed through without conversion,
- leading to misbehavior with non-ASCII characters when
- the database encoding was not UTF-8.
+ leading to misbehavior with non-ASCII characters when
+ the database encoding was not UTF-8.
@@ -7137,7 +7643,7 @@ XXX this is pending backpatch, may need to remove
-->
Add a nonlocalized version of
- the severity field in
+ the severity field in
error and notice messages (Tom Lane)
@@ -7154,17 +7660,17 @@ XXX this is pending backpatch, may need to remove
This commit is also listed under psql and PL/pgSQL
-->
- Introduce a feature in libpq whereby the
- CONTEXT field of messages can be suppressed, either
+ Introduce a feature in libpq whereby the
+ CONTEXT field of messages can be suppressed, either
always or only for non-error messages (Pavel Stehule)
The default behavior of PQerrorMessage()
- is now to print CONTEXT
+ linkend="libpq-pqerrormessage">PQerrorMessage()
+ is now to print CONTEXT
only for errors. The new function PQsetErrorContextVisibility()
+ linkend="libpq-pqseterrorcontextvisibility">PQsetErrorContextVisibility()
can be used to adjust this.
@@ -7174,14 +7680,14 @@ This commit is also listed under psql and PL/pgSQL
2016-04-03 [e3161b231] Add libpq support for recreating an error message with d
-->
- Add support in libpq for regenerating an error
+ Add support in libpq for regenerating an error
message with a different verbosity level (Alex Shulgin)
This is done with the new function PQresultVerboseErrorMessage().
- This supports psql's new \errverbose
+ linkend="libpq-pqresultverboseerrormessage">PQresultVerboseErrorMessage().
+ This supports psql's new \errverbose
feature, and may be useful for other clients as well.
@@ -7191,13 +7697,13 @@ This commit is also listed under psql and PL/pgSQL
2015-11-27 [40cb21f70] Improve PQhost() to return useful data for default Unix-
-->
- Improve libpq's PQhost() function to return
+ Improve libpq's PQhost() function to return
useful data for default Unix-socket connections (Tom Lane)
- Previously it would return NULL if no explicit host
+ Previously it would return NULL if no explicit host
specification had been given; now it returns the default socket
directory path.
@@ -7208,7 +7714,7 @@ This commit is also listed under psql and PL/pgSQL
2016-02-16 [fc1ae7d2e] Change ecpg lexer to accept comments with line breaks in
-->
- Fix ecpg's lexer to handle line breaks within
+ Fix ecpg's lexer to handle line breaks within
comments starting on preprocessor directive lines (Michael Meskes)
@@ -7227,9 +7733,9 @@ This commit is also listed under psql and PL/pgSQL
2015-09-14 [d02426029] Check existency of table/schema for -t/-n option (pg_dum
-->
- Add a
@@ -7249,7 +7755,7 @@ This commit is also listed under psql and PL/pgSQL
2016-05-06 [e1b120a8c] Only issue LOCK TABLE commands when necessary
-->
- In pg_dump, dump locally-made changes of privilege
+ In pg_dump, dump locally-made changes of privilege
assignments for system objects (Stephen Frost)
@@ -7257,7 +7763,7 @@ This commit is also listed under psql and PL/pgSQL
While it has always been possible for a superuser to change
the privilege assignments for built-in or extension-created
objects, such changes were formerly lost in a dump and reload.
- Now, pg_dump recognizes and dumps such changes.
+ Now, pg_dump recognizes and dumps such changes.
(This works only when dumping from a 9.6 or later server, however.)
@@ -7267,7 +7773,7 @@ This commit is also listed under psql and PL/pgSQL
2016-09-08 [31eb14504] Allow pg_dump to dump non-extension members of an extens
-->
- Allow pg_dump to dump non-extension-owned objects
+ Allow pg_dump to dump non-extension-owned objects
that are within an extension-owned schema
(Martín Marqués)
@@ -7283,7 +7789,7 @@ This commit is also listed under psql and PL/pgSQL
2016-04-06 [3b3fcc4ee] pg_dump: Add table qualifications to some tags
-->
- In pg_dump output, include the table name in object
+ In pg_dump output, include the table name in object
tags for object types that are only uniquely named per-table
(for example, triggers) (Peter Eisentraut)
@@ -7292,7 +7798,7 @@ This commit is also listed under psql and PL/pgSQL
- <xref linkend="APP-PSQL">
+ <xref linkend="app-psql">
@@ -7308,7 +7814,7 @@ this commit is also listed in the compatibility section
The specified operations are carried out in the order in which the
- options are given, and then psql terminates.
+ options are given, and then psql terminates.
@@ -7317,7 +7823,7 @@ this commit is also listed in the compatibility section
2016-04-08 [c09b18f21] Support \crosstabview in psql
-->
- Add a \crosstabview command that prints the results of
+ Add a \crosstabview command that prints the results of
a query in a cross-tabulated display (Daniel Vérité)
@@ -7333,13 +7839,13 @@ this commit is also listed in the compatibility section
2016-04-03 [3cc38ca7d] Add psql \errverbose command to see last server error at
-->
- Add an \errverbose command that shows the last server
+ Add an \errverbose command that shows the last server
error at full verbosity (Alex Shulgin)
This is useful after getting an unexpected error — you
- no longer need to adjust the VERBOSITY variable and
+ no longer need to adjust the VERBOSITY variable and
recreate the failure in order to see error fields that are not
shown by default.
@@ -7351,13 +7857,13 @@ this commit is also listed in the compatibility section
2016-05-06 [9b66aa006] Fix psql's \ev and \sv commands so that they handle view
-->
- Add \ev and \sv commands for editing and
+ Add \ev and \sv commands for editing and
showing view definitions (Petr Korobeinikov)
- These are parallel to the existing \ef and
- \sf commands for functions.
+ These are parallel to the existing \ef and
+ \sf commands for functions.
@@ -7366,7 +7872,7 @@ this commit is also listed in the compatibility section
2016-04-04 [2bbe9112a] Add a \gexec command to psql for evaluation of computed
-->
- Add a \gexec command that executes a query and
+ Add a \gexec command that executes a query and
re-submits the result(s) as new queries (Corey Huinker)
@@ -7376,9 +7882,9 @@ this commit is also listed in the compatibility section
2015-10-05 [2145a7660] psql: allow \pset C in setting the title, matches \C
-->
- Allow \pset C string
+ Allow \pset C string
to set the table title, for consistency with \C
- string (Bruce Momjian)
+ string (Bruce Momjian)
@@ -7387,7 +7893,7 @@ this commit is also listed in the compatibility section
2016-03-11 [69ab7b9d6] psql: Don't automatically use expanded format when there
-->
- In \pset expanded auto mode, do not use expanded
+ In \pset expanded auto mode, do not use expanded
format for query results with only one column (Andreas Karlsson,
Robert Haas)
@@ -7399,16 +7905,16 @@ this commit is also listed in the compatibility section
2016-06-15 [9901d8ac2] Use strftime("%c") to format timestamps in psql's \watch
-->
- Improve the headers output by the \watch command
+ Improve the headers output by the \watch command
(Michael Paquier, Tom Lane)
- Include the \pset title string if one has
+ Include the \pset title string if one has
been set, and shorten the prefabricated part of the
- header to be timestamp (every
- Ns). Also, the timestamp format now
- obeys psql's locale environment.
+ header to be timestamp (every
+ Ns). Also, the timestamp format now
+ obeys psql's locale environment.
@@ -7456,7 +7962,7 @@ this commit is also listed in the compatibility section
2015-07-07 [275f05c99] Add psql PROMPT variable showing the pid of the connecte
-->
- Add a PROMPT option %p to insert the
+ Add a PROMPT option %p to insert the
process ID of the connected backend (Julien Rouhaud)
@@ -7467,13 +7973,13 @@ this commit is also listed in the compatibility section
This commit is also listed under libpq and PL/pgSQL
-->
- Introduce a feature whereby the CONTEXT field of
+ Introduce a feature whereby the CONTEXT field of
messages can be suppressed, either always or only for non-error
messages (Pavel Stehule)
- Printing CONTEXT only for errors is now the default
+ Printing CONTEXT only for errors is now the default
behavior. This can be changed by setting the special variable
SHOW_CONTEXT.
@@ -7484,7 +7990,7 @@ This commit is also listed under libpq and PL/pgSQL
2016-07-11 [a670c24c3] Improve output of psql's \df+ command.
-->
- Make \df+ show function access privileges and
+ Make \df+ show function access privileges and
parallel-safety attributes (Michael Paquier)
@@ -7503,7 +8009,7 @@ This commit is also listed under libpq and PL/pgSQL
2016-03-20 [68ab8e8ba] SQL commands in pgbench scripts are now ended by semicol
-->
- SQL commands in pgbench scripts are now ended by
+ SQL commands in pgbench scripts are now ended by
semicolons, not newlines (Kyotaro Horiguchi, Tom Lane)
@@ -7512,7 +8018,7 @@ This commit is also listed under libpq and PL/pgSQL
Existing custom scripts will need to be modified to add a semicolon
at the end of each line that does not have one already. (Doing so
does not break the script for use with older versions
- of pgbench.)
+ of pgbench.)
@@ -7525,7 +8031,7 @@ This commit is also listed under libpq and PL/pgSQL
-->
Support floating-point arithmetic, as well as some built-in functions, in
+ linkend="pgbench-builtin-functions">built-in functions, in
expressions in backslash commands (Fabien Coelho)
@@ -7535,18 +8041,18 @@ This commit is also listed under libpq and PL/pgSQL
2016-03-29 [ad9566470] pgbench: Remove \setrandom.
-->
- Replace \setrandom with built-in functions (Fabien
+ Replace \setrandom with built-in functions (Fabien
Coelho)
The new built-in functions include random(),
- random_exponential(), and
- random_gaussian(), which perform the same work as
- \setrandom, but are easier to use since they can be
+ linkend="pgbench-functions">random(),
+ random_exponential(), and
+ random_gaussian(), which perform the same work as
+ \setrandom, but are easier to use since they can be
embedded in larger expressions. Since these additions have made
- \setrandom obsolete, remove it.
+ \setrandom obsolete, remove it.
@@ -7561,8 +8067,8 @@ This commit is also listed under libpq and PL/pgSQL
- This is done with the new switch, which works
+ similarly to for custom scripts.
@@ -7577,7 +8083,7 @@ This commit is also listed under libpq and PL/pgSQL
- When multiple scripts are specified, each pgbench
+ When multiple scripts are specified, each pgbench
transaction randomly chooses one to execute. Formerly this was
always done with uniform probability, but now different selection
probabilities can be specified for different scripts.
@@ -7604,7 +8110,7 @@ This commit is also listed under libpq and PL/pgSQL
2015-09-16 [1def9063c] pgbench progress with timestamp
-->
- Add a option to report progress
with Unix epoch timestamps, instead of time since the run started
(Fabien Coelho)
@@ -7615,8 +8121,8 @@ This commit is also listed under libpq and PL/pgSQL
2015-07-03 [ba3deeefb] Lift the limitation that # of clients must be a multiple
-->
- Allow the number of client connections () to not
+ be an exact multiple of the number of threads ()
(Fabien Coelho)
@@ -7626,13 +8132,13 @@ This commit is also listed under libpq and PL/pgSQL
2016-03-09 [accf7616f] pgbench: When -T is used, don't wait for transactions be
-->
- When the option is used, stop promptly at the end
of the specified time (Fabien Coelho)
Previously, specifying a low transaction rate could cause
- pgbench to wait significantly longer than
+ pgbench to wait significantly longer than
specified.
@@ -7653,15 +8159,15 @@ This commit is also listed under libpq and PL/pgSQL
2015-12-17 [66d947b9d] Adjust behavior of single-user -j mode for better initdb
-->
- Improve error reporting during initdb's
+ Improve error reporting during initdb's
post-bootstrap phase (Tom Lane)
Previously, an error here led to reporting the entire input
- file as the failing query; now just the current
+ file as the failing query; now just the current
query is reported. To get the desired behavior, queries in
- initdb's input files must be separated by blank
+ initdb's input files must be separated by blank
lines.
@@ -7672,7 +8178,7 @@ This commit is also listed under libpq and PL/pgSQL
2016-08-30 [d9720e437] Fix initdb misbehavior when user mis-enters superuser pa
-->
- Speed up initdb by using just one
+ Speed up initdb by using just one
standalone-backend session for all the post-bootstrap steps
(Tom Lane)
@@ -7683,7 +8189,7 @@ This commit is also listed under libpq and PL/pgSQL
2015-12-01 [e50cda784] Use pg_rewind when target timeline was switched
-->
- Improve pg_rewind
+ Improve pg_rewind
so that it can work when the target timeline changes (Alexander
Korotkov)
@@ -7709,7 +8215,7 @@ This commit is also listed under libpq and PL/pgSQL
-->
Remove obsolete
- heap_formtuple/heap_modifytuple/heap_deformtuple
+ heap_formtuple/heap_modifytuple/heap_deformtuple
functions (Peter Geoghegan)
@@ -7719,16 +8225,16 @@ This commit is also listed under libpq and PL/pgSQL
2016-08-27 [b9fe6cbc8] Add macros to make AllocSetContextCreate() calls simpler
-->
- Add macros to make AllocSetContextCreate() calls simpler
+ Add macros to make AllocSetContextCreate() calls simpler
and safer (Tom Lane)
Writing out the individual sizing parameters for a memory context
is now deprecated in favor of using one of the new
- macros ALLOCSET_DEFAULT_SIZES,
- ALLOCSET_SMALL_SIZES,
- or ALLOCSET_START_SMALL_SIZES.
+ macros ALLOCSET_DEFAULT_SIZES,
+ ALLOCSET_SMALL_SIZES,
+ or ALLOCSET_START_SMALL_SIZES.
Existing code continues to work, however.
@@ -7738,7 +8244,7 @@ This commit is also listed under libpq and PL/pgSQL
2015-08-05 [de6fd1c89] Rely on inline functions even if that causes warnings in
-->
- Unconditionally use static inline functions in header
+ Unconditionally use static inline functions in header
files (Andres Freund)
@@ -7759,7 +8265,7 @@ This commit is also listed under libpq and PL/pgSQL
2016-05-06 [6bd356c33] Add TAP tests for pg_dump
-->
- Improve TAP testing infrastructure (Michael
+ Improve TAP testing infrastructure (Michael
Paquier, Craig Ringer, Álvaro Herrera, Stephen Frost)
@@ -7774,7 +8280,7 @@ This commit is also listed under libpq and PL/pgSQL
2015-09-11 [aa65de042] When trace_lwlocks is used, identify individual lwlocks
-->
- Make trace_lwlocks identify individual locks by name
+ Make trace_lwlocks identify individual locks by name
(Robert Haas)
@@ -7786,7 +8292,7 @@ This commit is also listed under libpq and PL/pgSQL
2016-01-05 [4f18010af] Convert psql's tab completion for backslash commands to
-->
- Improve psql's tab-completion code infrastructure
+ Improve psql's tab-completion code infrastructure
(Thomas Munro, Michael Paquier)
@@ -7801,7 +8307,7 @@ This commit is also listed under libpq and PL/pgSQL
2016-01-05 [efa318bcf] Make pg_shseclabel available in early backend startup
-->
- Nail the pg_shseclabel system catalog into cache,
+ Nail the pg_shseclabel system catalog into cache,
so that it is available for access during connection authentication
(Adam Brightwell)
@@ -7820,21 +8326,21 @@ This commit is also listed under libpq and PL/pgSQL
-->
Restructure index access
- method API to hide most of it at
- the C level (Alexander Korotkov, Andrew Gierth)
+ method API to hide most of it at
+ the C level (Alexander Korotkov, Andrew Gierth)
- This change modernizes the index AM API to look more
+ This change modernizes the index AM API to look more
like the designs we have adopted for foreign data wrappers and
- tablesample handlers. This simplifies the C code
+ tablesample handlers. This simplifies the C code
and makes it much more practical to define index access methods in
installable extensions. A consequence is that most of the columns
- of the pg_am system catalog have disappeared.
+ of the pg_am system catalog have disappeared.
New inspection
functions have been added to allow SQL queries to determine
index AM properties that used to be discoverable
- from pg_am.
+ from pg_am.
@@ -7844,14 +8350,14 @@ This commit is also listed under libpq and PL/pgSQL
-->
Add pg_init_privs
+ linkend="catalog-pg-init-privs">pg_init_privs
system catalog to hold original privileges
- of initdb-created and extension-created objects
+ of initdb-created and extension-created objects
(Stephen Frost)
- This infrastructure allows pg_dump to dump changes
+ This infrastructure allows pg_dump to dump changes
that an installation may have made in privileges attached to
system objects. Formerly, such changes would be lost in a dump
and reload, but now they are preserved.
@@ -7863,14 +8369,14 @@ This commit is also listed under libpq and PL/pgSQL
2016-02-04 [c1772ad92] Change the way that LWLocks for extensions are allocated
-->
- Change the way that extensions allocate custom LWLocks
+ Change the way that extensions allocate custom LWLocks
(Amit Kapila, Robert Haas)
- The RequestAddinLWLocks() function is removed,
- and replaced by RequestNamedLWLockTranche().
- This allows better identification of custom LWLocks,
+ The RequestAddinLWLocks() function is removed,
+ and replaced by RequestNamedLWLockTranche().
+ This allows better identification of custom LWLocks,
and is less error-prone.
@@ -7894,7 +8400,7 @@ This commit is also listed under libpq and PL/pgSQL
- This change allows FDWs or custom scan providers
+ This change allows FDWs or custom scan providers
to store data in a plan tree in a more convenient format than
was previously possible.
@@ -7911,7 +8417,7 @@ This commit is also listed under libpq and PL/pgSQL
-->
Make the planner deal with post-scan/join query steps by generating
- and comparing Paths, replacing a lot of ad-hoc logic
+ and comparing Paths, replacing a lot of ad-hoc logic
(Tom Lane)
@@ -7961,7 +8467,7 @@ This commit is also listed under libpq and PL/pgSQL
2016-03-24 [c1156411a] Move psql's psqlscan.l into src/fe_utils.
-->
- Separate out psql's flex lexer to
+ Separate out psql's flex lexer to
make it usable by other client programs (Tom Lane, Kyotaro
Horiguchi)
@@ -7970,12 +8476,12 @@ This commit is also listed under libpq and PL/pgSQL
This eliminates code duplication for programs that need to be able
to parse SQL commands well enough to identify command boundaries.
Doing that in full generality is more painful than one could
- wish, and up to now only psql has really gotten
+ wish, and up to now only psql has really gotten
it right among our supported client programs.
- A new source-code subdirectory src/fe_utils/ has
+ A new source-code subdirectory src/fe_utils/ has
been created to hold this and other code that is shared across
our client programs. Formerly such sharing was accomplished by
symbolic linking or copying source files at build time, which
@@ -7988,7 +8494,7 @@ This commit is also listed under libpq and PL/pgSQL
2016-03-21 [98a64d0bd] Introduce WaitEventSet API.
-->
- Introduce WaitEventSet API to allow
+ Introduce WaitEventSet API to allow
efficient waiting for event sets that usually do not change from
one wait to the next (Andres Freund, Amit Kapila)
@@ -7999,16 +8505,16 @@ This commit is also listed under libpq and PL/pgSQL
2016-04-01 [65578341a] Add Generic WAL interface
-->
- Add a generic interface for writing WAL records
+ Add a generic interface for writing WAL records
(Alexander Korotkov, Petr Jelínek, Markus Nullmeier)
- This change allows extensions to write WAL records for
+ This change allows extensions to write WAL records for
changes to pages using a standard layout. The problem of needing to
- replay WAL without access to the extension is solved by
+ replay WAL without access to the extension is solved by
having generic replay code. This allows extensions to implement,
- for example, index access methods and have WAL
+ for example, index access methods and have WAL
support for them.
@@ -8018,13 +8524,13 @@ This commit is also listed under libpq and PL/pgSQL
2016-04-06 [3fe3511d0] Generic Messages for Logical Decoding
-->
- Support generic WAL messages for logical decoding
+ Support generic WAL messages for logical decoding
(Petr Jelínek, Andres Freund)
This feature allows extensions to insert data into the
- WAL stream that can be read by logical-decoding
+ WAL stream that can be read by logical-decoding
plugins, but is not connected to physical data restoration.
@@ -8036,12 +8542,12 @@ This commit is also listed under libpq and PL/pgSQL
-->
Allow SP-GiST operator classes to store an arbitrary
- traversal value while descending the index (Alexander
+ traversal value while descending the index (Alexander
Lebedev, Teodor Sigaev)
- This is somewhat like the reconstructed value, but it
+ This is somewhat like the reconstructed value, but it
could be any arbitrary chunk of data, not necessarily of the same
data type as the indexed column.
@@ -8052,12 +8558,12 @@ This commit is also listed under libpq and PL/pgSQL
2016-04-04 [66229ac00] Introduce a LOG_SERVER_ONLY ereport level, which is neve
-->
- Introduce a LOG_SERVER_ONLY message level for
- ereport() (David Steele)
+ Introduce a LOG_SERVER_ONLY message level for
+ ereport() (David Steele)
- This level acts like LOG except that the message is
+ This level acts like LOG except that the message is
never sent to the client. It is meant for use in auditing and
similar applications.
@@ -8068,14 +8574,14 @@ This commit is also listed under libpq and PL/pgSQL
2016-07-01 [548af97fc] Provide and use a makefile target to build all generated
-->
- Provide a Makefile target to build all generated
+ Provide a Makefile target to build all generated
headers (Michael Paquier, Tom Lane)
- submake-generated-headers can now be invoked to ensure
+ submake-generated-headers can now be invoked to ensure
that generated backend header files are up-to-date. This is
- useful in subdirectories that might be built standalone.
+ useful in subdirectories that might be built standalone.
@@ -8104,8 +8610,8 @@ This commit is also listed under libpq and PL/pgSQL
2016-03-13 [7a8d87483] Rename auto_explain.sample_ratio to sample_rate
-->
- Add configuration parameter auto_explain.sample_rate to
- allow contrib/auto_explain
+ Add configuration parameter auto_explain.sample_rate to
+ allow contrib/auto_explain
to capture just a configurable fraction of all queries (Craig
Ringer, Julien Rouhaud)
@@ -8121,7 +8627,7 @@ This commit is also listed under libpq and PL/pgSQL
2016-04-01 [9ee014fc8] Bloom index contrib module
-->
- Add contrib/bloom module that
+ Add contrib/bloom module that
implements an index access method based on Bloom filtering (Teodor
Sigaev, Alexander Korotkov)
@@ -8139,7 +8645,7 @@ This commit is also listed under libpq and PL/pgSQL
2015-12-28 [81ee726d8] Code and docs review for cube kNN support.
-->
- In contrib/cube, introduce
+ In contrib/cube, introduce
distance operators for cubes, and support kNN-style searches in
GiST indexes on cube columns (Stas Kelvich)
@@ -8150,19 +8656,19 @@ This commit is also listed under libpq and PL/pgSQL
2016-02-03 [41d2c081c] Make hstore_to_jsonb_loose match hstore_to_json_loose on
-->
- Make contrib/hstore's hstore_to_jsonb_loose()
- and hstore_to_json_loose() functions agree on what
+ Make contrib/hstore's hstore_to_jsonb_loose()
+ and hstore_to_json_loose() functions agree on what
is a number (Tom Lane)
- Previously, hstore_to_jsonb_loose() would convert
- numeric-looking strings to JSON numbers, rather than
- strings, even if they did not exactly match the JSON
+ Previously, hstore_to_jsonb_loose() would convert
+ numeric-looking strings to JSON numbers, rather than
+ strings, even if they did not exactly match the JSON
syntax specification for numbers. This was inconsistent with
- hstore_to_json_loose(), so tighten the test to match
- the JSON syntax.
+ hstore_to_json_loose(), so tighten the test to match
+ the JSON syntax.
@@ -8172,7 +8678,7 @@ This commit is also listed under libpq and PL/pgSQL
-->
Add selectivity estimation functions for
- contrib/intarray operators
+ contrib/intarray operators
to improve plans for queries using those operators (Yury Zhuravlev,
Alexander Korotkov)
@@ -8184,10 +8690,10 @@ This commit is also listed under libpq and PL/pgSQL
-->
Make contrib/pageinspect's
- heap_page_items() function show the raw data in each
- tuple, and add new functions tuple_data_split() and
- heap_page_item_attrs() for inspection of individual
+ linkend="pageinspect">contrib/pageinspect's
+ heap_page_items() function show the raw data in each
+ tuple, and add new functions tuple_data_split() and
+ heap_page_item_attrs() for inspection of individual
tuple fields (Nikolay Shaplov)
@@ -8197,9 +8703,9 @@ This commit is also listed under libpq and PL/pgSQL
2016-03-09 [188f359d3] pgcrypto: support changing S2K iteration count
-->
- Add an optional S2K iteration count parameter to
- contrib/pgcrypto's
- pgp_sym_encrypt() function (Jeff Janes)
+ Add an optional S2K iteration count parameter to
+ contrib/pgcrypto's
+ pgp_sym_encrypt() function (Jeff Janes)
@@ -8208,8 +8714,8 @@ This commit is also listed under libpq and PL/pgSQL
2016-03-16 [f576b17cd] Add word_similarity to pg_trgm contrib module.
-->
- Add support for word similarity to
- contrib/pg_trgm
+ Add support for word similarity to
+ contrib/pg_trgm
(Alexander Korotkov, Artur Zakirov)
@@ -8226,14 +8732,14 @@ This commit is also listed under libpq and PL/pgSQL
-->
Add configuration parameter
- pg_trgm.similarity_threshold for
- contrib/pg_trgm's similarity threshold (Artur Zakirov)
+ pg_trgm.similarity_threshold for
+ contrib/pg_trgm's similarity threshold (Artur Zakirov)
This threshold has always been configurable, but formerly it was
- controlled by special-purpose functions set_limit()
- and show_limit(). Those are now deprecated.
+ controlled by special-purpose functions set_limit()
+ and show_limit(). Those are now deprecated.
@@ -8242,7 +8748,7 @@ This commit is also listed under libpq and PL/pgSQL
2015-07-20 [97f301464] This supports the triconsistent function for pg_trgm GIN
-->
- Improve contrib/pg_trgm's GIN operator class to
+ Improve contrib/pg_trgm's GIN operator class to
speed up index searches in which both common and rare keys appear
(Jeff Janes)
@@ -8254,7 +8760,7 @@ This commit is also listed under libpq and PL/pgSQL
-->
Improve performance of similarity searches in
- contrib/pg_trgm GIN indexes (Christophe Fornaroli)
+ contrib/pg_trgm GIN indexes (Christophe Fornaroli)
@@ -8265,7 +8771,7 @@ This commit is also listed under libpq and PL/pgSQL
-->
Add contrib/pg_visibility module
+ linkend="pgvisibility">contrib/pg_visibility module
to allow examining table visibility maps (Robert Haas)
@@ -8275,9 +8781,9 @@ This commit is also listed under libpq and PL/pgSQL
2015-09-07 [49124613f] contrib/sslinfo: add ssl_extension_info SRF
-->
- Add ssl_extension_info()
- function to contrib/sslinfo, to print information
- about SSL extensions present in the X509
+ Add ssl_extension_info()
+ function to contrib/sslinfo, to print information
+ about SSL extensions present in the X509
certificate used for the current connection (Dmitry Voronin)
@@ -8285,7 +8791,7 @@ This commit is also listed under libpq and PL/pgSQL
- <link linkend="postgres-fdw"><filename>postgres_fdw</></>
+ <link linkend="postgres-fdw"><filename>postgres_fdw</filename></link>
@@ -8332,12 +8838,12 @@ This commit is also listed under libpq and PL/pgSQL
2016-03-18 [0bf3ae88a] Directly modify foreign tables.
-->
- When feasible, perform UPDATE or DELETE
+ When feasible, perform UPDATE or DELETE
entirely on the remote server (Etsuro Fujita)
- Formerly, remote updates involved sending a SELECT FOR UPDATE
+ Formerly, remote updates involved sending a SELECT FOR UPDATE
command and then updating or deleting the selected rows one-by-one.
While that is still necessary if the operation requires any local
processing, it can now be done remotely if all elements of the
@@ -8355,7 +8861,7 @@ This commit is also listed under libpq and PL/pgSQL
- Formerly, postgres_fdw always fetched 100 rows at
+ Formerly, postgres_fdw always fetched 100 rows at
a time from remote queries; now that behavior is configurable.