Release Date: 2005-10-04
This release contains a variety of fixes from 7.4.8. For information about new features in the 7.4 major release, see Section E.209.
A dump/restore is not required for those running 7.4.X. However, if you are upgrading from a version earlier than 7.4.8, see Section E.201.
Fix error that allowed VACUUM to remove ctid chains too soon, and add more checking in code that follows ctid links
This fixes a long-standing problem that could cause crashes in very rare circumstances.
Fix CHAR() to properly pad spaces to the specified length when using a multiple-byte character set (Yoshiyuki Asaba)
In prior releases, the padding of CHAR() was incorrect because it only padded to the specified number of bytes without considering how many characters were stored.
Fix the sense of the test for read-only transaction in COPY
The code formerly prohibited COPY TO, where it should prohibit COPY FROM.
Fix planning problem with outer-join ON clauses that reference only the inner-side relation
Further fixes for x FULL JOIN y ON true corner cases
array_recv more paranoid
about validating their OID parameter
Fix missing rows in queries like UPDATE a=... WHERE a... with GiST index on column a
Improve robustness of datetime parsing
Improve checking for partially-written WAL pages
Improve robustness of signal handling when SSL is enabled
Don't try to open more than max_files_per_process files during postmaster startup
Various memory leakage fixes
Various portability improvements
Fix PL/pgSQL to handle var := var correctly when the variable is of pass-by-reference type
Update contrib/tsearch2 to use current Snowball code
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.