Format: 1.8 Date: Sat, 25 Feb 2012 11:17:15 +0100 Source: postgresql-8.4 Binary: postgresql-8.4 postgresql-client-8.4 postgresql-server-dev-8.4 postgresql-doc-8.4 postgresql-contrib-8.4 postgresql-plperl-8.4 postgresql-plpython-8.4 postgresql-pltcl-8.4 Architecture: powerpc Version: 8.4.11-1 Distribution: precise Urgency: medium Maintainer: Ubuntu/powerpc Build Daemon Changed-By: Martin Pitt Description: postgresql-8.4 - object-relational SQL database, version 8.4 server postgresql-client-8.4 - front-end programs for PostgreSQL 8.4 postgresql-contrib-8.4 - additional facilities for PostgreSQL postgresql-doc-8.4 - documentation for the PostgreSQL database management system postgresql-plperl-8.4 - PL/Perl procedural language for PostgreSQL 8.4 postgresql-plpython-8.4 - PL/Python procedural language for PostgreSQL 8.4 postgresql-pltcl-8.4 - PL/Tcl procedural language for PostgreSQL 8.4 postgresql-server-dev-8.4 - development files for PostgreSQL 8.4 server-side programming Changes: postgresql-8.4 (8.4.11-1) unstable; urgency=medium . * Urgency medium due to security fixes. * New upstream bug fix/security release: - Require execute permission on the trigger function for "CREATE TRIGGER". This missing check could allow another user to execute a trigger function with forged input data, by installing it on a table he owns. This is only of significance for trigger functions marked SECURITY DEFINER, since otherwise trigger functions run as the table owner anyway. (CVE-2012-0866) - Remove arbitrary limitation on length of common name in SSL certificates. Both libpq and the server truncated the common name extracted from an SSL certificate at 32 bytes. Normally this would cause nothing worse than an unexpected verification failure, but there are some rather-implausible scenarios in which it might allow one certificate holder to impersonate another. The victim would have to have a common name exactly 32 bytes long, and the attacker would have to persuade a trusted CA to issue a certificate in which the common name has that string as a prefix. Impersonating a server would also require some additional exploit to redirect client connections. (CVE-2012-0867) - Convert newlines to spaces in names written in pg_dump comments. pg_dump was incautious about sanitizing object names that are emitted within SQL comments in its output script. A name containing a newline would at least render the script syntactically incorrect. Maliciously crafted object names could present a SQL injection risk when the script is reloaded. (CVE-2012-0868) - Fix btree index corruption from insertions concurrent with vacuuming. An index page split caused by an insertion could sometimes cause a concurrently-running "VACUUM" to miss removing index entries that it should remove. After the corresponding table rows are removed, the dangling index entries would cause errors (such as "could not read block N in file ...") or worse, silently wrong query results after unrelated rows are re-inserted at the now-free table locations. This bug has been present since release 8.2, but occurs so infrequently that it was not diagnosed until now. If you have reason to suspect that it has happened in your database, reindexing the affected index will fix things. - Update per-column permissions, not only per-table permissions, when changing table owner. Failure to do this meant that any previously granted column permissions were still shown as having been granted by the old owner. This meant that neither the new owner nor a superuser could revoke the now-untraceable-to-table-owner permissions. - Allow non-existent values for some settings in "ALTER USER/DATABASE SET". Allow default_text_search_config, default_tablespace, and temp_tablespaces to be set to names that are not known. This is because they might be known in another database where the setting is intended to be used, or for the tablespace cases because the tablespace might not be created yet. The same issue was previously recognized for search_path, and these settings now act like that one. - Avoid crashing when we have problems deleting table files post-commit. Dropping a table should lead to deleting the underlying disk files only after the transaction commits. In event of failure then (for instance, because of wrong file permissions) the code is supposed to just emit a warning message and go on, since it's too late to abort the transaction. This logic got broken as of release 8.4, causing such situations to result in a PANIC and an unrestartable database. - Track the OID counter correctly during WAL replay, even when it wraps around. Previously the OID counter would remain stuck at a high value until the system exited replay mode. The practical consequences of that are usually nil, but there are scenarios wherein a standby server that's been promoted to master might take a long time to advance the OID counter to a reasonable value once values are needed. - Fix regular expression back-references with - attached. Rather than enforcing an exact string match, the code would effectively accept any string that satisfies the pattern sub-expression referenced by the back-reference symbol. A similar problem still afflicts back-references that are embedded in a larger quantified expression, rather than being the immediate subject of the quantifier. This will be addressed in a future PostgreSQL release. - Fix recently-introduced memory leak in processing of inet/cidr values. - Fix dangling pointer after "CREATE TABLE AS"/"SELECT INTO" in a SQL-language function. In most cases this only led to an assertion failure in assert-enabled builds, but worse consequences seem possible. - Fix I/O-conversion-related memory leaks in plpgsql. - Improve pg_dump's handling of inherited table columns. pg_dump mishandled situations where a child column has a different default expression than its parent column. If the default is textually identical to the parent's default, but not actually the same (for instance, because of schema search path differences) it would not be recognized as different, so that after dump and restore the child would be allowed to inherit the parent's default. Child columns that are NOT NULL where their parent is not could also be restored subtly incorrectly. - Fix pg_restore's direct-to-database mode for INSERT-style table data. Direct-to-database restores from archive files made with "--inserts" or "--column-inserts" options fail when using pg_restore from a release dated September or December 2011, as a result of an oversight in a fix for another problem. The archive file itself is not at fault, and text-mode output is okay. - Allow AT option in ecpg DEALLOCATE statements. The infrastructure to support this has been there for awhile, but through an oversight there was still an error check rejecting the case. - Fix error in "contrib/intarray"'s int[] & int[] operator. If the smallest integer the two input arrays have in common is 1, and there are smaller values in either array, then 1 would be incorrectly omitted from the result. - Fix error detection in "contrib/pgcrypto"'s encrypt_iv() and decrypt_iv(). These functions failed to report certain types of invalid-input errors, and would instead return random garbage values for incorrect input. - Fix one-byte buffer overrun in "contrib/test_parser". The code would try to read one more byte than it should, which would crash in corner cases. Since "contrib/test_parser" is only example code, this is not a security issue in itself, but bad example code is still bad. - Use __sync_lock_test_and_set() for spinlocks on ARM, if available. This function replaces our previous use of the SWPB instruction, which is deprecated and not available on ARMv6 and later. Reports suggest that the old code doesn't fail in an obvious way on recent ARM boards, but simply doesn't interlock concurrent accesses, leading to bizarre failures in multiprocess operation. - Use "-fexcess-precision=standard" option when building with gcc versions that accept it. This prevents assorted scenarios wherein recent versions of gcc will produce creative results. - Allow use of threaded Python on FreeBSD. Our configure script previously believed that this combination wouldn't work; but FreeBSD fixed the problem, so remove that error check. * Drop 04-armel-tas.patch, applied upstream. Checksums-Sha1: 164f2fd25ac2dac59a3aaa53253bc374a3bb6073 5701636 postgresql-8.4_8.4.11-1_powerpc.deb 256a11202c47bd13c41604f2ee0069cb6709f35a 1511362 postgresql-client-8.4_8.4.11-1_powerpc.deb 2ebd25548fcd06d66d6edea80ea7359f51f41259 632320 postgresql-server-dev-8.4_8.4.11-1_powerpc.deb 4411463907d82d3122300d8259d22fec5e0b3387 382750 postgresql-contrib-8.4_8.4.11-1_powerpc.deb eeddc12778cba2483a7ca408c7b32b4fcdfc64f0 37702 postgresql-plperl-8.4_8.4.11-1_powerpc.deb 4fdd19cb181af3b2b30868cde672a3edbb3d48b7 40340 postgresql-plpython-8.4_8.4.11-1_powerpc.deb c7ccada59f2ba7b2c75a4e68979d4cb59b2db224 25798 postgresql-pltcl-8.4_8.4.11-1_powerpc.deb Checksums-Sha256: 2f515d320f450cfe8ac0411a5e2773c84274b3f49763e8f96c70d8defe063421 5701636 postgresql-8.4_8.4.11-1_powerpc.deb abdce11a64b32833c059e6dcd8820074a6318988b499433f59d747589dd5d5e9 1511362 postgresql-client-8.4_8.4.11-1_powerpc.deb 0253310a3c2052a185dc7923a2494b792775204d0f6c6cf786fb12358236b862 632320 postgresql-server-dev-8.4_8.4.11-1_powerpc.deb 76c31c76e7896b31c386cd85722d2fc98a859c77e1691a85c2bedcc75c646493 382750 postgresql-contrib-8.4_8.4.11-1_powerpc.deb 8700604917c5b7b8e5a8edd1bdbe0e5df3f987721aa07b92702b0a60b0a416ee 37702 postgresql-plperl-8.4_8.4.11-1_powerpc.deb a7117397d0eee287f2059acf4be71b7f34e7453bd2447e3c771fad43f357bddf 40340 postgresql-plpython-8.4_8.4.11-1_powerpc.deb dbc64a0d060d3e8706a4fdeeddc753ff995e936b53bebc6908fa45a70524fef3 25798 postgresql-pltcl-8.4_8.4.11-1_powerpc.deb Files: a9582aee17a4e4e4aa212ce745282771 5701636 database optional postgresql-8.4_8.4.11-1_powerpc.deb 94b68e859ae2ad06ab93a2544ebf698d 1511362 database optional postgresql-client-8.4_8.4.11-1_powerpc.deb 70e89a06d06801ed5faa1ae27fa08841 632320 libdevel optional postgresql-server-dev-8.4_8.4.11-1_powerpc.deb e636bc964d917995172e8b957de01bd9 382750 database optional postgresql-contrib-8.4_8.4.11-1_powerpc.deb 07bf98d9859b0edd25f18a7d80f2d0e9 37702 database optional postgresql-plperl-8.4_8.4.11-1_powerpc.deb 1c3746d85dd17e122be7278ac66860ab 40340 database optional postgresql-plpython-8.4_8.4.11-1_powerpc.deb 9d0e3b7ec636c0b2a82327cc9d196402 25798 database optional postgresql-pltcl-8.4_8.4.11-1_powerpc.deb