Accepted postgresql-9.0 9.0.5-1~bpo50+1 (source all i386)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 26 Sep 2011 16:43:22 +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: source all i386
Version: 9.0.5-1~bpo50+1
Distribution: lenny-backports-sloppy
Urgency: low
Maintainer: Martin Pitt <mpitt@debian.org>
Changed-By: Gerfried Fuchs <rhonda@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: 621492 627596 628505 636571
Changes:
postgresql-9.0 (9.0.5-1~bpo50+1) lenny-backports-sloppy; urgency=low
.
* Rebuild for lenny-backports-sloppy.
.
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.
.
postgresql-9.0 (9.0.4-3) unstable; urgency=low
.
* debian/control: Stop building the client-side libraries, they are built by
postgresql-9.1 now. Add libpq-dev build dependency.
* debian/rules: Drop check for uninstalled files, since it'd now break the
build due to the uninstalled libraries.
.
postgresql-9.0 (9.0.4-2) unstable; urgency=low
.
* debian/postgresql-9.0.postrm: Clean up pg_ctl.conf on purge.
* Add 03-cmsgcred-size.patch: Fix size of struct cmsgcred to fix ident
authentication on kFreeBSD 64 bit. Thanks to Petr Salinger for the
patch! (Closes: #627596)
* debian/control: Add explicit build dependency to jade. (Closes: #621492)
* debian/control: Drop the versionless metapackages, they are built by -9.1
now.
Checksums-Sha1:
f128740dbb986aadc1ad0f0c97e1965b484ea396 2078 postgresql-9.0_9.0.5-1~bpo50+1.dsc
1c71be5b1a7d519eff33bb60768776f47b44acf3 14344752 postgresql-9.0_9.0.5.orig.tar.bz2
860be6980245d0f22f7c33fbde315e8c6906f641 25693 postgresql-9.0_9.0.5-1~bpo50+1.debian.tar.gz
f4e7575542fa6123f093583515cb59581cbca7a1 2373872 postgresql-doc-9.0_9.0.5-1~bpo50+1_all.deb
adcf0b74a57d7790a7c4560498a43f61fcc3b14d 5886758 postgresql-9.0_9.0.5-1~bpo50+1_i386.deb
6c9317ed0caa684b98254e9c9380716b13000025 6918182 postgresql-9.0-dbg_9.0.5-1~bpo50+1_i386.deb
003937b99c4ff37f53124d92169affc631431183 1742146 postgresql-client-9.0_9.0.5-1~bpo50+1_i386.deb
0d5339d1136c63459a94a2b0d6fc95ae7c2a7b99 963796 postgresql-server-dev-9.0_9.0.5-1~bpo50+1_i386.deb
ac3cdd2c3969d3fcafa9120ed4d5b3264b3bdda1 719502 postgresql-contrib-9.0_9.0.5-1~bpo50+1_i386.deb
307026b9d1791992caf0a4e6e3f7081031ae3cde 372848 postgresql-plperl-9.0_9.0.5-1~bpo50+1_i386.deb
d41199ee9f8fd81f130864721e560de67f36bf0b 376980 postgresql-plpython-9.0_9.0.5-1~bpo50+1_i386.deb
b7ada73db4b0b9e1ef9642ad6b019ac24157bf2d 351614 postgresql-pltcl-9.0_9.0.5-1~bpo50+1_i386.deb
Checksums-Sha256:
d413d224d5b4ad31f4f9111b7f099e8811dde233509a633a768dfd2f3998aa66 2078 postgresql-9.0_9.0.5-1~bpo50+1.dsc
56d8ee809ceeabeae8461ae0a197943460cba5bf8fbe37324e4451cf2eb7d504 14344752 postgresql-9.0_9.0.5.orig.tar.bz2
16ed117432d7976f29e220fa800ffe06f4e7bf54d8a820592c8ceb59cbc1139f 25693 postgresql-9.0_9.0.5-1~bpo50+1.debian.tar.gz
93f085f2696ca4995b8d47ca1d01a86fb33def6da0d31f1e42d2df64a2cfebdb 2373872 postgresql-doc-9.0_9.0.5-1~bpo50+1_all.deb
b394a5f982e72fd96cdeb590ec489725abffc032a35371c8936000d341aae007 5886758 postgresql-9.0_9.0.5-1~bpo50+1_i386.deb
5dabe4587c2330ca19536d31b6fe5592ce2b008eeeb99dbbdeeda679029a3b39 6918182 postgresql-9.0-dbg_9.0.5-1~bpo50+1_i386.deb
0a3355cd2f306f62d3946c7621ec7ab82eb80e3cf31dd4bbd320fc181c273e3e 1742146 postgresql-client-9.0_9.0.5-1~bpo50+1_i386.deb
529549025619992cfa9fdf5ecc3fdf762a829a5a31e69762ca9948382337f73f 963796 postgresql-server-dev-9.0_9.0.5-1~bpo50+1_i386.deb
b3bc45e641391f013f22287ea57b3157ada797f16d9cbefa0f4a5d77815a2d1f 719502 postgresql-contrib-9.0_9.0.5-1~bpo50+1_i386.deb
f5a1badea24875f28c45945d688f9cc504c0b9831f25a0faadaea01d57f4e09d 372848 postgresql-plperl-9.0_9.0.5-1~bpo50+1_i386.deb
9305fb8a9b2ec04f8ae6f7c523fb7c375a78ffed630e00226518fcbc507ecbe7 376980 postgresql-plpython-9.0_9.0.5-1~bpo50+1_i386.deb
9cfc7010470b01e29baf05a28cfc507d3a5f249be96950a55c7c59016e10a133 351614 postgresql-pltcl-9.0_9.0.5-1~bpo50+1_i386.deb
Files:
d9be05f420157a83391f5744909f69cf 2078 database optional postgresql-9.0_9.0.5-1~bpo50+1.dsc
86816eb8a8513532957b96045abdfef9 14344752 database optional postgresql-9.0_9.0.5.orig.tar.bz2
30779860abd6b53554da542f8fed8597 25693 database optional postgresql-9.0_9.0.5-1~bpo50+1.debian.tar.gz
4f5c71f7f0aaa1cb7f02f74387648e6a 2373872 doc optional postgresql-doc-9.0_9.0.5-1~bpo50+1_all.deb
0fb635f5a875ee36ef3eb6540b54ef20 5886758 database optional postgresql-9.0_9.0.5-1~bpo50+1_i386.deb
6cebad3ee740755eda2463d598cb42ae 6918182 debug extra postgresql-9.0-dbg_9.0.5-1~bpo50+1_i386.deb
37107e9f648b3ea871818f9c388c77c9 1742146 database optional postgresql-client-9.0_9.0.5-1~bpo50+1_i386.deb
f4a9c5af62a6e542aa1f02ddde37f3cd 963796 libdevel optional postgresql-server-dev-9.0_9.0.5-1~bpo50+1_i386.deb
e6cd7c1ff7a67d6040b15eca201670ca 719502 database optional postgresql-contrib-9.0_9.0.5-1~bpo50+1_i386.deb
b4ee2b1f9487715caa7ec9bc24725bcb 372848 database optional postgresql-plperl-9.0_9.0.5-1~bpo50+1_i386.deb
ae50398a5991897e40a0ebdb2467bf35 376980 database optional postgresql-plpython-9.0_9.0.5-1~bpo50+1_i386.deb
95622e2014b1b4ba0ddb0913aff50f2d 351614 database optional postgresql-pltcl-9.0_9.0.5-1~bpo50+1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBCAAGBQJOgW1xAAoJEDH85+fdB5RhQWEIAI+gW9ueRilBugnrBG68Jnn0
1zMC7d2QShw0IARKq/0g8hTrJAilcSezI1xOEk56+vs+hlEikfoUitWlMHY4+ht8
KlSw4w0pRjJpIc0dTfsO9H3/OHHQFWUTyQyto/sepRtVM1t9BhBzqm2xrkt4NYxE
ybwVag4myiF92SIxu6oyxRDeLviv8xsbKS/LYvM0Hd+jjQPLKOL3j0k94Jhh0PcN
emkRCeJQgEjovg3AJWfBiR8tXAqdOA0XKEopxe/MH7JX7VnmwOAoL9zJ8fjAVkoQ
kHJmOeAzuS28XM6xV3KbHKD9Jf8RDGS1yxOy0ijBOeyU5EnkVDBz3iK8d+JBaEA=
=PJA9
-----END PGP SIGNATURE-----
Accepted:
postgresql-9.0-dbg_9.0.5-1~bpo50+1_i386.deb
to main/p/postgresql-9.0/postgresql-9.0-dbg_9.0.5-1~bpo50+1_i386.deb
postgresql-9.0_9.0.5-1~bpo50+1.debian.tar.gz
to main/p/postgresql-9.0/postgresql-9.0_9.0.5-1~bpo50+1.debian.tar.gz
postgresql-9.0_9.0.5-1~bpo50+1.dsc
to main/p/postgresql-9.0/postgresql-9.0_9.0.5-1~bpo50+1.dsc
postgresql-9.0_9.0.5-1~bpo50+1_i386.deb
to main/p/postgresql-9.0/postgresql-9.0_9.0.5-1~bpo50+1_i386.deb
postgresql-9.0_9.0.5.orig.tar.bz2
to main/p/postgresql-9.0/postgresql-9.0_9.0.5.orig.tar.bz2
postgresql-client-9.0_9.0.5-1~bpo50+1_i386.deb
to main/p/postgresql-9.0/postgresql-client-9.0_9.0.5-1~bpo50+1_i386.deb
postgresql-contrib-9.0_9.0.5-1~bpo50+1_i386.deb
to main/p/postgresql-9.0/postgresql-contrib-9.0_9.0.5-1~bpo50+1_i386.deb
postgresql-doc-9.0_9.0.5-1~bpo50+1_all.deb
to main/p/postgresql-9.0/postgresql-doc-9.0_9.0.5-1~bpo50+1_all.deb
postgresql-plperl-9.0_9.0.5-1~bpo50+1_i386.deb
to main/p/postgresql-9.0/postgresql-plperl-9.0_9.0.5-1~bpo50+1_i386.deb
postgresql-plpython-9.0_9.0.5-1~bpo50+1_i386.deb
to main/p/postgresql-9.0/postgresql-plpython-9.0_9.0.5-1~bpo50+1_i386.deb
postgresql-pltcl-9.0_9.0.5-1~bpo50+1_i386.deb
to main/p/postgresql-9.0/postgresql-pltcl-9.0_9.0.5-1~bpo50+1_i386.deb
postgresql-server-dev-9.0_9.0.5-1~bpo50+1_i386.deb
to main/p/postgresql-9.0/postgresql-server-dev-9.0_9.0.5-1~bpo50+1_i386.deb
Reply to: