Skip to content

Commit bb63cb8

Browse files
committed
Update for release. Add mention of new manuals.
1 parent 09b1875 commit bb63cb8

File tree

2 files changed

+26
-15
lines changed

2 files changed

+26
-15
lines changed

doc/TODO

Lines changed: 14 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
TODO list for PostgreSQL
22
========================
3-
Last updated: Sun Mar 1 00:18:59 EST 1998
3+
Last updated: Sun Mar 1 17:14:36 EST 1998
44

55
Current maintainer: Bruce Momjian (maillist@candle.pha.pa.us)
66

@@ -95,6 +95,7 @@ ENHANCEMENTS
9595
* add the concept of dataspaces
9696
* add DECIMAL, NUMERIC, DOUBLE PRECISION, BIT, BIT VARYING
9797
* NCHAR (as distinguished from ordinary varchar),
98+
* DOMAIN capability
9899
* Allow compression of large fields or a compressed field type
99100
* Fix the rules system(Jan?,Soo-Ho)
100101
* robust
@@ -216,13 +217,18 @@ System tables continue to be SELECT-able by PUBLIC.
216217

217218
We also have real deadlock detection code. No more sixty-second
218219
timeouts. And the new locking code implements a FIFO better, so there
219-
should be less resource starvation during heavy use. For performance
220-
reasons, time travel is gone, but can be implemented using triggers (see
221-
pgsql/contrib/spi/README). Please check out the new \d command for
222-
types, operators, etc. Also, views have their own permissions now, not
223-
based on the underlying tables, so permissions on them have to be set
224-
separately. Check /pgsql/interfaces for some new ways to talk to
225-
PostgreSQL.
220+
should be less resource starvation during heavy use.
221+
222+
Many complaints have been made about inadequate documenation in previous
223+
releases. Thomas has put much effort into many new manuals for this
224+
release. Check out the /doc directory.
225+
226+
For performance reasons, time travel is gone, but can be implemented
227+
using triggers (see pgsql/contrib/spi/README). Please check out the new
228+
\d command for types, operators, etc. Also, views have their own
229+
permissions now, not based on the underlying tables, so permissions on
230+
them have to be set separately. Check /pgsql/interfaces for some new
231+
ways to talk to PostgreSQL.
226232

227233
This is the first release that really required an explaination for
228234
existing users. In many ways, this was necessary because the new

migration/6.2.1_to_6.3

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -42,13 +42,18 @@ System tables continue to be SELECT-able by PUBLIC.
4242

4343
We also have real deadlock detection code. No more sixty-second
4444
timeouts. And the new locking code implements a FIFO better, so there
45-
should be less resource starvation during heavy use. For performance
46-
reasons, time travel is gone, but can be implemented using triggers (see
47-
pgsql/contrib/spi/README). Please check out the new \d command for
48-
types, operators, etc. Also, views have their own permissions now, not
49-
based on the underlying tables, so permissions on them have to be set
50-
separately. Check /pgsql/interfaces for some new ways to talk to
51-
PostgreSQL.
45+
should be less resource starvation during heavy use.
46+
47+
Many complaints have been made about inadequate documenation in previous
48+
releases. Thomas has put much effort into many new manuals for this
49+
release. Check out the /doc directory.
50+
51+
For performance reasons, time travel is gone, but can be implemented
52+
using triggers (see pgsql/contrib/spi/README). Please check out the new
53+
\d command for types, operators, etc. Also, views have their own
54+
permissions now, not based on the underlying tables, so permissions on
55+
them have to be set separately. Check /pgsql/interfaces for some new
56+
ways to talk to PostgreSQL.
5257

5358
This is the first release that really required an explaination for
5459
existing users. In many ways, this was necessary because the new

0 commit comments

Comments
 (0)