From: Tom Lane Date: Thu, 27 Jan 2011 21:10:00 +0000 (-0500) Subject: Update release notes for releases 9.0.3, 8.4.7, 8.3.14, and 8.2.20. X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=dea0a74cb231fff77e8c4b982b42d7a672247eb2;p=users%2Fc2main%2Fpostgres.git Update release notes for releases 9.0.3, 8.4.7, 8.3.14, and 8.2.20. --- diff --git a/doc/src/sgml/release-8.2.sgml b/doc/src/sgml/release-8.2.sgml index 195f8c90d2..dd82ee69d3 100644 --- a/doc/src/sgml/release-8.2.sgml +++ b/doc/src/sgml/release-8.2.sgml @@ -1,6 +1,125 @@ + + Release 8.2.20 + + + Release date + 2011-01-31 + + + + This release contains a variety of fixes from 8.2.19. + For information about new features in the 8.2 major release, see + . + + + + Migration to Version 8.2.20 + + + A dump/restore is not required for those running 8.2.X. + However, if you are upgrading from a version earlier than 8.2.14, + see the release notes for 8.2.14. + + + + + + Changes + + + + + + Avoid failures when EXPLAIN tries to display a simple-form + CASE expression (Tom Lane) + + + + If the CASE's test expression was a constant, the planner + could simplify the CASE into a form that confused the + expression-display code, resulting in unexpected CASE WHEN + clause errors. + + + + + + Fix assignment to an array slice that is before the existing range + of subscripts (Tom Lane) + + + + If there was a gap between the newly added subscripts and the first + pre-existing subscript, the code miscalculated how many entries needed + to be copied from the old array's null bitmap, potentially leading to + data corruption or crash. + + + + + + Avoid unexpected conversion overflow in planner for very distant date + values (Tom Lane) + + + + The date type supports a wider range of dates than can be + represented by the timestamp types, but the planner assumed it + could always convert a date to timestamp with impunity. + + + + + + Fix pg_restore's text output for large objects (BLOBs) + when standard_conforming_strings is on (Tom Lane) + + + + Although restoring directly to a database worked correctly, string + escaping was incorrect if pg_restore was asked for + SQL text output and standard_conforming_strings had been + enabled in the source database. + + + + + + Fix erroneous parsing of tsquery values containing + ... & !(subexpression) | ... (Tom Lane) + + + + Queries containing this combination of operators were not executed + correctly. The same error existed in contrib/intarray's + query_int type and contrib/ltree's + ltxtquery type. + + + + + + Fix bug in contrib/seg's GiST picksplit algorithm + (Alexander Korotkov) + + + + This could result in considerable inefficiency, though not actually + incorrect answers, in a GiST index on a seg column. + If you have such an index, consider REINDEXing it after + installing this update. (This is identical to the bug that was fixed in + contrib/cube in the previous update.) + + + + + + + + Release 8.2.19 diff --git a/doc/src/sgml/release-8.3.sgml b/doc/src/sgml/release-8.3.sgml index 877e2ad442..5d691a4183 100644 --- a/doc/src/sgml/release-8.3.sgml +++ b/doc/src/sgml/release-8.3.sgml @@ -1,6 +1,125 @@ + + Release 8.3.14 + + + Release date + 2011-01-31 + + + + This release contains a variety of fixes from 8.3.13. + For information about new features in the 8.3 major release, see + . + + + + Migration to Version 8.3.14 + + + A dump/restore is not required for those running 8.3.X. + However, if you are upgrading from a version earlier than 8.3.8, + see the release notes for 8.3.8. + + + + + + Changes + + + + + + Avoid failures when EXPLAIN tries to display a simple-form + CASE expression (Tom Lane) + + + + If the CASE's test expression was a constant, the planner + could simplify the CASE into a form that confused the + expression-display code, resulting in unexpected CASE WHEN + clause errors. + + + + + + Fix assignment to an array slice that is before the existing range + of subscripts (Tom Lane) + + + + If there was a gap between the newly added subscripts and the first + pre-existing subscript, the code miscalculated how many entries needed + to be copied from the old array's null bitmap, potentially leading to + data corruption or crash. + + + + + + Avoid unexpected conversion overflow in planner for very distant date + values (Tom Lane) + + + + The date type supports a wider range of dates than can be + represented by the timestamp types, but the planner assumed it + could always convert a date to timestamp with impunity. + + + + + + Fix pg_restore's text output for large objects (BLOBs) + when standard_conforming_strings is on (Tom Lane) + + + + Although restoring directly to a database worked correctly, string + escaping was incorrect if pg_restore was asked for + SQL text output and standard_conforming_strings had been + enabled in the source database. + + + + + + Fix erroneous parsing of tsquery values containing + ... & !(subexpression) | ... (Tom Lane) + + + + Queries containing this combination of operators were not executed + correctly. The same error existed in contrib/intarray's + query_int type and contrib/ltree's + ltxtquery type. + + + + + + Fix bug in contrib/seg's GiST picksplit algorithm + (Alexander Korotkov) + + + + This could result in considerable inefficiency, though not actually + incorrect answers, in a GiST index on a seg column. + If you have such an index, consider REINDEXing it after + installing this update. (This is identical to the bug that was fixed in + contrib/cube in the previous update.) + + + + + + + + Release 8.3.13 diff --git a/doc/src/sgml/release-8.4.sgml b/doc/src/sgml/release-8.4.sgml index 37be232214..8d00a55f5d 100644 --- a/doc/src/sgml/release-8.4.sgml +++ b/doc/src/sgml/release-8.4.sgml @@ -1,6 +1,125 @@ + + Release 8.4.7 + + + Release date + 2011-01-31 + + + + This release contains a variety of fixes from 8.4.6. + For information about new features in the 8.4 major release, see + . + + + + Migration to Version 8.4.7 + + + A dump/restore is not required for those running 8.4.X. + However, if you are upgrading from a version earlier than 8.4.2, + see the release notes for 8.4.2. + + + + + + Changes + + + + + + Avoid failures when EXPLAIN tries to display a simple-form + CASE expression (Tom Lane) + + + + If the CASE's test expression was a constant, the planner + could simplify the CASE into a form that confused the + expression-display code, resulting in unexpected CASE WHEN + clause errors. + + + + + + Fix assignment to an array slice that is before the existing range + of subscripts (Tom Lane) + + + + If there was a gap between the newly added subscripts and the first + pre-existing subscript, the code miscalculated how many entries needed + to be copied from the old array's null bitmap, potentially leading to + data corruption or crash. + + + + + + Avoid unexpected conversion overflow in planner for very distant date + values (Tom Lane) + + + + The date type supports a wider range of dates than can be + represented by the timestamp types, but the planner assumed it + could always convert a date to timestamp with impunity. + + + + + + Fix pg_restore's text output for large objects (BLOBs) + when standard_conforming_strings is on (Tom Lane) + + + + Although restoring directly to a database worked correctly, string + escaping was incorrect if pg_restore was asked for + SQL text output and standard_conforming_strings had been + enabled in the source database. + + + + + + Fix erroneous parsing of tsquery values containing + ... & !(subexpression) | ... (Tom Lane) + + + + Queries containing this combination of operators were not executed + correctly. The same error existed in contrib/intarray's + query_int type and contrib/ltree's + ltxtquery type. + + + + + + Fix bug in contrib/seg's GiST picksplit algorithm + (Alexander Korotkov) + + + + This could result in considerable inefficiency, though not actually + incorrect answers, in a GiST index on a seg column. + If you have such an index, consider REINDEXing it after + installing this update. (This is identical to the bug that was fixed in + contrib/cube in the previous update.) + + + + + + + + Release 8.4.6