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 Section E.181.
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 Section E.179.
Avoid failures when
EXPLAIN tries to display a simple-form
CASE expression (Tom
expression was a constant, the planner could simplify the
CASE into a form that
confused the expression-display code, resulting in
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)
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
Although restoring directly to a database worked
correctly, string escaping was incorrect if pg_restore was asked for SQL text
standard_conforming_strings had been
enabled in the source database.
Fix erroneous parsing of
tsquery values containing
... & !(subexpression) | ... (Tom
Queries containing this combination of operators were
not executed correctly. The same error existed in
query_int type and
Fix buffer overrun in
contrib/intarray's input function for
query_int type (Apple)
This bug is a security risk since the function's return address could be overwritten. Thanks to Apple Inc's security team for reporting this issue and supplying the fix. (CVE-2010-4015)
Fix bug in
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
it after installing this update. (This is identical to
the bug that was fixed in
contrib/cube in the previous
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.