Release Date
2016-??-??
- Current as of 2016-05-02 (commit 21c2b1c61)
+ Current as of 2016-05-05 (commit 7a622b273)
2016-04-27 [59eb55127] Fix EXPLAIN VERBOSE output for parallel aggregate.
-->
- Parallel queries (Robert Haas, Amit Kapila, many others)
+ Parallel queries (Robert Haas, Amit Kapila, David Rowley, many others)
- With 9.6,
PostgreSQL> introduces initial support
- for parallel execution of large queries. Scans over large tables can
- be parallelized, as can hash joins and computation of aggregate
- functions. Much remains to be done, but this is already a useful set
- of features.
+ 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 in
+ parallel, as can aggregation (for supported aggregates). Much
+ remains to be done, but this is already a useful set of features.
, and
.
-
- This section needs to get fleshed out, but by how much?
-
2016-04-13 [fa11a09fe] Fix assorted portability issues with using msync() for d
2016-04-24 [8f91d87d4] Fix documentation & config inconsistencies around 428b1d
2016-04-26 [72a98a639] Don't open formally non-existent segments in _mdfd_getse
+2016-05-04 [a71248708] Fix transient mdsync() errors of truncated relations due
-->
Where feasible, trigger kernel writeback after a configurable number
2016-04-08 [719c84c1b] Extend relations multiple blocks at a time to improve sc
-->
- Extend relations multiple blocks at a time (Dilip Kumar)
+ Extend relations multiple blocks at a time, when there is contention
+ for the relation's extension lock (Dilip Kumar)
- This reduces kernel traffic, and improves scalability when multiple
+ This reduces kernel traffic and improves scalability when multiple
processes are inserting into the same relation.
-->
Force backends to exit if the postmaster dies
- (Rajeev Rastogi and Robert Haas)
+ (Rajeev Rastogi, Robert Haas)
2016-01-28 [fbe5a3fb7] Only try to push down foreign joins if the user mapping
-->
- Push down joins of foreign tables to the foreign data wrapper only
- when the user mappings match (Shigeru Hanada, Ashutosh Bapat)
+ Consider performing joins of foreign tables remotely only when the
+ applicable user mappings match (Shigeru Hanada, Ashutosh Bapat)
Improve the accuracy of the ln()>, log()>,
-->
Ensure that trigonometric functions handle infinity and NaN inputs per
- spec (Dean Rasheed)
+ the POSIX standard (Dean Rasheed)
An example usage is CHECK(num_nonnulls(a,b,c) = 1)> which
asserts that exactly one of a,b,c isn't NULL. These functions can
- also be pressed into service to count the number of null or nonnull
- elements in an array.
+ also be used to count the number of null or nonnull elements in an
+ array.
This function converts strings like those produced
by pg_size_pretty()> into sizes in bytes. An example
- usage is WHERE pg_total_relation_size(oid) >
- pg_size_bytes('10 GB')>.
+ usage is SELECT oid::regclass FROM pg_class WHERE
+ pg_total_relation_size(oid) > pg_size_bytes('10 GB')>.
2015-11-06 [8a1fab36a] pg_size_pretty: Format negative values similar to positi
-->
- In pg_size_pretty()>, format negative numbers similarly to
- positive ones (Adrian Vondendriesch)
+ In pg_size_pretty()>, format negative numbers similarly
+ to positive ones (Adrian Vondendriesch)
+
+
+ Previously, negative numbers were never abbreviated, just printed
+ in bytes.
Add an optional missing_ok> argument to
the current_setting()> function (David Christensen)
+
+ This allows avoiding an error for an unrecognized parameter name;
+ instead the result is NULL.
+
Support some built-in
-->
Improve error reporting during
initdb>'s post-bootstrap
- phase, by not reporting the entire input file as the failing
- query> (Tom Lane)
+ phase (Tom Lane)
+
+
+ Previously, an error here led to reporting the entire input 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 lines.
2016-03-09 [aa09cd242] postgres_fdw: Consider foreign joining and foreign sorti
-->
- Push down joins to the remote server when possible (Shigeru Hanada,
+ Consider performing joins on the remote server (Shigeru Hanada,
Ashutosh Bapat)