summaryrefslogtreecommitdiff
path: root/databases/postgresql94-server
AgeCommit message (Collapse)AuthorFilesLines
2017-11-13postgresql: updated to the latestadam1-2/+1
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-12The PostgreSQL Global Development Group has released an update to all ↵adam1-1/+2
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-11The PostgreSQL Global Development Group has released an update to all ↵adam1-1/+4
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-29The PostgreSQL Global Development Group has released an update to all ↵adam1-1/+2
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-08Remove the stability entity, it has no meaning outside of an official context.jperkin1-1/+0
2016-06-08Change the service_bundle name to "export" to reduce diffs between thejperkin1-1/+1
original manifest.xml file and the output from "svccfg export".
2016-06-08Add or fix manpath entries to use the correct path.jperkin1-1/+1
2016-05-23This release fixes a number of issues reported by users over the last two ↵adam1-1/+3
months. Most database administrators should plan to upgrade at the next available downtime, unless they have been affected directly by the fixed issues.
2016-04-09The PostgreSQL Global Development Group has released an update to all ↵adam2-3/+5
supported versions of our database system, including 9.5.2, 9.4.7, 9.3.12, 9.2.16, and 9.1.21. This release fixes two security issues and one index corruption issue in version 9.5. It also contains a variety of bug fixes for earlier versions. Users of PostgreSQL 9.5.0 or 9.5.1 should update as soon as possible. This release closes security hole CVE-2016-2193, where a query plan might get reused for more than one ROLE in the same session. This could cause the wrong set of Row Level Security (RLS) policies to be used for the query. The update also fixes CVE-2016-3065, a server crash bug triggered by using pageinspect with BRIN index pages. Since an attacker might be able to expose a few bytes of server memory, this crash is being treated as a security issue.
2016-03-15Remove stray SunOS project definition from some SMF manifests.fhajny2-3/+3
These should never have made it in. Bump resp. PKGREVISIONs.
2016-03-05Bump PKGREVISION for security/openssl ABI bump.jperkin1-1/+2
2015-10-10Changes 9.4.5:adam1-1/+2
Two security issues have been fixed in this release which affect users of specific PostgreSQL features: CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service. CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
2015-02-12Changes 9.4.1:adam1-1/+2
Security Fixes * CVE-2015-0241 Buffer overruns in "to_char" functions. * CVE-2015-0242 Buffer overrun in replacement printf family of functions. * CVE-2015-0243 Memory errors in functions in the pgcrypto extension. * CVE-2015-0244 An error in extended protocol message reading. * CVE-2014-8161 Constraint violation errors can cause display of values in columns which the user would not normally have rights to see. JSON and JSONB Unicode Escapes Other Fixes and Improvements * Cope with the non-ASCII Norwegian Windows locale name. * Avoid data corruption when databases are moved to new tablespaces and back again. * Ensure that UNLOGGED tables are correctly copied during ALTER DATABASE operations. * Avoid deadlocks when locking recently modified rows. * Fix two SELECT FOR UPDATE query issues. * Prevent false negative for shortest-first regular expression matches. * Fix false positives and negatives in tsquery contains operator. * Fix namespace handling in xpath(). * Prevent row-producing functions from creating empty column names. * Make autovacuum use per-table cost_limit and cost_delay settings. * When autovacuum=off, limit autovacuum work to wraparound prevention only. * Multiple fixes for logical decoding in 9.4. * Fix transient errors on hot standby queries due to page replacement. * Prevent duplicate WAL file archiving at end of recovery or standby promotion. * Prevent deadlock in parallel restore of schema-only dump.
2015-01-14PostgreSQL 9.4.0:adam8-0/+1033
This release adds many new features which enhance PostgreSQL's flexibility, scalability and performance for many different types of database users, including improvements to JSON support, replication and index performance.