Sophie: postgresql9.4-docs-9.4.15-1.mga6 noarch

postgresql9.4-docs-9.4.15-1.mga6.noarch.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Release 8.4.19</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 9.4.15 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="Release Notes"
HREF="release.html"><LINK
REL="PREVIOUS"
TITLE="Release 8.4.20"
HREF="release-8-4-20.html"><LINK
REL="NEXT"
TITLE="Release 8.4.18"
HREF="release-8-4-18.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="2017-11-10T00:43:05"></HEAD
><BODY
CLASS="SECT1"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="4"
ALIGN="center"
VALIGN="bottom"
><A
HREF="index.html"
>PostgreSQL 9.4.15 Documentation</A
></TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
TITLE="Release 8.4.20"
HREF="release-8-4-20.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="release.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. Release Notes</TD
><TD
WIDTH="20%"
ALIGN="right"
VALIGN="top"
><A
TITLE="Release 8.4.18"
HREF="release-8-4-18.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="RELEASE-8-4-19"
>E.115. Release 8.4.19</A
></H1
><DIV
CLASS="FORMALPARA"
><P
><B
>Release date: </B
>2013-12-05</P
></DIV
><P
>   This release contains a variety of fixes from 8.4.18.
   For information about new features in the 8.4 major release, see
   <A
HREF="release-8-4.html"
>Section E.134</A
>.
  </P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN141679"
>E.115.1. Migration to Version 8.4.19</A
></H2
><P
>    A dump/restore is not required for those running 8.4.X.
   </P
><P
>    However, this release corrects a potential data corruption
    issue.  See the first changelog entry below to find out whether
    your installation has been affected and what steps you can take if so.
   </P
><P
>    Also, if you are upgrading from a version earlier than 8.4.17,
    see <A
HREF="release-8-4-17.html"
>Section E.117</A
>.
   </P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN141685"
>E.115.2. Changes</A
></H2
><P
></P
><UL
><LI
><P
>      Fix <TT
CLASS="COMMAND"
>VACUUM</TT
>'s tests to see whether it can
      update <TT
CLASS="STRUCTFIELD"
>relfrozenxid</TT
> (Andres Freund)
     </P
><P
>      In some cases <TT
CLASS="COMMAND"
>VACUUM</TT
> (either manual or autovacuum) could
      incorrectly advance a table's <TT
CLASS="STRUCTFIELD"
>relfrozenxid</TT
> value,
      allowing tuples to escape freezing, causing those rows to become
      invisible once 2^31 transactions have elapsed.  The probability of
      data loss is fairly low since multiple incorrect advancements would
      need to happen before actual loss occurs, but it's not zero.  Users
      upgrading from release 8.4.8 or earlier are not affected, but all later
      versions contain the bug.
     </P
><P
>      The issue can be ameliorated by, after upgrading, vacuuming all tables
      in all databases while having <A
HREF="runtime-config-client.html#GUC-VACUUM-FREEZE-TABLE-AGE"
><TT
CLASS="VARNAME"
>vacuum_freeze_table_age</TT
></A
>
      set to zero.  This will fix any latent corruption but will not be able
      to fix all pre-existing data errors.  However, an installation can be
      presumed safe after performing this vacuuming if it has executed fewer
      than 2^31 update transactions in its lifetime (check this with
      <TT
CLASS="LITERAL"
>SELECT txid_current() &#60; 2^31</TT
>).
     </P
></LI
><LI
><P
>      Fix race condition in GIN index posting tree page deletion (Heikki
      Linnakangas)
     </P
><P
>      This could lead to transient wrong answers or query failures.
     </P
></LI
><LI
><P
>      Avoid flattening a subquery whose <TT
CLASS="LITERAL"
>SELECT</TT
> list contains a
      volatile function wrapped inside a sub-<TT
CLASS="LITERAL"
>SELECT</TT
> (Tom Lane)
     </P
><P
>      This avoids unexpected results due to extra evaluations of the
      volatile function.
     </P
></LI
><LI
><P
>      Fix planner's processing of non-simple-variable subquery outputs
      nested within outer joins (Tom Lane)
     </P
><P
>      This error could lead to incorrect plans for queries involving
      multiple levels of subqueries within <TT
CLASS="LITERAL"
>JOIN</TT
> syntax.
     </P
></LI
><LI
><P
>      Fix premature deletion of temporary files (Andres Freund)
     </P
></LI
><LI
><P
>      Fix possible read past end of memory in rule printing (Peter Eisentraut)
     </P
></LI
><LI
><P
>      Fix array slicing of <TT
CLASS="TYPE"
>int2vector</TT
> and <TT
CLASS="TYPE"
>oidvector</TT
> values
      (Tom Lane)
     </P
><P
>      Expressions of this kind are now implicitly promoted to
      regular <TT
CLASS="TYPE"
>int2</TT
> or <TT
CLASS="TYPE"
>oid</TT
> arrays.
     </P
></LI
><LI
><P
>      Fix incorrect behaviors when using a SQL-standard, simple GMT offset
      timezone (Tom Lane)
     </P
><P
>      In some cases, the system would use the simple GMT offset value when
      it should have used the regular timezone setting that had prevailed
      before the simple offset was selected.  This change also causes
      the <CODE
CLASS="FUNCTION"
>timeofday</CODE
> function to honor the simple GMT offset
      zone.
     </P
></LI
><LI
><P
>      Prevent possible misbehavior when logging translations of Windows
      error codes (Tom Lane)
     </P
></LI
><LI
><P
>      Properly quote generated command lines in <SPAN
CLASS="APPLICATION"
>pg_ctl</SPAN
>
      (Naoya Anzai and Tom Lane)
     </P
><P
>      This fix applies only to Windows.
     </P
></LI
><LI
><P
>      Fix <SPAN
CLASS="APPLICATION"
>pg_dumpall</SPAN
> to work when a source database
      sets <A
HREF="runtime-config-client.html#GUC-DEFAULT-TRANSACTION-READ-ONLY"
><TT
CLASS="VARNAME"
>default_transaction_read_only</TT
></A
>
      via <TT
CLASS="COMMAND"
>ALTER DATABASE SET</TT
> (Kevin Grittner)
     </P
><P
>      Previously, the generated script would fail during restore.
     </P
></LI
><LI
><P
>      Fix <SPAN
CLASS="APPLICATION"
>ecpg</SPAN
>'s processing of lists of variables
      declared <TT
CLASS="TYPE"
>varchar</TT
> (Zolt&aacute;n B&ouml;sz&ouml;rm&eacute;nyi)
     </P
></LI
><LI
><P
>      Make <TT
CLASS="FILENAME"
>contrib/lo</TT
> defend against incorrect trigger definitions
      (Marc Cousin)
     </P
></LI
><LI
><P
>      Update time zone data files to <SPAN
CLASS="APPLICATION"
>tzdata</SPAN
> release 2013h
      for DST law changes in Argentina, Brazil, Jordan, Libya,
      Liechtenstein, Morocco, and Palestine.  Also, new timezone
      abbreviations WIB, WIT, WITA for Indonesia.
     </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-4-20.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-4-18.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Release 8.4.20</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.4.18</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>