This page in other versions: 9.0 / 9.1 / 9.2 / 9.3 / 9.4  |  Development versions: devel  |  Unsupported versions: 8.1 / 8.2 / 8.3 / 8.4

E.137. Release 8.1.14

Release Date: 2008-09-22

This release contains a variety of fixes from 8.1.13. For information about new features in the 8.1 major release, see Section E.151.

E.137.1. Migration to Version 8.1.14

A dump/restore is not required for those running 8.1.X. However, if you are upgrading from a version earlier than 8.1.2, see Section E.149.

E.137.2. Changes

  • Widen local lock counters from 32 to 64 bits (Tom)

    This responds to reports that the counters could overflow in sufficiently long transactions, leading to unexpected "lock is already held" errors.

  • Fix possible duplicate output of tuples during a GiST index scan (Teodor)

  • Add checks in executor startup to ensure that the tuples produced by an INSERT or UPDATE will match the target table's current rowtype (Tom)

    ALTER COLUMN TYPE, followed by re-use of a previously cached plan, could produce this type of situation. The check protects against data corruption and/or crashes that could ensue.

  • Fix AT TIME ZONE to first try to interpret its timezone argument as a timezone abbreviation, and only try it as a full timezone name if that fails, rather than the other way around as formerly (Tom)

    The timestamp input functions have always resolved ambiguous zone names in this order. Making AT TIME ZONE do so as well improves consistency, and fixes a compatibility bug introduced in 8.1: in ambiguous cases we now behave the same as 8.0 and before did, since in the older versions AT TIME ZONE accepted only abbreviations.

  • Fix datetime input functions to correctly detect integer overflow when running on a 64-bit platform (Tom)

  • Improve performance of writing very long log messages to syslog (Tom)

  • Fix bug in backwards scanning of a cursor on a SELECT DISTINCT ON query (Tom)

  • Fix planner bug with nested sub-select expressions (Tom)

    If the outer sub-select has no direct dependency on the parent query, but the inner one does, the outer value might not get recalculated for new parent query rows.

  • Fix planner to estimate that GROUP BY expressions yielding boolean results always result in two groups, regardless of the expressions' contents (Tom)

    This is very substantially more accurate than the regular GROUP BY estimate for certain boolean tests like col IS NULL.

  • Fix PL/pgSQL to not fail when a FOR loop's target variable is a record containing composite-type fields (Tom)

  • Fix PL/Tcl to behave correctly with Tcl 8.5, and to be more careful about the encoding of data sent to or from Tcl (Tom)

  • Fix PL/Python to work with Python 2.5

    This is a back-port of fixes made during the 8.2 development cycle.

  • Improve pg_dump and pg_restore's error reporting after failure to send a SQL command (Tom)

  • Fix pg_ctl to properly preserve postmaster command-line arguments across a restart (Bruce)

  • Update time zone data files to tzdata release 2008f (for DST law changes in Argentina, Bahamas, Brazil, Mauritius, Morocco, Pakistan, Palestine, and Paraguay)

Add Comment

Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.

Proceed to the comment form.

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group