database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-26 01:22:12 +03:00
Code Activity

Update for release. Add mention of new manuals.

Browse Source
This commit is contained in:
Bruce Momjian
1998-03-01 22:26:42 +00:00
parent 09b187598c
commit bb63cb8f79
2 changed files with 26 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
doc/TODO
View File

@ -1,6 +1,6 @@
TODO list for PostgreSQL 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) Current maintainer: Bruce Momjian (maillist@candle.pha.pa.us)
@ -95,6 +95,7 @@ ENHANCEMENTS
* add the concept of dataspaces * add the concept of dataspaces
* add DECIMAL, NUMERIC, DOUBLE PRECISION, BIT, BIT VARYING * add DECIMAL, NUMERIC, DOUBLE PRECISION, BIT, BIT VARYING
* NCHAR (as distinguished from ordinary varchar), * NCHAR (as distinguished from ordinary varchar),
* DOMAIN capability
* Allow compression of large fields or a compressed field type * Allow compression of large fields or a compressed field type
* Fix the rules system(Jan?,Soo-Ho) * Fix the rules system(Jan?,Soo-Ho)
* robust * 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 We also have real deadlock detection code. No more sixty-second
timeouts. And the new locking code implements a FIFO better, so there timeouts. And the new locking code implements a FIFO better, so there
should be less resource starvation during heavy use. For performance should be less resource starvation during heavy use.
reasons, time travel is gone, but can be implemented using triggers (see
pgsql/contrib/spi/README). Please check out the new \d command for Many complaints have been made about inadequate documenation in previous
types, operators, etc. Also, views have their own permissions now, not releases. Thomas has put much effort into many new manuals for this
based on the underlying tables, so permissions on them have to be set release. Check out the /doc directory.
separately. Check /pgsql/interfaces for some new ways to talk to
PostgreSQL. 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 This is the first release that really required an explaination for
existing users. In many ways, this was necessary because the new existing users. In many ways, this was necessary because the new

19
migration/6.2.1_to_6.3
View File

@ -42,13 +42,18 @@ System tables continue to be SELECT-able by PUBLIC.
We also have real deadlock detection code. No more sixty-second We also have real deadlock detection code. No more sixty-second
timeouts. And the new locking code implements a FIFO better, so there timeouts. And the new locking code implements a FIFO better, so there
should be less resource starvation during heavy use. For performance should be less resource starvation during heavy use.
reasons, time travel is gone, but can be implemented using triggers (see
pgsql/contrib/spi/README). Please check out the new \d command for Many complaints have been made about inadequate documenation in previous
types, operators, etc. Also, views have their own permissions now, not releases. Thomas has put much effort into many new manuals for this
based on the underlying tables, so permissions on them have to be set release. Check out the /doc directory.
separately. Check /pgsql/interfaces for some new ways to talk to
PostgreSQL. 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 This is the first release that really required an explaination for
existing users. In many ways, this was necessary because the new existing users. In many ways, this was necessary because the new