PostgreSQL (32-bit) 歷史版本列表
更新時間：2011-04-18
更新細節：
更新時間：2011-01-31
更新細節：
What's new in this version:
- Before exiting walreceiver, ensure all the received WAL is fsync'd to disk
Otherwise the standby server could replay some un-synced WAL, conceivably leading to data corruption if the system crashes just at that point.
- Avoid excess fsync activity in walreceiver
- Make ALTER TABLE revalidate uniqueness and exclusion constraints when needed
This was broken in 9.0 by a change that was intended to suppress revalidation during VACUUM FULL and CLUSTER, but unintentionally affected ALTER TABLE as well.
- Fix EvalPlanQual for UPDATE of an inheritance tree in which the tables are not all alike
Any variation in the table row types (including dropped columns present in only some child tables) would confuse the EvalPlanQual code, leading to misbehavior or even crashes. Since EvalPlanQual is only executed during concurrent updates to the same row, the problem was only seen intermittently.
- Avoid failures when EXPLAIN tries to display a simple-form CASE expression
If the CASE's test expression was a constant, the planner could simplify the CASE into a form that confused the expression-display code, resulting in "unexpected CASE WHEN clause" errors.
- Fix assignment to an array slice that is before the existing range of subscripts
If there was a gap between the newly added subscripts and the first pre-existing subscript, the code miscalculated how many entries needed to be copied from the old array's null bitmap, potentially leading to data corruption or crash.
- Avoid unexpected conversion overflow in planner for very distant date values
The date type supports a wider range of dates than can be represented by the timestamp types, but the planner assumed it could always convert a date to timestamp with impunity.
- 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) | ...
Queries containing this combination of operators were not executed correctly. The same error existed in contrib/intarray's query_int type and contrib/ltree's ltxtquery type.
- Fix buffer overrun in contrib/intarray's input function for the query_int type (Apple)
This bug is a security risk since the function's return address could be overwritten. Thanks to Apple Inc's security team for reporting this issue and supplying the fix.
- Fix bug in contrib/seg's GiST picksplit algorithm
更新時間：2011-01-31
更新細節：
更新時間：2010-12-17
更新細節：
What's new in this version:
- Force the default wal_sync_method to be fdatasync on Linux The default on Linux has actually been fdatasync for many years, but recent kernel changes caused PostgreSQL to choose open_datasync instead. This choice did not result in any performance improvement, and caused outright failures on certain filesystems, notably ext4 with the data=journal mount option.
- Fix too many KnownAssignedXids error during Hot Standby replay
- Fix race condition in lock acquisition during Hot Standby
- Avoid unnecessary conflicts during Hot Standby This fixes some cases where replay was considered to conflict with standby queries (causing delay of replay or possibly cancellation of the queries), but there was no real conflict.
- Fix assorted bugs in WAL replay logic for GIN indexes This could result in bad buffer id: 0 failures or corruption of index contents during replication.
- 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 The effective vacuum_cost_limit for an autovacuum worker could drop to nearly zero if it processed enough tables, causing it to run extremely slowly.
- Fix long-term memory leak in autovacuum launcher
- Avoid failure when trying to report an impending transaction wraparound condition from outside a transaction This oversight prevented recovery after transaction wraparound got too close, because database startup processing would fail.
- Add support for detecting register-stack overrun on IA64 The IA64 architecture has two hardware stacks. Full prevention of stack-overrun failures requires checking both.
- Add a check for stack overflow in copyObject() Certain code paths could crash due to stack overflow given a sufficiently complex query.
- Fix detection of page splits in temporary GiST indexes It is possible to have a concurrent page split in a temporary index, if for example there is an open cursor scanning the index when an insertion is done. GiST failed to detect this case and hence could deliver wrong results when execution of the cursor continued.
- Fix error checking during early connection processing The check for too many child processes was skipped in some cases, possibly leading to postmaster crash when attempting to add the new child process to fixed-size arrays.
- Improve efficiency of window functions Certain cases where a large number of tuples needed to be read in advance, but work_mem was large enough to allow them all to be held in memory, were unexpectedly slow. percent_rank(), cume_dist() and ntile() in particular were subject to this problem.
- Avoid memory leakage while ANALYZE'ing complex index expressions
- Ensure an index that uses a whole-row Var still depends on its table An index declared like create index i on t (foo(t.-)) would not automatically get dropped when its table was dropped.
- 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 This avoids a possible crash due to loss of information about the expected result rowtype.
- 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 (Heikki Linnakangas) 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 The planner would sometimes attempt to evaluate sub-expressions that in fact could never be reached, possibly leading to unexpected errors.
- Fix could not find pathkey item to sort planner failure with comparison of whole-row Vars
- 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
- Retry after receiving an invalid response packet from a RADIUS authentication server This fixes a low-risk potential denial of service condition.
- Fix missed unlink of temporary files when log_temp_files is active If an error occurred while attempting to emit the log message, the unlink was not done, resulting in accumulation of temp files.
- Add print functionality for InhRelation nodes This avoids a failure when debug_print_parse is enabled and certain types of query are executed.
- Fix incorrect calculation of distance from a point to a horizontal line segment This bug affected several different geometric distance-measurement operators.
- Fix incorrect calculation of transaction status in ecpg
- Fix errors in psql's Unicode-escape support
- Speed up parallel pg_restore when the archive contains many large objects (blobs)
- Fix PL/pgSQL's handling of simple expressions to not fail in recursion or error-recovery cases
- Fix PL/pgSQL's error reporting for no-such-column cases As of 9.0, it would sometimes report missing FROM-clause entry for table foo when record foo has no field bar would be more appropriate.
- Fix PL/Python to honor typmod (i.e., length or precision restrictions) when assigning to tuple fields This fixes a regression from 8.4.
- Fix PL/Python's handling of set-returning functions Attempts to call SPI functions within the iterator generating a set result would fail.
- Fix bug in contrib/cube's GiST picksplit algorithm This could result in considerable inefficiency, though not actually incorrect answers, in a GiST index on a cube column. If you have such an index, consider REINDEXing it after installing this update.
- 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 buffer overrun in contrib/pg_upgrade
- 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.
更新時間：2010-12-16
更新細節：
更新時間：2010-10-05
更新細節：
更新時間：2010-10-04
更新細節：
更新時間：2010-09-21
更新細節：
What's new in this version:
Major enhancements include:
- Built-in replication based on log shipping. This advance consists of two features: Streaming Replication, allowing continuous archive (WAL) files to be streamed over a network connection to a standby server, and Hot Standby, allowing continuous archive standby servers to execute read-only queries. The net effect is to support a single master with multiple read-only slave servers.
- Easier database object permissions management. GRANT/REVOKE IN SCHEMA supports mass permissions changes on existing objects, while ALTER DEFAULT PRIVILEGES allows control of privileges for objects created in the future. Large objects (BLOBs) now support permissions management as well.
- Broadly enhanced stored procedure support. The DO statement supports ad-hoc or "anonymous" code blocks. Functions can now be called using named parameters. PL/pgSQL is now installed by default, and PL/Perl and PL/Python have been enhanced in several ways, including support for Python3.
- Full support for 64-bit Windows.
- More advanced reporting queries, including additional windowing options (PRECEDING and FOLLOWING) and the ability to control the order in which values are fed to aggregate functions.
- New trigger features, including SQL-standard-compliant per-column triggers and conditional trigger execution.
- Deferrable unique constraints. Mass updates to unique keys are now possible without trickery
- Exclusion constraints. These provide a generalized version of unique constraints, allowing enforcement of complex conditions.
- New and enhanced security features, including RADIUS authentication, LDAP authentication improvements, and a new contrib module passwordcheck for testing password strength.
- New high-performance implementation of the LISTEN/NOTIFY feature. Pending events are now stored in a memory-based queue rather than a table. Also, a "payload" string can be sent with each event, rather than transmitting just an event name as before.
- New implementation of VACUUM FULL. This command now rewrites the entire table and indexes, rather than moving individual rows to compact space. It is substantially faster in most cases, and no longer results in index bloat.
- New contrib module pg_upgrade to support in-place upgrades from 8.3 or 8.4 to 9.0.
- Multiple performance enhancements for specific types of queries, including elimination of unnecessary joins. This helps optimize some automatically-generated queries, such as those produced by object-relational mappers (ORMs).
- EXPLAIN enhancements. The output is now available in JSON, XML, or YAML format, and includes buffer utilization and other data not previously available.
- hstore improvements, including new functions and greater data capacity.
更新時間：2010-06-08
更新細節：