From bb63cb8f795975bd1d9c21ad17b84c6ca0bb017b Mon Sep 17 00:00:00 2001 From: Bruce Momjian <bruce@momjian.us> Date: Sun, 1 Mar 1998 22:26:42 +0000 Subject: [PATCH] Update for release. Add mention of new manuals. --- doc/TODO | 22 ++++++++++++++-------- migration/6.2.1_to_6.3 | 19 ++++++++++++------- 2 files changed, 26 insertions(+), 15 deletions(-) diff --git a/doc/TODO b/doc/TODO index 62246095db9..c681bebe528 100644 --- a/doc/TODO +++ b/doc/TODO @@ -1,6 +1,6 @@ TODO list for PostgreSQL ======================== -Last updated: Sun Mar 1 00:18:59 EST 1998 +Last updated: Sun Mar 1 17:14:36 EST 1998 Current maintainer: Bruce Momjian (maillist@candle.pha.pa.us) @@ -95,6 +95,7 @@ ENHANCEMENTS * add the concept of dataspaces * add DECIMAL, NUMERIC, DOUBLE PRECISION, BIT, BIT VARYING * NCHAR (as distinguished from ordinary varchar), + * DOMAIN capability * Allow compression of large fields or a compressed field type * Fix the rules system(Jan?,Soo-Ho) * robust @@ -216,13 +217,18 @@ System tables continue to be SELECT-able by PUBLIC. We also have real deadlock detection code. No more sixty-second timeouts. And the new locking code implements a FIFO better, so there -should be less resource starvation during heavy use. For performance -reasons, time travel is gone, but can be implemented using triggers (see -pgsql/contrib/spi/README). Please check out the new \d command for -types, operators, etc. Also, views have their own permissions now, not -based on the underlying tables, so permissions on them have to be set -separately. Check /pgsql/interfaces for some new ways to talk to -PostgreSQL. +should be less resource starvation during heavy use. + +Many complaints have been made about inadequate documenation in previous +releases. Thomas has put much effort into many new manuals for this +release. Check out the /doc directory. + +For performance reasons, time travel is gone, but can be implemented +using triggers (see pgsql/contrib/spi/README). Please check out the new +\d command for types, operators, etc. Also, views have their own +permissions now, not based on the underlying tables, so permissions on +them have to be set separately. Check /pgsql/interfaces for some new +ways to talk to PostgreSQL. This is the first release that really required an explaination for existing users. In many ways, this was necessary because the new diff --git a/migration/6.2.1_to_6.3 b/migration/6.2.1_to_6.3 index 12921aab7a9..3f7ed410fa2 100644 --- a/migration/6.2.1_to_6.3 +++ b/migration/6.2.1_to_6.3 @@ -42,13 +42,18 @@ System tables continue to be SELECT-able by PUBLIC. We also have real deadlock detection code. No more sixty-second timeouts. And the new locking code implements a FIFO better, so there -should be less resource starvation during heavy use. For performance -reasons, time travel is gone, but can be implemented using triggers (see -pgsql/contrib/spi/README). Please check out the new \d command for -types, operators, etc. Also, views have their own permissions now, not -based on the underlying tables, so permissions on them have to be set -separately. Check /pgsql/interfaces for some new ways to talk to -PostgreSQL. +should be less resource starvation during heavy use. + +Many complaints have been made about inadequate documenation in previous +releases. Thomas has put much effort into many new manuals for this +release. Check out the /doc directory. + +For performance reasons, time travel is gone, but can be implemented +using triggers (see pgsql/contrib/spi/README). Please check out the new +\d command for types, operators, etc. Also, views have their own +permissions now, not based on the underlying tables, so permissions on +them have to be set separately. Check /pgsql/interfaces for some new +ways to talk to PostgreSQL. This is the first release that really required an explaination for existing users. In many ways, this was necessary because the new -- GitLab