postgresql-9.1 9.1.3-1 source package in Ubuntu
Changelog
postgresql-9.1 (9.1.3-1) unstable; urgency=medium * Urgency medium due to security fixes. * New upstream security/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 handling of data-modifying WITH subplans in READ COMMITTED rechecking. A WITH clause containing "INSERT"/"UPDATE"/"DELETE" would crash if the parent "UPDATE" or "DELETE" command needed to be re-evaluated at one or more rows due to concurrent updates in READ COMMITTED mode. - Fix corner case in SSI transaction cleanup. When finishing up a read-write serializable transaction, a crash could occur if all remaining active serializable transactions are read-only. - 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. - Fix "unsupported node type" error caused by COLLATE in an "INSERT" expression. - 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. - Prevent emitting misleading "consistent recovery state reached" log message at the beginning of crash recovery. - Fix initial value of pg_stat_replication.replay_location. - 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. - Fix planner's ability to push down index-expression restrictions through UNION ALL. - Fix planning of WITH clauses referenced in "UPDATE"/"DELETE" on an inherited table. This bug led to "could not find plan for CTE" failures. - Fix GIN cost estimation to handle column IN (...) index conditions. This oversight would usually lead to crashes if such a condition could be used with a GIN index. - 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. - Fix I/O-conversion-related memory leaks in plpgsql. - Work around bug in perl's SvPVutf8() function. This function crashes when handed a typeglob or certain read-only objects such as $^V. Make plperl avoid passing those to it. - In pg_dump, don't dump contents of an extension's configuration tables if the extension itself is not being dumped. - 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. - Teach pg_upgrade to handle renaming of plpython's shared library. Upgrading a pre-9.1 database that included plpython would fail because of this oversight. - 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. - 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 (Chris Rees) Our configure script previously believed that this combination wouldn't work; but FreeBSD fixed the problem, so remove that error check. * Drop 00git_inet_cidr_unpack.patch, 01-armel-tas.patch: Applied upstream. * debian/watch: Use ftp for checking, thanks Peter Eisentraut. (Closes: #656129) * debian/control: Bump Standards-Version to 3.9.3. No changes necessary. -- Martin Pitt <email address hidden> Mon, 27 Feb 2012 07:30:59 +0100
Upload details
- Uploaded by:
- Martin Pitt
- Uploaded to:
- Sid
- Original maintainer:
- Martin Pitt
- Architectures:
- any all
- Section:
- database
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
postgresql-9.1_9.1.3-1.dsc | 3.1 KiB | 3c90f889c1837826803f28aebe94c44cdf9b743d98cef013593eeeeff24a05f1 |
postgresql-9.1_9.1.3.orig.tar.bz2 | 14.9 MiB | 7a79800a624031c1d9bc9cdce73cb40050100ac50a82050cbf7bbbd16ac4d5d5 |
postgresql-9.1_9.1.3-1.debian.tar.gz | 29.0 KiB | cb6b5b414e7713536ec15053346a7d774cf3d2d29e3f2b34c7b8f69cbb2d7149 |
Available diffs
- diff from 9.1.2-4 (in Ubuntu) to 9.1.3-1 (1.4 MiB)
No changes file available.
Binary packages built by this source
- libecpg-compat3: older version of run-time library for ECPG programs
The libecpg_compat shared library is used by programs built with ecpg.
(Embedded PostgreSQL for C).
.
PostgreSQL is an object-relational SQL database management system.
- libecpg-dev: development files for ECPG (Embedded PostgreSQL for C)
This package contains the necessary files to build ECPG (Embedded
PostgreSQL for C) programs. It includes the development libraries
and the preprocessor program ecpg.
.
PostgreSQL is an object-relational SQL database management system.
.
Install this package if you want to write C programs with SQL statements
embedded in them (rather than run by an external process).
- libecpg6: run-time library for ECPG programs
The libecpg shared library is used by programs built with ECPG
(Embedded PostgreSQL for C).
.
PostgreSQL is an object-relational SQL database management system.
- libpgtypes3: shared library libpgtypes for PostgreSQL 9.1
The libpgtypes shared library is used by programs built with ecpg.
(Embedded PostgreSQL for C).
.
PostgreSQL is an object-relational SQL database management system.
- libpq-dev: header files for libpq5 (PostgreSQL library)
Header files and static library for compiling C programs to link
with the libpq library in order to communicate with a PostgreSQL
database backend.
.
PostgreSQL is an object-relational SQL database management system.
- libpq5: PostgreSQL C client library
libpq is a C library that enables user programs to communicate with
the PostgreSQL database server. The server can be on another machine
and accessed through TCP/IP. This version of libpq is compatible
with servers from PostgreSQL 8.2 or later.
.
This package contains the run-time library, needed by packages using
libpq.
.
PostgreSQL is an object-relational SQL database management system.
- postgresql-9.1: object-relational SQL database, version 9.1 server
PostgreSQL is a fully featured object-relational database management
system. It supports a large part of the SQL standard and is designed
to be extensible by users in many aspects. Some of the features are:
ACID transactions, foreign keys, views, sequences, subqueries,
triggers, user-defined types and functions, outer joins, multiversion
concurrency control. Graphical user interfaces and bindings for many
programming languages are available as well.
.
This package provides the database server for PostgreSQL 9.1. Servers
for other major release versions can be installed simultaneously and
are coordinated by the postgresql-common package. A package providing
ident-server is needed if you want to authenticate remote connections
with identd.
- postgresql-9.1-dbg: debug symbols for postgresql-9.1
PostgreSQL is a fully featured object-relational database management
system. It supports a large part of the SQL standard and is designed
to be extensible by users in many aspects. Some of the features are:
ACID transactions, foreign keys, views, sequences, subqueries,
triggers, user-defined types and functions, outer joins, multiversion
concurrency control. Graphical user interfaces and bindings for many
programming languages are available as well.
.
This package provides detached debugging symbols for PostgreSQL 9.1.
- postgresql-client-9.1: front-end programs for PostgreSQL 9.1
This package contains client and administrative programs for
PostgreSQL: these are the interactive terminal client psql and
programs for creating and removing users and databases.
.
This is the client package for PostgreSQL 9.1. If you install
PostgreSQL 9.1 on a standalone machine, you need the server package
postgresql-9.1, too. On a network, you can install this package on
many client machines, while the server package may be installed on
only one machine.
..
PostgreSQL is an object-relational SQL database management system.
- postgresql-contrib-9.1: additional facilities for PostgreSQL
The PostgreSQL contrib package provides several additional features
for the PostgreSQL database. This version is built to work with the
server package postgresql-9.1. contrib often serves as a testbed for
features before they are adopted into PostgreSQL proper:
.
adminpack - File and log manipulation routines, used by pgAdmin
btree_gist - B-Tree indexing using GiST (Generalised Search Tree)
chkpass - An auto-encrypted password datatype
cube - Multidimensional-cube datatype (GiST indexing example)
dblink - Functions to return results from a remote database
earthdistance - Operator for computing the distance (in miles) between
two points on the earth's surface
fuzzystrmatch - Levenshtein, metaphone, and soundex fuzzy string matching
hstore - Store (key, value) pairs
intagg - Integer aggregator/enumerator
_int - Index support for arrays of int4, using GiST (benchmark
needs the libdbd-pg-perl package)
isn - type extensions for ISBN, ISSN, ISMN, EAN13 product numbers
lo - Large Object maintenance
ltree - Tree-like data structures
oid2name - Maps OIDs to table names
pageinspect - Inspection of database pages
passwordcheck - Simple password strength checker
pg_buffercache - Real time queries on the shared buffer cache
pg_freespacemap- Displays the contents of the free space map (FSM)
pg_trgm - Determine the similarity of text based on trigram matching
pg_standby - Create a warm stand-by server
pgbench - TPC-B like benchmark
pgcrypto - Cryptographic functions
pgrowlocks - A function to return row locking information
pgstattuple - Returns the percentage of dead tuples in a table; this
indicates whether a vacuum is required.
seg - Confidence-interval datatype (GiST indexing example)
spi - PostgreSQL Server Programming Interface; 4 examples of
its use:
autoinc - A function for implementing AUTOINCREMENT/
IDENTITY
insert_ username - function for inserting user names
moddatetim e - Update modification timestamps
refint - Functions for implementing referential
integrity (foreign keys). Note that this is
now superseded by built-in referential
integrity.
timetravel - Re-implements in user code the time travel
feature that was removed in 6.3.
tablefunc - examples of functions returning tables
uuid-ossp - UUID generation functions
vacuumlo - Remove orphaned large objects
.
PostgreSQL is an object-relational SQL database management system.
- postgresql-doc-9.1: documentation for the PostgreSQL database management system
This package contains all README files, user manual, and examples for
PostgreSQL 9.1. The manual is in HTML format.
.
PostgreSQL is an object-relational SQL database management system.
- postgresql-plperl-9.1: PL/Perl procedural language for PostgreSQL 9.1
PL/Perl enables an SQL developer to write procedural language functions
for PostgreSQL 9.1 in Perl. You need this package if you have any
PostgreSQL 9.1 functions that use the languages plperl or plperlu.
.
PostgreSQL is an object-relational SQL database management system.
- postgresql-plpython-9.1: PL/Python procedural language for PostgreSQL 9.1
PL/Python enables an SQL developer to write procedural language functions
for PostgreSQL 9.1 in Python. You need this package if you have any
PostgreSQL 9.1 functions that use the languages plpython or plpythonu.
.
PostgreSQL is an object-relational SQL database management system.
- postgresql-plpython3-9.1: PL/Python 3 procedural language for PostgreSQL 9.1
PL/Python 3 enables an SQL developer to write procedural language functions
for PostgreSQL 9.1 in Python 3. You need this package if you have any
PostgreSQL 9.1 functions that use the languages plpython3 or plpython3u.
.
PostgreSQL is an object-relational SQL database management system.
- postgresql-pltcl-9.1: PL/Tcl procedural language for PostgreSQL 9.1
PL/Tcl enables an SQL developer to write procedural language functions
for PostgreSQL 9.1 in Tcl. You need this package if you have any
PostgreSQL 9.1 functions that use the languages pltcl or pltclu.
.
PostgreSQL is an object-relational SQL database management system.
- postgresql-server-dev-9.1: development files for PostgreSQL 9.1 server-side programming
Header files for compiling SSI code to link into PostgreSQL's backend; for
example, for C functions to be called from SQL.
.
This package also contains the Makefiles necessary for building add-on
modules of PostgreSQL, which would otherwise have to be built in the
PostgreSQL source-code tree.
.
PostgreSQL is an object-relational SQL database management system.