From 5dc0e67bd5ca723886887298ecfcb2a91d86ba4c Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter_e@gmx.net>
Date: Sat, 17 Mar 2001 18:15:36 +0000
Subject: [PATCH] Reformat the "major changes" to 72 or so columns.
---
HISTORY | 36 +++++++++++++++++++-----------------
1 file changed, 19 insertions(+), 17 deletions(-)
diff --git a/HISTORY b/HISTORY
index 3dc08b71b46..c2750faea30 100644
--- a/HISTORY
+++ b/HISTORY
@@ -1,4 +1,4 @@
- ------------------------------------------------------------------------
+ ------------------------------------------------------------------------
Release 7.1
------------------------------------------------------------------------
@@ -11,32 +11,34 @@ PostgreSQL code for many years.
Major changes in this release:
- Write-ahead Log (WAL) - To maintain database consistency in case
-of an operating system crash, previous releases of PostgreSQL have
-forced all data modifications to disk before each transaction commit.
-With WAL, only one log file must be flushed to disk, greatly improving
-performance. If you have been using -F in previous releases to disable
-disk flushes, you may want to consider discontinuing its use.
+ Write-ahead Log (WAL) - To maintain database consistency in
+case of an operating system crash, previous releases of PostgreSQL
+have forced all data modifications to disk before each transaction
+commit. With WAL, only one log file must be flushed to disk, greatly
+improving performance. If you have been using -F in previous releases
+to disable disk flushes, you may want to consider discontinuing its
+use.
TOAST - Previous releases had a compiled-in row length limit,
-typically 8k - 32k. This limit made storage of long text fields
-difficult. With TOAST, long rows of any length can be stored with good
-performance.
+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 performance.
Outer Joins - We now support outer joins. The UNION/NOT IN
workaround for outer joins is no longer required. We use the SQL92
outer join syntax.
- Function Manager - The previous C function manager did not handle NULLs properly,
-nor did it support 64-bit CPU's (Alpha). 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
+ Function Manager - The previous C function manager did not
+handle NULLs properly, nor did it support 64-bit CPU's (Alpha). 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.
Complex Queries - A large number of complex queries that were
-unsupported in previous releases now work. Many combinations of views,
-aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables
-now work properly. Inherited tables are now accessed by default.
-Subqueries in FROM are now supported.
+unsupported in previous releases now work. Many combinations of
+views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited
+tables now work properly. Inherited tables are now accessed by
+default. Subqueries in FROM are now supported.
Migration to 7.1
--
GitLab