Hello community,
here is the log from the commit of package postgresql for openSUSE:Factory
checked in at Thu Jan 7 20:27:36 CET 2010.
--------
--- postgresql/postgresql-pl.changes 2008-05-20 03:11:19.000000000 +0200
+++ /mounts/work_src_done/STABLE/postgresql/postgresql-pl.changes 2009-09-16 20:09:20.000000000 +0200
@@ -1,0 +2,5 @@
+Wed Sep 16 18:08:38 UTC 2009 - crrodriguez@novell.com
+
+- use find_lang to package language files correctly
+
+-------------------------------------------------------------------
--- postgresql/postgresql.changes 2009-09-10 14:55:53.000000000 +0200
+++ /mounts/work_src_done/STABLE/postgresql/postgresql.changes 2010-01-07 15:51:43.000000000 +0100
@@ -1,0 +2,196 @@
+Wed Dec 16 16:19:20 CET 2009 - max@suse.de
+
+- Security and bugfix release 8.4.2:
+
+ * CVE-2009-4136: Protect against indirect security threats
+ caused by index functions changing session-local state. This
+ change prevents allegedly-immutable index functions from
+ possibly subverting a superuser's session.
+
+ * CVE-2009-4034: Reject SSL certificates containing an embedded
+ null byte in the common name (CN) field. This prevents
+ unintended matching of a certificate to a server or client
+ name during SSL validation.
+
+ * Fix hash index corruption. The 8.4 change that made hash
+ indexes keep entries sorted by hash value failed to update the
+ bucket splitting and compaction routines to preserve the
+ ordering. So application of either of those operations could
+ lead to permanent corruption of an index, in the sense that
+ searches might fail to find entries that are present. To deal
+ with this, it is recommended to REINDEX any hash indexes you
+ may have after installing this update.
+
+ * Fix possible crash during backend-startup-time cache
+ initialization
+
+ * Avoid crash on empty thesaurus dictionary
+
+ * Prevent signals from interrupting VACUUM at unsafe times. This
+ fix prevents a PANIC if a VACUUM FULL is cancelled after it's
+ already committed its tuple movements, as well as transient
+ errors if a plain VACUUM is interrupted after having truncated
+ the table.
+
+ * Fix possible crash due to integer overflow in hash table size
+ calculation. This could occur with extremely large planner
+ estimates for the size of a hashjoin's result.
+
+ * Fix crash if a DROP is attempted on an internally-dependent
+ object.
+
+ * Fix very rare crash in inet/cidr comparisons.
+
+ * Ensure that shared tuple-level locks held by prepared
+ transactions are not ignored.
+
+ * Fix premature drop of temporary files used for a cursor that is
+ accessed within a subtransaction.
+
+ * Fix memory leak in syslogger process when rotating to a new CSV
+ logfile.
+
+ * Fix memory leak in postmaster when re-parsing "pg_hba.conf".
+
+ * Make FOR UPDATE/SHARE in the primary query not propagate into
+ WITH queries.
+
+ * Fix bug with a WITH RECURSIVE query immediately inside another
+ one.
+
+ * Fix concurrency bug in hash indexes. Concurrent insertions
+ could cause index scans to transiently report wrong results.
+
+ * Fix incorrect logic for GiST index page splits, when the split
+ depends on a non-first column of the index.
+
+ * Fix wrong search results for a multi-column GIN index with
+ fastupdate enabled.
+
+ * Fix bugs in WAL entry creation for GIN indexes. These bugs were
+ masked when full_page_writes was on, but with it off a WAL
+ replay failure was certain if a crash occurred before the next
+ checkpoint.
+
+ * Don't error out if recycling or removing an old WAL file fails
+ at the end of checkpoint. It's better to treat the problem as
+ non-fatal and allow the checkpoint to complete. Future
+ checkpoints will retry the removal. Such problems are not
+ expected in normal operation, but have been seen to be caused
+ by misdesigned Windows anti-virus and backup software.
+
+ * Ensure WAL files aren't repeatedly archived on Windows. This is
+ another symptom that could happen if some other process
+ interfered with deletion of a no-longer-needed file.
+
+ * Fix PAM password processing to be more robust. The previous
+ code is known to fail with the combination of the Linux
+ pam_krb5 PAM module with Microsoft Active Directory as the
+ domain controller. It might have problems elsewhere too, since
+ it was making unjustified assumptions about what arguments the
+ PAM stack would pass to it.
+
+ * Raise the maximum authentication token (Kerberos ticket) size
+ in GSSAPI and SSPI authentication methods. While the old
+ 2000-byte limit was more than enough for Unix Kerberos
+ implementations, tickets issued by Windows Domain Controllers
+ can be much larger.
+
+ * Ensure that domain constraints are enforced in constructs like
+ ARRAY[...]::domain, where the domain is over an array type.
+
+ * Fix foreign-key logic for some cases involving composite-type
+ columns as foreign keys.
+
+ * Ensure that a cursor's snapshot is not modified after it is
+ created. This could lead to a cursor delivering wrong results
+ if later operations in the same transaction modify the data the
+ cursor is supposed to return.
+
+ * Fix CREATE TABLE to properly merge default expressions coming
+ from different inheritance parent tables. This used to work but
+ was broken in 8.4.
+
+ * Re-enable collection of access statistics for sequences. This
+ used to work but was broken in 8.3.
+
+ * Fix processing of ownership dependencies during CREATE OR REPLACE
+ FUNCTION.
+
+ * Fix incorrect handling of WHERE "x"="x" conditions. In some cases
+ these could get ignored as redundant, but they aren't -- they're
+ equivalent to "x" IS NOT NULL.
+
+ * Fix incorrect plan construction when using hash aggregation to
+ implement DISTINCT for textually identical volatile
+ expressions.
+
+ * Fix Assert failure for a volatile SELECT DISTINCT ON expression.
+
+ * Fix ts_stat() to not fail on an empty tsvector value.
+
+ * Make text search parser accept underscores in XML attributes.
+
+ * Fix encoding handling in xml binary input. If the XML header
+ doesn't specify an encoding, we now assume UTF-8 by default;
+ the previous handling was inconsistent.
+
+ * Fix bug with calling plperl from plperlu or vice versa. An
+ error exit from the inner function could result in crashes due
+ to failure to re-select the correct Perl interpreter for the
+ outer function.
+
+ * Fix session-lifespan memory leak when a PL/Perl function is
+ redefined.
+
+ * Ensure that Perl arrays are properly converted to PostgreSQL
+ arrays when returned by a set-returning PL/Perl function. This
+ worked correctly already for non-set-returning functions.
+
+ * Fix rare crash in exception processing in PL/Python.
+
+ * Fix ecpg problem with comments in DECLARE CURSOR statements.
+
+ * Fix ecpg to not treat recently-added keywords as reserved
+ words. This affected the keywords CALLED, CATALOG, DEFINER,
+ ENUM, FOLLOWING, INVOKER, OPTIONS, PARTITION, PRECEDING, RANGE,
+ SECURITY, SERVER, UNBOUNDED, and WRAPPER.
+
+ * Re-allow regular expression special characters in psql's \df
+ function name parameter.
+
+ * In "contrib/pg_standby", disable triggering failover with a
+ signal on Windows. This never did anything useful, because
+ Windows doesn't have Unix-style signals, but recent changes
+ made it actually crash.
+
+ * Put FREEZE and VERBOSE options in the right order in the VACUUM
+ command that "contrib/vacuumdb" produces.
+
+ * Fix possible leak of connections when "contrib/dblink"
+ encounters an error.
+
+ * Ensure psql's flex module is compiled with the correct system
+ header definitions. This fixes build failures on platforms
+ where --enable-largefile causes incompatible changes in the
+ generated code.
+
+ * Make the postmaster ignore any application_name parameter in
+ connection request packets, to improve compatibility with
+ future libpq versions.
+
+ * Update the timezone abbreviation files to match current reality
+ This includes adding IDT to the default timezone abbreviation
+ set.
+
+-------------------------------------------------------------------
+Mon Dec 14 16:08:29 CET 2009 - jengelh@medozas.de
+
+- add baselibs.conf as a source
+
+-------------------------------------------------------------------
+Wed Sep 16 18:00:20 UTC 2009 - crrodriguez@novell.com
+
+- use find_lang to package language files correctly
+
+-------------------------------------------------------------------
calling whatdependson for head-i586
Old:
----
postgresql-8.4.1.tar.bz2
New:
----
postgresql-8.4.2.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ postgresql-pl.spec ++++++
--- /var/tmp/diff_new_pack.q40al6/_old 2010-01-07 20:27:11.000000000 +0100
+++ /var/tmp/diff_new_pack.q40al6/_new 2010-01-07 20:27:11.000000000 +0100
@@ -1,7 +1,7 @@
#
-# spec file for package postgresql-pl (Version 8.4.1)
+# spec file for package postgresql-pl (Version 8.4.2)
#
-# Copyright (c) 2009 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2010 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@@ -23,10 +23,10 @@
BuildRequires: ncurses-devel
BuildRequires: python-devel tcl-devel
Summary: The PL/Tcl, PL/Perl, and PL/Python Procedural Languages for PostgreSQL
-Version: 8.4.1
+Version: 8.4.2
Release: 1
%define pg_minor_version %(echo %version | cut -f1-2 -d.)
-License: BSD 3-clause (or similar)
+License: BSD3c(or similar)
Group: Productivity/Databases/Servers
Source0: postgresql-%version.tar.bz2
NoSource: 0
@@ -59,7 +59,7 @@
Jan Wieck