PostgreSQL (64-bit) 歷史版本列表
更新時間：2011-12-07
更新細節：
What's new in this version:
* Fix bugs in information_schema.referential_constraints view
- This view was being insufficiently careful about matching the foreign-key constraint to the depended-on primary or unique key constraint. That could result in failure to show a foreign key constraint at all, or showing it multiple times, or claiming that it depends on a different constraint than the one it really does.
- Since the view definition is installed by initdb, merely upgrading will not fix the problem. If you need to fix this in an existing installation, you can (as a superuser) drop the information_schema schema then re-create it by sourcing SHAREDIR/information_schema.sql. (Run pg_config --sharedir if you're uncertain where SHAREDIR is.) This must be repeated in each database to be fixed.
* Make contrib/citext's upgrade script fix collations of citext columns and indexes
- Existing citext columns and indexes aren't correctly marked as being of a collatable data type during pg_upgrade from a pre-9.1 server. That leads to operations on them failing with errors such as "could not determine which collation to use for string comparison". This change allows them to be fixed by the same script that upgrades the citext module into a proper 9.1 extension during CREATE EXTENSION citext FROM unpackaged.
- If you have a previously-upgraded database that is suffering from this problem, and you already ran the CREATE EXTENSION command, you can manually run (as superuser) the UPDATE commands found at the end of SHAREDIR/extension/citext--unpackaged--1.0.sql. (Run pg_config --sharedir if you're uncertain where SHAREDIR is.)
* Fix possible crash during UPDATE or DELETE that joins to the output of a scalar-returning function
- A crash could only occur if the target row had been concurrently updated, so this problem surfaced only intermittently.
* Fix incorrect replay of WAL records for GIN index updates
- This could result in transiently failing to find index entries after a crash, or on a hot-standby server. The problem would be repaired by the next VACUUM of the index, however.
* Fix TOAST-related data corruption during CREATE TABLE dest AS SELECT * FROM src or INSERT INTO dest SELECT * FROM src
- If a table has been modified by ALTER TABLE ADD COLUMN, attempts to copy its data verbatim to another table could produce corrupt results in certain corner cases. The problem can only manifest in this precise form in 8.4 and later, but we patched earlier versions as well in case there are other code paths that could trigger the same bug.
* Fix possible failures during hot standby startup
* Start hot standby faster when initial snapshot is incomplete
* Fix race condition during toast table access from stale syscache entries
- The typical symptom was transient errors like "missing chunk number 0 for toast value NNNNN in pg_toast_2619", where the cited toast table would always belong to a system catalog.
* Track dependencies of functions on items used in parameter default expressions
- Previously, a referenced object could be dropped without having dropped or modified the function, leading to misbehavior when the function was used. Note that merely installing this update will not fix the missing dependency entries; to do that, you'd need to CREATE OR REPLACE each such function afterwards. If you have functions whose defaults depend on non-built-in objects, doing so is recommended.
* Fix incorrect management of placeholder variables in nestloop joins
- This bug is known to lead to "variable not found in subplan target list" planner errors, and could possibly result in wrong query output when outer joins are involved.
* Fix window functions that sort by expressions involving aggregates
- Previously these could fail with "could not find pathkey item to sort" planner errors.
* Fix "MergeAppend child's targetlist doesn't match MergeAppend" planner errors
* Fix index matching for operators with both collatable and noncollatable inputs
- In 9.1.0, an indexable operator that has a non-collatable left-hand input type and a collatable right-hand input type would not be recognized as matching the left-hand column's index. An example is the hstore ? text operator.
* Allow inlining of set-returning SQL functions with multiple OUT parameters
* Don't trust deferred-unique indexes for join removal
- A deferred uniqueness constraint might not hold intra-transaction, so assuming that it does could give incorrect query results.
* Make DatumGetInetP() unpack inet datums that have a 1-byte header, and add a new macro, DatumGetInetPP(), that does not
- This change affects no core code, but might prevent crashes in add-on code that expects DatumGetInetP() to produce an unpacked datum as per usual convention.
* Improve locale support in money type's input and output
- Aside from not supporting all standard lc_monetary formatting options, the input and output functions were inconsistent, meaning there were locales in which dumped money values could not be re-read.
* Don't let transform_null_equals affect CASE foo WHEN NULL ... constructs
- transform_null_equals is only supposed to affect foo = NULL expressions written directly by the user, not equality checks generated internally by this form of CASE.
* Change foreign-key trigger creation order to better support self-referential foreign keys
- For a cascading foreign key that references its own table, a row update will fire both the ON UPDATE trigger and the CHECK trigger as one event. The ON UPDATE trigger must execute first, else the CHECK will check a non-final state of the row and possibly throw an inappropriate error. However, the firing order of these triggers is determined by their names, which generally sort in creation order since the triggers have auto-generated names following the convention "RI_ConstraintTrigger_NNNN". A proper fix would require modifying that convention, which we will do in 9.2, but it seems risky to change it in existing releases. So this patch just changes the creation order of the triggers. Users encountering this type of error should drop and re-create the foreign key constraint to get its triggers into the right order.
* Fix IF EXISTS to work correctly in DROP OPERATOR FAMILY
* Disallow dropping of an extension from within its own script
- This prevents odd behavior in case of incorrect management of extension dependencies.
* Don't mark auto-generated types as extension members
- Relation rowtypes and automatically-generated array types do not need to have their own extension membership entries in pg_depend, and creating such entries complicates matters for extension upgrades.
* Cope with invalid pre-existing search_path settings during CREATE EXTENSION
* Avoid floating-point underflow while tracking buffer allocation rate
- While harmless in itself, on certain platforms this would result in annoying kernel log messages.
* Prevent autovacuum transactions from running in serializable mode
- Autovacuum formerly used the cluster-wide default transaction isolation level, but there is no need for it to use anything higher than READ COMMITTED, and using SERIALIZABLE could result in unnecessary delays for other processes.
* Ensure walsender processes respond promptly to SIGTERM
* Exclude postmaster.opts from base backups
* Preserve configuration file name and line number values when starting child processes under Windows
- Formerly, these would not be displayed correctly in the pg_settings view.
* Fix incorrect field alignment in ecpg's SQLDA area
* Preserve blank lines within commands in psql's command history
- The former behavior could cause problems if an empty line was removed from within a string literal, for example.
* Avoid platform-specific infinite loop in pg_dump
* Fix compression of plain-text output format in pg_dump
- pg_dump has historically understood -Z with no -F switch to mean that it should emit a gzip-compressed version of its plain text output. Restore that behavior.
* Fix pg_dump to dump user-defined casts between auto-generated types, such as table rowtypes
* Fix missed quoting of foreign server names in pg_dump
* Assorted fixes for pg_upgrade
- Handle exclusion constraints correctly, avoid failures on Windows, don't complain about mismatched toast table names in 8.4 databases.
* In PL/pgSQL, allow foreign tables to define row types
* Fix up conversions of PL/Perl functions' results
- Restore the pre-9.1 behavior that PL/Perl functions returning void ignore the result value of their last Perl statement; 9.1.0 would throw an error if that statement returned a reference. Also, make sure it works to return a string value for a composite type, so long as the string meets the type's input format. In addition, throw errors for attempts to return Perl arrays or hashes when the function's declared result type is not an array or composite type, respectively. (Pre-9.1 versions rather uselessly returned strings like ARRAY(0x221a9a0) or HASH(0x221aa90) in such cases.)
* Ensure PL/Perl strings are always correctly UTF8-encoded
* Use the preferred version of xsubpp to build PL/Perl, not necessarily the operating system's main copy
* Correctly propagate SQLSTATE in PL/Python exceptions
* Do not install PL/Python extension files for Python major versions other than the one built against
* Change all the contrib extension script files to report a useful error message if they are fed to psql
- This should help teach people about the new method of using CREATE EXTENSION to load these files. In most cases, sourcing the scripts directly would fail anyway, but with harder-to-interpret messages.
* Fix incorrect coding in contrib/dict_int and contrib/dict_xsyn
- Some functions incorrectly assumed that memory returned by palloc() is guaranteed zeroed.
* Remove contrib/sepgsql tests from the regular regression test mechanism
- Since these tests require root privileges for setup, they're impractical to run automatically. Switch over to a manual approach instead, and provide a testing script to help with that.
* Fix assorted errors in contrib/unaccent's configuration file parsing
* Honor query cancel interrupts promptly in pgstatindex()
* Fix incorrect quoting of log file name in Mac OS X start script
* Revert unintentional enabling of WAL_DEBUG
- Fortunately, as debugging tools go, this one is pretty cheap; but it's not intended to be enabled by default, so revert.
* Ensure VPATH builds properly install all server header files
* Shorten file names reported in verbose error messages
- Regular builds have always reported just the name of the C file containing the error message call, but VPATH builds formerly reported an absolute path name.
* Fix interpretation of Windows timezone names for Central America
- Map "Central America Standard Time" to CST6, not CST6CDT, because DST is generally not observed anywhere in Central America.
* Update time zone data files to tzdata release 2011n for DST law changes in Brazil, Cuba, Fiji, Palestine, Russia, and Samoa; also historical corrections for Alaska and British East Africa.
更新時間：2011-12-05
更新細節：
更新時間：2011-09-26
更新細節：
What's new in this version:
- Make pg_options_to_table return NULL for an option with no value , Previously such cases would result in a server crash.
- Fix memory leak at end of a GiST index scan , Commands that perform many separate GiST index scans, such as verification of a new GiST-based exclusion constraint on a table already containing many rows, could transiently require large amounts of memory due to this leak.
- Fix explicit reference to pg_temp schema in CREATE TEMPORARY TABLE , This used to be allowed, but failed in 9.1.0.
更新時間：2011-09-26
更新細節：
更新時間：2011-09-13
更新細節：
What's new in this version:
- Allow synchronous replication
- Add support for foreign tables
- Add per-column collation support
- Add extensions which simplify packaging of additions to PostgreSQL
- Add a true serializable isolation level
- Support unlogged tables using the UNLOGGED option in CREATE TABLE
- Allow data-modification commands (INSERT/UPDATE/DELETE) in WITH clauses
- Add nearest-neighbor (order-by-operator) searching to GiST indexes
- Add a SECURITY LABEL command and support for SELinux permissions control
- Update the PL/Python server-side language
更新時間：2011-07-29
更新細節：
What's new in this version:
- Support Real time view of "who cut me",
- Support change gateway/change network on fly. (i.e) when you switch WIFI network from Starbuck to mcdonalds network, you don't need restart
更新時間：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
更新時間：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-10-05
更新細節：