Format: 1.8 Date: Mon, 27 Feb 2012 14:48:01 +0100 Source: postgresql-9.1 Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 postgresql-9.1 postgresql-9.1-dbg postgresql-client-9.1 postgresql-server-dev-9.1 postgresql-doc-9.1 postgresql-contrib-9.1 postgresql-plperl-9.1 postgresql-plpython-9.1 postgresql-pltcl-9.1 Architecture: powerpc powerpc_translations Version: 9.1.3-0ubuntu0.11.10 Distribution: oneiric Urgency: low Maintainer: Ubuntu/powerpc Build Daemon Changed-By: Martin Pitt Description: libecpg-compat3 - older version of run-time library for ECPG programs libecpg-dev - development files for ECPG (Embedded PostgreSQL for C) libecpg6 - run-time library for ECPG programs libpgtypes3 - shared library libpgtypes for PostgreSQL 9.1 libpq-dev - header files for libpq5 (PostgreSQL library) libpq5 - PostgreSQL C client library postgresql-9.1 - object-relational SQL database, version 9.1 server postgresql-9.1-dbg - debug symbols for postgresql-9.1 postgresql-client-9.1 - front-end programs for PostgreSQL 9.1 postgresql-contrib-9.1 - additional facilities for PostgreSQL postgresql-doc-9.1 - documentation for the PostgreSQL database management system postgresql-plperl-9.1 - PL/Perl procedural language for PostgreSQL 9.1 postgresql-plpython-9.1 - PL/Python procedural language for PostgreSQL 9.1 postgresql-pltcl-9.1 - PL/Tcl procedural language for PostgreSQL 9.1 postgresql-server-dev-9.1 - development files for PostgreSQL 9.1 server-side programming Launchpad-Bugs-Fixed: 941912 Changes: postgresql-9.1 (9.1.3-0ubuntu0.11.10) oneiric-security; urgency=low . * New upstream security/bug fix release: (LP: #941912) - 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. - Fix transient zeroing of shared buffers during WAL replay. The replay logic would sometimes zero and refill a shared buffer, so that the contents were transiently invalid. In hot standby mode this can result in a query that's executing in parallel seeing garbage data. Various symptoms could result from that, but the most common one seems to be "invalid memory alloc request size". - Fix handling of data-modifying WITH subplans in READ COMMITTED rechecking. A WITH clause containing "INSERT"/"UPDATE"/"DELETE" would crash if the parent "UPDATE" or "DELETE" command needed to be re-evaluated at one or more rows due to concurrent updates in READ COMMITTED mode. - Fix corner case in SSI transaction cleanup. When finishing up a read-write serializable transaction, a crash could occur if all remaining active serializable transactions are read-only. - Fix postmaster to attempt restart after a hot-standby crash. A logic error caused the postmaster to terminate, rather than attempt to restart the cluster, if any backend process crashed while operating in hot standby mode. - Fix "CLUSTER"/"VACUUM FULL" handling of toast values owned by recently-updated rows. This oversight could lead to "duplicate key value violates unique constraint" errors being reported against the toast table's index during one of these commands. - 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. - Support foreign data wrappers and foreign servers in "REASSIGN OWNED". This command failed with "unexpected classid" errors if it needed to change the ownership of any such objects. - 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. - Fix "unsupported node type" error caused by COLLATE in an "INSERT" expression. - 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. - Recover from errors occurring during WAL replay of "DROP TABLESPACE". Replay will attempt to remove the tablespace's directories, but there are various reasons why this might fail (for example, incorrect ownership or permissions on those directories). Formerly the replay code would panic, rendering the database unrestartable without manual intervention. It seems better to log the problem and continue, since the only consequence of failure to remove the directories is some wasted disk space. - Fix race condition in logging AccessExclusiveLocks for hot standby. Sometimes a lock would be logged as being held by "transaction zero". This is at least known to produce assertion failures on slave servers, and might be the cause of more serious problems. - Track the OID counter correctly during WAL replay, even when it wraps around. - Prevent emitting misleading "consistent recovery state reached" log message at the beginning of crash recovery. - Fix initial value of pg_stat_replication.replay_location. - 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 planner's ability to push down index-expression restrictions through UNION ALL. - Fix planning of WITH clauses referenced in "UPDATE"/"DELETE" on an inherited table. This bug led to "could not find plan for CTE" failures. - Fix GIN cost estimation to handle column IN (...) index conditions. This oversight would usually lead to crashes if such a condition could be used with a GIN index. - 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. - Work around bug in perl's SvPVutf8() function. This function crashes when handed a typeglob or certain read-only objects such as $^V. Make plperl avoid passing those to it. - In pg_dump, don't dump contents of an extension's configuration tables if the extension itself is not being dumped. - 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. - Teach pg_upgrade to handle renaming of plpython's shared library. Upgrading a pre-9.1 database that included plpython would fail because of this oversight. - Allow pg_upgrade to process tables containing regclass columns. Since pg_upgrade now takes care to preserve pg_class OIDs, there was no longer any reason for this restriction. - Make libpq ignore ENOTDIR errors when looking for an SSL client certificate file. This allows SSL connections to be established, though without a certificate, even when the user's home directory is set to something like /dev/null. - Fix some more field alignment issues in ecpg's SQLDA area. - 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. - Do not use the variable name when defining a varchar structure in ecpg. - Fix "contrib/auto_explain"'s JSON output mode to produce valid JSON. - 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 (Chris Rees) Our configure script previously believed that this combination wouldn't work; but FreeBSD fixed the problem, so remove that error check. * Drop 00git_inet_cidr_unpack.patch, 01-armel-tas.patch: Applied upstream. Checksums-Sha1: ef42323327fd2842ed86cff58b0912b9f72f156c 207946 libpq-dev_9.1.3-0ubuntu0.11.10_powerpc.deb 3083d5894c0babe23f9fa470ab92cc07e6cb2f2c 87892 libpq5_9.1.3-0ubuntu0.11.10_powerpc.deb ee6e97c0d8582562e383c6d21459b017e5ad410e 39232 libecpg6_9.1.3-0ubuntu0.11.10_powerpc.deb b4aa6796db4b674c9cb33e3f3297f45fc83cd078 261558 libecpg-dev_9.1.3-0ubuntu0.11.10_powerpc.deb e2136c1ca97a77c94ee8c290100bb0d35c862361 11594 libecpg-compat3_9.1.3-0ubuntu0.11.10_powerpc.deb 6a79c6a0a99a252f269771aa8cce76c1ed0a5fe8 49058 libpgtypes3_9.1.3-0ubuntu0.11.10_powerpc.deb 913318041b2c206617f4a05108b8d06ef97907c6 4576760 postgresql-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 0acadc66fef4084f28221b254dae2eb12526b183 8581650 postgresql-9.1-dbg_9.1.3-0ubuntu0.11.10_powerpc.deb f016813eb01b714b5963d54fc55584bbed0aa3af 961656 postgresql-client-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 9f4f9fe91c8a8ca9406b0dd23274866fc7a8385d 686564 postgresql-server-dev-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 4d40fe61c06d5b53d868ee52e66ab1ff7ed72685 435354 postgresql-contrib-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 1c47e26e50dd8b328ee4c692cc38a125143430f9 57328 postgresql-plperl-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 9b25084aff01026d66560724a70f2e33b3dfe86f 50958 postgresql-plpython-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 304700c3cfd2bb302d69c7fe452b135b7772cacb 34378 postgresql-pltcl-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 0b88ba0bd61017926537ce67e09015f0691d7ac2 4778676 postgresql-9.1_9.1.3-0ubuntu0.11.10_powerpc_translations.tar.gz Checksums-Sha256: 6a0bf9bfd0b02c48a0b195795417ce0edfa5cfd54c912580925e5e98dde3e65f 207946 libpq-dev_9.1.3-0ubuntu0.11.10_powerpc.deb 85057cfa7529a5cba02e7b3a5eb50a79deb5dd3dba806d4b5f8c5f1035f7e7fc 87892 libpq5_9.1.3-0ubuntu0.11.10_powerpc.deb daf3882f495d91c55a8af64ee205f02a2dab0b35a64d7afb6a519000c6504dc9 39232 libecpg6_9.1.3-0ubuntu0.11.10_powerpc.deb 7ceb7f3574224c87ca63403dc1a2ce30a3ffc94d9082780208b9c5d4fc6c33de 261558 libecpg-dev_9.1.3-0ubuntu0.11.10_powerpc.deb b214da6bdf443f0c582b900278eecc9c6eb28885e49172872b1f88d71b3bb7af 11594 libecpg-compat3_9.1.3-0ubuntu0.11.10_powerpc.deb c7be095a11c134bc1187924de37446512ba7b120b87457b62a2bc52d5a8a02f9 49058 libpgtypes3_9.1.3-0ubuntu0.11.10_powerpc.deb 89760edd6f5e8b962dc8d2422c9b7cf3dd4796eb3c8cebb546264bd9f78f9df7 4576760 postgresql-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 74a90970fddf45203973d64223861cd2329494919ce6f85d724094329c6d4cf5 8581650 postgresql-9.1-dbg_9.1.3-0ubuntu0.11.10_powerpc.deb aa4b69cf03935aef2eb10632bf17e1390c2a4b2ca69d4719c4f7e92e68d57a8e 961656 postgresql-client-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 6a6baa19693409282aafd81a8b001ef20cec0e0d7da46d3df525bff01124975e 686564 postgresql-server-dev-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 7269235edbc6c0d4a1099112070601a4e375ead8b49b55be38bd364cfd347416 435354 postgresql-contrib-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb a4d5855f127bd4ed5327aca100e1e154c7e18cc3be8f38138e5f111108493d61 57328 postgresql-plperl-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 7a7e2720a170b519546cbfca992593bd9154b1c1bf123b80b860dbdf9f20be44 50958 postgresql-plpython-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 27b27933389674221dddc5a74a111a55bc2bac71b9b7688608297fb9fd4d522e 34378 postgresql-pltcl-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 8694a49d1bf51944cb6c860dca6e30021aef7c008eed15293fa1cf544bdc1fc3 4778676 postgresql-9.1_9.1.3-0ubuntu0.11.10_powerpc_translations.tar.gz Files: a32d01966fbf3901249548939d737ce5 207946 libdevel optional libpq-dev_9.1.3-0ubuntu0.11.10_powerpc.deb e8b86fc6169d908da5561ff7c5c9fa31 87892 libs optional libpq5_9.1.3-0ubuntu0.11.10_powerpc.deb ec8b850f83f55ab158f078fd51f0a2f1 39232 libs optional libecpg6_9.1.3-0ubuntu0.11.10_powerpc.deb 687eb2cbe7cc828ed087aeea01572e7c 261558 libdevel optional libecpg-dev_9.1.3-0ubuntu0.11.10_powerpc.deb c8f9a4ace47d383fd63ae77f714944bd 11594 libs optional libecpg-compat3_9.1.3-0ubuntu0.11.10_powerpc.deb 0e91c644034f94e70e28c5dc4db28ade 49058 libs optional libpgtypes3_9.1.3-0ubuntu0.11.10_powerpc.deb 36723f9473a06c0f4f3ce28241814e4c 4576760 database optional postgresql-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb cdabe35d4479703d464388222cdb40ae 8581650 debug extra postgresql-9.1-dbg_9.1.3-0ubuntu0.11.10_powerpc.deb 660ac2dd32654c0beae3bd19cdf1bc64 961656 database optional postgresql-client-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 527d40649a6d541c259f1157691f4368 686564 libdevel optional postgresql-server-dev-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 445c44174f910bca6dcad4996267222a 435354 database optional postgresql-contrib-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb dc81409dc878498949845b6294bac968 57328 database optional postgresql-plperl-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb b9c78fd58f445fd99b821f2a11884cfb 50958 database optional postgresql-plpython-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb f1c4c86efcc3cf82ccfdf6e604f036d6 34378 database optional postgresql-pltcl-9.1_9.1.3-0ubuntu0.11.10_powerpc.deb 3e594636f0cdd24a0d055b86bd4e872a 4778676 raw-translations - postgresql-9.1_9.1.3-0ubuntu0.11.10_powerpc_translations.tar.gz Original-Maintainer: Martin Pitt