Stabilization targets: =dev-db/postgresql-9.3.21 ~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 =dev-db/postgresql-9.4.16 ~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 =dev-db/postgresql-9.5.11 ~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 =dev-db/postgresql-9.6.7 ~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 =dev-db/postgresql-10.2 ~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 =app-eselect/eselect-postgresql-2.3 ~hppa 2018-02-08 Security Update Release ================================== The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 10.2, 9.6.7, 9.5.11, 9.4.16, 9.3.21. This release fixes two security issues. This release also fixes issues with VACUUM, GIN indexes, and hash indexes that could lead to data corruption, as well as fixes for using parallel queries and logical replication. All users using the affected versions of PostgreSQL should update as soon as possible. Please see the notes on "Updating" below for any post-update steps that may be required. Please note that PostgreSQL changed its versioning scheme with the release of version 10.0, so updating to version 10.2 from 10.0 or 10.1 is considered a minor update. Security Issues --------------- Two security vulnerabilities have been fixed by this release: * CVE-2018-1052: Fix the processing of partition keys containing multiple expressions * CVE-2018-1053: Ensure that all temporary files made with "pg_upgrade" are non-world-readable Updating -------- All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply shutdown PostgreSQL and update its binaries. If your installation is affected by one of the following issues, you may need to perform additional post-update steps: * Users affected by the GIN and hash index issues should consider rebuilding these indexes * Users who copied the INSTR example from the PostgreSQL documentation should analyze their code to determine if they need to apply the corrected INSTR example * Users who use the "~>" operator found in "contrib/cube" with expression indexes or materialized views will need to reindex and refresh them, respectively. This change is also backwards incompatible, so please test any code using this operator before releasing to a production environment. Users who have skipped one or more update releases may need to run additional, post-update steps; please see the release notes for earlier versions for details.
amd64 stable
x86 stable
*** Bug 647806 has been marked as a duplicate of this bug. ***
*** Bug 647804 has been marked as a duplicate of this bug. ***
ia64 stable
Stable on alpha.
ppc/ppc64 stable for newer versions, per bug 649288
An automated check of this bug failed - the following atoms are unknown: dev-db/postgresql-9.5.11 dev-db/postgresql-10.2 dev-db/postgresql-9.4.16 dev-db/postgresql-9.3.21 Please verify the atom list.
I guess we're not needed here any more, removing remaining arches.
cleanup will occur in bug #647246 GLSA Vote: No
