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

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



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

Format: 1.8
Date: Wed, 21 Dec 2011 20:19:08 +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~bpo60+1
Distribution: squeeze-backports
Urgency: medium
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
Closes: 551880 589523 603599 616180 616949 621492 627596 628505 636571
Changes: 
 postgresql-9.0 (9.0.6-1~bpo60+1) squeeze-backports; urgency=low
 .
   * Rebuild for squeeze-backports.
 .
 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.
Checksums-Sha1: 
 a7186852c666f59adf73f8e0ae4a2a4d100cfbe2 2458 postgresql-9.0_9.0.6-1~bpo60+1.dsc
 4a9a7d5579d3683ca1992b2ba116a4356094b3ca 14777282 postgresql-9.0_9.0.6.orig.tar.bz2
 46490c23c0bc24fc89ec38b4a9b90037a9650cf3 32837 postgresql-9.0_9.0.6-1~bpo60+1.debian.tar.gz
 ce38398ecdedf7337d5f7c397f544709ac240f2e 2611776 postgresql-doc-9.0_9.0.6-1~bpo60+1_all.deb
 f1074f947fc373b49aa040498a0362f361dc565e 5926380 postgresql-9.0_9.0.6-1~bpo60+1_i386.deb
 041ee4a810339e49c717fba5d289debb81385664 6883038 postgresql-9.0-dbg_9.0.6-1~bpo60+1_i386.deb
 e8f5de104b8ad72de6fa05811f77ffa2946ecfc7 1776204 postgresql-client-9.0_9.0.6-1~bpo60+1_i386.deb
 00400868b1867685083d01f4edf235bd92fcdefb 980466 postgresql-server-dev-9.0_9.0.6-1~bpo60+1_i386.deb
 48365ba7fc71685946c3de71110d2ba1c6b64b5f 734686 postgresql-contrib-9.0_9.0.6-1~bpo60+1_i386.deb
 22e7cda5d54aa59a777c916cb83de243642b1370 383492 postgresql-plperl-9.0_9.0.6-1~bpo60+1_i386.deb
 c04301b651989323e4a91bcfc74e36597bdbb735 386746 postgresql-plpython-9.0_9.0.6-1~bpo60+1_i386.deb
 d276023f2a031c8f27304c3edec1a95a8e809eb5 362582 postgresql-pltcl-9.0_9.0.6-1~bpo60+1_i386.deb
Checksums-Sha256: 
 6c5154bb8fc9383df31654e91e3d427d208f0455d8cc3f36d2d642e803ec179d 2458 postgresql-9.0_9.0.6-1~bpo60+1.dsc
 317d99d2ff9e1de8da0cae107bc06c9fd455b1df0c0fb77b8fbb61fb08276056 14777282 postgresql-9.0_9.0.6.orig.tar.bz2
 117c6504a7b01b205427b5df05064a94de8c6da06ee7f60a0ef68a0ebe8e4d2f 32837 postgresql-9.0_9.0.6-1~bpo60+1.debian.tar.gz
 c0be768c318b3b9fd6aab2edc5b8be33fa95d669a69d888c6975a81640e4c1b6 2611776 postgresql-doc-9.0_9.0.6-1~bpo60+1_all.deb
 eb2bdb7b36271affa723d6b30c42499738059262d7a52022d2b76494b84b37df 5926380 postgresql-9.0_9.0.6-1~bpo60+1_i386.deb
 6c8659c3c66a70a359b44bcea41f55bbbf8655cf0895e35e2e75fa03f8bf8676 6883038 postgresql-9.0-dbg_9.0.6-1~bpo60+1_i386.deb
 a0a252bb70e712fbbf79a627b21c6362baedffe51dc46bb80d37846c81987ad4 1776204 postgresql-client-9.0_9.0.6-1~bpo60+1_i386.deb
 feeb13f5970f520411e60a99e92e937c2a07e29c818c77c88a03bec423808c2d 980466 postgresql-server-dev-9.0_9.0.6-1~bpo60+1_i386.deb
 081c94a564e161f2f9df1ec2588a36d8fda16b1b2bfb27f7e28c25e4e01ab2e5 734686 postgresql-contrib-9.0_9.0.6-1~bpo60+1_i386.deb
 b9a0c325fea2888133f68498f26367c22505e825adb07938e8f32e968f3023bf 383492 postgresql-plperl-9.0_9.0.6-1~bpo60+1_i386.deb
 1e6cd6edf66c2d58f73ac5d91acb020ea2b8e5b2fe62e485623c3bbe6cd0025c 386746 postgresql-plpython-9.0_9.0.6-1~bpo60+1_i386.deb
 78f4a37edc144d6674be80e2fc6edaf08a936499e2072dd2ce6efa5b04d68ac8 362582 postgresql-pltcl-9.0_9.0.6-1~bpo60+1_i386.deb
