|
1 | 1 | TODO list for PostgreSQL
|
2 | 2 | ========================
|
3 |
| -Last updated: Sun Mar 1 00:18:59 EST 1998 |
| 3 | +Last updated: Sun Mar 1 17:14:36 EST 1998 |
4 | 4 |
|
5 | 5 | Current maintainer: Bruce Momjian (maillist@candle.pha.pa.us)
|
6 | 6 |
|
@@ -95,6 +95,7 @@ ENHANCEMENTS
|
95 | 95 | * add the concept of dataspaces
|
96 | 96 | * add DECIMAL, NUMERIC, DOUBLE PRECISION, BIT, BIT VARYING
|
97 | 97 | * NCHAR (as distinguished from ordinary varchar),
|
| 98 | + * DOMAIN capability |
98 | 99 | * Allow compression of large fields or a compressed field type
|
99 | 100 | * Fix the rules system(Jan?,Soo-Ho)
|
100 | 101 | * robust
|
@@ -216,13 +217,18 @@ System tables continue to be SELECT-able by PUBLIC.
|
216 | 217 |
|
217 | 218 | We also have real deadlock detection code. No more sixty-second
|
218 | 219 | 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. |
226 | 232 |
|
227 | 233 | This is the first release that really required an explaination for
|
228 | 234 | existing users. In many ways, this was necessary because the new
|
|
0 commit comments