PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Fri Jul 1 13:05:46 EDT 2005
+Last updated: Fri Jul 1 13:32:12 EDT 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
* Remove behavior of postmaster -o after making postmaster/postgres
flags unique
-* Allow limits on per-db/user connections
+* Allow limits on per-db/role connections
* Allow server log information to be output as INSERT statements
This would allow server log information to be easily loaded into
a database for analysis.
-* Prevent default re-use of sysids for dropped users and roles
-
- Currently, if a user is removed while he still owns objects, a new
- user given might be given their user id and inherit the
- previous users objects.
-
* Prevent dropping user that still owns objects, or auto-drop the objects
* Allow pooled connections to list all prepared queries
* Add ON COMMIT capability to CREATE TABLE AS SELECT
* Add NOVICE output level for helpful messages like automatic sequence/index
creation
-* Add COMMENT ON for all cluster global objects (users, roles, databases
+* Add COMMENT ON for all cluster global objects (roles, databases
and tablespaces)
* Add an option to automatically use savepoints for each statement in a
multi-statement transaction.
o Add dumping of comments on composite type columns
o Add dumping of comments on index columns
o Replace crude DELETE FROM method of pg_dumpall for cleaning of
- users and roles with separate DROP commands
+ roles with separate DROP commands
o -Add dumping and restoring of LOB comments
o Stop dumping CASCADE on DROP TYPE commands in clean mode
o Add full object name to the tag field. eg. for operators we need
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated: Fri Jul 1 13:05:46 EDT 2005
+Last updated: Fri Jul 1 13:32:12 EDT 2005
</p>
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
<ul>
<li>Remove behavior of postmaster -o after making postmaster/postgres
flags unique
- </li><li>Allow limits on per-db/user connections
+ </li><li>Allow limits on per-db/role connections
</li><li>Allow server log information to be output as INSERT statements
<p> This would allow server log information to be easily loaded into
a database for analysis.
-</p>
- </li><li>Prevent default re-use of sysids for dropped users and roles
-<p> Currently, if a user is removed while he still owns objects, a new
- user given might be given their user id and inherit the
- previous users objects.
</p>
</li><li>Prevent dropping user that still owns objects, or auto-drop the objects
</li><li>Allow pooled connections to list all prepared queries
</li><li>Add ON COMMIT capability to CREATE TABLE AS SELECT
</li><li>Add NOVICE output level for helpful messages like automatic sequence/index
creation
- </li><li>Add COMMENT ON for all cluster global objects (users, roles, databases
+ </li><li>Add COMMENT ON for all cluster global objects (roles, databases
and tablespaces)
</li><li>Add an option to automatically use savepoints for each statement in a
multi-statement transaction.
</li><li>Add dumping of comments on composite type columns
</li><li>Add dumping of comments on index columns
</li><li>Replace crude DELETE FROM method of pg_dumpall for cleaning of
- users and roles with separate DROP commands
+ roles with separate DROP commands
</li><li>-<em>Add dumping and restoring of LOB comments</em>
</li><li>Stop dumping CASCADE on DROP TYPE commands in clean mode
</li><li>Add full object name to the tag field. eg. for operators we need
projects / postgresql / commitdiff