![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql90-datatypes
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Retire EOLed PostgreSQL 8.4 and 9.0.
Include btree-gist module, useful e.g. for range exclusions.
The PostgreSQL Global Development Group has released a critical update to all supported versions of the PostgreSQL database system, which includes minor versions 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19. This update fixes three serious data-loss bugs affecting replication and database maintenance. All users are urged to update their installations at the earliest opportunity. The replication issue affects some users of PostgreSQL binary replication, and can cause minor data loss between the master and the standby. While not all users are affected, it is difficult to predict when the bug will occur, so we urge all users of replication and continuous backup (PITR) to update immediately. Additionally, users who had replication running under PostgreSQL minor versions 9.3.0, 9.3.1, 9.2.5, 9.1.10, or 9.0.14 should plan to take a fresh base backup of each standby after update, in order to ensure no prior data corruption already exists. This release also fixes two timing issues with VACUUM, which can cause old, overwritten or deleted rows to re-appear at a later date under some circumstances. Users with very high transaction rates, particularly those who experience "transaction ID wraparound" every few weeks or less, are the most at risk for this issue. Those users should set vacuum_freeze_table_age to 0, and run a database-wide VACUUM after the update. The second of the two VACUUM issues affects only 9.3, making it expecially important for 9.3 users to update.
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".
Changes 9.0.3: * Before exiting walreceiver, ensure all the received WAL is fsync'd to disk * Avoid excess fsync activity in walreceiver * Make "ALTER TABLE" revalidate uniqueness and exclusion constraints when needed * Fix EvalPlanQual for "UPDATE" of an inheritance tree in which the tables are not all alike * 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 PL/Python crash when an array contains null entries * Remove ecpg's fixed length limit for constants defining an array dimension * 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
Restore PG_SUBPREFIX.
Changes 9.0.2: * Force the default wal_sync_method to be fdatasync on Linux * Fix "too many KnownAssignedXids" error during Hot Standby replay * Fix race condition in lock acquisition during Hot Standby * Avoid unnecessary conflicts during Hot Standby * 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 corner-case bug when streaming replication is enabled immediately after creating the master database cluster * Fix persistent slowdown of autovacuum workers when multiple workers remain active for a long time * Fix long-term memory leak in autovacuum launcher * Avoid failure when trying to report an impending transaction wraparound condition from outside a transaction * 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 * Fix error checking during early connection processing * Improve efficiency of window functions * Avoid memory leakage while "ANALYZE"'ing complex index expressions * Ensure an index that uses a whole-row Var still depends on its table * Add missing support in "DROP OWNED BY" for removing foreign data wrapper/server privileges belonging to a user * Do not "inline" a SQL function with multiple OUT parameters * Fix crash when inline-ing a set-returning function whose argument list contains a reference to an inline-able user function * Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is attached to the VALUES part of INSERT ... VALUES * Make the OFF keyword unreserved This prevents problems with using off as a variable name in PL/pgSQL. That worked before 9.0, but was now broken because PL/pgSQL now treats all core reserved words as reserved. * Fix constant-folding of COALESCE() expressions
Import PostgreSQL 9.0 data types support modules as databases/postgresql90-datatypes This package provides the following PostgreSQL modules: - citext - hstore - intarray - isn - ltree - lo - uuid-ossp - unaccent The "citext" module provides a case-insensitive character string type, citext. Essentially, it internally calls lower when comparing values. Otherwise, it behaves almost exactly like text. The "hstore" module implements the "hstore" data type for storing sets of key/value pairs within a single PostgreSQL value. This can be useful in various scenarios, such as rows with many attributes that are rarely examined, or semi-structured data. Keys and values are simply text strings. The "intarray" module provides a number of useful functions and operators for manipulating one-dimensional arrays of integers. There is also support for indexed searches using some of the operators. The "isn" module provides data types for the following international product numbering standards: EAN13, UPC, ISBN (books), ISMN (music), and ISSN (serials). Numbers are validated on input, and correctly hyphenated on output. The "ltree" module implements a data type ltree for representing labels of data stored in a hierarchical tree-like structure. Extensive facilities for searching through label trees are provided. The "lo" module provides support for managing Large Objects (also called LOs or BLOBs). This includes a data type "lo" and a trigger "lo_manage." The "uuid-ossp" module provides functions to generate universally unique identifiers (UUIDs) using one of several standard algorithms. There are also functions to produce certain special UUID constants. "unaccent" is a text search dictionary that removes accents (diacritic signs) from lexemes. It's a filtering dictionary, which means its output is always passed to the next dictionary (if any), unlike the normal behavior of dictionaries. This allows accent-insensitive processing for full text search.
Initial revision