kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/postgresql84/distinfo

19 lines
1 KiB
Text
Raw Normal View History

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
2012-12-07 22:19:50 +01:00
$NetBSD: distinfo,v 1.23 2012/12/07 21:19:51 adam Exp $
Many of the changes in PostgreSQL 8.4 are new or improved administration and monitoring tools and commands. Each user has their own favorite features which will make day-to-day work with PostgreSQL easier and more productive for them. Among the most popular enhancements are: * Parallel Database Restore, speeding up recovery from backup up to 8 times * Per-Column Permissions, allowing more granular control of sensitive data * Per-database Collation Support, making PostgreSQL more useful in multi-lingual environments * In-place Upgrades through pg_migrator (beta), enabling upgrades from 8.3 to 8.4 without extensive downtime * New Query Monitoring Tools, giving administrators more insight into query activity * Greatly Reduced VACUUM Overhead through the Visibility Map * New Monitoring Tools for current queries, query load and deadlocks Version 8.4 also makes data analysis easier through the advanced ANSI SQL2003 features of windowing functions, common table expressions and recursive queries. Enhancements to stored procedures, such as default parameters and variadic parameters, make database server programming simpler and more compact. Of course, there are also performance improvements included in this version.
2009-07-29 08:26:17 +02:00
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
2012-12-07 22:19:50 +01:00
SHA1 (postgresql-8.4.15.tar.bz2) = ba422537cd877153d251498fe8090ea5cfdafe72
RMD160 (postgresql-8.4.15.tar.bz2) = 309bfc4bbb7af065de068006867b79e16189ecd2
Size (postgresql-8.4.15.tar.bz2) = 14701182 bytes
Changes 8.4.9: * Fix bugs in indexing of in-doubt HOT-updated tuples * Fix multiple bugs in GiST index page split processing * Fix possible buffer overrun in tsvector_concat() * Fix crash in xml_recv when processing a "standalone" parameter * Make pg_options_to_table return NULL for an option with no value * Avoid possibly accessing off the end of memory in "ANALYZE" and in SJIS-2004 encoding conversion * Prevent intermittent hang in interactions of startup process with bgwriter process * Fix race condition in relcache init file invalidation * Fix memory leak at end of a GiST index scan * Fix incorrect memory accounting (leading to possible memory bloat) in tuplestores supporting holdable cursors and plpgsql's RETURN NEXT command * Fix performance problem when constructing a large, lossy bitmap * Fix join selectivity estimation for unique columns * Fix nested PlaceHolderVar expressions that appear only in sub-select target lists * Allow nested EXISTS queries to be optimized properly * Fix array- and path-creating functions to ensure padding bytes are zeroes * Fix "EXPLAIN" to handle gating Result nodes within inner-indexscan subplans * Work around gcc 4.6.0 bug that breaks WAL replay * Fix dump bug for VALUES in a view * Disallow SELECT FOR UPDATE/SHARE on sequences This operation doesn't work as expected and can lead to failures. * Fix "VACUUM" so that it always updates pg_class.reltuples/relpages * more...
2011-09-27 13:04:30 +02:00
SHA1 (patch-aa) = 72437773d67939c8d8c8e9a99caf430590fd726f
SHA1 (patch-ab) = aa46d88c8a72edaf95880de48474ea484d6d2bf5
Many of the changes in PostgreSQL 8.4 are new or improved administration and monitoring tools and commands. Each user has their own favorite features which will make day-to-day work with PostgreSQL easier and more productive for them. Among the most popular enhancements are: * Parallel Database Restore, speeding up recovery from backup up to 8 times * Per-Column Permissions, allowing more granular control of sensitive data * Per-database Collation Support, making PostgreSQL more useful in multi-lingual environments * In-place Upgrades through pg_migrator (beta), enabling upgrades from 8.3 to 8.4 without extensive downtime * New Query Monitoring Tools, giving administrators more insight into query activity * Greatly Reduced VACUUM Overhead through the Visibility Map * New Monitoring Tools for current queries, query load and deadlocks Version 8.4 also makes data analysis easier through the advanced ANSI SQL2003 features of windowing functions, common table expressions and recursive queries. Enhancements to stored procedures, such as default parameters and variadic parameters, make database server programming simpler and more compact. Of course, there are also performance improvements included in this version.
2009-07-29 08:26:17 +02:00
SHA1 (patch-ac) = 0b82797d0b80bdd1e9b5f3de4989fe3848adf6cb
Changes 8.4.4: * Enforce restrictions in plperl using an opmask applied to the whole interpreter, instead of using "Safe.pm" * Prevent PL/Tcl from executing untrustworthy code from pltcl_modules * Fix data corruption during WAL replay of ALTER ... SET TABLESPACE * Fix possible crash if a cache reset message is received during rebuild of a relcache entry * Apply per-function GUC settings while running the language validator for the function * Do constraint exclusion for inherited "UPDATE" and "DELETE" target tables when constraint_exclusion = partition * Do not allow an unprivileged user to reset superuser-only parameter settings * Avoid possible crash during backend shutdown if shutdown occurs when a CONTEXT addition would be made to log entries * Fix erroneous handling of %r parameter in recovery_end_command * Ensure the archiver process responds to changes in archive_command as soon as possible * Fix pl/pgsql's CASE statement to not fail when the case expression is a query that returns no rows * Update pl/perl's "ppport.h" for modern Perl versions * Fix assorted memory leaks in pl/python * Handle empty-string connect parameters properly in ecpg * Prevent infinite recursion in psql when expanding a variable that refers to itself * Fix psql's \copy to not add spaces around a dot within \copy (select ...) * Avoid formatting failure in psql when running in a locale context that doesn't match the client_encoding * Fix unnecessary "GIN indexes do not support whole-index scans" errors for unsatisfiable queries using "contrib/intarray" operators * Ensure that "contrib/pgstattuple" functions respond to cancel interrupts promptly * Make server startup deal properly with the case that shmget() returns EINVAL for an existing shared memory segment * Avoid possible crashes in syslogger process on Windows * Deal more robustly with incomplete time zone information in the Windows registry * Update the set of known Windows time zone names * Update time zone data files to tzdata release 2010j for DST law changes in Argentina, Australian Antarctic, Bangladesh, Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia; also historical corrections for Taiwan. Also, add PKST (Pakistan Summer Time) to the default set of timezone abbreviations.
2010-05-20 14:36:38 +02:00
SHA1 (patch-ad) = fb75df841bbcc25e840ed9c2fed59232d7189200
Many of the changes in PostgreSQL 8.4 are new or improved administration and monitoring tools and commands. Each user has their own favorite features which will make day-to-day work with PostgreSQL easier and more productive for them. Among the most popular enhancements are: * Parallel Database Restore, speeding up recovery from backup up to 8 times * Per-Column Permissions, allowing more granular control of sensitive data * Per-database Collation Support, making PostgreSQL more useful in multi-lingual environments * In-place Upgrades through pg_migrator (beta), enabling upgrades from 8.3 to 8.4 without extensive downtime * New Query Monitoring Tools, giving administrators more insight into query activity * Greatly Reduced VACUUM Overhead through the Visibility Map * New Monitoring Tools for current queries, query load and deadlocks Version 8.4 also makes data analysis easier through the advanced ANSI SQL2003 features of windowing functions, common table expressions and recursive queries. Enhancements to stored procedures, such as default parameters and variadic parameters, make database server programming simpler and more compact. Of course, there are also performance improvements included in this version.
2009-07-29 08:26:17 +02:00
SHA1 (patch-af) = a73769cf05223d2ee06249c9e69c85038c2cd936
SHA1 (patch-ag) = 85dac95e40efc16270885087f868aeb76e1b9214
SHA1 (patch-ah) = 25102dce1b9b22385353af23500636fb18e3bf64
Changes 8.4.3: * Add new configuration parameter ssl_renegotiation_limit to control how often we do session key renegotiation for an SSL connection * Fix possible deadlock during backend startup * Fix possible crashes due to not handling errors during relcache reload cleanly * Fix possible crash due to use of dangling pointer to a cached plan * Fix possible crash due to overenthusiastic invalidation of cached plan for "ROLLBACK" * Fix possible crashes when trying to recover from a failure in subtransaction start * Fix server memory leak associated with use of savepoints and a client encoding different from server's encoding * Fix incorrect WAL data emitted during end-of-recovery cleanup of a GIST index page split * Fix bug in WAL redo cleanup method for GIN indexes * Fix incorrect comparison of scan key in GIN index search * Make substring() for bit types treat any negative length as meaning "all the rest of the string" The previous coding treated only -1 that way, and would produce an invalid result value for other negative values, possibly leading to a crash (CVE-2010-0442). * Fix integer-to-bit-string conversions to handle the first fractional byte correctly when the output bit width is wider than the given integer by something other than a multiple of 8 bits * Fix some cases of pathologically slow regular expression matching * Fix bug occurring when trying to inline a SQL function that returns a set of a composite type that contains dropped columns * Fix bug with trying to update a field of an element of a composite-type array column * Avoid failure when "EXPLAIN" has to print a FieldStore or assignment ArrayRef expression These cases can arise now that "EXPLAIN VERBOSE" tries to print plan node target lists. * Avoid an unnecessary coercion failure in some cases where an undecorated literal string appears in a subquery within "UNION"/"INTERSECT"/"EXCEPT" This fixes a regression for some cases that worked before 8.4. * Avoid undesirable rowtype compatibility check failures in some cases where a whole-row Var has a rowtype that contains dropped columns * Fix the STOP WAL LOCATION entry in backup history files to report the next WAL segment's name when the end location is exactly at a segment boundary * Always pass the catalog ID to an option validator function specified in "CREATE FOREIGN DATA WRAPPER" * Fix some more cases of temporary-file leakage * Add support for doing FULL JOIN ON FALSE * Improve constraint exclusion processing of boolean-variable cases, in particular make it possible to exclude a partition that has a "bool_column = false" constraint * Prevent treating an INOUT cast as representing binary compatibility * Include column name in the message when warning about inability to grant or revoke column-level privileges This is more useful than before and helps to prevent confusion when a "REVOKE" generates multiple messages, which formerly appeared to be duplicates. * When reading "pg_hba.conf" and related files, do not treat @something as a file inclusion request if the @ appears inside quote marks; also, never treat @ by itself as a file inclusion request * Prevent infinite loop on some platforms if a directory is named as an inclusion target in "pg_hba.conf" and related files * Fix possible infinite loop if SSL_read or SSL_write fails without setting errno This is reportedly possible with some Windows versions of openssl. * Disallow GSSAPI authentication on local connections, since it requires a hostname to function correctly * Protect ecpg against applications freeing strings unexpectedly * Make ecpg report the proper SQLSTATE if the connection disappears * Fix translation of cell contents in psql \d output * Fix psql's numericlocale option to not format strings it shouldn't in latex and troff output formats * Fix a small per-query memory leak in psql * Make psql return the correct exit status (3) when ON_ERROR_STOP and --single-transaction are both specified and an error occurs during the implied "COMMIT" * Fix pg_dump's output of permissions for foreign servers * Fix possible crash in parallel pg_restore due to out-of-range dependency IDs * Fix plpgsql failure in one case where a composite column is set to NULL * Fix possible failure when calling PL/Perl functions from PL/PerlU or vice versa * Add volatile markings in PL/Python to avoid possible compiler-specific misbehavior * Ensure PL/Tcl initializes the Tcl interpreter fully The only known symptom of this oversight is that the Tcl clock command misbehaves if using Tcl 8.5 or later. * Prevent ExecutorEnd from being run on portals created within a failed transaction or subtransaction This is known to cause issues when using "contrib/auto_explain". * Prevent crash in "contrib/dblink" when too many key columns are specified to a dblink_build_sql_* function * Allow zero-dimensional arrays in "contrib/ltree" operations * Fix assorted crashes in "contrib/xml2" caused by sloppy memory management * Make building of "contrib/xml2" more robust on Windows * Fix race condition in Windows signal handling One known symptom of this bug is that rows in pg_listener could be dropped under heavy load. * Make the configure script report failure if the C compiler does not provide a working 64-bit integer datatype This case has been broken for some time, and no longer seems worth supporting, so just reject it at configure time instead. * Update time zone data files to tzdata release 2010e for DST law changes in Bangladesh, Chile, Fiji, Mexico, Paraguay, Samoa.
2010-04-12 11:58:38 +02:00
SHA1 (patch-ai) = 0d6f536f7593e362ec216eafa73c718ad6bed8fc
Changes 8.4.9: * Fix bugs in indexing of in-doubt HOT-updated tuples * Fix multiple bugs in GiST index page split processing * Fix possible buffer overrun in tsvector_concat() * Fix crash in xml_recv when processing a "standalone" parameter * Make pg_options_to_table return NULL for an option with no value * Avoid possibly accessing off the end of memory in "ANALYZE" and in SJIS-2004 encoding conversion * Prevent intermittent hang in interactions of startup process with bgwriter process * Fix race condition in relcache init file invalidation * Fix memory leak at end of a GiST index scan * Fix incorrect memory accounting (leading to possible memory bloat) in tuplestores supporting holdable cursors and plpgsql's RETURN NEXT command * Fix performance problem when constructing a large, lossy bitmap * Fix join selectivity estimation for unique columns * Fix nested PlaceHolderVar expressions that appear only in sub-select target lists * Allow nested EXISTS queries to be optimized properly * Fix array- and path-creating functions to ensure padding bytes are zeroes * Fix "EXPLAIN" to handle gating Result nodes within inner-indexscan subplans * Work around gcc 4.6.0 bug that breaks WAL replay * Fix dump bug for VALUES in a view * Disallow SELECT FOR UPDATE/SHARE on sequences This operation doesn't work as expected and can lead to failures. * Fix "VACUUM" so that it always updates pg_class.reltuples/relpages * more...
2011-09-27 13:04:30 +02:00
SHA1 (patch-ao) = b098032408fc951865966710554667a249db6320
Force common shared library version scheme on FreeBSD to avoid PLIST divergence.
2012-07-16 23:17:10 +02:00
SHA1 (patch-ba) = f8de4ee18a433b65a54280d047d18b161d3e9ca8
Fix build on SunOS.
2011-09-14 17:53:35 +02:00
SHA1 (patch-bb) = 22859530d2694cf4c347f5e4c02eff0483d536d1
Fix build on SunOS.
2011-10-12 21:43:26 +02:00
SHA1 (patch-src_pl_plperl_plperl.h) = 8d448cc8e0e0dbc4d15dad369d3ca7a796874ac2
databases/postgresql84-server: Fix rpath of plpgsql.so Due to updated PKG_DEVELOPER checks, postgresql84-server started failing with the following message: ERROR: lib/postgresql/plpgsql.so: missing libintl.so.8 The plpgsql.so library had no rpath set other than what the base compiler adds by default. On DragonFly, the libintl.so library would likely have been found anyway as /usr/pkg/lib is part of the LD_CONFIG hint file search path, but that isn't a guarantee. The new patch adds ${libdir} to the plpgsql.so rpath so it passes PKG_DEVELOPER checks now.
2012-07-12 20:57:27 +02:00
SHA1 (patch-src_pl_plpgsql_src_Makefile) = 1592ecb85d6ef1bd691f77b320f639b6fc822e14
Reference in a new issue Copy permalink