Format: 1.8 Date: Mon, 27 Feb 2012 07:30:59 +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-plpython3-9.1 postgresql-pltcl-9.1 Architecture: amd64 amd64_translations Version: 9.1.3-1 Distribution: precise Urgency: medium Maintainer: Ubuntu/amd64 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-plpython3-9.1 - PL/Python 3 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 Closes: 656129 Changes: postgresql-9.1 (9.1.3-1) unstable; urgency=medium . * Urgency medium due to security fixes. * New upstream security/bug fix 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. - 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. * debian/watch: Use ftp for checking, thanks Peter Eisentraut. (Closes: #656129) * debian/control: Bump Standards-Version to 3.9.3. No changes necessary. Checksums-Sha1: a72e697223eda8569061b9cc8558ac3bab677941 213890 libpq-dev_9.1.3-1_amd64.deb a57886b4cccb0e11e2c37eb6d5ec1aa040283413 94050 libpq5_9.1.3-1_amd64.deb 6def8a38c9c707b891c3fbb849f372fded31c5dd 40000 libecpg6_9.1.3-1_amd64.deb d6b6dfb9857403ca313927ca0ea7fcc5ef299237 265914 libecpg-dev_9.1.3-1_amd64.deb 1dd6bd51a42a62656e2bc5d6b2da330450dda53a 12686 libecpg-compat3_9.1.3-1_amd64.deb a0ae81855edf2354878662279b66156cd6b45de7 47760 libpgtypes3_9.1.3-1_amd64.deb 19970f9e03d0f244008b572032ffc84345998825 4329274 postgresql-9.1_9.1.3-1_amd64.deb 4e5959ae851dd3f1c3ce4dd99982fe92d5fa5049 8547536 postgresql-9.1-dbg_9.1.3-1_amd64.deb e40ea539f999de55ffbc6639f8545a755d799c45 988436 postgresql-client-9.1_9.1.3-1_amd64.deb 00f4a156f586c5780b92da15540faec32af211f5 676012 postgresql-server-dev-9.1_9.1.3-1_amd64.deb 5dcccee812a57e96485e6b1065e0876e83a64d6e 460708 postgresql-contrib-9.1_9.1.3-1_amd64.deb aea13eb943a142f81d0f772071984b5588d8eaa1 45850 postgresql-plperl-9.1_9.1.3-1_amd64.deb fba7ae796b4821116d4365fc601ac7e7fd39d82b 42816 postgresql-plpython-9.1_9.1.3-1_amd64.deb 9cfba28c3d9151b28e98a7cbd473dad489a4fd76 42756 postgresql-plpython3-9.1_9.1.3-1_amd64.deb 698ee51ee9b75a9abb5ac3ec2fa05b089c06d984 24938 postgresql-pltcl-9.1_9.1.3-1_amd64.deb c6b43a769ec01b96560a8441f400962715ef55d1 4667919 postgresql-9.1_9.1.3-1_amd64_translations.tar.gz Checksums-Sha256: 0745118a5c96f3e27ece27f704ac3f821726c98297212dde601df012d0166e1f 213890 libpq-dev_9.1.3-1_amd64.deb 022f9f2003d8b5d7eb96863db3c65c0205a25a866d934fe65f0680ca5446b613 94050 libpq5_9.1.3-1_amd64.deb 79912fc3ac6c49e7632f0e9d3a386a56ddfc46a8a31df715f8923b278810ec27 40000 libecpg6_9.1.3-1_amd64.deb 23324b7b961df120527dcea6cf990ac4f1df21419d92a0042a0b719ed388782b 265914 libecpg-dev_9.1.3-1_amd64.deb 145b4e37b427d27e821d6c9a747221db35ccea4c6389a4cea4cae7bd2714fe65 12686 libecpg-compat3_9.1.3-1_amd64.deb f96995e5f8f8f592439a665b780b977f37bb9187b8e4afa44fe747e6ec794db4 47760 libpgtypes3_9.1.3-1_amd64.deb f887f3b8a990924d6faa75e048900e0d63819e528944b87e8588840eff507a1b 4329274 postgresql-9.1_9.1.3-1_amd64.deb ca264d6ef00d45d86697ab6008ecf7a27fffb6498139457ecdee43e79e0cf505 8547536 postgresql-9.1-dbg_9.1.3-1_amd64.deb 6086014fb39ee0548236baf188062827f1f387433069c970905b4d9138e106de 988436 postgresql-client-9.1_9.1.3-1_amd64.deb 2e515741335300cd3354b857d0675b0b9ccb260970877f894caf5b6cbae52eb1 676012 postgresql-server-dev-9.1_9.1.3-1_amd64.deb f8a5bec6dc2cd17699b2e90e01a45a8cbccb2e78edb46f08e2bb6098006f6446 460708 postgresql-contrib-9.1_9.1.3-1_amd64.deb d3fd9fa34e96162fba4c540b44881a317813585f5b02059e271da25f177f2253 45850 postgresql-plperl-9.1_9.1.3-1_amd64.deb 8f59be7c607bb4244687f7945b4b2aa9010770458f968c609052b3c8780b0a90 42816 postgresql-plpython-9.1_9.1.3-1_amd64.deb af0a803eaefafaf414266406f32ebc0edfd54e62b1ff50f03cfa084c13469f16 42756 postgresql-plpython3-9.1_9.1.3-1_amd64.deb 0342c1e148a412f85f1e95aecff8d52a44f16b6ecf55ef8bfecf84973c655800 24938 postgresql-pltcl-9.1_9.1.3-1_amd64.deb 974eac989c95b9c7892fdf19ad600441e2255a0ca0d22b2760f355b5ad5ec4a5 4667919 postgresql-9.1_9.1.3-1_amd64_translations.tar.gz Files: 93fd7b1a22048b0b0d9a2d3359c15dd8 213890 libdevel optional libpq-dev_9.1.3-1_amd64.deb 6b13f873c9d5a13e7fb7eb92dfcbfc3f 94050 libs optional libpq5_9.1.3-1_amd64.deb c9cba54b1fb28b9f06a6894114e05088 40000 libs optional libecpg6_9.1.3-1_amd64.deb 64faaf828f80f1ebaab5ad346ab91c63 265914 libdevel optional libecpg-dev_9.1.3-1_amd64.deb 632cbff14390a48e87dbc66e9ff1aecc 12686 libs optional libecpg-compat3_9.1.3-1_amd64.deb 6d41adb81478bfd553b1bfa736a67272 47760 libs optional libpgtypes3_9.1.3-1_amd64.deb 9416ae8085cfbb57b4b20655ab4c5f3e 4329274 database optional postgresql-9.1_9.1.3-1_amd64.deb 0d42f1d08f15bfa6c69c473adf4630b7 8547536 debug extra postgresql-9.1-dbg_9.1.3-1_amd64.deb 2aca57d4c6c4ac6dbcc1541652ad798d 988436 database optional postgresql-client-9.1_9.1.3-1_amd64.deb f36d11e39997572e3b3d9cb9dc7b4896 676012 libdevel optional postgresql-server-dev-9.1_9.1.3-1_amd64.deb 1b526e03c8d57835c9196a8d5f5c6aee 460708 database optional postgresql-contrib-9.1_9.1.3-1_amd64.deb 6f673d040af7dc9d973033dc92aee6f2 45850 database optional postgresql-plperl-9.1_9.1.3-1_amd64.deb 8f92e73a2ba305226d43c2e8fceda0f5 42816 database optional postgresql-plpython-9.1_9.1.3-1_amd64.deb b4b71ce0300c2ac12d2492a73ee59b93 42756 database optional postgresql-plpython3-9.1_9.1.3-1_amd64.deb 1fa8f952ffee2d46b640a7e6859f335f 24938 database optional postgresql-pltcl-9.1_9.1.3-1_amd64.deb 87bfcd6399611bbdf5ce5315db874767 4667919 raw-translations - postgresql-9.1_9.1.3-1_amd64_translations.tar.gz