Format: 1.8 Date: Sun, 25 Sep 2011 14:23:07 +0200 Source: postgresql-9.0 Binary: postgresql-9.0 postgresql-9.0-dbg postgresql-client-9.0 postgresql-server-dev-9.0 postgresql-doc-9.0 postgresql-contrib-9.0 postgresql-plperl-9.0 postgresql-plpython-9.0 postgresql-pltcl-9.0 Architecture: all i386 Version: 9.0.5-1 Distribution: precise Urgency: low Maintainer: Ubuntu/i386 Build Daemon Changed-By: Martin Pitt Description: postgresql-9.0 - object-relational SQL database, version 9.0 server postgresql-9.0-dbg - debug symbols for postgresql-9.0 postgresql-client-9.0 - front-end programs for PostgreSQL 9.0 postgresql-contrib-9.0 - additional facilities for PostgreSQL postgresql-doc-9.0 - documentation for the PostgreSQL database management system postgresql-plperl-9.0 - PL/Perl procedural language for PostgreSQL 9.0 postgresql-plpython-9.0 - PL/Python procedural language for PostgreSQL 9.0 postgresql-pltcl-9.0 - PL/Tcl procedural language for PostgreSQL 9.0 postgresql-server-dev-9.0 - development files for PostgreSQL 9.0 server-side programming Closes: 628505 636571 Changes: postgresql-9.0 (9.0.5-1) unstable; urgency=low . * New upstream bug fix release: - Fix catalog cache invalidation after a "VACUUM FULL" or "CLUSTER" on a system catalog. In some cases the relocation of a system catalog row to another place would not be recognized by concurrent server processes, allowing catalog corruption to occur if they then tried to update that row. The worst-case outcome could be as bad as complete loss of a table. - Fix incorrect order of operations during sinval reset processing, and ensure that TOAST OIDs are preserved in system catalogs. These mistakes could lead to transient failures after a "VACUUM FULL" or "CLUSTER" on a system catalog. - Fix bugs in indexing of in-doubt HOT-updated tuples. These bugs could result in index corruption after reindexing a system catalog. They are not believed to affect user indexes. - Fix multiple bugs in GiST index page split processing. - Fix possible buffer overrun in tsvector_concat(). - Fix crash in xml_recv when processing a "standalone" parameter. - Make pg_options_to_table return NULL for an option with no value. Previously such cases would result in a server crash. - Avoid possibly accessing off the end of memory in "ANALYZE" and in SJIS-2004 encoding conversion. This fixes some very-low-probability server crash scenarios. - Protect pg_stat_reset_shared() against NULL input. - Fix possible failure when a recovery conflict deadlock is detected within a sub-transaction. - Avoid spurious conflicts while recycling btree index pages during hot standby. - Shut down WAL receiver if it's still running at end of recovery. The postmaster formerly panicked in this situation, but it's actually a legitimate case. - Fix race condition in relcache init file invalidation. There was a window wherein a new backend process could read a stale init file but miss the inval messages that would tell it the data is stale. The result would be bizarre failures in catalog accesses, typically "could not read block 0 in file ..." later during startup. - Fix memory leak at end of a GiST index scan. - Fix memory leak when encoding conversion has to be done on incoming command strings and "LISTEN" is active. - Fix incorrect memory accounting (leading to possible memory bloat) in tuplestores supporting holdable cursors and plpgsql's RETURN NEXT command. - Fix trigger WHEN conditions when both BEFORE and AFTER triggers exist. Evaluation of WHEN conditions for AFTER ROW UPDATE triggers could crash if there had been a BEFORE ROW trigger fired for the same update. - Fix performance problem when constructing a large, lossy bitmap. - Fix join selectivity estimation for unique columns. - Fix nested PlaceHolderVar expressions that appear only in sub-select target lists. This mistake could result in outputs of an outer join incorrectly appearing as NULL. - Allow the planner to assume that empty parent tables really are empty. Normally an empty table is assumed to have a certain minimum size for planning purposes; but this heuristic seems to do more harm than good for the parent table of an inheritance hierarchy, which often is permanently empty. - Allow nested EXISTS queries to be optimized properly. - Fix array- and path-creating functions to ensure padding bytes are zeroes. This avoids some situations where the planner will think that semantically-equal constants are not equal, resulting in poor optimization. - Fix "EXPLAIN" to handle gating Result nodes within inner-indexscan subplans. The usual symptom of this oversight was "bogus varno" errors. - Fix btree preprocessing of "indexedcol" IS NULL conditions. Such a condition is unsatisfiable if combined with any other type of btree-indexable condition on the same index column. The case was handled incorrectly in 9.0.0 and later, leading to query output where there should be none. - Work around gcc 4.6.0 bug that breaks WAL replay. This could lead to loss of committed transactions after a server crash. - Fix dump bug for VALUES in a view. - Disallow SELECT FOR UPDATE/SHARE on sequences. This operation doesn't work as expected and can lead to failures. - Fix "VACUUM" so that it always updates pg_class.reltuples/relpages. This fixes some scenarios where autovacuum could make increasingly poor decisions about when to vacuum tables. - Defend against integer overflow when computing size of a hash table. - Fix cases where "CLUSTER" might attempt to access already-removed TOAST data. - Fix premature timeout failures during initial authentication transaction. - Fix portability bugs in use of credentials control messages for "peer" authentication. (see #627596, already fixed in Debian before) - Fix SSPI login when multiple roundtrips are required. The typical symptom of this problem was "The function requested is not supported" errors during SSPI login. - Fix failure when adding a new variable of a custom variable class to "postgresql.conf". - Throw an error if "pg_hba.conf" contains hostssl but SSL is disabled. This was concluded to be more user-friendly than the previous behavior of silently ignoring such lines. - Fix failure when "DROP OWNED BY" attempts to remove default privileges on sequences. - Fix typo in pg_srand48 seed initialization. This led to failure to use all bits of the provided seed. This function is not used on most platforms (only those without srandom), and the potential security exposure from a less-random-than-expected seed seems minimal in any case. - Avoid integer overflow when the sum of LIMIT and OFFSET values exceeds 2^63. - Add overflow checks to int4 and int8 versions of generate_series() - Fix trailing-zero removal in to_char(). In a format with FM and no digit positions after the decimal point, zeroes to the left of the decimal point could be removed incorrectly. - Fix pg_size_pretty() to avoid overflow for inputs close to 2^63. - Weaken plpgsql's check for typmod matching in record values. An overly enthusiastic check could lead to discarding length modifiers that should have been kept. - In pg_upgrade, avoid dumping orphaned temporary tables. This prevents situations wherein table OID assignments could get out of sync between old and new installations. - Fix pg_upgrade to preserve toast tables' relfrozenxids during an upgrade from 8.3. Failure to do this could lead to "pg_clog" files being removed too soon after the upgrade. - Fix psql's counting of script file line numbers during COPY from a different file. - Fix pg_restore's direct-to-database mode for standard_conforming_strings. pg_restore could emit incorrect commands when restoring directly to a database server from an archive file that had been made with standard_conforming_strings set to on. - Be more user-friendly about unsupported cases for parallel pg_restore. This change ensures that such cases are detected and reported before any restore actions have been taken. - Fix write-past-buffer-end and memory leak in libpq's LDAP service lookup code. - In libpq, avoid failures when using nonblocking I/O and an SSL connection. - Improve libpq's handling of failures during connection startup. In particular, the response to a server report of fork() failure during SSL connection startup is now saner. - Improve libpq's error reporting for SSL failures. - Fix PQsetvalue() to avoid possible crash when adding a new tuple to a PGresult originally obtained from a server query. - Make ecpglib write double values with 15 digits precision. - In ecpglib, be sure LC_NUMERIC setting is restored after an error. - Apply upstream fix for blowfish signed-character bug (CVE-2011-2483) (Tom Lane) (Closes: #636571) "contrib/pg_crypto"'s blowfish encryption code could give wrong results on platforms where char is signed (which is most), leading to encrypted passwords being weaker than they should be. - Fix memory leak in "contrib/seg". - Fix pgstatindex() to give consistent results for empty indexes. - Allow building with perl 5.14. (Closes: #628505) * Drop 03-cmsgcred-size.patch. Fixed upstream in a different way. Checksums-Sha1: e76a852a89194317a7026c584e54d01341704b05 2061824 postgresql-doc-9.0_9.0.5-1_all.deb c64f2b5bfceb651eabaa355dcb2d164592cf0a35 5678764 postgresql-9.0_9.0.5-1_i386.deb 68acca2dedb5863f45dd0000be1503422b4522f9 7130256 postgresql-9.0-dbg_9.0.5-1_i386.deb ae1584500eed49dae0e11273bb70e8569f50e131 1455632 postgresql-client-9.0_9.0.5-1_i386.deb 919097e4eff3d0b5fd117177eb679de27bc74771 652852 postgresql-server-dev-9.0_9.0.5-1_i386.deb 7fd62525ed1f00b2dabd132ce4e7bb0da47ae8d5 435832 postgresql-contrib-9.0_9.0.5-1_i386.deb 4f0b381a97147bc0ce2d2bc353bdaa8d036ccb54 64336 postgresql-plperl-9.0_9.0.5-1_i386.deb 8b893687f04fc1151c7c01593eb3e27c5cf851d5 65132 postgresql-plpython-9.0_9.0.5-1_i386.deb 15530a85e6601ce0d36fb43349ecded43c28a6d8 38732 postgresql-pltcl-9.0_9.0.5-1_i386.deb Checksums-Sha256: df19db17ac0b8f9c8802cb4689447e68c83814f8722b45b6e4d0615e9268733a 2061824 postgresql-doc-9.0_9.0.5-1_all.deb 5d07a8c338fbe32dc9fb9d1e508d889894a9acb9a6d367d4c0ebba8890f53b23 5678764 postgresql-9.0_9.0.5-1_i386.deb 748e5deb3b2480e4b279adbfad47c06c0c970d68e561e32a6dd1419e5d6481fb 7130256 postgresql-9.0-dbg_9.0.5-1_i386.deb 702f8b25c9cfb0343dd4c54d5d3c3d5f04dcd0088b71e94847132d43c74563bb 1455632 postgresql-client-9.0_9.0.5-1_i386.deb 64b3f38df987b7b0315a58cec5aad5f15e07e7aef490712912b9addf9a7cd096 652852 postgresql-server-dev-9.0_9.0.5-1_i386.deb d928f4d119e9c38c16a2894d8d1fcd27fe6b49ba46bce87e58acac8cbcf82930 435832 postgresql-contrib-9.0_9.0.5-1_i386.deb 4c673f18e094ff5697b32d6d3490b0827385d328fb18a094ab648a5dab1e1dc8 64336 postgresql-plperl-9.0_9.0.5-1_i386.deb e2a3a3033beb5fd65bbb85d839fee968ff284dc5369a362c6b8ab04b11f905c2 65132 postgresql-plpython-9.0_9.0.5-1_i386.deb 5ffd3da542b2caf142d4ff6b65bf573d3c22e28ead62b57d8a47d33bf747bc81 38732 postgresql-pltcl-9.0_9.0.5-1_i386.deb Files: ff2739c1dc58162d7e2a533d56cfed8b 2061824 doc optional postgresql-doc-9.0_9.0.5-1_all.deb 7774dd6c8c00bdf2e99af46166098237 5678764 database optional postgresql-9.0_9.0.5-1_i386.deb 1e79ebd489455c1d064e79ace77fb227 7130256 debug extra postgresql-9.0-dbg_9.0.5-1_i386.deb 1fca0b432cc3c2ac0b99e369b2cf599f 1455632 database optional postgresql-client-9.0_9.0.5-1_i386.deb 544bb0ca73b3ae1f11560efa37b3c127 652852 libdevel optional postgresql-server-dev-9.0_9.0.5-1_i386.deb 705decfc03db9c942ee9f6b395d5ca4f 435832 database optional postgresql-contrib-9.0_9.0.5-1_i386.deb ed910ac4d15de8edcbbeb03f4b074da8 64336 database optional postgresql-plperl-9.0_9.0.5-1_i386.deb 49e27714dd86858fb5a99ecc1048c06a 65132 database optional postgresql-plpython-9.0_9.0.5-1_i386.deb 5f2778156f9d8deae50c598dc4f4a29c 38732 database optional postgresql-pltcl-9.0_9.0.5-1_i386.deb