Skip to content

P
Postgres FD Implementation
Commit 5dc0e67b authored by Peter Eisentraut's avatar Peter Eisentraut
Browse files
Options

Reformat the "major changes" to 72 or so columns.

parent 11fd9157
Show whitespace changes
Inline Side-by-side
Showing with 19 additions and 17 deletions
HISTORY
View file @ 5dc0e67b
...@@ -11,32 +11,34 @@ PostgreSQL code for many years. ...@@ -11,32 +11,34 @@ PostgreSQL code for many years.
Major changes in this release: Major changes in this release:
Write-ahead Log (WAL) - To maintain database consistency in case Write-ahead Log (WAL) - To maintain database consistency in
of an operating system crash, previous releases of PostgreSQL have case of an operating system crash, previous releases of PostgreSQL
forced all data modifications to disk before each transaction commit. have forced all data modifications to disk before each transaction
With WAL, only one log file must be flushed to disk, greatly improving commit. With WAL, only one log file must be flushed to disk, greatly
performance. If you have been using -F in previous releases to disable improving performance. If you have been using -F in previous releases
disk flushes, you may want to consider discontinuing its use. to disable disk flushes, you may want to consider discontinuing its
use.
TOAST - Previous releases had a compiled-in row length limit, TOAST - Previous releases had a compiled-in row length limit,
typically 8k - 32k. This limit made storage of long text fields typically 8 - 32 kB. This limit made storage of long text fields
difficult. With TOAST, long rows of any length can be stored with good difficult. With TOAST, long rows of any length can be stored with
performance. good performance.
Outer Joins - We now support outer joins. The UNION/NOT IN Outer Joins - We now support outer joins. The UNION/NOT IN
workaround for outer joins is no longer required. We use the SQL92 workaround for outer joins is no longer required. We use the SQL92
outer join syntax. outer join syntax.
Function Manager - The previous C function manager did not handle NULLs properly, Function Manager - The previous C function manager did not
nor did it support 64-bit CPU's (Alpha). The new function manager does. You can continue handle NULLs properly, nor did it support 64-bit CPU's (Alpha). The
using your old custom functions, but you may want to rewrite them in the future to use the new function manager does. You can continue using your old custom
functions, but you may want to rewrite them in the future to use the
new function manager call interface. new function manager call interface.
Complex Queries - A large number of complex queries that were Complex Queries - A large number of complex queries that were
unsupported in previous releases now work. Many combinations of views, unsupported in previous releases now work. Many combinations of
aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited
now work properly. Inherited tables are now accessed by default. tables now work properly. Inherited tables are now accessed by
Subqueries in FROM are now supported. default. Subqueries in FROM are now supported.
Migration to 7.1 Migration to 7.1
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment