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 9.3.4</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 9.3.5"
HREF="release-9-3-5.html"><LINK
REL="NEXT"
TITLE="Release 9.3.3"
HREF="release-9-3-3.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 9.3.5"
HREF="release-9-3-5.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 9.3.3"
HREF="release-9-3-3.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="RELEASE-9-3-4"
>E.33. Release 9.3.4</A
></H1
><DIV
CLASS="FORMALPARA"
><P
><B
>Release date: </B
>2014-03-20</P
></DIV
><P
>   This release contains a variety of fixes from 9.3.3.
   For information about new features in the 9.3 major release, see
   <A
HREF="release-9-3.html"
>Section E.37</A
>.
  </P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN125681"
>E.33.1. Migration to Version 9.3.4</A
></H2
><P
>    A dump/restore is not required for those running 9.3.X.
   </P
><P
>    However, the error fixed in the first changelog entry below could have
    resulted in corrupt data on standby servers.  It may be prudent to
    reinitialize standby servers from fresh base backups after installing
    this update.
   </P
><P
>    Also, if you are upgrading from a version earlier than 9.3.3,
    see <A
HREF="release-9-3-3.html"
>Section E.34</A
>.
   </P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN125687"
>E.33.2. Changes</A
></H2
><P
></P
><UL
><LI
><P
>      Fix WAL replay of locking an already-updated tuple (Andres Freund,
      &Aacute;lvaro Herrera)
     </P
><P
>      This error caused updated rows to not be found by index scans, resulting
      in inconsistent query results depending on whether an index scan was
      used.  Subsequent processing could result in constraint violations,
      since the previously updated row would not be found by later index
      searches, thus possibly allowing conflicting rows to be inserted.
      Since this error is in WAL replay, it would only manifest during crash
      recovery or on standby servers.  The improperly-replayed case most
      commonly arises when a table row that is referenced by a foreign-key
      constraint is updated concurrently with creation of a referencing row.
     </P
></LI
><LI
><P
>      Restore GIN metapages unconditionally to avoid torn-page risk
      (Heikki Linnakangas)
     </P
><P
>      Although this oversight could theoretically result in a corrupted
      index, it is unlikely to have caused any problems in practice, since
      the active part of a GIN metapage is smaller than a standard 512-byte
      disk sector.
     </P
></LI
><LI
><P
>      Avoid race condition in checking transaction commit status during
      receipt of a <TT
CLASS="COMMAND"
>NOTIFY</TT
> message (Marko Tiikkaja)
     </P
><P
>      This prevents a scenario wherein a sufficiently fast client might
      respond to a notification before database updates made by the
      notifier have become visible to the recipient.
     </P
></LI
><LI
><P
>      Allow materialized views to be referenced in <TT
CLASS="COMMAND"
>UPDATE</TT
>
      and <TT
CLASS="COMMAND"
>DELETE</TT
> commands (Michael Paquier)
     </P
><P
>      Previously such queries failed with a complaint about not being able
      to lock rows in the materialized view.
     </P
></LI
><LI
><P
>      Allow regular-expression operators to be terminated early by query
      cancel requests (Tom Lane)
     </P
><P
>      This prevents scenarios wherein a pathological regular expression
      could lock up a server process uninterruptibly for a long time.
     </P
></LI
><LI
><P
>      Remove incorrect code that tried to allow <TT
CLASS="LITERAL"
>OVERLAPS</TT
> with
      single-element row arguments (Joshua Yanovski)
     </P
><P
>      This code never worked correctly, and since the case is neither
      specified by the SQL standard nor documented, it seemed better to
      remove it than fix it.
     </P
></LI
><LI
><P
>      Avoid getting more than <TT
CLASS="LITERAL"
>AccessShareLock</TT
> when de-parsing a
      rule or view (Dean Rasheed)
     </P
><P
>      This oversight resulted in <SPAN
CLASS="APPLICATION"
>pg_dump</SPAN
> unexpectedly
      acquiring <TT
CLASS="LITERAL"
>RowExclusiveLock</TT
> locks on tables mentioned as
      the targets of <TT
CLASS="LITERAL"
>INSERT</TT
>/<TT
CLASS="LITERAL"
>UPDATE</TT
>/<TT
CLASS="LITERAL"
>DELETE</TT
>
      commands in rules.  While usually harmless, that could interfere with
      concurrent transactions that tried to acquire, for example,
      <TT
CLASS="LITERAL"
>ShareLock</TT
> on those tables.
     </P
></LI
><LI
><P
>      Improve performance of index endpoint probes during planning (Tom Lane)
     </P
><P
>      This change fixes a significant performance problem that occurred
      when there were many not-yet-committed rows at the end of the index,
      which is a common situation for indexes on sequentially-assigned
      values such as timestamps or sequence-generated identifiers.
     </P
></LI
><LI
><P
>      Use non-default selectivity estimates for
      <TT
