[ubuntu/dapper-proposed] postgresql-8.1 8.1.15-0ubuntu0.6.06 (Accepted)
Martin Pitt
martin.pitt at ubuntu.com
Wed Nov 5 08:13:42 GMT 2008
postgresql-8.1 (8.1.15-0ubuntu0.6.06) dapper-proposed; urgency=low
* New upstream bugfix release 8.1.15: (LP: #293758)
- Fix GiST index corruption due to marking the wrong index entry
"dead" after a deletion. This would result in index searches failing to
find rows they should have found.
- Fix backend crash when the client encoding cannot represent a
localized error message.
- Fix possible crash when deeply nested functions are invoked from a
trigger.
- Fix mis-expansion of rule queries when a sub-SELECT appears in a
function call in FROM, a multi-row VALUES list, or a RETURNING list.
The usual symptom of this problem is an "unrecognized node type"
error.
- Ensure an error is reported when a newly-defined PL/pgSQL trigger
function is invoked as a normal function.
- Prevent possible collision of relfilenode numbers when moving a
table to another tablespace with "ALTER SET TABLESPACE".
The command tried to re-use the existing filename, instead of
picking one that is known unused in the destination directory.
- Fix incorrect tsearch2 headline generation when single query item
matches first word of text.
- Fix improper display of fractional seconds in interval values when
using a non-ISO datestyle in an "--enable-integer-datetimes" build.
- Ensure SPI_getvalue and SPI_getbinval behave correctly when the
passed tuple and tuple descriptor have different numbers of columns.
This situation is normal when a table has had columns added or
removed, but these two functions didn't handle it properly. The
only likely consequence is an incorrect error indication.
- Fix ecpg's parsing of "CREATE ROLE".
- Fix recent breakage of pg_ctl restart.
* New upstream bugfix release 8.1.14:
- Widen local lock counters from 32 to 64 bits. This responds to reports
that the counters could overflow in sufficiently long transactions,
leading to unexpected "lock is already held" errors.
- Fix possible duplicate output of tuples during a GiST index scan.
- Add checks in executor startup to ensure that the tuples produced
by an "INSERT" or "UPDATE" will match the target table's current
rowtype. "ALTER COLUMN TYPE", followed by re-use of a previously cached
plan, could produce this type of situation. The check protects
against data corruption and/or crashes that could ensue.
- Fix AT TIME ZONE to first try to interpret its timezone argument as
a timezone abbreviation, and only try it as a full timezone name if
that fails, rather than the other way around as formerly. The timestamp
input functions have always resolved ambiguous zone names in this order.
Making AT TIME ZONE do so as well improves consistency, and fixes a
compatibility bug introduced in 8.1: in ambiguous cases we now behave
the same as 8.0 and before did, since in the older versions AT TIME ZONE
accepted -only* abbreviations.
- Fix datetime input functions to correctly detect integer overflow
when running on a 64-bit platform.
- Improve performance of writing very long log messages to syslog.
- Fix bug in backwards scanning of a cursor on a SELECT DISTINCT ON
query.
- Fix planner bug with nested sub-select expressions. If the outer
sub-select has no direct dependency on the parent query, but the inner
one does, the outer value might not get recalculated for new parent
query rows.
- Fix planner to estimate that GROUP BY expressions yielding boolean
results always result in two groups, regardless of the expressions'
contents. This is very substantially more accurate than the regular
GROUP BY estimate for certain boolean tests like "col" IS NULL.
- Fix PL/PgSQL to not fail when a FOR loop's target variable is a
record containing composite-type fields.
- Improve pg_dump and pg_restore's error reporting after failure to
send a SQL command.
- Fix pg_ctl to properly preserve postmaster command-line arguments
across a restart.
* 03-gettext-domains.patch: Unfuzz for new upstream version.
Date: Tue, 04 Nov 2008 21:20:52 +0100
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Maintainer: Martin Pitt <mpitt at debian.org>
https://edge.launchpad.net/ubuntu/dapper/+source/postgresql-8.1/8.1.15-0ubuntu0.6.06
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 04 Nov 2008 21:20:52 +0100
Source: postgresql-8.1
Binary: postgresql-8.1 postgresql-pltcl-8.1 postgresql-plperl-8.1 libpgtypes2 libpq-dev libpq4 postgresql-doc-8.1 postgresql-plpython-8.1 libecpg-compat2 libecpg5 libecpg-dev postgresql-client-8.1 postgresql-server-dev-8.1 postgresql-contrib-8.1
Architecture: source
Version: 8.1.15-0ubuntu0.6.06
Distribution: dapper-proposed
Urgency: low
Maintainer: Martin Pitt <mpitt at debian.org>
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Description:
libecpg-compat2 - older version of run-time library for ECPG programs
libecpg-dev - development files for ECPG (Embedded PostgreSQL for C)
libecpg5 - run-time library for ECPG programs
libpgtypes2 - shared library libpgtypes for PostgreSQL 8.1
libpq-dev - header files for libpq4 (PostgreSQL library)
libpq4 - PostgreSQL C client library
postgresql-8.1 - object-relational SQL database, version 8.1 server
postgresql-client-8.1 - front-end programs for PostgreSQL 8.1
postgresql-contrib-8.1 - additional facilities for PostgreSQL
postgresql-doc-8.1 - documentation for the PostgreSQL database management system
postgresql-plperl-8.1 - PL/Perl procedural language for PostgreSQL 8.1
postgresql-plpython-8.1 - PL/Python procedural language for PostgreSQL 8.1
postgresql-pltcl-8.1 - PL/TCL procedural language for PostgreSQL 8.1
postgresql-server-dev-8.1 - development files for PostgreSQL 8.1 server-side programming
Changes:
postgresql-8.1 (8.1.15-0ubuntu0.6.06) dapper-proposed; urgency=low
.
* New upstream bugfix release 8.1.15: (LP: #293758)
- Fix GiST index corruption due to marking the wrong index entry
"dead" after a deletion. This would result in index searches failing to
find rows they should have found.
- Fix backend crash when the client encoding cannot represent a
localized error message.
- Fix possible crash when deeply nested functions are invoked from a
trigger.
- Fix mis-expansion of rule queries when a sub-SELECT appears in a
function call in FROM, a multi-row VALUES list, or a RETURNING list.
The usual symptom of this problem is an "unrecognized node type"
error.
- Ensure an error is reported when a newly-defined PL/pgSQL trigger
function is invoked as a normal function.
- Prevent possible collision of relfilenode numbers when moving a
table to another tablespace with "ALTER SET TABLESPACE".
The command tried to re-use the existing filename, instead of
picking one that is known unused in the destination directory.
- Fix incorrect tsearch2 headline generation when single query item
matches first word of text.
- Fix improper display of fractional seconds in interval values when
using a non-ISO datestyle in an "--enable-integer-datetimes" build.
- Ensure SPI_getvalue and SPI_getbinval behave correctly when the
passed tuple and tuple descriptor have different numbers of columns.
This situation is normal when a table has had columns added or
removed, but these two functions didn't handle it properly. The
only likely consequence is an incorrect error indication.
- Fix ecpg's parsing of "CREATE ROLE".
- Fix recent breakage of pg_ctl restart.
* New upstream bugfix release 8.1.14:
- Widen local lock counters from 32 to 64 bits. This responds to reports
that the counters could overflow in sufficiently long transactions,
leading to unexpected "lock is already held" errors.
- Fix possible duplicate output of tuples during a GiST index scan.
- Add checks in executor startup to ensure that the tuples produced
by an "INSERT" or "UPDATE" will match the target table's current
rowtype. "ALTER COLUMN TYPE", followed by re-use of a previously cached
plan, could produce this type of situation. The check protects
against data corruption and/or crashes that could ensue.
- Fix AT TIME ZONE to first try to interpret its timezone argument as
a timezone abbreviation, and only try it as a full timezone name if
that fails, rather than the other way around as formerly. The timestamp
input functions have always resolved ambiguous zone names in this order.
Making AT TIME ZONE do so as well improves consistency, and fixes a
compatibility bug introduced in 8.1: in ambiguous cases we now behave
the same as 8.0 and before did, since in the older versions AT TIME ZONE
accepted -only* abbreviations.
- Fix datetime input functions to correctly detect integer overflow
when running on a 64-bit platform.
- Improve performance of writing very long log messages to syslog.
- Fix bug in backwards scanning of a cursor on a SELECT DISTINCT ON
query.
- Fix planner bug with nested sub-select expressions. If the outer
sub-select has no direct dependency on the parent query, but the inner
one does, the outer value might not get recalculated for new parent
query rows.
- Fix planner to estimate that GROUP BY expressions yielding boolean
results always result in two groups, regardless of the expressions'
contents. This is very substantially more accurate than the regular
GROUP BY estimate for certain boolean tests like "col" IS NULL.
- Fix PL/PgSQL to not fail when a FOR loop's target variable is a
record containing composite-type fields.
- Improve pg_dump and pg_restore's error reporting after failure to
send a SQL command.
- Fix pg_ctl to properly preserve postmaster command-line arguments
across a restart.
* 03-gettext-domains.patch: Unfuzz for new upstream version.
Files:
6afae6970cb803baf7da093686877046 1130 misc optional postgresql-8.1_8.1.15-0ubuntu0.6.06.dsc
be27555014b20bff3830743f13831b25 11475238 misc optional postgresql-8.1_8.1.15.orig.tar.gz
22643e1f2cd9164e9be4f0ba30af49c7 29907 misc optional postgresql-8.1_8.1.15-0ubuntu0.6.06.diff.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkkQsncACgkQDecnbV4Fd/JNSQCeL9Tq+xFC3xaa1sYPBfBqciWK
32gAoJ6K6cf3DTtt1S828sQ8eaaQP8Fu
=1zjn
-----END PGP SIGNATURE-----
More information about the dapper-changes
mailing list