[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted postgresql-9.0 9.0.6-1~bpo50+1 (source all i386)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 22 Dec 2011 12:54:54 +0100
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: source all i386
Version: 9.0.6-1~bpo50+1
Distribution: lenny-backports-sloppy
Urgency: low
Maintainer: Martin Pitt <mpitt@debian.org>
Changed-By: Christoph Berg <myon@debian.org>
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
Changes: 
 postgresql-9.0 (9.0.6-1~bpo50+1) lenny-backports-sloppy; urgency=low
 .
   * Rebuild for lenny-backports-sloppy.
 .
 postgresql-9.0 (9.0.6-1) unstable; urgency=low
 .
   * New upstream bug fix release.
     - Fix bugs in information_schema.referential_constraints view.
       This view was being insufficiently careful about matching the
       foreign-key constraint to the depended-on primary or unique key
       constraint. That could result in failure to show a foreign key
       constraint at all, or showing it multiple times, or claiming that
       it depends on a different constraint than the one it really does.
       Since the view definition is installed by initdb, merely upgrading
       will not fix the problem. If you need to fix this in an existing
       installation, you can (as a superuser) drop the information_schema
       schema then re-create it by sourcing
       "SHAREDIR/information_schema.sql". (Run pg_config --sharedir if
       you're uncertain where "SHAREDIR" is.) This must be repeated in
       each database to be fixed.
     - Fix possible crash during "UPDATE" or "DELETE" that joins to the
       output of a scalar-returning function. A crash could only occur if the
       target row had been concurrently updated, so this problem surfaced only
       intermittently.
     - Fix incorrect replay of WAL records for GIN index updates.
       This could result in transiently failing to find index entries
       after a crash, or on a hot-standby server. The problem would be
       repaired by the next "VACUUM" of the index, however.
     - Fix TOAST-related data corruption during CREATE TABLE dest AS
       SELECT - FROM src or INSERT INTO dest SELECT * FROM src.
       If a table has been modified by "ALTER TABLE ADD COLUMN", attempts
       to copy its data verbatim to another table could produce corrupt
       results in certain corner cases. The problem can only manifest in
       this precise form in 8.4 and later, but we patched earlier versions
       as well in case there are other code paths that could trigger the
       same bug.
     - Fix possible failures during hot standby startup.
     - Start hot standby faster when initial snapshot is incomplete.
     - Fix race condition during toast table access from stale syscache
       entries. The typical symptom was transient errors like "missing chunk
       number 0 for toast value NNNNN in pg_toast_2619", where the cited toast
       table would always belong to a system catalog.
     - Track dependencies of functions on items used in parameter default
       expressions. Previously, a referenced object could be dropped without
       having dropped or modified the function, leading to misbehavior when the
       function was used. Note that merely installing this update will not fix
       the missing dependency entries; to do that, you'd need to "CREATE OR
       REPLACE" each such function afterwards. If you have functions whose
       defaults depend on non-built-in objects, doing so is recommended.
     - Allow inlining of set-returning SQL functions with multiple OUT
       parameters.
     - Don't trust deferred-unique indexes for join removal.  A deferred
       uniqueness constraint might not hold intra-transaction, so assuming that
       it does could give incorrect query results.
     - Make DatumGetInetP() unpack inet datums that have a 1-byte header,
       and add a new macro, DatumGetInetPP(), that does not.
       This change affects no core code, but might prevent crashes in
       add-on code that expects DatumGetInetP() to produce an unpacked
       datum as per usual convention.
     - Improve locale support in money type's input and output. Aside from not
       supporting all standard lc_monetary formatting options, the input and
       output functions were inconsistent, meaning there were locales in which
       dumped money values could not be re-read.
     - Don't let transform_null_equals affect CASE foo WHEN NULL ...
       constructs.
     - Change foreign-key trigger creation order to better support
       self-referential foreign keys.
       For a cascading foreign key that references its own table, a row
       update will fire both the ON UPDATE trigger and the CHECK trigger
       as one event. The ON UPDATE trigger must execute first, else the
       CHECK will check a non-final state of the row and possibly throw an
       inappropriate error. However, the firing order of these triggers is
       determined by their names, which generally sort in creation order
       since the triggers have auto-generated names following the
       convention "RI_ConstraintTrigger_NNNN". A proper fix would require
       modifying that convention, which we will do in 9.2, but it seems
       risky to change it in existing releases. So this patch just changes
       the creation order of the triggers. Users encountering this type of
       error should drop and re-create the foreign key constraint to get
       its triggers into the right order.
     - Avoid floating-point underflow while tracking buffer allocation
       rate.
     - Fix incorrect field alignment in ecpg's SQLDA area.
     - Preserve blank lines within commands in psql's command history.
       The former behavior could cause problems if an empty line was
       removed from within a string literal, for example.
     - Fix pg_dump to dump user-defined casts between auto-generated
       types, such as table rowtypes.
     - Assorted fixes for pg_upgrade. Handle exclusion constraints correctly,
       don't complain about mismatched toast table names in 8.4 databases.
     - Use the preferred version of xsubpp to build PL/Perl, not
       necessarily the operating system's main copy.
     - Fix incorrect coding in "contrib/dict_int" and "contrib/dict_xsyn".
     - Fix assorted errors in "contrib/unaccent"'s configuration file
       parsing.
     - Honor query cancel interrupts promptly in pgstatindex().
     - Ensure VPATH builds properly install all server header files.
     - Shorten file names reported in verbose error messages.
       Regular builds have always reported just the name of the C file
       containing the error message call, but VPATH builds formerly
       reported an absolute path name.
 .
 postgresql-9.0 (9.0.5-1~bpo50+1) lenny-backports-sloppy; urgency=low
 .
   * Rebuild for lenny-backports-sloppy.
Checksums-Sha1: 
 7c73d44a5870c58deb761c099b90a6d10569f6c9 2457 postgresql-9.0_9.0.6-1~bpo50+1.dsc
 4a9a7d5579d3683ca1992b2ba116a4356094b3ca 14777282 postgresql-9.0_9.0.6.orig.tar.bz2
 e8b2c65c5ec8ad9477b017b98245de52e955fcdb 27893 postgresql-9.0_9.0.6-1~bpo50+1.debian.tar.gz
 d6d8578454c2574807091f2c62664ff2bd174ea3 2611680 postgresql-doc-9.0_9.0.6-1~bpo50+1_all.deb
 ed3ddcd9c71ceecc5de43bb9ee4ba541fd898509 5919776 postgresql-9.0_9.0.6-1~bpo50+1_i386.deb
 b280a9e034dc15043ce0f6047bfe9b70bba20387 6971944 postgresql-9.0-dbg_9.0.6-1~bpo50+1_i386.deb
 8ed461b507a9c329882b4647d7480f1817dec18d 1771032 postgresql-client-9.0_9.0.6-1~bpo50+1_i386.deb
 c0d7e2e91489bc577be13dfa483869edbe75d89f 980448 postgresql-server-dev-9.0_9.0.6-1~bpo50+1_i386.deb
 6de5df92812224815c4bc8b9e35df300f7e084e7 731990 postgresql-contrib-9.0_9.0.6-1~bpo50+1_i386.deb
 8340b95ad0db006df33623ff75ef796ba6adb764 383340 postgresql-plperl-9.0_9.0.6-1~bpo50+1_i386.deb
 8aeb3c58e64bbee9562e3a3b35c25cc01918dbd7 386754 postgresql-plpython-9.0_9.0.6-1~bpo50+1_i386.deb
 dc88023e89e7d544cab25509d4d95b4ac67d1d73 362502 postgresql-pltcl-9.0_9.0.6-1~bpo50+1_i386.deb
Checksums-Sha256: 
 9cdbd9e02f3b1889ed43993f2788a28def8408e63554dde575488831cd758731 2457 postgresql-9.0_9.0.6-1~bpo50+1.dsc
 317d99d2ff9e1de8da0cae107bc06c9fd455b1df0c0fb77b8fbb61fb08276056 14777282 postgresql-9.0_9.0.6.orig.tar.bz2
 3b8210a0c7cd0ff8a6cb17fe20ead96601929f98de64c2358207c560d74a05c5 27893 postgresql-9.0_9.0.6-1~bpo50+1.debian.tar.gz
 1ab455e08a7d56ec70046706daf992ac78cff1a9621449046191756c55a4bffb 2611680 postgresql-doc-9.0_9.0.6-1~bpo50+1_all.deb
 888f18512d465f0561b5672875aabc188e32c4404dcab3625ad334f55e225e57 5919776 postgresql-9.0_9.0.6-1~bpo50+1_i386.deb
 f078459422ebd550974e1528966d535577a421b9b9889db305a7f6420844f559 6971944 postgresql-9.0-dbg_9.0.6-1~bpo50+1_i386.deb
 655e55bfc43175fc6081a833281f89b839566d4eee33f963cde7d39fe6a86c2e 1771032 postgresql-client-9.0_9.0.6-1~bpo50+1_i386.deb
 9a937664a11638cab7d2930cd1461d9c51768407d4e3310702ff8d9e2c2ceb45 980448 postgresql-server-dev-9.0_9.0.6-1~bpo50+1_i386.deb
 d878b6aa96308867c3a83bdb0b98edb7f65b865d1875c6d2c35a5c9f80d2f44e 731990 postgresql-contrib-9.0_9.0.6-1~bpo50+1_i386.deb
 69a3cc4ff5d7720bce0ac444c296cf7f2c16d6b4fd947d066db411635cb45007 383340 postgresql-plperl-9.0_9.0.6-1~bpo50+1_i386.deb
 1ab4376a5b50e3b2db0d528e5523c8db78bdb1542845dd6ae83922985c565334 386754 postgresql-plpython-9.0_9.0.6-1~bpo50+1_i386.deb
 fd143caed9549d23efca6aeaffce080ff909c9f419f1da4485afa115cafa4b17 362502 postgresql-pltcl-9.0_9.0.6-1~bpo50+1_i386.deb
Files: 
 3f27994d2b6c8af37f1bd9e002c5d5b1 2457 database optional postgresql-9.0_9.0.6-1~bpo50+1.dsc
 4ad7e4fc31ef8b8a75a3e4243933963f 14777282 database optional postgresql-9.0_9.0.6.orig.tar.bz2
 2bce91ac296bbeb26725bc441a4bb9a7 27893 database optional postgresql-9.0_9.0.6-1~bpo50+1.debian.tar.gz
 db65ea8afbdd0ac2edda4f7576cae264 2611680 doc optional postgresql-doc-9.0_9.0.6-1~bpo50+1_all.deb
 614fd7b789d67b4ee1713b3bf023aca7 5919776 database optional postgresql-9.0_9.0.6-1~bpo50+1_i386.deb
 661c31f56ab1d54e7b6caf42e17d6225 6971944 debug extra postgresql-9.0-dbg_9.0.6-1~bpo50+1_i386.deb
 a36380f51fac9a98fdaa960dc99ef1d7 1771032 database optional postgresql-client-9.0_9.0.6-1~bpo50+1_i386.deb
 6e388f57704a6ef6e13846390c739f3a 980448 libdevel optional postgresql-server-dev-9.0_9.0.6-1~bpo50+1_i386.deb
 adcdc9afd70fad5b16fe886285adcd34 731990 database optional postgresql-contrib-9.0_9.0.6-1~bpo50+1_i386.deb
 a0bbc5b8cb664b2ae7500e61b77d1448 383340 database optional postgresql-plperl-9.0_9.0.6-1~bpo50+1_i386.deb
 f096d7ab904bff85fe01ac45bca454d6 386754 database optional postgresql-plpython-9.0_9.0.6-1~bpo50+1_i386.deb
 dd6f76c4bca8093538e2a724d4079c85 362502 database optional postgresql-pltcl-9.0_9.0.6-1~bpo50+1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJO8x7NAAoJEExaa6sS0qeuVxoP/R3fvKVQFdeJ++1r5wglP6z5
0bOMLq1VtKe2e0bzbsd9ZyNcSUJ04kwExmc5vdhNcJx6itu2iyaqLTXK4RyzRDAQ
k7lfLaalWkQZNCl4RR2tnjumoTqODYIQK/mM6q7E2oYrCYRlKJhJawBk8jtpKKs1
F7JbQUsrNAnt+80+9ik+aGmTFxupWznnjZhdW6vDK4sYyDuFGhQ/N551NYHQU0zo
AxvBDMX14cW5tTIEdTwH7fUDFjoD9fS7LR+Vbc6GdLV6EVMoW/yAK/sKpUL9Y5AA
eQopFWsz0s8acH3iEvhYwAu6XSMKmtYtphbwu2N4Mk3Nl1v3AbZ2Vtlk95QTtyod
/vCkzB6ug9a3iMQJhSHLE9afYAef5xkYid8VkhLZIeraPjZx4r7CppO5ncgyqInw
9K+826HwvXv5O6paqUKotuXPmUuIE6ipaYPnpEqkcr7zD884/H16Gz+eW2KrbZQq
Cdprs31KJ48SF6w/cpmWNXF5nR+eS1j55qey5dQovZtDc7d3RS2E2IpqiAeimgbf
JB9k9d9O48Wqqcm2NRw9Jfn+JPQiQ69S1C5TnpEq9q+u2vfQrLpsdj8PmQ/ZaWpu
GPwS8IDBiGMWCP++76PpgZ9pAs7/DN6x6a30dve47od309wQzV0AMjs6a5CdvumA
/Ghe3ARlaNqVSjH4bgjh
=YYUQ
-----END PGP SIGNATURE-----


Accepted:
postgresql-9.0-dbg_9.0.6-1~bpo50+1_i386.deb
  to main/p/postgresql-9.0/postgresql-9.0-dbg_9.0.6-1~bpo50+1_i386.deb
postgresql-9.0_9.0.6-1~bpo50+1.debian.tar.gz
  to main/p/postgresql-9.0/postgresql-9.0_9.0.6-1~bpo50+1.debian.tar.gz
postgresql-9.0_9.0.6-1~bpo50+1.dsc
  to main/p/postgresql-9.0/postgresql-9.0_9.0.6-1~bpo50+1.dsc
postgresql-9.0_9.0.6-1~bpo50+1_i386.deb
  to main/p/postgresql-9.0/postgresql-9.0_9.0.6-1~bpo50+1_i386.deb
postgresql-client-9.0_9.0.6-1~bpo50+1_i386.deb
  to main/p/postgresql-9.0/postgresql-client-9.0_9.0.6-1~bpo50+1_i386.deb
postgresql-contrib-9.0_9.0.6-1~bpo50+1_i386.deb
  to main/p/postgresql-9.0/postgresql-contrib-9.0_9.0.6-1~bpo50+1_i386.deb
postgresql-doc-9.0_9.0.6-1~bpo50+1_all.deb
  to main/p/postgresql-9.0/postgresql-doc-9.0_9.0.6-1~bpo50+1_all.deb
postgresql-plperl-9.0_9.0.6-1~bpo50+1_i386.deb
  to main/p/postgresql-9.0/postgresql-plperl-9.0_9.0.6-1~bpo50+1_i386.deb
postgresql-plpython-9.0_9.0.6-1~bpo50+1_i386.deb
  to main/p/postgresql-9.0/postgresql-plpython-9.0_9.0.6-1~bpo50+1_i386.deb
postgresql-pltcl-9.0_9.0.6-1~bpo50+1_i386.deb
  to main/p/postgresql-9.0/postgresql-pltcl-9.0_9.0.6-1~bpo50+1_i386.deb
postgresql-server-dev-9.0_9.0.6-1~bpo50+1_i386.deb
  to main/p/postgresql-9.0/postgresql-server-dev-9.0_9.0.6-1~bpo50+1_i386.deb


Reply to: