From fee590c8b110c9f761526595b1b10ce8b8778ee6 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 1 Jul 2005 17:32:21 +0000 Subject: [PATCH] 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 --- doc/TODO | 14 ++++---------- doc/src/FAQ/TODO.html | 13 ++++--------- 2 files changed, 8 insertions(+), 19 deletions(-) diff --git a/doc/TODO b/doc/TODO index d804c3d04a..5b67a1a770 100644 --- 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 diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index ddfa950343..e814ed2ef4 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,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. @@ -26,15 +26,10 @@ first.