Update for roles:

< * Allow limits on per-db/user connections > * Allow limits on per-db/role connections < * 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. < 450c444 < * Add COMMENT ON for all cluster global objects (users, roles, databases > * Add COMMENT ON for all cluster global objects (roles, databases 609c603 < users and roles with separate DROP commands > roles with separate DROP commands

Update for roles:
< * Allow limits on per-db/user connections > * Allow limits on per-db/role connections < * 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. < 450c444 < * Add COMMENT ON for all cluster global objects (users, roles, databases > * Add COMMENT ON for all cluster global objects (roles, databases 609c603 < users and roles with separate DROP commands > roles with separate DROP commands
fee590c8 · Bruce Momjian · b00f557d · fee590c8 · fee590c8
隐藏空白更改
内联并排

Showing with 8 addition and 19 deletion

doc/TODO doc/TODO +4 -10

doc/src/FAQ/TODO.html doc/src/FAQ/TODO.html +4 -9

未找到文件。
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 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.
@@ -21,18 +21,12 @@ Administration

 * 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

@@ -447,7 +441,7 @@ Commands
 * 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.
@@ -606,7 +600,7 @@ Clients
 	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

--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 <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>.
@@ -26,15 +26,10 @@ first.
 <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
@@ -413,7 +408,7 @@ first.
  </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.
@@ -562,7 +557,7 @@ first.
    </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