Change log for postgresql-9.0 package in Ubuntu
| 1 → 5 of 5 results | First • Previous • Next • Last |
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.
-- Ubuntu Archive Auto-Sync <email address hidden> Fri, 16 Dec 2011 16:27:19 +0000
Available diffs
- diff from 9.0.5-1build1 to 9.0.6-1 (741.7 KiB)
| Superseded in precise-release |
postgresql-9.0 (9.0.5-1build1) precise; urgency=low * Rebuild for Perl 5.14. -- Colin Watson <email address hidden> Wed, 16 Nov 2011 18:43:48 +0000
Available diffs
- diff from 9.0.5-1 to 9.0.5-1build1 (330 bytes)
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.
Available diffs
- diff from 9.0.4-1build1 to 9.0.5-1 (2.2 MiB)
| Deleted in oneiric-release (Reason: moved to postgresql-9.1, LP#833684) |
postgresql-9.0 (9.0.4-1build1) oneiric; urgency=low * Rebuild for Perl 5.12. -- Colin Watson <email address hidden> Thu, 12 May 2011 06:41:15 +0100
Available diffs
- diff from 9.0.4-1 to 9.0.4-1build1 (350 bytes)
postgresql-9.0 (9.0.4-1) unstable; urgency=medium
Priority medium due to data-loss pg_upgrade bug.
* New upstream bug fix release:
- If your installation was upgraded from a previous major release by
running pg_upgrade, you should take action to prevent possible data loss
due to a now-fixed bug in pg_upgrade. The recommended solution is to run
"VACUUM FREEZE" on all TOAST tables. More information is available at
http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix.
- Fix pg_upgrade's handling of TOAST tables.
This error poses a significant risk of data loss for installations
that have been upgraded with pg_upgrade. This patch corrects the
problem for future uses of pg_upgrade, but does not in itself cure
the issue in installations that have been processed with a buggy
version of pg_upgrade.
- Suppress incorrect "PD_ALL_VISIBLE flag was incorrectly set"
warning.
- Use better SQLSTATE error codes for hot standby conflict cases.
- Prevent intermittent hang in interactions of startup process with
bgwriter process. This affected recovery in non-hot-standby cases.
- Disallow including a composite type in itself.
- Avoid potential deadlock during catalog cache initialization.
- Fix dangling-pointer problem in BEFORE ROW UPDATE trigger handling
when there was a concurrent update to the target tuple.
- Disallow "DROP TABLE" when there are pending deferred trigger
events for the table.
Formerly the "DROP" would go through, leading to "could not open
relation with OID nnn" errors when the triggers were eventually
fired.
- Allow "replication" as a user name in "pg_hba.conf".
"replication" is special in the database name column, but it was
mistakenly also treated as special in the user name column.
- Prevent crash triggered by constant-false WHERE conditions during
GEQO optimization.
- Improve planner's handling of semi-join and anti-join cases.
- Fix handling of SELECT FOR UPDATE in a sub-SELECT.
This bug typically led to "cannot extract system attribute from
virtual tuple" errors.
- Fix selectivity estimation for text search to account for NULLs.
- Fix get_actual_variable_range() to support hypothetical indexes
injected by an index adviser plugin.
- Fix PL/Python memory leak involving array slices.
- Allow libpq's SSL initialization to succeed when user's home
directory is unavailable.
If the SSL mode is such that a root certificate file is not
required, there is no need to fail. This change restores the
behavior to what it was in pre-9.0 releases.
- Fix libpq to return a useful error message for errors detected in
conninfo_array_parse.
- Fix ecpg preprocessor's handling of float constants.
- Fix parallel pg_restore to handle comments on POST_DATA items
correctly.
- Fix pg_restore to cope with long lines (over 1KB) in TOC files.
- Put in more safeguards against crashing due to division-by-zero
with overly enthusiastic compiler optimization. (Closes: #616180)
* debian/control: Build debug package. (Closes: #551880)
* debian/control, debian/rules: Drop usage of pycentral. We don't ship any
Python extension/module, so we don't need a python helper at all.
(Closes: #616949)
| 1 → 5 of 5 results | First • Previous • Next • Last |
