| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
| Name: postgresql-server | Distribution: openSUSE 11.2 |
| Version: 8.4.4 | Vendor: openSUSE |
| Release: 0.1.1 | Build date: Tue May 25 18:45:12 2010 |
| Group: Productivity/Databases/Servers | Build host: build21 |
| Size: 13117666 | Source RPM: postgresql-8.4.4-0.1.1.src.rpm |
| Packager: http://bugs.opensuse.org | |
| Url: http://www.postgresql.org/ | |
| Summary: The Programs Needed to Create and Run a PostgreSQL Server | |
PostgreSQL is an advanced object-relational database management system
that supports an extended subset of the SQL standard, including
transactions, foreign keys, sub-queries, triggers, and user-defined
types and functions.
This package includes the programs needed to create and run a
PostgreSQL server, which will in turn allow you to create and maintain
PostgreSQL databases.
Authors:
--------
Marc G. Fournier <scrappy@hub.org>
Tom Lane <tgl@sss.pgh.pa.us>
Vadim B. Mikheev <vadim4o@yahoo.com>
Bruce Momjian <pgman@candle.pha.pa.us>
Jan Wieck <JanWieck@Yahoo.com>
BSD3c(or similar)
* Fri May 21 2010 max@suse.de
- Security and bugfix release 8.4.4 (bnc#607778):
* Enforce restrictions in plperl using an opmask applied to the
whole interpreter, instead of using Safe.pm. Recent
developments have convinced us that Safe.pm is too insecure to
rely on for making plperl trustable. This change removes use of
Safe.pm altogether, in favor of using a separate interpreter
with an opcode mask that is always applied. Pleasant side
effects of the change include that it is now possible to use
Perl's strict pragma in a natural way in plperl, and that
Perl's $a and $b variables work as expected in sort routines,
and that function compilation is significantly
faster. (CVE-2010-1169)
* Prevent PL/Tcl from executing untrustworthy code from
pltcl_modules. PL/Tcl's feature for autoloading Tcl code from
a database table could be exploited for trojan-horse attacks,
because there was no restriction on who could create or insert
into that table. This change disables the feature unless
pltcl_modules is owned by a superuser. (However, the
permissions on the table are not checked, so installations that
really need a less-than-secure modules table can still grant
suitable privileges to trusted non-superusers.) Also, prevent
loading code into the unrestricted "normal" Tcl interpreter
unless we are really going to execute a pltclu
function. (CVE-2010-1170)
* Fix data corruption during WAL replay of ALTER ... SET
TABLESPACE. When archive_mode is on, ALTER ... SET TABLESPACE
generates a WAL record whose replay logic was incorrect. It
could write the data to the wrong place, leading to
possibly-unrecoverable data corruption. Data corruption would
be observed on standby slaves, and could occur on the master as
well if a database crash and recovery occurred after committing
the ALTER and before the next checkpoint.
* Fix possible crash if a cache reset message is received during
rebuild of a relcache entry. This error was introduced in 8.4.3
while fixing a related failure.
* Apply per-function GUC settings while running the language
validator for the function.
* This avoids failures if the function's code is invalid without
the setting; an example is that SQL functions may not parse if
the search_path is not correct.
* Do constraint exclusion for inherited UPDATE and DELETE target
tables when constraint_exclusion = partition. Due to an
oversight, this setting previously only caused constraint
exclusion to be checked in SELECT commands.
* Do not allow an unprivileged user to reset superuser-only
parameter settings. Previously, if an unprivileged user ran
ALTER USER ... RESET ALL for himself, or ALTER DATABASE
... RESET ALL for a database he owns, this would remove all
special parameter settings for the user or database, even ones
that are only supposed to be changeable by a superuser. Now,
the ALTER will only remove the parameters that the user has
permission to change.
* Avoid possible crash during backend shutdown if shutdown occurs
when a CONTEXT addition would be made to log entries. In some
cases the context-printing function would fail because the
current transaction had already been rolled back when it came
time to print a log message.
* Fix erroneous handling of %r parameter in recovery_end_command.
The value always came out zero.
* Ensure the archiver process responds to changes in
archive_command as soon as possible.
* Fix pl/pgsql's CASE statement to not fail when the case
expression is a query that returns no rows.
* Update pl/perl's ppport.h for modern Perl versions.
* Fix assorted memory leaks in pl/python.
* Handle empty-string connect parameters properly in ecpg.
* Prevent infinite recursion in psql when expanding a variable
that refers to itself.
* Fix psql's \copy to not add spaces around a dot within \copy
(select ...). Addition of spaces around the decimal point in a
numeric literal would result in a syntax error.
* Avoid formatting failure in psql when running in a locale
context that doesn't match the client_encoding.
* Fix unnecessary "GIN indexes do not support whole-index scans"
errors for unsatisfiable queries using contrib/intarray
operators.
* Ensure that contrib/pgstattuple functions respond to cancel
interrupts promptly.
* Make server startup deal properly with the case that shmget()
returns EINVAL for an existing shared memory segment.
This behavior has been observed on BSD-derived kernels
including OS X. It resulted in an entirely-misleading startup
failure complaining that the shared memory request size was too
large.
* Mon Mar 29 2010 max@suse.de
- Security and bugfix release 8.4.3:
* Add new configuration parameter ssl_renegotiation_limit to
control how often we do session key renegotiation for an SSL
connection. This can be set to zero to disable renegotiation
completely, which may be required if a broken SSL library is
used. In particular, some vendors are shipping stopgap patches
for CVE-2009-3555 that cause renegotiation attempts to fail.
* Fix possible deadlock during backend startup.
* Fix possible crashes due to not handling errors during relcache
reload cleanly.
* Fix possible crash due to use of dangling pointer to a cached
plan.
* Fix possible crash due to overenthusiastic invalidation of
cached plan for "ROLLBACK".
* Fix possible crashes when trying to recover from a failure in
subtransaction start.
* Fix server memory leak associated with use of savepoints and a
client encoding different from server's encoding.
* Fix incorrect WAL data emitted during end-of-recovery cleanup
of a GIST index page split. This would result in index
corruption, or even more likely an error during WAL replay, if
we were unlucky enough to crash during end-of-recovery cleanup
after having completed an incomplete GIST insertion.
* Fix bug in WAL redo cleanup method for GIN indexes.
* Fix incorrect comparison of scan key in GIN index search.
* Make substring() for bit types treat any negative length as
meaning "all the rest of the string". The previous coding
treated only -1 that way, and would produce an invalid result
value for other negative values, possibly leading to a crash
(CVE-2010-0442).
* Fix integer-to-bit-string conversions to handle the first
fractional byte correctly when the output bit width is wider
than the given integer by something other than a multiple of 8
bits.
* Fix some cases of pathologically slow regular expression
matching.
* Fix bug occurring when trying to inline a SQL function that
returns a set of a composite type that contains dropped
columns.
* Fix bug with trying to update a field of an element of a
composite-type array column.
* Avoid failure when "EXPLAIN" has to print a FieldStore or
assignment ArrayRef expression. These cases can arise now that
"EXPLAIN VERBOSE" tries to print plan node target lists.
* Avoid an unnecessary coercion failure in some cases where an
undecorated literal string appears in a subquery within
"UNION"/"INTERSECT"/"EXCEPT". This fixes a regression for some
cases that worked before 8.4.
* Avoid undesirable rowtype compatibility check failures in some
cases where a whole-row Var has a rowtype that contains dropped
columns.
* Fix the STOP WAL LOCATION entry in backup history files to
report the next WAL segment's name when the end location is
exactly at a segment boundary.
* Always pass the catalog ID to an option validator function
specified in "CREATE FOREIGN DATA WRAPPER".
* Fix some more cases of temporary-file leakage. This corrects a
problem introduced in the previous minor release. One case
that failed is when a plpgsql function returning set is called
within another function's exception handler.
* Add support for doing FULL JOIN ON FALSE. This prevents a
regression from pre-8.4 releases for some queries that can now
be simplified to a constant-false join condition.
* Improve constraint exclusion processing of boolean-variable
cases, in particular make it possible to exclude a partition
that has a "bool_column = false" constraint.
* Prevent treating an INOUT cast as representing binary
compatibility.
* Include column name in the message when warning about inability
to grant or revoke column-level privileges. This is more
useful than before and helps to prevent confusion when a
"REVOKE" generates multiple messages, which formerly appeared
to be duplicates.
* When reading "pg_hba.conf" and related files, do not treat
@something as a file inclusion request if the @ appears inside
quote marks; also, never treat @ by itself as a file inclusion
request. This prevents erratic behavior if a role or database
name starts with @. If you need to include a file whose path
name contains spaces, you can still do so, but you must write
@"/path to/file" rather than putting the quotes around the
whole construct.
* Prevent infinite loop on some platforms if a directory is named
as an inclusion target in "pg_hba.conf" and related files.
* Fix possible infinite loop if SSL_read or SSL_write fails
without setting errno. This is reportedly possible with some
Windows versions of openssl.
* Disallow GSSAPI authentication on local connections, since it
requires a hostname to function correctly.
* Protect ecpg against applications freeing strings unexpectedly.
* Make ecpg report the proper SQLSTATE if the connection
disappears.
* Fix translation of cell contents in psql \d output.
* Fix psql's numericlocale option to not format strings it
shouldn't in latex and troff output formats.
* Fix a small per-query memory leak in psql.
* Make psql return the correct exit status (3) when ON_ERROR_STOP
and --single-transaction are both specified and an error occurs
during the implied "COMMIT".
* Fix pg_dump's output of permissions for foreign servers.
* Fix possible crash in parallel pg_restore due to out-of-range
dependency IDs.
* Fix plpgsql failure in one case where a composite column is set
to NULL.
* Fix possible failure when calling PL/Perl functions from
PL/PerlU or vice versa.
* Add volatile markings in PL/Python to avoid possible
compiler-specific misbehavior.
* Ensure PL/Tcl initializes the Tcl interpreter fully. The only
known symptom of this oversight is that the Tcl clock command
misbehaves if using Tcl 8.5 or later.
* Prevent ExecutorEnd from being run on portals created within a
failed transaction or subtransaction. This is known to cause
issues when using "contrib/auto_explain".
* Prevent crash in "contrib/dblink" when too many key columns are
specified to a dblink_build_sql_* function.
* Allow zero-dimensional arrays in "contrib/ltree" operations.
This case was formerly rejected as an error, but it's more
convenient to treat it the same as a zero-element array. In
particular this avoids unnecessary failures when an ltree
operation is applied to the result of ARRAY(SELECT ...) and the
sub-select returns no rows.
* Fix assorted crashes in "contrib/xml2" caused by sloppy memory
management.
* Make the configure script report failure if the C compiler does
not provide a working 64-bit integer datatype. This case has
been broken for some time, and no longer seems worth
supporting, so just reject it at configure time instead.
* Wed Dec 16 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 2009 jengelh@medozas.de
- add baselibs.conf as a source
* Wed Sep 16 2009 crrodriguez@novell.com
- use find_lang to package language files correctly
* Thu Sep 10 2009 max@suse.de
- Security and bugfix release 8.4.1:
* Fix WAL page header initialization at the end of archive
recovery. This could lead to failure to process the WAL in a
subsequent archive recovery.
* Fix "cannot make new WAL entries during recovery" error.
* Fix problem that could make expired rows visible after a crash.
This bug involved a page status bit potentially not being set
correctly after a server crash.
* Disallow RESET ROLE and RESET SESSION AUTHORIZATION inside
security-definer functions. This covers a case that was missed
in the previous patch that disallowed SET ROLE and SET SESSION
AUTHORIZATION inside security-definer functions.
(See CVE-2007-6600)
* Make LOAD of an already-loaded loadable module into a no-op.
* Formerly, LOAD would attempt to unload and re-load the module,
but this is unsafe and not all that useful.
* Make window function PARTITION BY and ORDER BY items always be
interpreted as simple expressions. In 8.4.0 these lists were
parsed following the rules used for top-level GROUP BY and
ORDER BY lists. But this was not correct per the SQL standard,
and it led to possible circularity.
* Fix several errors in planning of semi-joins. These led to
wrong query results in some cases where IN or EXISTS was used
together with another join.
* Fix handling of whole-row references to subqueries that are
within an outer join. An example is SELECT COUNT(ss.*) FROM
... LEFT JOIN (SELECT ...) ss ON .... Here, ss.* would be
treated as ROW(NULL,NULL,...) for null-extended join rows,
which is not the same as a simple NULL. Now it is treated as a
simple NULL.
* Fix Windows shared-memory allocation code. This bug led to the
often-reported "could not reattach to shared memory" error
message.
* Fix locale handling with plperl.
This bug could cause the server's locale setting to change when
a plperl function is called, leading to data corruption.
* Fix handling of reloptions to ensure setting one option doesn't
force default values for others.
* Ensure that a "fast shutdown" request will forcibly terminate
open sessions, even if a "smart shutdown" was already in
progress.
* Avoid memory leak for array_agg() in GROUP BY queries.
* Treat to_char(..., 'TH') as an uppercase ordinal suffix with
'HH'/'HH12'. It was previously handled as 'th' (lowercase).
* Include the fractional part in the result of EXTRACT(second)
and EXTRACT(milliseconds) for time and time with time zone
inputs.
This has always worked for floating-point datetime
configurations, but was broken in the integer datetime code.
* Fix overflow for INTERVAL 'x ms' when x is more than 2 million
and integer datetimes are in use.
* Improve performance when processing toasted values in index
scans. This is particularly useful for PostGIS.
* Fix a typo that disabled commit_delay.
* Output early-startup messages to postmaster.log if the server
is started in silent mode. Previously such error messages were
discarded, leading to difficulty in debugging.
* Remove translated FAQs. They are now on the wiki. The main FAQ
was moved to the wiki some time ago.
* Fix pg_ctl to not go into an infinite loop if postgresql.conf
is empty.
* Fix several errors in pg_dump's --binary-upgrade mode.
* pg_dump --binary-upgrade is used by pg_migrator.
* Fix contrib/xml2's xslt_process() to properly handle the
maximum number of parameters (twenty).
* Improve robustness of libpq's code to recover from errors
during COPY FROM STDIN.
* Avoid including conflicting readline and editline header files
when both libraries are installed.
* Work around gcc bug that causes "floating-point exception"
instead of "division by zero" on some platforms.
* Mon Jul 27 2009 poeml@suse.de
- postgresql-8.4.0-sle10-timestamptz.patch added, and applied
_only_ on SLE10. It fixes a build failure due to a test case that
seems to be confused by daylight saving time in the time zone
that the test expects its result (PDT vs. PST). Since this
failure happened only on SLE10, I assume that the test case isn't
broken, and some peculiarity on that (rather old now) platform is
to blame (possibly too old timezone files). Also, the testcase is
checking correctness when converting timezones > 32 bit, which
actually seems to work.
* Wed Jul 15 2009 poeml@suse.de
- replace "ident sameuser" with "ident" as auth method for the
initdb call in the init script, because the former doesn't work
with PostgreSQL 8.4. With the generated pg_hba.conf, PostgreSQL
failed to start. Added note to the upgrade READMEs. [bnc#522375]
* Tue Jul 07 2009 max@suse.de
- New major release: 8.4.0
- Improvements include:
* Windowing Functions
* Common Table Expressions and Recursive Queries
* Default and variadic parameters for functions
* Parallel Restore
* Column Permissions
* Per-database locale settings
* Improved hash indexes
* Improved join performance for EXISTS and NOT EXISTS queries
* Easier-to-use Warm Standby
* Automatic sizing of the Free Space Map
* Visibility Map (greatly reduces vacuum overhead for
slowly-changing tables)
* Version-aware psql (backslash commands work against older
servers)
* Support SSL certificates for user authentication
* Per-function runtime statistics
* Easy editing of functions in psql
* New contrib modules: pg_stat_statements, auto_explain, citext,
btree_gin
* Wed May 06 2009 max@suse.de
- Remove dependency on local posixrules from horology test.
* Mon Mar 23 2009 max@suse.de
- Security release 8.3.7
* Fixes a vulnerability that allowed remote authenticated
users to cause a denial of service (stack consumption)
via mismatched encoding conversion requests.
* Details of the other bugfixes contained in this and
previous releases can be found here:
http://www.postgresql.org/docs/8.3/static/release.html
/usr/share/doc/packages/postgresql/HISTORY
- Users of GiST indexes should "REINDEX" them after installing
this update.
- Re-added libpgport.a to the devel package, as some apps require
it, although it is meant to be internal to the PostgreSQL
backend.
- Fix removal of leftover files on database startup (bnc#473644).
* Wed Jan 07 2009 olh@suse.de
- obsolete old -XXbit packages (bnc#437293)
* Wed Nov 05 2008 max@suse.de
- Bugfix release: 8.3.5
* 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 in bytea-to-XML mapping.
* Fix possible crash when deeply nested functions are invoked
from a trigger.
* Improve optimization of "expression" IN ("expression-list")
queries.
* 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.
* Fix Assert failure during rescan of an IS NULL search of
a GiST index.
* Fix memory leak during rescan of a hashed aggregation plan.
* Ensure an error is reported when a newly-defined PL/pgSQL
trigger function is invoked as a normal function.
* Force a checkpoint before "CREATE DATABASE" starts to copy
files This prevents a possible failure if files had recently
been deleted in the source database.
* Prevent possible collision of relfilenode numbers when moving
a table to another tablespace with "ALTER SET TABLESPACE".
* Fix incorrect text search 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.
* Make ILIKE compare characters case-insensitively even when
they're escaped.
* Ensure "DISCARD" is handled properly by statement logging.
* Fix incorrect logging of last-completed-transaction time
during PITR recovery.
* Ensure SPI_getvalue and SPI_getbinval behave correctly when
the passed tuple and tuple descriptor have different numbers
of columns.
* Fix small memory leak when using libpq's gsslib parameter.
* Ensure libgssapi is linked into libpq if needed.
* Fix ecpg's parsing of "CREATE ROLE".
* Fix recent breakage of pg_ctl restart.
* Thu Sep 25 2008 max@suse.de
- Bugfix release: 8.3.4
- Issues fixed include autovacuum crashes reported by several
users, two Heap Only Tuple bugs, a foreign key failure
condition, a too-small lock address space, two Write Ahead Log
bugs, several planner mistakes, and numerous "corner condition"
bugs.
* Fri Sep 05 2008 max@suse.de
- New version: 8.3.3 with countless bug fixes over 8.3.1.
- For details, see
http://www.postgresql.org/docs/8.3/static/release-8-3-2.html ,
http://www.postgresql.org/docs/8.3/static/release-8-3-3.html ,
or /usr/share/doc/packages/postgresql/HISTORY .
* Thu Aug 28 2008 cthiel@suse.de
- fix init script
* Mon May 19 2008 schwab@suse.de
- Fix broken configure check.
* Fri May 09 2008 aj@suse.de
- Add baselibs.conf.
* Fri Apr 18 2008 max@suse.de
- Removed static libs from postgresql-devel.
- Removed more old Obsoletes: tags.
- Fixed path to pid file in init script.
- Moved "make check" to %check section
- Silence some bogus rpmlint warnings
* Thu Apr 10 2008 max@suse.de
- Adopt the 8.3.1 package from Peter Eisentraut's OBS project.
- New features in PostgreSQL 8.3 include:
* Full text search is integrated into the core database system
* Support for the SQL/XML standard, including new operators and
an XML data type
* Enumerated data types (ENUM)
* Arrays of composite types
* Universally Unique Identifier (UUID) data type
* Add control over whether NULLs sort first or last
* Updatable cursors
* Server configuration parameters can now be set on a
per-function basis
* User-defined types can now have type modifiers
* Automatically re-plan cached queries when table definitions
change or statistics are updated
* Numerous improvements in logging and statistics collection
* Support multiple concurrent autovacuum processes, and other
autovacuum improvements
- Remove old provides/obsoletes tags for way-back package renames.
* Thu Apr 10 2008 ro@suse.de
- added baselibs.conf file to build xxbit packages
for multilib support
* Thu Jan 10 2008 max@suse.de
- Update to 8.2.6 to fix five security issues:
- Index Functions Privilege Escalation: CVE-2007-6600
- Regular Expression Denial-of-Service: CVE-2007-4772,
CVE-2007-6067, CVE-2007-4769, #329282
- DBLink Privilege Escalation: CVE-2007-6601, #328403
* Wed Jun 06 2007 max@suse.de
- New version: 8.2.4
- The list of changes between the 8.1 and 8.2 series is too long
to reproduce here. It can be found under
/usr/share/doc/packages/postgresql/HISTORY when the postgresql
package is installed or online at http://www.postgresql.org.
- Splited the postgresql-pl package into individual packages for
PL/Perl, PL/Python and PL/Tcl.
- Added a config file for SuSEfirewall2 (#247370).
* Thu Mar 29 2007 rguenther@suse.de
- Add bison, flex and zlib-devel BuildRequires.
* Tue Oct 17 2006 max@suse.de
- New patchlevel release: 8.1.5
- Disallow aggregate functions in "UPDATE" commands, except within
sub-SELECTs. The behavior of such an aggregate was unpredictable,
and in 8.1.X could cause a crash, so it has been disabled.
- Fix core dump when an untyped literal is taken as ANYARRAY.
- Fix core dump in duration logging for extended query protocol when
a "COMMIT" or "ROLLBACK" is executed.
- Fix mishandling of AFTER triggers when query contains a SQL function
returning multiple rows.
- Fix "ALTER TABLE ... TYPE" to recheck NOT NULL for USING clause.
- Fix string_to_array() to handle overlapping matches for the
separator string.
- Fix to_timestamp() for AM/PM formats.
- Fix autovacuum's calculation that decides whether "ANALYZE" is
needed.
- Fix corner cases in pattern matching for psql's \d commands.
- Fix index-corrupting bugs in /contrib/ltree.
- Numerous robustness fixes in ecpg.
- Fix backslash escaping in /contrib/dbmirror.
- Minor fixes in /contrib/dblink and /contrib/tsearch2.
- Efficiency improvements in hash tables and bitmap index scans.
/etc/init.d/postgresql /etc/sysconfig/SuSEfirewall2.d/services/postgresql /usr/bin/initdb /usr/bin/pg_controldata /usr/bin/pg_ctl /usr/bin/pg_resetxlog /usr/bin/postgres /usr/bin/postmaster /usr/lib64/postgresql /usr/lib64/postgresql/ascii_and_mic.so /usr/lib64/postgresql/backup /usr/lib64/postgresql/cyrillic_and_mic.so /usr/lib64/postgresql/dict_snowball.so /usr/lib64/postgresql/euc_cn_and_mic.so /usr/lib64/postgresql/euc_jis_2004_and_shift_jis_2004.so /usr/lib64/postgresql/euc_jp_and_sjis.so /usr/lib64/postgresql/euc_kr_and_mic.so /usr/lib64/postgresql/euc_tw_and_big5.so /usr/lib64/postgresql/latin2_and_win1250.so /usr/lib64/postgresql/latin_and_mic.so /usr/lib64/postgresql/plpgsql.so /usr/lib64/postgresql/utf8_and_ascii.so /usr/lib64/postgresql/utf8_and_big5.so /usr/lib64/postgresql/utf8_and_cyrillic.so /usr/lib64/postgresql/utf8_and_euc_cn.so /usr/lib64/postgresql/utf8_and_euc_jis_2004.so /usr/lib64/postgresql/utf8_and_euc_jp.so /usr/lib64/postgresql/utf8_and_euc_kr.so /usr/lib64/postgresql/utf8_and_euc_tw.so /usr/lib64/postgresql/utf8_and_gb18030.so /usr/lib64/postgresql/utf8_and_gbk.so /usr/lib64/postgresql/utf8_and_iso8859.so /usr/lib64/postgresql/utf8_and_iso8859_1.so /usr/lib64/postgresql/utf8_and_johab.so /usr/lib64/postgresql/utf8_and_shift_jis_2004.so /usr/lib64/postgresql/utf8_and_sjis.so /usr/lib64/postgresql/utf8_and_uhc.so /usr/lib64/postgresql/utf8_and_win.so /usr/sbin/rcpostgresql /usr/share/locale/cs/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/de/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/de/LC_MESSAGES/pg_controldata-8.4.mo /usr/share/locale/de/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/de/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/de/LC_MESSAGES/plpgsql-8.4.mo /usr/share/locale/de/LC_MESSAGES/postgres-8.4.mo /usr/share/locale/es/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/es/LC_MESSAGES/pg_controldata-8.4.mo /usr/share/locale/es/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/es/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/es/LC_MESSAGES/plpgsql-8.4.mo /usr/share/locale/es/LC_MESSAGES/postgres-8.4.mo /usr/share/locale/fr/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/fr/LC_MESSAGES/pg_controldata-8.4.mo /usr/share/locale/fr/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/fr/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/fr/LC_MESSAGES/plpgsql-8.4.mo /usr/share/locale/fr/LC_MESSAGES/postgres-8.4.mo /usr/share/locale/it/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/it/LC_MESSAGES/pg_controldata-8.4.mo /usr/share/locale/it/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/it/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/it/LC_MESSAGES/plpgsql-8.4.mo /usr/share/locale/ja/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/ja/LC_MESSAGES/pg_controldata-8.4.mo /usr/share/locale/ja/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/ja/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/ja/LC_MESSAGES/plpgsql-8.4.mo /usr/share/locale/ja/LC_MESSAGES/postgres-8.4.mo /usr/share/locale/ko/LC_MESSAGES/pg_controldata-8.4.mo /usr/share/locale/ko/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/ko/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/pt_BR/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/pt_BR/LC_MESSAGES/pg_controldata-8.4.mo /usr/share/locale/pt_BR/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/pt_BR/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/pt_BR/LC_MESSAGES/postgres-8.4.mo /usr/share/locale/ro/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/ro/LC_MESSAGES/plpgsql-8.4.mo /usr/share/locale/ru/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/ru/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/ru/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/sv/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/sv/LC_MESSAGES/pg_controldata-8.4.mo /usr/share/locale/sv/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/sv/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/ta/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/ta/LC_MESSAGES/pg_controldata-8.4.mo /usr/share/locale/ta/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/ta/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/tr/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/tr/LC_MESSAGES/pg_controldata-8.4.mo /usr/share/locale/tr/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/tr/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/tr/LC_MESSAGES/postgres-8.4.mo /usr/share/locale/zh_CN/LC_MESSAGES/initdb-8.4.mo /usr/share/locale/zh_CN/LC_MESSAGES/pg_controldata-8.4.mo /usr/share/locale/zh_CN/LC_MESSAGES/pg_ctl-8.4.mo /usr/share/locale/zh_CN/LC_MESSAGES/pg_resetxlog-8.4.mo /usr/share/locale/zh_CN/LC_MESSAGES/plpgsql-8.4.mo /usr/share/locale/zh_CN/LC_MESSAGES/postgres-8.4.mo /usr/share/man/man1/initdb.1.gz /usr/share/man/man1/pg_controldata.1.gz /usr/share/man/man1/pg_ctl.1.gz /usr/share/man/man1/pg_resetxlog.1.gz /usr/share/man/man1/postgres.1.gz /usr/share/man/man1/postmaster.1.gz /usr/share/postgresql /usr/share/postgresql/conversion_create.sql /usr/share/postgresql/information_schema.sql /usr/share/postgresql/pg_hba.conf.sample /usr/share/postgresql/pg_ident.conf.sample /usr/share/postgresql/pg_service.conf.sample /usr/share/postgresql/postgres.bki /usr/share/postgresql/postgres.description /usr/share/postgresql/postgres.shdescription /usr/share/postgresql/postgresql.conf.sample /usr/share/postgresql/psqlrc.sample /usr/share/postgresql/recovery.conf.sample /usr/share/postgresql/snowball_create.sql /usr/share/postgresql/sql_features.txt /usr/share/postgresql/system_views.sql /usr/share/postgresql/timezonesets /usr/share/postgresql/timezonesets/Africa.txt /usr/share/postgresql/timezonesets/America.txt /usr/share/postgresql/timezonesets/Antarctica.txt /usr/share/postgresql/timezonesets/Asia.txt /usr/share/postgresql/timezonesets/Atlantic.txt /usr/share/postgresql/timezonesets/Australia /usr/share/postgresql/timezonesets/Australia.txt /usr/share/postgresql/timezonesets/Default /usr/share/postgresql/timezonesets/Etc.txt /usr/share/postgresql/timezonesets/Europe.txt /usr/share/postgresql/timezonesets/India /usr/share/postgresql/timezonesets/Indian.txt /usr/share/postgresql/timezonesets/Pacific.txt /usr/share/postgresql/tsearch_data /usr/share/postgresql/tsearch_data/danish.stop /usr/share/postgresql/tsearch_data/dutch.stop /usr/share/postgresql/tsearch_data/english.stop /usr/share/postgresql/tsearch_data/finnish.stop /usr/share/postgresql/tsearch_data/french.stop /usr/share/postgresql/tsearch_data/german.stop /usr/share/postgresql/tsearch_data/hungarian.stop /usr/share/postgresql/tsearch_data/hunspell_sample.affix /usr/share/postgresql/tsearch_data/ispell_sample.affix /usr/share/postgresql/tsearch_data/ispell_sample.dict /usr/share/postgresql/tsearch_data/italian.stop /usr/share/postgresql/tsearch_data/norwegian.stop /usr/share/postgresql/tsearch_data/portuguese.stop /usr/share/postgresql/tsearch_data/russian.stop /usr/share/postgresql/tsearch_data/spanish.stop /usr/share/postgresql/tsearch_data/swedish.stop /usr/share/postgresql/tsearch_data/synonym_sample.syn /usr/share/postgresql/tsearch_data/thesaurus_sample.ths /usr/share/postgresql/tsearch_data/turkish.stop /usr/share/postgresql/tsearch_data/xsyn_sample.rules /var/adm/fillup-templates/sysconfig.postgresql /var/lib/pgsql /var/lib/pgsql/.bash_profile /var/lib/pgsql/backups /var/lib/pgsql/data
Generated by rpm2html 1.8.1
Fabrice Bellet, Mon May 13 04:37:24 2013