Supported Versions: Current (16) / 15 / 14 / 13 / 12
Development Versions: 17 / devel
Unsupported versions: 11 / 10 / 9.6 / 9.5 / 9.4 / 9.3 / 9.2 / 9.1 / 9.0 / 8.4 / 8.3 / 8.2 / 8.1 / 8.0 / 7.4 / 7.3 / 7.2 / 7.1
This documentation is for an unsupported version of PostgreSQL.
You may want to view the same page for the current version, or one of the other supported versions listed above instead.

Appendix E. Release Notes

Table of Contents
E.1. Release 7.4.30
E.2. Release 7.4.29
E.3. Release 7.4.28
E.4. Release 7.4.27
E.5. Release 7.4.26
E.6. Release 7.4.25
E.7. Release 7.4.24
E.8. Release 7.4.23
E.9. Release 7.4.22
E.10. Release 7.4.21
E.11. Release 7.4.20
E.12. Release 7.4.19
E.13. Release 7.4.18
E.14. Release 7.4.17
E.15. Release 7.4.16
E.16. Release 7.4.15
E.17. Release 7.4.14
E.18. Release 7.4.13
E.19. Release 7.4.12
E.20. Release 7.4.11
E.21. Release 7.4.10
E.22. Release 7.4.9
E.23. Release 7.4.8
E.24. Release 7.4.7
E.25. Release 7.4.6
E.26. Release 7.4.5
E.27. Release 7.4.4
E.28. Release 7.4.3
E.29. Release 7.4.2
E.30. Release 7.4.1
E.31. Release 7.4
E.32. Release 7.3.21
E.33. Release 7.3.20
E.34. Release 7.3.19
E.35. Release 7.3.18
E.36. Release 7.3.17
E.37. Release 7.3.16
E.38. Release 7.3.15
E.39. Release 7.3.14
E.40. Release 7.3.13
E.41. Release 7.3.12
E.42. Release 7.3.11
E.43. Release 7.3.10
E.44. Release 7.3.9
E.45. Release 7.3.8
E.46. Release 7.3.7
E.47. Release 7.3.6
E.48. Release 7.3.5
E.49. Release 7.3.4
E.50. Release 7.3.3
E.51. Release 7.3.2
E.52. Release 7.3.1
E.53. Release 7.3
E.54. Release 7.2.8
E.55. Release 7.2.7
E.56. Release 7.2.6
E.57. Release 7.2.5
E.58. Release 7.2.4
E.59. Release 7.2.3
E.60. Release 7.2.2
E.61. Release 7.2.1
E.62. Release 7.2
E.63. Release 7.1.3
E.64. Release 7.1.2
E.65. Release 7.1.1
E.66. Release 7.1
E.67. Release 7.0.3
E.68. Release 7.0.2
E.69. Release 7.0.1
E.70. Release 7.0
E.71. Release 6.5.3
E.72. Release 6.5.2
E.73. Release 6.5.1
E.74. Release 6.5
E.75. Release 6.4.2
E.76. Release 6.4.1
E.77. Release 6.4
E.78. Release 6.3.2
E.79. Release 6.3.1
E.80. Release 6.3
E.81. Release 6.2.1
E.82. Release 6.2
E.83. Release 6.1.1
E.84. Release 6.1
E.85. Release 6.0
E.86. Release 1.09
E.87. Release 1.02
E.88. Release 1.01
E.89. Release 1.0
E.90. Postgres95 Release 0.03
E.91. Postgres95 Release 0.02
E.92. Postgres95 Release 0.01

The release notes contain the significant changes in each PostgreSQL release, with major features and migration issues listed at the top. The release notes do not contain changes that affect only a few users or changes that are internal and therefore not user-visible. For example, the optimizer is improved in almost every release, but the improvements are usually observed by users as simply faster queries.

A complete list of changes for each release can be obtained by viewing the Git logs for each release. The pgsql-committers email list records all source code changes as well. There is also a web interface that shows changes to specific files.

The name appearing next to each item represents the major developer for that item. Of course all changes involve community discussion and patch review, so each item is truly a community effort.

E.1. Release 7.4.30

Release date: 2010-10-04

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

This is expected to be the last PostgreSQL release in the 7.4.X series. Users are encouraged to update to a newer release branch soon.

E.1.1. Migration to Version 7.4.30

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 the release notes for 7.4.26.

E.1.2. Changes

  • 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)

  • 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.

  • Take care to fsync the contents of lockfiles (both 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.

  • Improve contrib/dblink's handling of tables containing dropped columns (Tom Lane)

  • Fix connection leak after "duplicate connection name" errors in contrib/dblink (Itagaki Takahiro)

  • Update build infrastructure and documentation to reflect the source code repository's move from CVS to Git (Magnus Hagander and others)