Release date: 2010-05-17
This release contains a variety of fixes from 7.4.28. For information about new features in the 7.4 major release, see Section E.304.
The PostgreSQL community will stop releasing updates for the 7.4.X release series in July 2010. Users are encouraged to update to a newer release branch soon.
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.278.
Enforce restrictions in
using an opmask applied to the whole interpreter, instead of using
Safe.pm (Tim Bunce, Andrew
Recent developments have convinced us that
Safe.pm is too insecure to rely on for making
plperl trustable. This change removes
Safe.pm altogether, in favor
of using a separate interpreter with an opcode mask that is always
applied. Pleasant side effects of the change include that it is now
possible to use Perl's
in a natural way in
plperl, and that
$b variables work as expected in sort routines,
and that function compilation is significantly faster.
Prevent PL/Tcl from executing untrustworthy code from
PL/Tcl's feature for autoloading Tcl code from a database table
could be exploited for trojan-horse attacks, because there was no
restriction on who could create or insert into that table. This
change disables the feature unless
pltcl_modules is owned by a superuser.
(However, the permissions on the table are not checked, so
installations that really need a less-than-secure modules table can
still grant suitable privileges to trusted non-superusers.) Also,
prevent loading code into the unrestricted “normal” Tcl interpreter
unless we are really going to execute a
pltclu function. (CVE-2010-1170)
Do not allow an unprivileged user to reset superuser-only parameter settings (Alvaro)
Previously, if an unprivileged user ran
ALTER USER ... RESET ALL for himself, or
ALTER DATABASE ... RESET ALL for a
database he owns, this would remove all special parameter settings
for the user or database, even ones that are only supposed to be
changeable by a superuser. Now, the
ALTER will only remove the parameters that the
user has permission to change.
Avoid possible crash during backend shutdown if shutdown occurs
CONTEXT addition would be made
to log entries (Tom)
In some cases the context-printing function would fail because the current transaction had already been rolled back when it came time to print a log message.
modern Perl versions (Andrew)
Fix assorted memory leaks in PL/Python (Andreas Freund, Tom)
functions respond to cancel interrupts promptly (Tatsuhito
Make server startup deal properly with the case that
EINVAL for an existing shared memory segment
This behavior has been observed on BSD-derived kernels including macOS. It resulted in an entirely-misleading startup failure complaining that the shared memory request size was too large.
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.