Skip to content

Commit e444d9a

Browse files
bmomjianbmomjian
committed
Improve indentation of sublists: < The proper solution to this will probably the use of a master/slave < replication solution like Sloney and a connection pooling tool like < pgpool. > The proper solution to this will probably the use of a master/slave > replication solution like Sloney and a connection pooling tool like > pgpool. 114,116c114,116 < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. > You can use any of the master/slave replication servers to use a > standby server for data warehousing. To allow read/write queries to > multiple servers, you need multi-master replication like pgcluster. 166,167c166,167 < Currently large objects entries do not have owners. Permissions can < only be set at the pg_largeobject table level. > Currently large objects entries do not have owners. Permissions can > only be set at the pg_largeobject table level. 173c173 < This requires the TOAST column to be stored EXTERNAL. > This requires the TOAST column to be stored EXTERNAL. 359,360c359,360 < One complexity is whether moving a schema should move all existing < schema objects or just define the location for future object creation. > One complexity is whether moving a schema should move all existing > schema objects or just define the location for future object creation. 364,365c364,365 < Currently non-global system tables must be in the default database < schema. Global system tables can never be moved. > Currently non-global system tables must be in the default database > schema. Global system tables can never be moved. 371,375c371,375 < This might require some background daemon to maintain clustering < during periods of low usage. It might also require tables to be only < paritally filled for easier reorganization. Another idea would < be to create a merged heap/index data file so an index lookup would < automatically access the heap data too. > This might require some background daemon to maintain clustering > during periods of low usage. It might also require tables to be only > paritally filled for easier reorganization. Another idea would > be to create a merged heap/index data file so an index lookup would > automatically access the heap data too. 379,380c379,380 < To do this, determine the ideal cluster index for each system < table and set the cluster setting during initdb. > To do this, determine the ideal cluster index for each system > table and set the cluster setting during initdb. 385,386c385,386 < This requires the use of a savepoint before each COPY line is < processed, with ROLLBACK on COPY failure. > This requires the use of a savepoint before each COPY line is > processed, with ROLLBACK on COPY failure. 395,398c395,398 < This requires using the row ctid to map cursor rows back to the < original heap row. This become more complicated if WITH HOLD cursors < are to be supported because WITH HOLD cursors have a copy of the row < and no FOR UPDATE lock. > This requires using the row ctid to map cursor rows back to the > original heap row. This become more complicated if WITH HOLD cursors > are to be supported because WITH HOLD cursors have a copy of the row > and no FOR UPDATE lock. 405,406c405,406 < Because WITH HOLD cursors exist outside transactions, this allows < them to be listed so they can be closed. > Because WITH HOLD cursors exist outside transactions, this allows > them to be listed so they can be closed. 413,415c413,415 < This is useful for returning the auto-generated key for an INSERT. < One complication is how to handle rules that run as part of < the insert. > This is useful for returning the auto-generated key for an INSERT. > One complication is how to handle rules that run as part of > the insert. 422c422 < This is basically the same as SET search_path. > This is basically the same as SET search_path. 426,427c426,427 < This requires a checking function to be called after the server < configuration file is read. > This requires a checking function to be called after the server > configuration file is read. 432c432 < Currently only constants are supported. > Currently only constants are supported. 438,439c438,439 < This requires the cached PL/PgSQL byte code to be invalidated when < an object referenced in the function is changed. > This requires the cached PL/PgSQL byte code to be invalidated when > an object referenced in the function is changed. 512,513c512,513 < Document differences between ecpg and the SQL standard and < information about the Informix-compatibility module. > Document differences between ecpg and the SQL standard and > information about the Informix-compatibility module.
1 parent 51aacec commit e444d9a

File tree

1 file changed

+40
-40
lines changed

1 file changed

+40
-40
lines changed

‎doc/TODO

Lines changed: 40 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ TODO list for PostgreSQL
55
Bracketed items "[]" have more detail.
66

77
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
8-
Last updated: Sun Oct 17 23:26:56 EDT 2004
8+
Last updated: Mon Oct 18 12:13:19 EDT 2004
99

1010
The most recent version of this document can be viewed at the PostgreSQL web
1111
site, http://www.PostgreSQL.org.
@@ -105,15 +105,15 @@ Administration
105105
* Improve replication solutions
106106
o Automatic failover
107107

108-
The proper solution to this will probably the use of a master/slave
109-
replication solution like Sloney and a connection pooling tool like
110-
pgpool.
108+
The proper solution to this will probably the use of a master/slave
109+
replication solution like Sloney and a connection pooling tool like
110+
pgpool.
111111

112112
o Load balancing
113113

114-
You can use any of the master/slave replication servers to use a
115-
standby server for data warehousing. To allow read/write queries to
116-
multiple servers, you need multi-master replication like pgcluster.
114+
You can use any of the master/slave replication servers to use a
115+
standby server for data warehousing. To allow read/write queries to
116+
multiple servers, you need multi-master replication like pgcluster.
117117

118118
o Allow replication over unreliable or non-persistent links
119119

@@ -163,14 +163,14 @@ Data Types
163163
o Improve vacuum of large objects, like /contrib/vacuumlo (?)
164164
o Add security checking for large objects
165165

166-
Currently large objects entries do not have owners. Permissions can
167-
only be set at the pg_largeobject table level.
166+
Currently large objects entries do not have owners. Permissions can
167+
only be set at the pg_largeobject table level.
168168

169169
o Auto-delete large objects when referencing row is deleted
170170

171171
o Allow read/write into TOAST values like large objects
172172

173-
This requires the TOAST column to be stored EXTERNAL.
173+
This requires the TOAST column to be stored EXTERNAL.
174174

175175

176176
Multi-Language Support
@@ -356,34 +356,34 @@ Commands
356356
o Allow ALTER TABLESPACE to move to different directories
357357
o Allow databases and schemas to be moved to different tablespaces
358358

359-
One complexity is whether moving a schema should move all existing
360-
schema objects or just define the location for future object creation.
359+
One complexity is whether moving a schema should move all existing
360+
schema objects or just define the location for future object creation.
361361

362362
o Allow moving system tables to other tablespaces, where possible
363363

364-
Currently non-global system tables must be in the default database
365-
schema. Global system tables can never be moved.
364+
Currently non-global system tables must be in the default database
365+
schema. Global system tables can never be moved.
366366

367367

368368
* CLUSTER
369369
o Automatically maintain clustering on a table
370370

371-
This might require some background daemon to maintain clustering
372-
during periods of low usage. It might also require tables to be only
373-
paritally filled for easier reorganization. Another idea would
374-
be to create a merged heap/index data file so an index lookup would
375-
automatically access the heap data too.
371+
This might require some background daemon to maintain clustering
372+
during periods of low usage. It might also require tables to be only
373+
paritally filled for easier reorganization. Another idea would
374+
be to create a merged heap/index data file so an index lookup would
375+
automatically access the heap data too.
376376

377377
o Add default clustering to system tables
378378

379-
To do this, determine the ideal cluster index for each system
380-
table and set the cluster setting during initdb.
379+
To do this, determine the ideal cluster index for each system
380+
table and set the cluster setting during initdb.
381381

382382
* COPY
383383
o Allow COPY to report error lines and continue
384384

385-
This requires the use of a savepoint before each COPY line is
386-
processed, with ROLLBACK on COPY failure.
385+
This requires the use of a savepoint before each COPY line is
386+
processed, with ROLLBACK on COPY failure.
387387

388388
o Allow COPY to understand \x as a hex byte
389389
o Have COPY return the number of rows loaded/unloaded (?)
@@ -392,51 +392,51 @@ Commands
392392
* CURSOR
393393
o Allow UPDATE/DELETE WHERE CURRENT OF cursor
394394

395-
This requires using the row ctid to map cursor rows back to the
396-
original heap row. This become more complicated if WITH HOLD cursors
397-
are to be supported because WITH HOLD cursors have a copy of the row
398-
and no FOR UPDATE lock.
395+
This requires using the row ctid to map cursor rows back to the
396+
original heap row. This become more complicated if WITH HOLD cursors
397+
are to be supported because WITH HOLD cursors have a copy of the row
398+
and no FOR UPDATE lock.
399399

400400
o Prevent DROP TABLE from dropping a row referenced by its own open
401401
cursor (?)
402402

403403
o Allow pooled connections to list all open WITH HOLD cursors
404404

405-
Because WITH HOLD cursors exist outside transactions, this allows
406-
them to be listed so they can be closed.
405+
Because WITH HOLD cursors exist outside transactions, this allows
406+
them to be listed so they can be closed.
407407

408408
* INSERT
409409
o Allow INSERT/UPDATE of the system-generated oid value for a row
410410
o Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..)
411411
o Allow INSERT/UPDATE ... RETURNING new.col or old.col
412412

413-
This is useful for returning the auto-generated key for an INSERT.
414-
One complication is how to handle rules that run as part of
415-
the insert.
413+
This is useful for returning the auto-generated key for an INSERT.
414+
One complication is how to handle rules that run as part of
415+
the insert.
416416

417417
* SHOW/SET
418418
o Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
419419
ANALYZE, and CLUSTER
420420
o Add SET PATH for schemas (?)
421421

422-
This is basically the same as SET search_path.
422+
This is basically the same as SET search_path.
423423

424424
o Prevent conflicting SET options from being set
425425

426-
This requires a checking function to be called after the server
427-
configuration file is read.
426+
This requires a checking function to be called after the server
427+
configuration file is read.
428428

429429
* SERVER-SIDE LANGUAGES
430430
o Allow PL/PgSQL's RAISE function to take expressions (?)
431431

432-
Currently only constants are supported.
432+
Currently only constants are supported.
433433

434434
o Change PL/PgSQL to use palloc() instead of malloc()
435435
o Handle references to temporary tables that are created, destroyed,
436436
then recreated during a session, and EXECUTE is not used
437437

438-
This requires the cached PL/PgSQL byte code to be invalidated when
439-
an object referenced in the function is changed.
438+
This requires the cached PL/PgSQL byte code to be invalidated when
439+
an object referenced in the function is changed.
440440

441441
o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW
442442
o Improve PL/PgSQL exception handling using savepoints
@@ -509,8 +509,8 @@ Clients
509509
* ECPG (?)
510510
o Docs
511511

512-
Document differences between ecpg and the SQL standard and
513-
information about the Informix-compatibility module.
512+
Document differences between ecpg and the SQL standard and
513+
information about the Informix-compatibility module.
514514

515515
o Solve cardinality > 1 for input descriptors / variables (?)
516516
o Improve error handling (?)

0 commit comments

Comments
 (0)