<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Release 9.3.2</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.3.9 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="Release Notes"
HREF="release.html"><LINK
REL="PREVIOUS"
TITLE="Release 9.3.3"
HREF="release-9-3-3.html"><LINK
REL="NEXT"
TITLE="Release 9.3.1"
HREF="release-9-3-1.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="2015-06-13T20:07:22"></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"
><A
HREF="index.html"
>PostgreSQL 9.3.9 Documentation</A
></TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
TITLE="Release 9.3.3"
HREF="release-9-3-3.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.1"
HREF="release-9-3-1.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-2"
>E.8. Release 9.3.2</A
></H1
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Release Date: </B
>2013-12-05</P
></BLOCKQUOTE
></DIV
><P
> This release contains a variety of fixes from 9.3.1.
For information about new features in the 9.3 major release, see
<A
HREF="release-9-3.html"
>Section E.10</A
>.
</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN115894"
>E.8.1. Migration to Version 9.3.2</A
></H2
><P
> A dump/restore is not required for those running 9.3.X.
</P
><P
> However, this release corrects a number of potential data corruption
issues. See the first three changelog entries 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 9.3.1,
see <A
HREF="release-9-3-1.html"
>Section E.9</A
>.
</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN115900"
>E.8.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. In 9.2.0
and later, the probability of loss is higher, and it's also possible
to get <SPAN
CLASS="QUOTE"
>"could not access status of transaction"</SPAN
> errors as a
consequence of this bug. Users upgrading from releases 9.0.4 or 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() < 2^31</TT
>).
</P
></LI
><LI
><P
> Fix multiple bugs in MultiXactId freezing (Andres Freund,
Álvaro Herrera)
</P
><P
> These bugs could lead to <SPAN
CLASS="QUOTE"
>"could not access status of
transaction"</SPAN
> errors, or to duplicate or vanishing rows.
Users upgrading from releases prior to 9.3.0 are not affected.
</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 latent corruption but will not be able to
fix all pre-existing data errors.
</P
><P
> As a separate issue, these bugs can also cause standby servers to get
out of sync with the primary, thus exhibiting data errors that are not
in the primary. Therefore, it's recommended that 9.3.0 and 9.3.1
standby servers be re-cloned from the primary (e.g., with a new base
backup) after upgrading.
</P
></LI
><LI
><P
> Fix initialization of <TT
CLASS="FILENAME"
>pg_clog</TT
> and <TT
CLASS="FILENAME"
>pg_subtrans</TT
>
during hot standby startup (Andres Freund, Heikki Linnakangas)
</P
><P
> This bug can cause data loss on standby servers at the moment they
start to accept hot-standby queries, by marking committed transactions
as uncommitted. The likelihood of such corruption is small unless, at
the time of standby startup, the primary server has executed many
updating transactions since its last checkpoint. Symptoms include
missing rows, rows that should have been deleted being still visible,
and obsolete versions of updated rows being still visible alongside
their newer versions.
</P
><P
> This bug was introduced in versions 9.3.0, 9.2.5, 9.1.10, and 9.0.14.
Standby servers that have only been running earlier releases are not
at risk. It's recommended that standby servers that have ever run any
of the buggy releases be re-cloned from the primary (e.g., with a new
base backup) after upgrading.
</P
></LI
><LI
><P
> Fix multiple bugs in update chain traversal (Andres Freund,
Álvaro Herrera)
</P
><P
> These bugs could result in incorrect behavior, such as locking or even
updating the wrong row, in the presence of concurrent updates.
Spurious <SPAN
CLASS="QUOTE"
>"unable to fetch updated version of tuple"</SPAN
> errors
were also possible.
</P
></LI
><LI
><P
> Fix dangling-pointer problem in fast-path locking (Tom Lane)
</P
><P
> This could lead to corruption of the lock data structures in shared
memory, causing <SPAN
CLASS="QUOTE"
>"lock already held"</SPAN
> and other odd errors.
</P
></LI
><LI
><P
> Fix assorted race conditions in timeout management (Tom Lane)
</P
><P
> These errors could result in a server process becoming unresponsive
because it had blocked SIGALRM and/or SIGINT.
</P
></LI
><LI
><P
> Truncate <TT
CLASS="FILENAME"
>pg_multixact</TT
> contents during WAL replay
(Andres Freund)
</P
><P
> This avoids ever-increasing disk space consumption in standby servers.
</P
></LI
><LI
><P
> Ensure an anti-wraparound <TT
CLASS="COMMAND"
>VACUUM</TT
> counts a page as scanned
when it's only verified that no tuples need freezing (Sergey
Burladyan, Jeff Janes)
</P
><P
> This bug could result in failing to
advance <TT
CLASS="STRUCTFIELD"
>relfrozenxid</TT
>, so that the table would still be
thought to need another anti-wraparound vacuum. In the worst case the
database might even shut down to prevent wraparound.
</P
></LI
><LI
><P
> Fix full-table-vacuum request mechanism for MultiXactIds (Andres Freund)
</P
><P
> This bug could result in large amounts of useless autovacuum activity.
</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
> Fix <SPAN
CLASS="QUOTE"
>"unexpected spgdoinsert() failure"</SPAN
> error during SP-GiST
index creation (Teodor Sigaev)
</P
></LI
><LI
><P
> Fix assorted bugs in materialized views (Kevin Grittner, Andres Freund)
</P
></LI
><LI
><P
> Re-allow duplicate table aliases if they're within aliased JOINs
(Tom Lane)
</P
><P
> Historically <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> has accepted queries like
</P><PRE
CLASS="PROGRAMLISTING"
>SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z</PRE
><P>
although a strict reading of the SQL standard would forbid the
duplicate usage of table alias <TT
CLASS="LITERAL"
>x</TT
>. A misguided change in
9.3.0 caused it to reject some such cases that were formerly accepted.
Restore the previous behavior.
</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 incorrect planning in cases where the same non-strict expression
appears in multiple <TT
CLASS="LITERAL"
>WHERE</TT
> and outer <TT
CLASS="LITERAL"
>JOIN</TT
>
equality clauses (Tom Lane)
</P
></LI
><LI
><P
> Fix planner crash with whole-row reference to a subquery (Tom Lane)
</P
></LI
><LI
><P
> Fix incorrect generation of optimized MIN()/MAX() plans for
inheritance trees (Tom Lane)
</P
><P
> The planner could fail in cases where the MIN()/MAX() argument was an
expression rather than a simple variable.
</P
></LI
><LI
><P
> Fix premature deletion of temporary files (Andres Freund)
</P
></LI
><LI
><P
> Prevent intra-transaction memory leak when printing range values
(Tom Lane)
</P
><P
> This fix actually cures transient memory leaks in any datatype output
function, but range types are the only ones known to have had a
significant problem.
</P
></LI
><LI
><P
> Fix memory leaks when reloading configuration files (Heikki
Linnakangas, Hari Babu)
</P
></LI
><LI
><P
> Prevent incorrect display of dropped columns in NOT NULL and CHECK
constraint violation messages (Michael Paquier and Tom Lane)
</P
></LI
><LI
><P
> Allow default arguments and named-argument notation for window
functions (Tom Lane)
</P
><P
> Previously, these cases were likely to crash.
</P
></LI
><LI
><P
> Suppress trailing whitespace on each line when pretty-printing rules
and views (Tom Lane)
</P
><P
> 9.3.0 generated such whitespace in many more cases than previous
versions did. To reduce unexpected behavioral changes, suppress
unnecessary whitespace in all cases.
</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
> Return a valid JSON value when converting an empty <TT
CLASS="TYPE"
>hstore</TT
> value
to <TT
CLASS="TYPE"
>json</TT
>
(Oskari Saarenmaa)
</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"
>pg_isready</SPAN
> to handle its <TT
CLASS="OPTION"
>-d</TT
> option
properly (Fabrízio de Royes Mello and Fujii Masao)
</P
></LI
><LI
><P
> Fix parsing of WAL file names in <SPAN
CLASS="APPLICATION"
>pg_receivexlog</SPAN
>
(Heikki Linnakangas)
</P
><P
> This error made <SPAN
CLASS="APPLICATION"
>pg_receivexlog</SPAN
> unable to restart
streaming after stopping, once at least 4 GB of WAL had been written.
</P
></LI
><LI
><P
> Report out-of-disk-space failures properly
in <SPAN
CLASS="APPLICATION"
>pg_upgrade</SPAN
> (Peter Eisentraut)
</P
></LI
><LI
><P
> Make <SPAN
CLASS="APPLICATION"
>ecpg</SPAN
> search for quoted cursor names
case-sensitively (Zoltán Böszörményi)
</P
></LI
><LI
><P
> Fix <SPAN
CLASS="APPLICATION"
>ecpg</SPAN
>'s processing of lists of variables
declared <TT
CLASS="TYPE"
>varchar</TT
> (Zoltán Böszörmé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-9-3-3.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-1.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Release 9.3.3</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.1</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
