Log message:
The PostgreSQL Global Development Group has released a security update to all \ 
current versions of the PostgreSQL database system, including versions 9.2.4, \ 
9.1.9, 9.0.13, and 8.4.17. This update fixes a high-exposure security \ 
vulnerability in versions 9.0 and later. All users of the affected versions are \ 
strongly urged to apply the update immediately.

A major security issue fixed in this release, CVE-2013-1899, makes it possible \ 
for a connection request containing a database name that begins with \ 
"-" to be crafted that can damage or destroy files within a server's \ 
data directory. Anyone with access to the port the PostgreSQL server listens on \ 
can initiate this request.

Two lesser security fixes are also included in this release: CVE-2013-1900, \ 
wherein random numbers generated by contrib/pgcrypto functions may be easy for \ 
another database user to guess, and CVE-2013-1901, which mistakenly allows an \ 
unprivileged user to run commands that could interfere with in-progress backups. \ 
Finally, this release fixes two security issues with the graphical installers \ 
for Linux and Mac OS X: insecure passing of superuser passwords to a script, \ 
CVE-2013-1903 and the use of predictable filenames in /tmp CVE-2013-1902.

Log message:
The PostgreSQL Global Development Group has released a security update to all \ 
current versions of the PostgreSQL database system, including versions 9.2.3, \ 
9.1.8, 9.0.12, 8.4.16, and 8.3.23. This update fixes a denial-of-service (DOS) \ 
vulnerability. All users should update their PostgreSQL installations as soon as \ 
possible.

The security issue fixed in this release, CVE-2013-0255, allows a previously \ 
authenticated user to crash the server by calling an internal function with \ 
invalid arguments. This issue was discovered by independent security researcher \ 
Sumit Soni this week and reported via Secunia SVCRP, and we are grateful for \ 
their efforts in making PostgreSQL more secure.

Today's update also fixes a performance regression which caused a decrease in \ 
throughput when using dynamic queries in stored procedures in version 9.2. \ 
Applications which use PL/pgSQL's EXECUTE are strongly affected by this \ 
regression and should be updated. Additionally, we have fixed intermittent \ 
crashes caused by CREATE/DROP INDEX CONCURRENTLY, and multiple minor issues with \ 
replication.

This release is expected to be the final update for version 8.3, which is now \ 
End-of-Life (EOL). Users of version 8.3 should plan to upgrade to a later \ 
version of PostgreSQL immediately. For more information, see our Versioning \ 
Policy.

This update release also contains fixes for many minor issues discovered and \ 
patched by the PostgreSQL community in the last two months, including:

* Prevent unnecessary table scans during vacuuming
* Prevent spurious cached plan error in PL/pgSQL
* Allow sub-SELECTs to be subscripted
* Prevent DROP OWNED from dropping databases or tablespaces
* Make ECPG use translated messages
* Allow PL/Python to use multi-table trigger functions (again) in 9.1 and 9.2
* Fix several activity log management issues on Windows
* Prevent autovacuum file truncation from being cancelled by deadlock_timeout
* Make extensions build with the .exe suffix automatically on Windows
* Fix concurrency issues with CREATE/DROP DATABASE
* Reject out-of-range values in to_date() conversion function
* Revert cost estimation for large indexes back to pre-9.2 behavior
* Make pg_basebackup tolerate timeline switches
* Cleanup leftover temp table entries during crash recovery
* Prevent infinite loop when COPY inserts a large tuple into a table with a \ 
large fillfactor
* Prevent integer overflow in dynahash creation
* Make pg_upgrade work with INVALID indexes
* Fix bugs in TYPE privileges
* Allow Contrib installchecks to run in their own databases
* Many documentation updates
* Add new timezone "FET".

Log message:
PKGREVISION bumps for the security/openssl 1.0.1d update.

Log message:
The PostgreSQL Global Development Group has released an update to all current \ 
versions of the PostgreSQL database system, including 9.2.1, 9.1.6, 9.0.10, \ 
8.4.14 and 8.3.21. This update fixes critical issues for major versions 9.1 and \ 
9.2, and users running those versions should apply it as soon as possible. Users \ 
of versions 8.3, 8.4 and 9.0 should plan to update at the next scheduled \ 
downtime.

The update fixes two potential data corruption issues present in the PostgreSQL \ 
9.1 and 9.2 for any server which has crashed, been shutdown with \ 
"immediate", or was failed over to a standby. First, the PostgreSQL \ 
development team has discovered a chance of corruption of BTREE and GIN indexes \ 
for databases. Second, there is a significant chance of corruption of the \ 
visibility map. This update fixes both issues.

We strongly advise users of 9.1 and 9.2 to run VACUUM and/or index rebuilds \ 
after applying the update. Please see the 2012-09-24 Update wiki page for \ 
detailed instructions.

This update release also contains fixes for many minor issues discovered and \ 
patched by the PostgreSQL community in the last month, including many fixes for \ 
the newly released version 9.2. These include:

fix sorting issue with IN lists and indexes
fix planner failure when combining GROUP BY with window functions
improve selectivity of text searches using prefixes
prevent rescanning of WITH clauses from giving wrong answers
fix PL/Perl crashing issue
reduce bloat for multi-column GiST indexes
time zone data changes for Fiji
disallow Extensions from circular schema assignment
prevent crashes when default_transaction_isolation is set to "serializable"
several minor fixes to pg_upgrade

Log message:
Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.

Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Log message:
Remove PKGREVISION

Log message:
Recursive PKGREVISION bump for libxml2 buildlink addition.