Accepted postgresql-9.0 9.0.7-1~bpo60+1 (source all amd64)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 28 Mar 2012 10:02:34 +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 amd64
Version: 9.0.7-1~bpo60+1
Distribution: squeeze-backports
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.7-1~bpo60+1) squeeze-backports; urgency=low
.
* Rebuild for squeeze-backports.
.
postgresql-9.0 (9.0.7-1) unstable; urgency=low
.
* New upstream 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 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.
- 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
Previously the OID counter would remain stuck at a high value until the
system exited replay mode. The practical consequences of that are usually
nil, but there are scenarios wherein a standby server that's been
promoted to master might take a long time to advance the OID counter to a
reasonable value once values are needed.
- Prevent emitting misleading "consistent recovery state reached" log
message at the beginning of crash recovery
- Fix initial value of pg_stat_replication.replay_location
Previously, the value shown would be wrong until at least one WAL record
had been replayed.
- 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
A patch in the December 2011 releases of PostgreSQL caused memory leakage
in these operations, which could be significant in scenarios such as
building a btree index on such a column.
- 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.
- Avoid double close of file handle in syslogger on Windows
Ordinarily this error was invisible, but it would cause an exception when
running on a debug version of Windows.
- Fix I/O-conversion-related memory leaks in plpgsql
Certain operations would leak memory until the end of the current
function.
- 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.
- 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
The output used brackets at the top level, when it should have used braces.
- 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
Our configure script previously believed that this combination wouldn't
work; but FreeBSD fixed the problem, so remove that error check.
.
* Changes merged from 9.1 branch:
* debian/control: Add missing docbook-dsssl build dependency to fix
generation of documentation. (See: #654330)
* debian/control: Use openjade instead of the ancient jade for building the
documentation.
* debian/control: Re-add bison and flex build dependencies, so that the
generated and shipped Makefile.global gets non-empty BISON and FLEX
values. (See: #647135)
* Add docbook-xsl, opensp and xsltproc build dependencies.
* debian/watch: Use ftp for checking, thanks Peter Eisentraut.
(See: #656129)
* debian/control: Bump Standards-Version to 3.9.3. No changes necessary.
* debian/control, debian/rules: Support and prefer dpkg-buildflags when
building with dpkg-dev >= 1.16.1~. Fall back to hardening-wrapper
otherwise, to keep supporting backports.
* debian/rules: Build with "-z now" for some extra hardening. We can't use
the full "hardening=+all", as PIE causes build failures.
Checksums-Sha1:
6767c750d85c9f068eca431268cc67cfa0aa40a4 2545 postgresql-9.0_9.0.7-1~bpo60+1.dsc
c0cf6de3cfa131b36107b3748ae44786ad638e12 14977437 postgresql-9.0_9.0.7.orig.tar.bz2
1b32f0dfdceb698eab90b41f9221f4a6f5afdd82 41094 postgresql-9.0_9.0.7-1~bpo60+1.debian.tar.gz
71727e07ce8df5a9408f6bc84733afd9108eef95 2642508 postgresql-doc-9.0_9.0.7-1~bpo60+1_all.deb
f904d2f2451d7c4265c04463d0c615ee3bdd713f 6243472 postgresql-9.0_9.0.7-1~bpo60+1_amd64.deb
e98544d66739f1123fb23f8e59bdd49d05292866 7090526 postgresql-9.0-dbg_9.0.7-1~bpo60+1_amd64.deb
546d13ee79bd99e9db1c4d5cfe0a29d1c7dea36c 1913534 postgresql-client-9.0_9.0.7-1~bpo60+1_amd64.deb
a6105219b4d718738647079d23f20fecbe0e6df2 997864 postgresql-server-dev-9.0_9.0.7-1~bpo60+1_amd64.deb
80b6df1d992bc15c960c49422aecd7b5d0ef2952 791636 postgresql-contrib-9.0_9.0.7-1~bpo60+1_amd64.deb
c91a11bad2e773f69f36bccf500a7fd5059a4a4f 400032 postgresql-plperl-9.0_9.0.7-1~bpo60+1_amd64.deb
06553069865ca84cbcb506bff08991889dc06963 405470 postgresql-plpython-9.0_9.0.7-1~bpo60+1_amd64.deb
61980e8607c4e76fee3cad6bfcc05c2446f815d6 377296 postgresql-pltcl-9.0_9.0.7-1~bpo60+1_amd64.deb
Checksums-Sha256:
e65c9a8b488b9f94b1e5fc23f709a97a2bfee21679a53a199d298c4fd5d8acb8 2545 postgresql-9.0_9.0.7-1~bpo60+1.dsc
dabe26d71d8b595f9514da1363dc20c3f4b90b6908026dd06984cac448a6d833 14977437 postgresql-9.0_9.0.7.orig.tar.bz2
aaa2b8d8475ea0cc14226cc6f1d635bb8294e0e020f56f1acda137b59522bf61 41094 postgresql-9.0_9.0.7-1~bpo60+1.debian.tar.gz
ce0040dcea774521ecc7293483241a06adf18ba12fdef30f812201433b5e7a42 2642508 postgresql-doc-9.0_9.0.7-1~bpo60+1_all.deb
5df379486c4a0074b61b6f27e03dbbfca406bd8ddc113c5de2e0af4cda68e395 6243472 postgresql-9.0_9.0.7-1~bpo60+1_amd64.deb
85a91818c39f71061cc0087064cfa9918a1cf1df56272ec80b9f4b4e803ecc97 7090526 postgresql-9.0-dbg_9.0.7-1~bpo60+1_amd64.deb
2b9a68bf1f7bd92a2260a4bcee1582ef51779e7125b96faf0129f93f8b47ba28 1913534 postgresql-client-9.0_9.0.7-1~bpo60+1_amd64.deb
6491329222862c57e2f4965aaa04662bceba827fc4614adaf83bf2a9fe293ea5 997864 postgresql-server-dev-9.0_9.0.7-1~bpo60+1_amd64.deb
2b3826dc7d48e9ab3f2da26c2b04374aff5a2773d1d51872ee3aa2095ea064a7 791636 postgresql-contrib-9.0_9.0.7-1~bpo60+1_amd64.deb
5dc680801823cd04d541b350e2cc5e9bad707aa8a3e9ab880428ce2e8be33619 400032 postgresql-plperl-9.0_9.0.7-1~bpo60+1_amd64.deb
fc4294bc98c2059031cfa9672410d7fdd0864c1e391440e0262d6059bfda3134 405470 postgresql-plpython-9.0_9.0.7-1~bpo60+1_amd64.deb
9223211bbc2b094732bc7365f0a53806ec8291e4eab5f78f190f7d52535271eb 377296 postgresql-pltcl-9.0_9.0.7-1~bpo60+1_amd64.deb
Files:
6e0823486b13f766f888eda1c1410821 2545 database optional postgresql-9.0_9.0.7-1~bpo60+1.dsc
27e67f48607c29df8ca6aab2a6fdf0b8 14977437 database optional postgresql-9.0_9.0.7.orig.tar.bz2
331d74e0f1567492581821baeba1da88 41094 database optional postgresql-9.0_9.0.7-1~bpo60+1.debian.tar.gz
c417bd6924911c6c7130f1546080333b 2642508 doc optional postgresql-doc-9.0_9.0.7-1~bpo60+1_all.deb
a7ab1d3171a0b27d2da2f6b20c2d9e8c 6243472 database optional postgresql-9.0_9.0.7-1~bpo60+1_amd64.deb
a3860b209ad3b57bba415df081d0a646 7090526 debug extra postgresql-9.0-dbg_9.0.7-1~bpo60+1_amd64.deb
cc38919d721c43c2fbcc2260e20a4b3a 1913534 database optional postgresql-client-9.0_9.0.7-1~bpo60+1_amd64.deb
d36641dc507e801cd32d89a9628d3f3f 997864 libdevel optional postgresql-server-dev-9.0_9.0.7-1~bpo60+1_amd64.deb
255f152d605c081dfaf17de3cf6ec32e 791636 database optional postgresql-contrib-9.0_9.0.7-1~bpo60+1_amd64.deb
ae2a0b55036a96afa53f7b08b70829c2 400032 database optional postgresql-plperl-9.0_9.0.7-1~bpo60+1_amd64.deb
34d46cb21f20a413c4ee7db701f2fdd2 405470 database optional postgresql-plpython-9.0_9.0.7-1~bpo60+1_amd64.deb
1cca386c96a879c8f050632ed76443cc 377296 database optional postgresql-pltcl-9.0_9.0.7-1~bpo60+1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJPcs9jAAoJEExaa6sS0qeuFdgP/j01G2hKQdeBxvHMbArL59c0
FtNQ9ZNpRCW37I1ScLfHo2v/PRFbchc/Q8bW6MOOqGOlOHQofMR+nYlIRKSQyC3+
+/JO53zJrWBJ/zIBnijumkKdWkhDgtuvTXtZGLiY6VsverVGlLaDcGxwvuKqWNPc
qUGglKgd417omd4Jj3+5T4wU4zmSHDPD2woUpKC3/ulW+VYxQKWSS0r6dMxGESNA
pOTNkfhwRdtzc9nVMEkruQ7y8Qn2vZ3qSnt2RzjPvkRVPhSfrT1qObZ+HOa7eFrW
Z8iXjdg/GmRKOKOZqWpqlBCHFeMdwfGIxIzMfkrKkBrL5UmREQgOuI7lJKNuuw8/
j4FTrFcLYLdZC37IfhDdQK647OvbtIEuh5x10a4pGawvnSAb4F3Qr/cJQWWPa87a
quPgLORaoLQj5B5qGi61Ycr7ivvj8fTqkk/642Z3L3Dt53kM5iYaIbkRlDyc2klL
OiH+h69vJuKvexAIYf7lFVKDDrFGOXgdz8NkMordUFnyjE5xCifwtTuZ4S1Juu71
249WTsODTDM2liOgUkfkdfSqcYo6/+IDj/VHCHxb/Wxr2yebwgKQrMMdO72mdHGi
bVEo0pXq9T0z7Hc/EUm1EQ1+pAkkRbt0IRd3D6OdfnGW8NiEGsKH5+9q71crZCvR
8vc+P7QHc4rllG3I+WtM
=oJVP
-----END PGP SIGNATURE-----
Accepted:
postgresql-9.0-dbg_9.0.7-1~bpo60+1_amd64.deb
to main/p/postgresql-9.0/postgresql-9.0-dbg_9.0.7-1~bpo60+1_amd64.deb
postgresql-9.0_9.0.7-1~bpo60+1.debian.tar.gz
to main/p/postgresql-9.0/postgresql-9.0_9.0.7-1~bpo60+1.debian.tar.gz
postgresql-9.0_9.0.7-1~bpo60+1.dsc
to main/p/postgresql-9.0/postgresql-9.0_9.0.7-1~bpo60+1.dsc
postgresql-9.0_9.0.7-1~bpo60+1_amd64.deb
to main/p/postgresql-9.0/postgresql-9.0_9.0.7-1~bpo60+1_amd64.deb
postgresql-9.0_9.0.7.orig.tar.bz2
to main/p/postgresql-9.0/postgresql-9.0_9.0.7.orig.tar.bz2
postgresql-client-9.0_9.0.7-1~bpo60+1_amd64.deb
to main/p/postgresql-9.0/postgresql-client-9.0_9.0.7-1~bpo60+1_amd64.deb
postgresql-contrib-9.0_9.0.7-1~bpo60+1_amd64.deb
to main/p/postgresql-9.0/postgresql-contrib-9.0_9.0.7-1~bpo60+1_amd64.deb
postgresql-doc-9.0_9.0.7-1~bpo60+1_all.deb
to main/p/postgresql-9.0/postgresql-doc-9.0_9.0.7-1~bpo60+1_all.deb
postgresql-plperl-9.0_9.0.7-1~bpo60+1_amd64.deb
to main/p/postgresql-9.0/postgresql-plperl-9.0_9.0.7-1~bpo60+1_amd64.deb
postgresql-plpython-9.0_9.0.7-1~bpo60+1_amd64.deb
to main/p/postgresql-9.0/postgresql-plpython-9.0_9.0.7-1~bpo60+1_amd64.deb
postgresql-pltcl-9.0_9.0.7-1~bpo60+1_amd64.deb
to main/p/postgresql-9.0/postgresql-pltcl-9.0_9.0.7-1~bpo60+1_amd64.deb
postgresql-server-dev-9.0_9.0.7-1~bpo60+1_amd64.deb
to main/p/postgresql-9.0/postgresql-server-dev-9.0_9.0.7-1~bpo60+1_amd64.deb
Reply to: