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:
This release fixes a significant page ordering issue with Hot Standby which \ 
could cause index corruption on the standby under some circumstances. In \ 
addition, this update patches timing issues with checkpoint and transaction ID \ 
wraparound which could cause data corruption in some cases. Today's update also \ 
fixes multiple issues with CREATE INDEX CONCURRENTLY and DROP INDEX \ 
CONCURRENTLY, which can cause those commands to fail or produce corrupt indexes. \ 
Users who use this feature may want to REINDEX or recreate affected indexes (see \ 
below).

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

* Prevent psql crash due to incorrectly encoded input data
* Fix pg_regress gmake build issues
* Make sure correct directory is created for extensions
* Fix some issues with buffer locks and VACUUM
* Multiple fixes and improvements for pg_upgrade
* Fix bugs with end-of-recovery when failing over to a standby
* Avoid bogus "out-of-sequence timeline ID" errors in standby-mode
* Don't launch new child processes during shutdown
* Improve the ability of JOINs to use partial indexes
* Fix assorted integer overflow errors
* Eliminate memory leaks in record_out() and record_send()
* Skip searching for subtransaction logs at COMMIT
* Fix WaitLatch() timing issues
* Fix handling of inherited check constraints in ALTER COLUMN TYPE
* Make ALTER EXTENSION SET SCHEMA behave as documented
* Have SEQUENCE SET statements in the "data" section of sectional dumps
* Prevent parser from believing that VIEWs have system columns
* Fix --clean mode for pg_dump
* Prevent hash table corruption on out-of-memory
* Various query planner and executor fixes and improvements
* Multiple documentation updates
* DST updates for seven timezones

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:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Log message:
Changes:
* CVE-2012-3488: PostgreSQL insecure use of libxslt
* CVE-2012-3489: PostgreSQL insecure use of libxml2
* Updates and corrections to time zone data
* Multiple documentation updates and corrections
* Add limit on max_wal_senders
* Fix dependencies generated during ALTER TABLE ADD CONSTRAINT USING INDEX.
* Correct behavior of unicode conversions for PL/Python
* Fix WITH attached to a nested set operation (UNION/INTERSECT/EXCEPT).
* Fix syslogger so that log_truncate_on_rotation works in the first rotation.
* Only allow autovacuum to be auto-canceled by a directly blocked process.
* Improve fsync request queue operation
* Prevent corner-case core dump in rfree().
* Fix Walsender so that it responds correctly to timeouts and deadlocks
* Several PL/Perl fixes for encoding-related issues
* Make selectivity operators use the correct collation
* Prevent unsuitable slaves from being selected for synchronous replication
* Make REASSIGN OWNED work on extensions as well
* Fix race condition with ENUM comparisons
* Make NOTIFY cope with out-of-disk-space
* Fix memory leak in ARRAY subselect queries
* Reduce data loss at replication failover
* Fix behavior of subtransactions with Hot Standby

Log message:
Remove PKGREVISION

Log message:
Security update to version 8.3.19.

Changes:

* Fix incorrect password transformation in contrib/pgcrypto's DES crypt() \ 
function (Solar Designer)
* If a password string contained the byte value 0x80, the remainder of the \ 
password was ignored, causing the password to be much weaker than it appeared. \ 
With this fix, the rest of the string is properly included in the DES hash. Any \ 
stored password values that are affected by this bug will thus no longer match, \ 
so the stored values may need to be updated. (CVE-2012-2143)
* Ignore SECURITY DEFINER and SET attributes for a procedural language's call \ 
handler (Tom Lane)
* Applying such attributes to a call handler could crash the server. (CVE-2012-2655)
* Allow numeric timezone offsets in timestamp input to be up to 16 hours away \ 
from UTC (Tom Lane)
* Some historical time zones have offsets larger than 15 hours, the previous \ 
limit. This could result in dumped data values being rejected during reload.
* Fix timestamp conversion to cope when the given time is exactly the last DST \ 
transition time for the current timezone (Tom Lane)
* This oversight has been there a long time, but was not noticed previously \ 
because most DST-using zones are presumed to have an indefinite sequence of \ 
future DST transitions.
* Fix text to name and char to name casts to perform string truncation correctly \ 
in multibyte encodings (Karl Schnaitter)
* Fix memory copying bug in to_tsquery() (Heikki Linnakangas)
* Fix slow session startup when pg_attribute is very large (Tom Lane)
* If pg_attribute exceeds one-fourth of shared_buffers, cache rebuilding code \ 
that is sometimes needed during session start would trigger the \ 
synchronized-scan logic, causing it to take many times longer than normal. The \ 
problem was particularly acute if many new sessions were starting at once.
* Ensure sequential scans check for query cancel reasonably often (Merlin Moncure)
* A scan encountering many consecutive pages that contain no live tuples would \ 
not respond to interrupts meanwhile.
* Ensure the Windows implementation of PGSemaphoreLock() clears \ 
ImmediateInterruptOK before returning (Tom Lane)
* This oversight meant that a query-cancel interrupt received later in the same \ 
query could be accepted at an unsafe time, with unpredictable but not good \ 
consequences.
* Show whole-row variables safely when printing views or rules (Abbas Butt, Tom Lane)
* Corner cases involving ambiguous names (that is, the name could be either a \ 
table or column name of the query) were printed in an ambiguous way, risking \ 
that the view or rule would be interpreted differently after dump and reload. \ 
Avoid the ambiguous case by attaching a no-op cast.
* Ensure autovacuum worker processes perform stack depth checking properly \ 
(Heikki Linnakangas)
* Previously, infinite recursion in a function invoked by auto-ANALYZE could \ 
crash worker processes.
* Fix logging collector to not lose log coherency under high load (Andrew Dunstan)
* The collector previously could fail to reassemble large messages if it got too \ 
busy.
* Fix logging collector to ensure it will restart file rotation after receiving \ 
SIGHUP (Tom Lane)
* Fix PL/pgSQL's GET DIAGNOSTICS command when the target is the function's first \ 
variable (Tom Lane)
* Fix several performance problems in pg_dump when the database contains many \ 
objects (Jeff Janes, Tom Lane)
* pg_dump could get very slow if the database contained many schemas, or if many \ 
objects are in dependency loops, or if there are many owned sequences.
* Fix contrib/dblink's dblink_exec() to not leak temporary database connections \ 
upon error (Tom Lane)
* Update time zone data files to tzdata release 2012c for DST law changes in \ 
Antarctica, Armenia, Chile, Cuba, Falkland Islands, Gaza, Haiti, Hebron, \ 
Morocco, Syria, and Tokelau Islands; also historical corrections for Canada.

Log message:
Recursive PKGREVISION bump for libxml2 buildlink addition.