2013-04-04 23:08:38 by Adam Ciarcinski | Files touched by this commit (66) | ![Package removed](https://pkgsrc.se/images/remove.gif) |
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.
|
2013-02-09 12:19:19 by Adam Ciarcinski | Files touched by this commit (86) | ![Package updated](https://pkgsrc.se/images/update.gif) |
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".
|
2013-02-07 00:24:19 by Jonathan Perkin | Files touched by this commit (1351) | ![Package updated](https://pkgsrc.se/images/update.gif) |
Log message:
PKGREVISION bumps for the security/openssl 1.0.1d update.
|
2012-10-02 23:25:56 by Aleksej Saushev | Files touched by this commit (323) |
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
|
2012-07-01 21:21:14 by Daniel Horecki | Files touched by this commit (7) |
Log message:
Remove PKGREVISION
|
2012-06-14 09:45:42 by Steven Drake | Files touched by this commit (1202) |
Log message:
Recursive PKGREVISION bump for libxml2 buildlink addition.
|
2011-04-23 00:58:18 by OBATA Akio | Files touched by this commit (4) | ![Package updated](https://pkgsrc.se/images/update.gif) |
Log message:
reset PKGREVISION from base pkg update.
|
2011-04-22 15:45:23 by OBATA Akio | Files touched by this commit (2234) |
Log message:
recursive bump from gettext-lib shlib bump.
|
2011-02-15 10:06:33 by Adam Ciarcinski | Files touched by this commit (17) |
Log message:
Changes 8.3.14:
* Avoid failures when "EXPLAIN" tries to display a simple-form CASE
expression.
* Fix assignment to an array slice that is before the existing range
of subscripts.
* Avoid unexpected conversion overflow in planner for very distant
date values.
* Fix pg_restore's text output for large objects (BLOBs) when
standard_conforming_strings is on.
* Fix erroneous parsing of tsquery values containing ... &
!(subexpression) | ...
* Fix buffer overrun in "contrib/intarray"'s input function for the
query_int type.
* Fix bug in "contrib/seg"'s GiST picksplit algorithm.
|
2010-12-19 10:53:55 by Adam Ciarcinski | Files touched by this commit (20) |
Log message:
Changes 8.3.13:
* Force the default wal_sync_method to be fdatasync on Linux
* Fix assorted bugs in WAL replay logic for GIN indexes
* Fix recovery from base backup when the starting checkpoint WAL
record is not in the same WAL segment as its redo point
* Fix persistent slowdown of autovacuum workers when multiple workers
remain active for a long time
* Add support for detecting register-stack overrun on IA64
* Add a check for stack overflow in copyObject()
* Fix detection of page splits in temporary GiST indexes
* Avoid memory leakage while "ANALYZE"'ing complex index expressions
* Ensure an index that uses a whole-row Var still depends on its
table
* Do not "inline" a SQL function with multiple OUT parameters
* Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is
attached to the VALUES part of INSERT ... VALUES
* Fix constant-folding of COALESCE() expressions
* Fix postmaster crash when connection acceptance (accept() or one of
the calls made immediately after it) fails, and the postmaster was
compiled with GSSAPI support
* Fix missed unlink of temporary files when log_temp_files is active
* Add print functionality for InhRelation nodes
* Fix incorrect calculation of distance from a point to a horizontal
line segment
* Fix PL/pgSQL's handling of "simple" expressions to not fail in
recursion or error-recovery cases
* Fix PL/Python's handling of set-returning functions
* Fix bug in "contrib/cube"'s GiST picksplit algorithm
* Don't emit "identifier will be truncated" notices in
"contrib/dblink" except when creating new connections
* Fix potential coredump on missing public key in "contrib/pgcrypto"
* Fix memory leak in "contrib/xml2"'s XPath query functions
* Update time zone data files to tzdata release 2010o for DST law
changes in Fiji and Samoa; also historical corrections for Hong
Kong.
|