From eec1a8cb6cbc6ea44cf58cfaeaa01ad8ee2bc8e8 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 23 Feb 2018 17:20:26 -0500 Subject: First-draft release notes for 10.3. --- doc/src/sgml/release-10.sgml | 206 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 206 insertions(+) diff --git a/doc/src/sgml/release-10.sgml b/doc/src/sgml/release-10.sgml index 7b0fde2b93d..718ad4cb0c5 100644 --- a/doc/src/sgml/release-10.sgml +++ b/doc/src/sgml/release-10.sgml @@ -1,6 +1,212 @@ + + Release 10.3 + + + Release date: + 2018-03-01 + + + + This release contains a variety of fixes from 10.2. + For information about new features in major release 10, see + . + + + + Migration to Version 10.3 + + + A dump/restore is not required for those running 10.X. + + + + However, if you are upgrading from a version earlier than 10.2, + see . + + + + + Changes + + + + + + + Fix misbehavior of concurrent-update rechecks with CTE references + appearing in subplans (Tom Lane) + + + + If a CTE (WITH clause reference) is used in an + InitPlan or SubPlan, and the query requires a recheck due to trying + to update or lock a concurrently-updated row, incorrect results could + be obtained. + + + + + + + Fix planner failures with overlapping mergejoin clauses in an outer + join (Tom Lane) + + + + These mistakes led to left and right pathkeys do not match in + mergejoin or outer pathkeys do not match + mergeclauses planner errors in corner cases. + + + + + + + Repair pg_upgrade's failure to + preserve relfrozenxid for materialized + views (Tom Lane, Andres Freund) + + + + This oversight could lead to data corruption in materialized views + after an upgrade, manifesting as could not access status of + transaction or found xmin from before + relfrozenxid errors. The problem would be more likely to + occur in seldom-refreshed materialized views, or ones that were + maintained only with REFRESH MATERIALIZED VIEW + CONCURRENTLY. + + + + If such corruption is observed, it can be repaired by refreshing the + materialized view (without CONCURRENTLY). + + + + + + + Fix incorrect pg_dump output for some + non-default sequence limit values (Alexey Bashtanov) + + + + + + + Fix pg_dump's mishandling + of STATISTICS objects (Tom Lane) + + + + An extended statistics object's schema was mislabeled in the dump's + table of contents, possibly leading to the wrong results in a + schema-selective restore. Its ownership was not correctly restored, + either. Also, change the logic so that statistics objects are + dumped/restored, or not, as independent objects rather than tying + them to the dump/restore decision for the table they are on. The + original definition could not scale to the planned future extension to + cross-table statistics. + + + + + + + Fix incorrect reporting of PL/Python function names in + error CONTEXT stacks (Tom Lane) + + + + An error occurring within a nested PL/Python function call (that is, + one reached via a SPI query from another PL/Python function) would + result in a stack trace showing the inner function's name twice, + rather than the expected results. Also, an error in a nested + PL/Python DO block could result in a null pointer + dereference crash on some platforms. + + + + + + + Allow contrib/auto_explain's + log_min_duration setting to range up + to INT_MAX, or about 24 days instead of 35 minutes + (Tom Lane) + + + + + + + Mark assorted GUC variables as PGDLLIMPORT, to + ease porting extension modules to Windows (Metin Doslu) + + + + + + + + Release 10.2 -- cgit v1.2.3