<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Release 8.3.14</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:pgsql-docs@postgresql.org"><LINK
REL="HOME"
TITLE="PostgreSQL 8.4.12 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="Release Notes"
HREF="release.html"><LINK
REL="PREVIOUS"
TITLE="Release 8.3.15"
HREF="release-8-3-15.html"><LINK
REL="NEXT"
TITLE="Release 8.3.13"
HREF="release-8-3-13.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"><META
NAME="creation"
CONTENT="2012-05-31T23:30:11"></HEAD
><BODY
CLASS="SECT1"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="5"
ALIGN="center"
VALIGN="bottom"
>PostgreSQL 8.4.12 Documentation</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="release-8-3-15.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="release.html"
>Fast Backward</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. Release Notes</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="release.html"
>Fast Forward</A
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="release-8-3-13.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="RELEASE-8-3-14"
>E.19. Release 8.3.14</A
></H1
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Release Date: </B
>2011-01-31</P
></BLOCKQUOTE
></DIV
><P
> This release contains a variety of fixes from 8.3.13.
For information about new features in the 8.3 major release, see
<A
HREF="release-8-3.html"
>Section E.33</A
>.
</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN97881"
>E.19.1. Migration to Version 8.3.14</A
></H2
><P
> 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.
</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN97884"
>E.19.2. Changes</A
></H2
><P
></P
><UL
><LI
><P
> Avoid failures when <TT
CLASS="COMMAND"
>EXPLAIN</TT
> tries to display a simple-form
<TT
CLASS="LITERAL"
>CASE</TT
> expression (Tom Lane)
</P
><P
> If the <TT
CLASS="LITERAL"
>CASE</TT
>'s test expression was a constant, the planner
could simplify the <TT
CLASS="LITERAL"
>CASE</TT
> into a form that confused the
expression-display code, resulting in <SPAN
CLASS="QUOTE"
>"unexpected CASE WHEN
clause"</SPAN
> errors.
</P
></LI
><LI
><P
> Fix assignment to an array slice that is before the existing range
of subscripts (Tom Lane)
</P
><P
> 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.
</P
></LI
><LI
><P
> Avoid unexpected conversion overflow in planner for very distant date
values (Tom Lane)
</P
><P
> The <TT
CLASS="TYPE"
>date</TT
> type supports a wider range of dates than can be
represented by the <TT
CLASS="TYPE"
>timestamp</TT
> types, but the planner assumed it
could always convert a date to timestamp with impunity.
</P
></LI
><LI
><P
> Fix <SPAN
CLASS="APPLICATION"
>pg_restore</SPAN
>'s text output for large objects (BLOBs)
when <TT
CLASS="VARNAME"
>standard_conforming_strings</TT
> is on (Tom Lane)
</P
><P
> Although restoring directly to a database worked correctly, string
escaping was incorrect if <SPAN
CLASS="APPLICATION"
>pg_restore</SPAN
> was asked for
SQL text output and <TT
CLASS="VARNAME"
>standard_conforming_strings</TT
> had been
enabled in the source database.
</P
></LI
><LI
><P
> Fix erroneous parsing of <TT
CLASS="TYPE"
>tsquery</TT
> values containing
<TT
CLASS="LITERAL"
>... & !(subexpression) | ...</TT
> (Tom Lane)
</P
><P
> Queries containing this combination of operators were not executed
correctly. The same error existed in <TT
CLASS="FILENAME"
>contrib/intarray</TT
>'s
<TT
CLASS="TYPE"
>query_int</TT
> type and <TT
CLASS="FILENAME"
>contrib/ltree</TT
>'s
<TT
CLASS="TYPE"
>ltxtquery</TT
> type.
</P
></LI
><LI
><P
> Fix buffer overrun in <TT
CLASS="FILENAME"
>contrib/intarray</TT
>'s input function
for the <TT
CLASS="TYPE"
>query_int</TT
> type (Apple)
</P
><P
> 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)
</P
></LI
><LI
><P
> Fix bug in <TT
CLASS="FILENAME"
>contrib/seg</TT
>'s GiST picksplit algorithm
(Alexander Korotkov)
</P
><P
> This could result in considerable inefficiency, though not actually
incorrect answers, in a GiST index on a <TT
CLASS="TYPE"
>seg</TT
> column.
If you have such an index, consider <TT
CLASS="COMMAND"
>REINDEX</TT
>ing it after
installing this update. (This is identical to the bug that was fixed in
<TT
CLASS="FILENAME"
>contrib/cube</TT
> in the previous update.)
</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="release-8-3-15.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="release-8-3-13.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Release 8.3.15</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="release.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Release 8.3.13</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
distrib
>
Mandriva
>
current
>
i586
>
media
>
main-updates
>
by-pkgid
>
fc62ce67f262cdcd253dc7f849ce3223
>
files
>
653
