Release Date: 2004-03-02
This release contains a variety of fixes from 7.3.5.
A dump/restore is not required for those running 7.3.*.
Revert erroneous changes in rule permissions checking
A patch applied in 7.3.3 to fix a corner case in rule permissions checks turns out to have disabled rule-related permissions checks in many not-so-corner cases. This would for example allow users to insert into views they weren't supposed to have permission to insert into. We have therefore reverted the 7.3.3 patch. The original bug will be fixed in 8.0.
Repair incorrect order of operations in GetNewTransactionId()
This bug could result in failure under out-of-disk-space conditions, including inability to restart even after disk space is freed.
Ensure configure selects -fno-strict-aliasing even when an external value for CFLAGS is supplied
On some platforms, building with -fstrict-aliasing causes bugs.
Make pg_restore handle 64-bit off_t correctly
This bug prevented proper restoration from archive files exceeding 4 GB.
Make contrib/dblink not assume that local and remote type OIDs match (Joe)
Quote connectby()'s start_with argument properly (Joe)
Don't crash when a rowtype argument to a plpgsql function is NULL
Avoid generating invalid character encoding sequences in corner cases when planning LIKE operations
Ensure text_position() cannot scan past end of source string in multibyte cases (Korea PostgreSQL Users' Group)
Fix index optimization and selectivity estimates for LIKE operations on bytea columns (Joe)
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.