Files: 
 1d1309c2702212b3a6c78df7e5d1561c 2458 database optional postgresql-9.0_9.0.6-1~bpo60+1.dsc
 4ad7e4fc31ef8b8a75a3e4243933963f 14777282 database optional postgresql-9.0_9.0.6.orig.tar.bz2
 0665bc26883e6efa671a4f519b54d782 32837 database optional postgresql-9.0_9.0.6-1~bpo60+1.debian.tar.gz
 b20215353cf45db17f81f9b5b2bd09f3 2611776 doc optional postgresql-doc-9.0_9.0.6-1~bpo60+1_all.deb
 235bfceacbb9d8a51e6de478c467cc4a 5926380 database optional postgresql-9.0_9.0.6-1~bpo60+1_i386.deb
 20c8492fbb6fa09553e877a17482021d 6883038 debug extra postgresql-9.0-dbg_9.0.6-1~bpo60+1_i386.deb
 a450770f987656e08d22265e319bdd1a 1776204 database optional postgresql-client-9.0_9.0.6-1~bpo60+1_i386.deb
 4832ea284c4ed654ed2d0d5487d54696 980466 libdevel optional postgresql-server-dev-9.0_9.0.6-1~bpo60+1_i386.deb
 844ec059987b512b2b21f0a238e14bbc 734686 database optional postgresql-contrib-9.0_9.0.6-1~bpo60+1_i386.deb
 5db0b5436f4d8b7e296673feff5bdf03 383492 database optional postgresql-plperl-9.0_9.0.6-1~bpo60+1_i386.deb
 cb8996bb16327bd62167be63142ac2aa 386746 database optional postgresql-plpython-9.0_9.0.6-1~bpo60+1_i386.deb
 cd9a64be9da323433a48abc9e8ab28ba 362582 database optional postgresql-pltcl-9.0_9.0.6-1~bpo60+1_i386.deb

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

iQIcBAEBCAAGBQJO8j0hAAoJEExaa6sS0qeuXjsP/iiEy9lAqR7nCT0Lm8xhu0vi
vTtV/nB19kDV+tNYiG5YtJ1OIkuly4w6e1TiiHqh/uhmuPc4qhl5conLYcrPkRTW
mJhZ5qsSPbRhuyxhggp3wlx/IRKBdYbxHVfdhT2UoryKn5UM/i8tMUzGYgfMo07J
kZsgfapms3k00hSk6BAZGoV9OFIujnf/BdO9H7EbnNx5ERyVYg/TTGKQOxoarLk7
N8a/QdbhlMfx6sjLkMnM10FVB6OF1FpyqumMln5sZKmpodc67ldmnRDcGr7/NeAS
gp0mn6R/OFGPMknna/+06LrvgMKvjsNr/7102G5c+4zwCC0ZCy7y06rKFnNWjnJX
vaclGJrs7xzoK2Fj/3aGX2ijuv/6tKZYGHgNkp0cPu4uLsZzlOmHJHPstyE8K7zk
woLPYHKAQG8+o0PqfTKnzl41zTJRVCsBzHPyv4TUumFCg/wWJlF+HScJ2lg9aaPB
aDTJEEkf084p4J5h5M6CmwIVGZJ2v/6fSHiUmx1jrM0rm8a0tIIRCbEfSaBxauSF
f126b5kVd/24CDOLZvtuczRjDiucBjmzolDG6wEsfArRcwrXIjDvff1VIUxBSBc4
L2D2gKoszguEeOFALz6Hz7XsQyAN0IfyJUL/c5wTyR/yamDHTmMM4FtD/SIj8A4X
zKkLoojZw2JrB5vaWu1s
=6VJ8
-----END PGP SIGNATURE-----


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


Reply to: