Release date: 2006-02-14
This release contains a variety of fixes from 8.0.6. For information about new features in the 8.0 major release, see Section E.274.
A dump/restore is not required for those running 8.0.X. However, if you are upgrading from a version earlier than 8.0.6, see Section E.268.
Fix potential crash in
SESSION AUTHORIZATION (CVE-2006-0553)
An unprivileged user could crash the server process, resulting in momentary denial of service to other users, if the server has been compiled with Asserts enabled (which is not the default). Thanks to Akio Ishida for reporting this problem.
Fix bug with row visibility logic in self-inserted rows (Tom)
Under rare circumstances a row inserted by the current command could be seen as already valid, when it should not be. Repairs bug created in 8.0.4, 7.4.9, and 7.3.11 releases.
Fix race condition that could lead to “file already exists” errors during pg_clog and pg_subtrans file creation (Tom)
Fix cases that could lead to crashes if a cache-invalidation message arrives at just the wrong time (Tom)
parameters in prepared statements (Neil)
ALTER COLUMN TYPE
PRIMARY KEY constraints in the proper
order (Nakano Yoshihisa)
Fixes to allow restoring dumps that have cross-schema references to custom operators or operator classes (Tom)
Allow pg_restore to
continue properly after a
COPY failure; formerly it tried to treat
COPY data as
SQL commands (Stephen Frost)
unregister crash when the
data directory is not specified (Magnus)
Fix ecpg crash on AMD64 and PPC (Neil)
Recover properly if error occurs during argument passing in PL/Python (Neil)
Fix PL/Perl's handling of locales on Win32 to match the backend (Andrew)
Fix crash when
log_min_messages is set to
DEBUG3 or above in
postgresql.conf on Win32 (Bruce)
-L library path specification for Win32,
Cygwin, macOS, AIX (Bruce)
Check that SID is enabled while checking for Win32 admin privileges (Magnus)
Properly reject out-of-range date inputs (Kris Jurka)
Portability fix for testing presence of
isinf during configure (Tom)
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.