Release date: 2012-06-04
This release contains a variety of fixes from 9.1.3. For information about new features in the 9.1 major release, see Section E.132.
A dump/restore is not required for those running 9.1.X.
However, if you use the
type, and you upgraded from a previous major release by running
pg_upgrade, you should run
CREATE EXTENSION citext FROM
unpackaged to avoid collation-related failures in
citext operations. The same is necessary
if you restore a dump from a pre-9.1 database that contains an
instance of the
citext data type. If
you've already run the
EXTENSION command before upgrading to 9.1.4, you will
instead need to do manual catalog updates as explained in the third
changelog item below.
Also, if you are upgrading from a version earlier than 9.1.2, see Section E.130.
Fix incorrect password transformation in
crypt() function (Solar Designer)
If a password string contained the byte value
0x80, 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.
SECURITY DEFINER and
SET attributes for a procedural
language's call handler (Tom Lane)
Applying such attributes to a call handler could crash the server. (CVE-2012-2655)
script fix collations of
and domains over
citext (Tom Lane)
Release 9.1.2 provided a fix for collations of
citext 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
citext. 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.
Allow numeric timezone offsets in
timestamp input to be up to 16 hours away from UTC
Some historical time zones have offsets larger than 15 hours, the previous limit. This could result in dumped data values being rejected during reload.
Fix timestamp conversion to cope when the given time is exactly the last DST transition time for the current timezone (Tom Lane)
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.
name casts to perform string truncation
correctly in multibyte encodings (Karl Schnaitter)
Fix memory copying bug in
to_tsquery() (Heikki Linnakangas)
txid_current() reports the
correct epoch when executed in hot standby (Simon Riggs)
Fix planner's handling of outer PlaceHolderVars within subqueries (Tom Lane)
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 “ERROR: Upper-level PlaceHolderVar found where not expected”. 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.
Fix planning of
subqueries with output columns that are not simple variables (Tom
Planning of such cases got noticeably worse in 9.1 as a result of a misguided fix for “MergeAppend child's targetlist doesn't match MergeAppend” errors. Revert that fix and do it another way.
Fix slow session startup when
pg_attribute is very large (Tom Lane)
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.
Ensure sequential scans check for query cancel reasonably often (Merlin Moncure)
A scan encountering many consecutive pages that contain no live tuples would not respond to interrupts meanwhile.
Ensure the Windows implementation of
ImmediateInterruptOK before returning (Tom
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.
Show whole-row variables safely when printing views or rules (Abbas Butt, Tom Lane)
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.
COPY FROM to properly handle
null marker strings that correspond to invalid encoding (Tom
A null marker string such as
should work, and did work in the past, but the case got broken in
EXPLAIN VERBOSE for writable
RETURNING clauses (Tom
PREPARE TRANSACTION to work
correctly in the presence of advisory locks (Tom Lane)
has simply ignored any session-level advisory locks the session
holds, but this case was accidentally broken in 9.1.
Fix truncation of unlogged tables (Robert Haas)
Ignore missing schemas during non-interactive assignments of
search_path (Tom Lane)
This re-aligns 9.1's behavior with that of older branches.
Previously 9.1 would throw an error for nonexistent schemas
obtained from places such as
Fix bugs with temporary or transient tables used in extension scripts (Tom Lane)
This includes cases such as a rewriting
ALTER TABLE within an extension update script,
since that uses a transient table behind the scenes.
Ensure autovacuum worker processes perform stack depth checking properly (Heikki Linnakangas)
Previously, infinite recursion in a function invoked by
ANALYZE could crash worker
Fix logging collector to not lose log coherency under high load (Andrew Dunstan)
The collector previously could fail to reassemble large messages if it got too busy.
Fix logging collector to ensure it will restart file rotation after receiving SIGHUP (Tom Lane)
Fix “too many LWLocks taken” failure in GiST indexes (Heikki Linnakangas)
Fix WAL replay logic for GIN indexes to not fail if the index was subsequently dropped (Tom Lane)
Correctly detect SSI conflicts of prepared transactions after a crash (Dan Ports)
Avoid synchronous replication delay when committing a transaction that only modified temporary tables (Heikki Linnakangas)
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.
Fix error handling in pg_basebackup (Thomas Ogrisegg, Fujii Masao)
Fix walsender to not go into a busy loop if connection is terminated (Fujii Masao)
Fix memory leak in PL/pgSQL's
NEXT command (Joe Conway)
command when the target is the function's first variable (Tom
Ensure that PL/Perl package-qualifies the
_TD variable (Alex Hunsaker)
This bug caused trigger invocations to fail when they are nested within a function invocation that changes the current package.
Fix PL/Python functions returning composite types to accept a string for their result value (Jan Urbanski)
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.
Fix potential access off the end of memory in psql's expanded display (
\x) mode (Peter Eisentraut)
Fix several performance problems in pg_dump when the database contains many objects (Jeff Janes, Tom Lane)
pg_dump 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.
Fix memory and file descriptor leaks in pg_restore when reading a directory-format archive (Peter Eisentraut)
Fix pg_upgrade for the case that a database stored in a non-default tablespace contains a table in the cluster's default tablespace (Bruce Momjian)
In ecpg, fix rare memory leaks
and possible overwrite of one byte after the
sqlca_t structure (Peter Eisentraut)
dblink_exec() to not leak temporary database
connections upon error (Tom Lane)
contrib/dblink to report the
correct connection name in error messages (Kyotaro Horiguchi)
contrib/vacuumlo to use
multiple transactions when dropping many large objects (Tim Lewis,
Robert Haas, Tom Lane)
This change avoids exceeding
max_locks_per_transaction when many objects need
to be dropped. The behavior can be adjusted with the new
-l (limit) option.
Update time zone data files to tzdata 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.
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.