This page in other versions: 9.1 / 9.2 / 9.3 / 9.4 / current (9.5)  |  Development versions: devel  |  Unsupported versions: 7.4 / 8.0 / 8.1 / 8.2 / 8.3 / 8.4 / 9.0

E.213. Release 7.4.27

Release Date: 2009-12-14

This release contains a variety of fixes from 7.4.26. For information about new features in the 7.4 major release, see Section E.240.

E.213.1. Migration to Version 7.4.27

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

E.213.2. Changes

  • Protect against indirect security threats caused by index functions changing session-local state (Gurjeet Singh, Tom)

    This change prevents allegedly-immutable index functions from possibly subverting a superuser's session (CVE-2009-4136).

  • Reject SSL certificates containing an embedded null byte in the common name (CN) field (Magnus)

    This prevents unintended matching of a certificate to a server or client name during SSL validation (CVE-2009-4034).

  • Fix possible crash during backend-startup-time cache initialization (Tom)

  • Prevent signals from interrupting VACUUM at unsafe times (Alvaro)

    This fix prevents a PANIC if a VACUUM FULL is canceled after it's already committed its tuple movements, as well as transient errors if a plain VACUUM is interrupted after having truncated the table.

  • Fix possible crash due to integer overflow in hash table size calculation (Tom)

    This could occur with extremely large planner estimates for the size of a hashjoin's result.

  • Fix very rare crash in inet/cidr comparisons (Chris Mikkelson)

  • Fix PAM password processing to be more robust (Tom)

    The previous code is known to fail with the combination of the Linux pam_krb5 PAM module with Microsoft Active Directory as the domain controller. It might have problems elsewhere too, since it was making unjustified assumptions about what arguments the PAM stack would pass to it.

  • Make the postmaster ignore any application_name parameter in connection request packets, to improve compatibility with future libpq versions (Tom)

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-2016 The PostgreSQL Global Development Group