Release date: 2010-10-04
This release contains a variety of fixes from 8.3.11. For information about new features in the 8.3 major release, see Section E.205.
A dump/restore is not required for those running 8.3.X. However, if you are upgrading from a version earlier than 8.3.8, see Section E.197.
Use a separate interpreter for each calling SQL userid in PL/Perl and PL/Tcl (Tom Lane)
This change prevents security problems that can be
caused by subverting Perl or Tcl code that will be
executed later in the same session under another SQL user
identity (for example, within a
SECURITY DEFINER function). Most
scripting languages offer numerous ways that that might
be done, such as redefining standard functions or
operators called by the target function. Without this
change, any SQL user with Perl or Tcl language usage
rights can do essentially anything with the SQL
privileges of the target function's owner.
The cost of this change is that intentional communication among Perl and Tcl functions becomes more difficult. To provide an escape hatch, PL/PerlU and PL/TclU functions continue to use only one interpreter per session. This is not considered a security issue since all such functions execute at the trust level of a database superuser already.
It is likely that third-party procedural languages that claim to offer trusted execution have similar security issues. We advise contacting the authors of any PL you are depending on for security-critical purposes.
Our thanks to Tim Bunce for pointing out this issue (CVE-2010-3433).
Prevent possible crashes in
pg_get_expr() by disallowing it from
being called with an argument that is not one of the
system catalog columns it's intended to be used with
(Heikki Linnakangas, Tom Lane)
Treat exit code 128 (
ERROR_WAIT_NO_CHILDREN) as non-fatal on
Windows (Magnus Hagander)
Under high load, Windows processes will sometimes fail at startup with this error code. Formerly the postmaster treated this as a panic condition and restarted the whole database, but that seems to be an overreaction.
Fix incorrect usage of non-strict OR joinclauses in Append indexscans (Tom Lane)
This is a back-patch of an 8.4 fix that was missed in
the 8.3 branch. This corrects an error introduced in
8.3.8 that could cause incorrect results for outer joins
when the inner relation is an inheritance tree or
UNION ALL subquery.
Fix possible duplicate scans of
UNION ALL member relations (Tom
Fix “cannot handle unplanned sub-select” error (Tom Lane)
This occurred when a sub-select contains a join alias reference that expands into an expression containing another sub-select.
Fix failure to mark cached plans as transient (Tom Lane)
If a plan is prepared while
CREATE INDEX CONCURRENTLY is in progress
for one of the referenced tables, it is supposed to be
re-planned once the index is ready for use. This was not
Reduce PANIC to ERROR in some occasionally-reported btree failure cases, and provide additional detail in the resulting error messages (Tom Lane)
This should improve the system's robustness with corrupted indexes.
Prevent show_session_authorization() from crashing within autovacuum processes (Tom Lane)
Defend against functions returning setof record where not all the returned rows are actually of the same rowtype (Tom Lane)
Fix possible failure when hashing a pass-by-reference function result (Tao Ma, Tom Lane)
Improve merge join's handling of NULLs in the join columns (Tom Lane)
A merge join can now stop entirely upon reaching the first NULL, if the sort order is such that NULLs sort high.
Take care to fsync the contents of lockfiles (both
postmaster.pid and the
socket lockfile) while writing them (Tom Lane)
This omission could result in corrupted lockfile contents if the machine crashes shortly after postmaster start. That could in turn prevent subsequent attempts to start the postmaster from succeeding, until the lockfile is manually removed.
Avoid recursion while assigning XIDs to heavily-nested subtransactions (Andres Freund, Robert Haas)
The original coding could result in a crash if there was limited stack space.
Avoid holding open old WAL segments in the walwriter process (Magnus Hagander, Heikki Linnakangas)
The previous coding would prevent removal of no-longer-needed segments.
%i escape, which could
produce junk early in backend startup (Tom Lane)
Fix possible data corruption in
ALTER TABLE ... SET TABLESPACE when
archiving is enabled (Jeff Davis)
CREATE DATABASE and
ALTER DATABASE ... SET
TABLESPACE to be interrupted by query-cancel
REASSIGN OWNED to
handle operator classes and families (Asko Tiidumaa)
Fix possible core dump when comparing two empty
tsquery values (Tom Lane)
LIKE's handling of
_ (Tom Lane)
We've fixed this before, but there were still some incorrectly-handled cases.
In PL/Python, defend against null pointer results from
Make psql recognize
ALL as a command that should not be encased in a
transaction block in autocommit-off mode (Itagaki
Fix ecpg to process
correctly (Michael Meskes)
handling of tables containing dropped columns (Tom
Fix connection leak after “duplicate connection
name” errors in
contrib/dblink (Itagaki Takahiro)
handle connection names longer than 62 bytes correctly
This function is the recommended substitute for the
operator. It was back-patched so that future-proofed code
can be used with older server versions. Note that the
patch will be effective only after
contrib/hstore is installed or
reinstalled in a particular database. Users might prefer
to execute the
FUNCTION command by hand, instead.
Update build infrastructure and documentation to reflect the source code repository's move from CVS to Git (Magnus Hagander and others)
Update time zone data files to tzdata release 2010l for DST law changes in Egypt and Palestine; also historical corrections for Finland.
This change also adds new names for two Micronesian timezones: Pacific/Chuuk is now preferred over Pacific/Truk (and the preferred abbreviation is CHUT not TRUT) and Pacific/Pohnpei is preferred over Pacific/Ponape.
Make Windows' “N. Central Asia Standard Time” timezone map to Asia/Novosibirsk, not Asia/Almaty (Magnus Hagander)
Microsoft changed the DST behavior of this zone in the timezone update from KB976098. Asia/Novosibirsk is a better match to its new behavior.
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.