CLASS="LITERAL"
><TT
CLASS="REPLACEABLE"
><I
>value</I
></TT
> IN (<TT
CLASS="REPLACEABLE"
><I
>list</I
></TT
>)</TT
> and
      <TT
CLASS="LITERAL"
><TT
CLASS="REPLACEABLE"
><I
>value</I
></TT
> <TT
CLASS="REPLACEABLE"
><I
>operator</I
></TT
> ANY
      (<TT
CLASS="REPLACEABLE"
><I
>array</I
></TT
>)</TT
>
      expressions when the righthand side is a stable expression (Tom Lane)
     </P
></LI
><LI
><P
>      Remove the correct per-database statistics file during <TT
CLASS="COMMAND"
>DROP
      DATABASE</TT
> (Tomas Vondra)
     </P
><P
>      This fix prevents a permanent leak of statistics file space.
      Users who have done many <TT
CLASS="COMMAND"
>DROP DATABASE</TT
> commands since
      upgrading to <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> 9.3 may wish to check their
      statistics directory and delete statistics files that do not
      correspond to any existing database.  Please note
      that <TT
CLASS="FILENAME"
>db_0.stat</TT
> should not be removed.
     </P
></LI
><LI
><P
>      Fix <SPAN
CLASS="APPLICATION"
>walsender</SPAN
> ping logic to avoid inappropriate
      disconnects under continuous load (Andres Freund, Heikki Linnakangas)
     </P
><P
>      <SPAN
CLASS="APPLICATION"
>walsender</SPAN
> failed to send ping messages to the client
      if it was constantly busy sending WAL data; but it expected to see
      ping responses despite that, and would therefore disconnect
      once <A
HREF="runtime-config-replication.html#GUC-WAL-SENDER-TIMEOUT"
>wal_sender_timeout</A
> elapsed.
     </P
></LI
><LI
><P
>      Fix <SPAN
CLASS="APPLICATION"
>walsender</SPAN
>'s failure to shut down cleanly when client
      is <SPAN
CLASS="APPLICATION"
>pg_receivexlog</SPAN
> (Fujii Masao)
     </P
></LI
><LI
><P
>      Check WAL level and hot standby parameters correctly when doing crash
      recovery that will be followed by archive recovery (Heikki Linnakangas)
     </P
></LI
><LI
><P
>      Fix test to see if hot standby connections can be allowed immediately
      after a crash (Heikki Linnakangas)
     </P
></LI
><LI
><P
>      Add read-only <A
HREF="runtime-config-preset.html#GUC-DATA-CHECKSUMS"
>data_checksums</A
> parameter to
      display whether page checksums are enabled (Heikki Linnakangas)
     </P
><P
>      Without this parameter, determining the state of checksum
      processing was difficult.
     </P
></LI
><LI
><P
>      Prevent interrupts while reporting non-<TT
CLASS="LITERAL"
>ERROR</TT
> messages
      (Tom Lane)
     </P
><P
>      This guards against rare server-process freezeups due to recursive
      entry to <CODE
CLASS="FUNCTION"
>syslog()</CODE
>, and perhaps other related problems.
     </P
></LI
><LI
><P
>      Fix memory leak in PL/Perl when returning a composite result, including
      multiple-OUT-parameter cases (Alex Hunsaker)
     </P
></LI
><LI
><P
>      Fix tracking of <SPAN
CLASS="APPLICATION"
>psql</SPAN
> script line numbers
      during <TT
CLASS="LITERAL"
>\copy</TT
> from out-of-line data
      (Kumar Rajeev Rastogi, Amit Khandekar)
     </P
><P
>      <TT
CLASS="LITERAL"
>\copy ... from</TT
> incremented the script file line number
      for each data line, even if the data was not coming from the script
      file.  This mistake resulted in wrong line numbers being reported for
      any errors occurring later in the same script file.
     </P
></LI
><LI
><P
>      Fix <SPAN
CLASS="APPLICATION"
>contrib/postgres_fdw</SPAN
> to handle multiple join
      conditions properly (Tom Lane)
     </P
><P
>      This oversight could result in sending <TT
CLASS="LITERAL"
>WHERE</TT
> clauses to
      the remote server for execution even though the clauses are not known
      to have the same semantics on the remote server (for example, clauses
      that use non-built-in operators).  The query might succeed anyway,
      but it could also fail with errors from the remote server, or worse
      give silently wrong answers.
     </P
></LI
><LI
><P
>      Prevent intermittent <SPAN
CLASS="QUOTE"
>"could not reserve shared memory region"</SPAN
>
      failures on recent Windows versions (MauMau)
     </P
></LI
><LI
><P
>      Update time zone data files to <SPAN
CLASS="APPLICATION"
>tzdata</SPAN
> release 2014a
      for DST law changes in Fiji and Turkey, plus historical changes in
      Israel and Ukraine.
     </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-9-3-5.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-9-3-3.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Release 9.3.5</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 9.3.3</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>