Log message:
Remove PostgreSQL split-up contrib packages, now replaced by
single postgresql9[1-5]-contrib packages. OK by adam@.

Log message:
The PostgreSQL Global Development Group has released an update to all 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.

Log message:
Bump PKGREVISION for security/openssl ABI bump.

Log message:
The PostgreSQL Global Development Group has released an update with multiple \ 
functionality and security fixes to all supported versions of the PostgreSQL \ 
database system, which includes minor versions 9.4.2, 9.3.7, 9.2.11, 9.1.16, and \ 
9.0.20. The update contains a critical fix for a potential data corruption issue \ 
in PostgreSQL 9.3 and 9.4; users of those versions should update their servers \ 
at the next possible opportunity.

Log message:
Changes 9.3.6:
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.

Log message:
Include btree-gist module, useful e.g. for range exclusions.

Log message:
Changes:
This update fixes CVE-2014-0060, in which PostgreSQL did not properly enforce \ 
the WITH ADMIN OPTION permission for ROLE management.
This update also fixes some issues which affect binary replication and row \ 
locking, and can cause recoverable data corruption in some cases.
In addition to the above, the following issues are fixed in this release:

Fix WAL logging of visibility map change
Make sure that GIN indexes log all insertions
Get pause_at_recovery_target to pause at correct time
Ensure walreceiver sends hot-standby feedback messages on time
Prevent timeout interrupts from taking control away from mainline code
Eliminate several race conditions
Fix some broken HINTs in error messages
Prevent server lockup on SSL connection loss
Fix two Unicode handling issues
Prevent crash on certain subselect syntax
Prevent crash on select from zero column table
Fix two bugs with LATERAL
Fix issue with UNION ALL, partitioning, and updates
Ensure that ANALYZE understands domains over ranges
Eliminate permissions check when using default tablespace
Fix memory leakage in JSON functions
Allow extensions with event triggers
Distinguish numbers correctly in JSON output
Fix permissions for pg_start_backup() and pg_stop_backup()
Accept SHIFT_JIS as locale name
Fix .* expansion for SQL function variables
Prevent infinite loop on some COPY connection failures
Several fixes for client issues on Windows
Enable building PostgreSQL with Visual Studio 2013
Update time zone files for recent changes

Log message:
Recursive PKGREVISION bump for OpenSSL API version bump.

Log message:
Bump PKGREVISION to mark the lib name change in devel/ossp-uuid.

Log message:
The PostgreSQL Global Development Group has released a critical update to all \ 
supported versions of the PostgreSQL database system, which includes minor \ 
versions 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19. This update fixes three \ 
serious data-loss bugs affecting replication and database maintenance. All users \ 
are urged to update their installations at the earliest opportunity.

The replication issue affects some users of PostgreSQL binary replication, and \ 
can cause minor data loss between the master and the standby. While not all \ 
users are affected, it is difficult to predict when the bug will occur, so we \ 
urge all users of replication and continuous backup (PITR) to update \ 
immediately. Additionally, users who had replication running under PostgreSQL \ 
minor versions 9.3.0, 9.3.1, 9.2.5, 9.1.10, or 9.0.14 should plan to take a \ 
fresh base backup of each standby after update, in order to ensure no prior data \ 
corruption already exists.

This release also fixes two timing issues with VACUUM, which can cause old, \ 
overwritten or deleted rows to re-appear at a later date under some \ 
circumstances. Users with very high transaction rates, particularly those who \ 
experience "transaction ID wraparound" every few weeks or less, are \ 
the most at risk for this issue. Those users should set vacuum_freeze_table_age \ 
to 0, and run a database-wide VACUUM after the update. The second of the two \ 
VACUUM issues affects only 9.3, making it expecially important for 9.3 users to \ 
update.