pkgsrc/databases/postgresql83/distinfo
adam 78eee1bf9f 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.1 KiB
Text

$NetBSD: distinfo,v 1.28 2013/02/09 11:19:08 adam Exp $
SHA1 (postgresql-8.3.23.tar.bz2) = e479f3eced32a14ada66082de7c8b33f77e2588b
RMD160 (postgresql-8.3.23.tar.bz2) = ac0ee6a829f04e7cdca0179a2c881244c54f31cd
Size (postgresql-8.3.23.tar.bz2) = 14684669 bytes
SHA1 (patch-aa) = 6d5e9aa58975181d189060f8523c022aa6c82277
SHA1 (patch-ab) = 1ba1bb53ca5a74d09fc2b7d07d98b0a0ffd57202
SHA1 (patch-ac) = 8e3a7021fdd01810d4ebcbd20002b28164b22279
SHA1 (patch-ad) = bbafd1f18408f7a0f5d1a6608860bf1353a93769
SHA1 (patch-af) = fcb43276c1f3349f62acfc37ac0bd6ccaae96f29
SHA1 (patch-ag) = 402d5d211af99efdfa35677299c97e91e14ed85d
SHA1 (patch-ah) = 3640573195f66a46c37d9fca2648d6be39f5593b
SHA1 (patch-ai) = a2364b8e1e8a3094e1c5bfb0cad2d0babe0a8841
SHA1 (patch-ba) = 4a1a9df19eca3c602df19a4201041494a49262f9
SHA1 (patch-src_interfaces_ecpg_ecpglib_Makefile) = 9107a858d4066f0c1e7ece8332d4b32ded718af1
SHA1 (patch-src_makefiles_Makefile.solaris) = 21fd5b1103e1c8aaf339ee6ef91e0d6dab5bea3a
SHA1 (patch-src_pl_plperl_plperl.h) = a521489a0e233a8dbaa8c56dd8fe5c411b0639c5
SHA1 (patch-src_pl_plpgsql_src_Makefile) = 1d6a40da68d28c5080cbfd1738d6314e0de571ee