<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Release 9.1.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.3.9 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="Release Notes"
HREF="release.html"><LINK
REL="PREVIOUS"
TITLE="Release 9.1.5"
HREF="release-9-1-5.html"><LINK
REL="NEXT"
TITLE="Release 9.1.3"
HREF="release-9-1-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="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.1.5"
HREF="release-9-1-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.1.3"
HREF="release-9-1-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-1-4"
>E.39. Release 9.1.4</A
></H1
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Release Date: </B
>2012-06-04</P
></BLOCKQUOTE
></DIV
><P
> This release contains a variety of fixes from 9.1.3.
For information about new features in the 9.1 major release, see
<A
HREF="release-9-1.html"
>Section E.43</A
>.
</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN122437"
>E.39.1. Migration to Version 9.1.4</A
></H2
><P
> A dump/restore is not required for those running 9.1.X.
</P
><P
> However, if you use the <TT
CLASS="TYPE"
>citext</TT
> data type, and you upgraded
from a previous major release by running <SPAN
CLASS="APPLICATION"
>pg_upgrade</SPAN
>,
you should run <TT
CLASS="LITERAL"
>CREATE EXTENSION citext FROM unpackaged</TT
>
to avoid collation-related failures in <TT
CLASS="TYPE"
>citext</TT
> operations.
The same is necessary if you restore a dump from a pre-9.1 database
that contains an instance of the <TT
CLASS="TYPE"
>citext</TT
> data type.
If you've already run the <TT
CLASS="COMMAND"
>CREATE EXTENSION</TT
> command before
upgrading to 9.1.4, you will instead need to do manual catalog updates
as explained in the third changelog item below.
</P
><P
> Also, if you are upgrading from a version earlier than 9.1.2,
see <A
HREF="release-9-1-2.html"
>Section E.41</A
>.
</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN122449"
>E.39.2. Changes</A
></H2
><P
></P
><UL
><LI
><P
> Fix incorrect password transformation in
<TT
CLASS="FILENAME"
>contrib/pgcrypto</TT
>'s DES <CODE
CLASS="FUNCTION"
>crypt()</CODE
> function
(Solar Designer)
</P
><P
> If a password string contained the byte value <TT
CLASS="LITERAL"
>0x80</TT
>, the
remainder of the password was ignored, causing the password to be much
weaker than it appeared. With this fix, the rest of the string is
properly included in the DES hash. Any stored password values that are
affected by this bug will thus no longer match, so the stored values may
need to be updated. (CVE-2012-2143)
</P
></LI
><LI
><P
> Ignore <TT
CLASS="LITERAL"
>SECURITY DEFINER</TT
> and <TT
CLASS="LITERAL"
>SET</TT
> attributes for
a procedural language's call handler (Tom Lane)
</P
><P
> Applying such attributes to a call handler could crash the server.
(CVE-2012-2655)
</P
></LI
><LI
><P
> Make <TT
CLASS="FILENAME"
>contrib/citext</TT
>'s upgrade script fix collations of
<TT
CLASS="TYPE"
>citext</TT
> arrays and domains over <TT
CLASS="TYPE"
>citext</TT
>
(Tom Lane)
</P
><P
> Release 9.1.2 provided a fix for collations of <TT
CLASS="TYPE"
>citext</TT
> columns
and indexes in databases upgraded or reloaded from pre-9.1
installations, but that fix was incomplete: it neglected to handle arrays
and domains over <TT
CLASS="TYPE"
>citext</TT
>. This release extends the module's
upgrade script to handle these cases. As before, if you have already
run the upgrade script, you'll need to run the collation update
commands by hand instead. See the 9.1.2 release notes for more
information about doing this.
</P
></LI
><LI
><P
> Allow numeric timezone offsets in <TT
CLASS="TYPE"
>timestamp</TT
> input to be up to
16 hours away from UTC (Tom Lane)
</P
><P
> Some historical time zones have offsets larger than 15 hours, the
previous limit. This could result in dumped data values being rejected
during reload.
</P
></LI
><LI
><P
> Fix timestamp conversion to cope when the given time is exactly the
last DST transition time for the current timezone (Tom Lane)
</P
><P
> This oversight has been there a long time, but was not noticed
previously because most DST-using zones are presumed to have an
indefinite sequence of future DST transitions.
</P
></LI
><LI
><P
> Fix <TT
CLASS="TYPE"
>text</TT
> to <TT
CLASS="TYPE"
>name</TT
> and <TT
CLASS="TYPE"
>char</TT
> to <TT
CLASS="TYPE"
>name</TT
>
casts to perform string truncation correctly in multibyte encodings
(Karl Schnaitter)
</P
></LI
><LI
><P
> Fix memory copying bug in <CODE
CLASS="FUNCTION"
>to_tsquery()</CODE
> (Heikki Linnakangas)
</P
></LI
><LI
><P
> Ensure <CODE
CLASS="FUNCTION"
>txid_current()</CODE
> reports the correct epoch when
executed in hot standby (Simon Riggs)
</P
></LI
><LI
><P
> Fix planner's handling of outer PlaceHolderVars within subqueries (Tom
Lane)
</P
><P
> This bug concerns sub-SELECTs that reference variables coming from the
nullable side of an outer join of the surrounding query.
In 9.1, queries affected by this bug would fail with <SPAN
CLASS="QUOTE"
>"ERROR:
Upper-level PlaceHolderVar found where not expected"</SPAN
>. But in 9.0 and
8.4, you'd silently get possibly-wrong answers, since the value
transmitted into the subquery wouldn't go to null when it should.
</P
></LI
><LI
><P
> Fix planning of <TT
CLASS="LITERAL"
>UNION ALL</TT
> subqueries with output columns
that are not simple variables (Tom Lane)
</P
><P
> Planning of such cases got noticeably worse in 9.1 as a result of a
misguided fix for <SPAN
CLASS="QUOTE"
>"MergeAppend child's targetlist doesn't match
MergeAppend"</SPAN
> errors. Revert that fix and do it another way.
</P
></LI
><LI
><P
> Fix slow session startup when <TT
CLASS="STRUCTNAME"
>pg_attribute</TT
> is very large
(Tom Lane)
</P
><P
> If <TT
CLASS="STRUCTNAME"
>pg_attribute</TT
> exceeds one-fourth of
<TT
CLASS="VARNAME"
>shared_buffers</TT
>, cache rebuilding code that is sometimes
needed during session start would trigger the synchronized-scan logic,
causing it to take many times longer than normal. The problem was
particularly acute if many new sessions were starting at once.
</P
></LI
><LI
><P
> Ensure sequential scans check for query cancel reasonably often (Merlin
Moncure)
</P
><P
> A scan encountering many consecutive pages that contain no live tuples
would not respond to interrupts meanwhile.
</P
></LI
><LI
><P
> Ensure the Windows implementation of <CODE
CLASS="FUNCTION"
>PGSemaphoreLock()</CODE
>
clears <TT
CLASS="VARNAME"
>ImmediateInterruptOK</TT
> before returning (Tom Lane)
</P
><P
> This oversight meant that a query-cancel interrupt received later
in the same query could be accepted at an unsafe time, with
unpredictable but not good consequences.
</P
></LI
><LI
><P
> Show whole-row variables safely when printing views or rules
(Abbas Butt, Tom Lane)
</P
><P
> Corner cases involving ambiguous names (that is, the name could be
either a table or column name of the query) were printed in an
ambiguous way, risking that the view or rule would be interpreted
differently after dump and reload. Avoid the ambiguous case by
attaching a no-op cast.
</P
></LI
><LI
><P
> Fix <TT
CLASS="COMMAND"
>COPY FROM</TT
> to properly handle null marker strings that
correspond to invalid encoding (Tom Lane)
</P
><P
> A null marker string such as <TT
CLASS="LITERAL"
>E'\\0'</TT
> should work, and did
work in the past, but the case got broken in 8.4.
</P
></LI
><LI
><P
> Fix <TT
CLASS="COMMAND"
>EXPLAIN VERBOSE</TT
> for writable CTEs containing
<TT
CLASS="LITERAL"
>RETURNING</TT
> clauses (Tom Lane)
</P
></LI
><LI
><P
> Fix <TT
CLASS="COMMAND"
>PREPARE TRANSACTION</TT
> to work correctly in the presence
of advisory locks (Tom Lane)
</P
><P
> Historically, <TT
CLASS="COMMAND"
>PREPARE TRANSACTION</TT
> has simply ignored any
session-level advisory locks the session holds, but this case was
accidentally broken in 9.1.
</P
></LI
><LI
><P
> Fix truncation of unlogged tables (Robert Haas)
</P
></LI
><LI
><P
> Ignore missing schemas during non-interactive assignments of
<TT
CLASS="VARNAME"
>search_path</TT
> (Tom Lane)
</P
><P
> This re-aligns 9.1's behavior with that of older branches. Previously
9.1 would throw an error for nonexistent schemas mentioned in
<TT
CLASS="VARNAME"
>search_path</TT
> settings obtained from places such as
<TT
CLASS="COMMAND"
>ALTER DATABASE SET</TT
>.
</P
></LI
><LI
><P
> Fix bugs with temporary or transient tables used in extension scripts
(Tom Lane)
</P
><P
> This includes cases such as a rewriting <TT
CLASS="COMMAND"
>ALTER TABLE</TT
> within
an extension update script, since that uses a transient table behind
the scenes.
</P
></LI
><LI
><P
> Ensure autovacuum worker processes perform stack depth checking
properly (Heikki Linnakangas)
</P
><P
> Previously, infinite recursion in a function invoked by
auto-<TT
CLASS="COMMAND"
>ANALYZE</TT
> could crash worker processes.
</P
></LI
><LI
><P
> Fix logging collector to not lose log coherency under high load (Andrew
Dunstan)
</P
><P
> The collector previously could fail to reassemble large messages if it
got too busy.
</P
></LI
><LI
><P
> Fix logging collector to ensure it will restart file rotation
after receiving <SPAN
CLASS="SYSTEMITEM"
>SIGHUP</SPAN
> (Tom Lane)
</P
></LI
><LI
><P
> Fix <SPAN
CLASS="QUOTE"
>"too many LWLocks taken"</SPAN
> failure in GiST indexes (Heikki
Linnakangas)
</P
></LI
><LI
><P
> Fix WAL replay logic for GIN indexes to not fail if the index was
subsequently dropped (Tom Lane)
</P
></LI
><LI
><P
> Correctly detect SSI conflicts of prepared transactions after a crash
(Dan Ports)
</P
></LI
><LI
><P
> Avoid synchronous replication delay when committing a transaction that
only modified temporary tables (Heikki Linnakangas)
</P
><P
> In such a case the transaction's commit record need not be flushed to
standby servers, but some of the code didn't know that and waited for
it to happen anyway.
</P
></LI
><LI
><P
> Fix error handling in <SPAN
CLASS="APPLICATION"
>pg_basebackup</SPAN
>
(Thomas Ogrisegg, Fujii Masao)
</P
></LI
><LI
><P
> Fix <SPAN
CLASS="APPLICATION"
>walsender</SPAN
> to not go into a busy loop if connection
is terminated (Fujii Masao)
</P
></LI
><LI
><P
> Fix memory leak in PL/pgSQL's <TT
CLASS="COMMAND"
>RETURN NEXT</TT
> command (Joe
Conway)
</P
></LI
><LI
><P
> Fix PL/pgSQL's <TT
CLASS="COMMAND"
>GET DIAGNOSTICS</TT
> command when the target
is the function's first variable (Tom Lane)
</P
></LI
><LI
><P
> Ensure that PL/Perl package-qualifies the <TT
CLASS="VARNAME"
>_TD</TT
> variable
(Alex Hunsaker)
</P
><P
> This bug caused trigger invocations to fail when they are nested
within a function invocation that changes the current package.
</P
></LI
><LI
><P
> Fix PL/Python functions returning composite types to accept a string
for their result value (Jan Urbanski)
</P
><P
> This case was accidentally broken by the 9.1 additions to allow a
composite result value to be supplied in other formats, such as
dictionaries.
</P
></LI
><LI
><P
> Fix potential access off the end of memory in <SPAN
CLASS="APPLICATION"
>psql</SPAN
>'s
expanded display (<TT
CLASS="COMMAND"
>\x</TT
>) mode (Peter Eisentraut)
</P
></LI
><LI
><P
> Fix several performance problems in <SPAN
CLASS="APPLICATION"
>pg_dump</SPAN
> when
the database contains many objects (Jeff Janes, Tom Lane)
</P
><P
> <SPAN
CLASS="APPLICATION"
>pg_dump</SPAN
> could get very slow if the database contained
many schemas, or if many objects are in dependency loops, or if there
are many owned sequences.
</P
></LI
><LI
><P
> Fix memory and file descriptor leaks in <SPAN
CLASS="APPLICATION"
>pg_restore</SPAN
>
when reading a directory-format archive (Peter Eisentraut)
</P
></LI
><LI
><P
> Fix <SPAN
CLASS="APPLICATION"
>pg_upgrade</SPAN
> for the case that a database stored in a
non-default tablespace contains a table in the cluster's default
tablespace (Bruce Momjian)
</P
></LI
><LI
><P
> In <SPAN
CLASS="APPLICATION"
>ecpg</SPAN
>, fix rare memory leaks and possible overwrite
of one byte after the <TT
CLASS="STRUCTNAME"
>sqlca_t</TT
> structure (Peter Eisentraut)
</P
></LI
><LI
><P
> Fix <TT
CLASS="FILENAME"
>contrib/dblink</TT
>'s <CODE
CLASS="FUNCTION"
>dblink_exec()</CODE
> to not leak
temporary database connections upon error (Tom Lane)
</P
></LI
><LI
><P
> Fix <TT
CLASS="FILENAME"
>contrib/dblink</TT
> to report the correct connection name in
error messages (Kyotaro Horiguchi)
</P
></LI
><LI
><P
> Fix <TT
CLASS="FILENAME"
>contrib/vacuumlo</TT
> to use multiple transactions when
dropping many large objects (Tim Lewis, Robert Haas, Tom Lane)
</P
><P
> This change avoids exceeding <TT
CLASS="VARNAME"
>max_locks_per_transaction</TT
> when
many objects need to be dropped. The behavior can be adjusted with the
new <TT
CLASS="LITERAL"
>-l</TT
> (limit) option.
</P
></LI
><LI
><P
> Update time zone data files to <SPAN
CLASS="APPLICATION"
>tzdata</SPAN
> release 2012c
for DST law changes in Antarctica, Armenia, Chile, Cuba, Falkland
Islands, Gaza, Haiti, Hebron, Morocco, Syria, and Tokelau Islands;
also historical corrections for Canada.
</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-1-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-1-3.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Release 9.1.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.1.3</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
