2018-05-21 10:06:41 by Adam Ciarcinski | Files touched by this commit (54) | |
Log message:
Removed (jdbc-)postgresql92(-*)
|
2017-12-15 17:57:25 by David A. Holland | Files touched by this commit (16) |
Log message:
Bump PKGREVISION of postgresql92 and postgresql93 packages (all to 1)
for the PR 52787 options adjustment, as a precaution.
|
2017-11-13 10:33:33 by Adam Ciarcinski | Files touched by this commit (38) | |
Log message:
postgresql: updated to the latest
The PostgreSQL Global Development Group has released an update to all supported \
versions of our database system, including 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, \
and 9.2.24. This release fixes three security issues. This release also fixes \
issues found in BRIN indexing, logical replication and other bugs reported over \
the past three months.
All users using the affected versions of PostgreSQL should update as soon as \
possible. If you use BRIN indexes or contrib/start-scripts, please see the \
release notes for additional post-upgrade steps.
Security Issues
Three security vulnerabilities have been fixed by this release:
CVE-2017-12172: Start scripts permit database administrator to modify root-owned \
files
CVE-2017-15098: Memory disclosure in JSON functions
CVE-2017-15099: INSERT ... ON CONFLICT DO UPDATE fails to enforce SELECT privileges
Bug Fixes and Improvements
This update also fixes a number of bugs reported in the last few months. Some of \
these issues affect only version 10, but many affect all supported versions:
Fix a race condition in BRIN indexing that could cause some rows to not be \
included in the indexing.
Fix crash when logical decoding is invoked from a PL language function.
Several fixes for logical replication.
Restored behavior for CTEs attached to INSERT/UPDATE/DELETE statements to \
pre-version 10.
Prevent low-probability crash in processing of nested trigger firings.
Do not evaluate an aggregate function's argument expressions when the conditions \
in the FILTER clause evaluate to FALSE. This complies with SQL-standard \
behavior.
Fix incorrect query results when multiple GROUPING SETS columns contain the same \
simple variable.
Fix memory leak over the lifespan of a query when evaluating a set-returning \
function from the target list in a SELECT.
Several fixes for parallel query execution, including fixing a crash in the \
parallel execution of certain queries that contain a certain type of bitmap \
scan.
Fix json_build_array(), json_build_object(), jsonb_build_array(), and \
jsonb_build_object() to handle explicit VARIADIC arguments correctly.
Prevent infinite float values from being casted to the numeric type.
Fix autovacuum's “work item” logic to prevent possible crashes and silent \
loss of work items.
Several fixes for VIEWs around adding columns to the end of a view.
Fix for hashability detection of range data types that are created by a user.
Improvements on using extended statistics on columns for the purposes of query \
planning.
Prevent idle_in_transaction_session_timeout from being ignored when a \
statement_timeout occurred earlier.
Fix low-probability loss of NOTIFY messages due more than 2 billion transactions \
processing before any queries are executed in the session.
Several file system interaction fixes.
Correctly restore the umask setting when file creation fails in COPY or lo_export().
Fix pg_dump to ensure that it emits GRANT commands in a valid order.
Fix pg_basebackup's matching of tablespace paths to canonicalize both paths \
before comparing to help improve Windows compatibility.
Fix libpq to not require user's home directory to exist when trying to read the \
"~/.pgpass" file.
Several fixes for ecpg.
|
2017-05-12 21:37:55 by Adam Ciarcinski | Files touched by this commit (23) | |
Log message:
The PostgreSQL Global Development Group has released an update to all supported \
versions of our database system, including 9.6.3, 9.5.7, 9.4.12, 9.3.17, and \
9.2.21. This release fixes three security issues. It also patches a number of \
other bugs reported over the last three months. Users who use the PGREQUIRESSL \
environment variable to control connections, and users who rely on security \
isolation between database users when using foreign servers, should update as \
soon as possible. Other users should plan to update at the next convenient \
downtime.
|
2017-02-11 11:18:53 by Adam Ciarcinski | Files touched by this commit (23) | |
Log message:
The PostgreSQL Global Development Group has released an update to all supported \
versions of our database system, including 9.6.2, 9.5.6, 9.4.11, 9.3.16, and \
9.2.20. This release includes fixes that prevent data corruption issues in index \
builds and in certain write-ahead-log replay situations, which are detailed \
below. It also patches over 75 other bugs reported over the last three months.
|
2016-10-29 21:41:55 by Adam Ciarcinski | Files touched by this commit (20) | |
Log message:
The PostgreSQL Global Development Group has released an update to all supported \
versions of our database system, including 9.6.1, 9.5.5, 9.4.10, 9.3.15, 9.2.19, \
and 9.1.24. This is also the last update for the PostgreSQL 9.1 series as it is \
now end-of-life. This release fixes two issues that can cause data corruption, \
which are described in more detail below. It also patches a number of other bugs \
reported over the last three months. The project urges users to apply this \
update at the next possible downtime.
|
2016-06-08 12:16:57 by Jonathan Perkin | Files touched by this commit (89) |
Log message:
Remove the stability entity, it has no meaning outside of an official context.
|
2016-06-08 12:02:27 by Jonathan Perkin | Files touched by this commit (44) |
Log message:
Change the service_bundle name to "export" to reduce diffs between the
original manifest.xml file and the output from "svccfg export".
|
2016-06-08 11:58:06 by Jonathan Perkin | Files touched by this commit (24) |
Log message:
Add or fix manpath entries to use the correct path.
|
2016-05-23 16:27:35 by Adam Ciarcinski | Files touched by this commit (26) |
Log message:
This release fixes a number of issues reported by users over the last two \
months. Most database administrators should plan to upgrade at the next \
available downtime, unless they have been affected directly by the fixed issues.
|