pkgsrc/databases/postgresql84/distinfo
adam 96bac04f07 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".
2013-02-09 11:19:08 +00:00

18 lines
1 KiB
Text

$NetBSD: distinfo,v 1.24 2013/02/09 11:19:09 adam Exp $
SHA1 (postgresql-8.4.16.tar.bz2) = af6c3caf75d3fb895774106875de08ce61258116
RMD160 (postgresql-8.4.16.tar.bz2) = 64c114cee18ad1c9dab05e42362f72007a4d9ab4
Size (postgresql-8.4.16.tar.bz2) = 14784029 bytes
SHA1 (patch-aa) = 72437773d67939c8d8c8e9a99caf430590fd726f
SHA1 (patch-ab) = aa46d88c8a72edaf95880de48474ea484d6d2bf5
SHA1 (patch-ac) = 0b82797d0b80bdd1e9b5f3de4989fe3848adf6cb
SHA1 (patch-ad) = fb75df841bbcc25e840ed9c2fed59232d7189200
SHA1 (patch-af) = a73769cf05223d2ee06249c9e69c85038c2cd936
SHA1 (patch-ag) = 85dac95e40efc16270885087f868aeb76e1b9214
SHA1 (patch-ah) = 25102dce1b9b22385353af23500636fb18e3bf64
SHA1 (patch-ai) = 0d6f536f7593e362ec216eafa73c718ad6bed8fc
SHA1 (patch-ao) = b098032408fc951865966710554667a249db6320
SHA1 (patch-ba) = f8de4ee18a433b65a54280d047d18b161d3e9ca8
SHA1 (patch-bb) = 22859530d2694cf4c347f5e4c02eff0483d536d1
SHA1 (patch-src_pl_plperl_plperl.h) = 8d448cc8e0e0dbc4d15dad369d3ca7a796874ac2
SHA1 (patch-src_pl_plpgsql_src_Makefile) = 1592ecb85d6ef1bd691f77b320f639b6fc822e14