From 914314493573e5adffcd79ed84c8c2f2c358504f Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 9 Jun 2006 18:41:57 +0000 Subject: [PATCH] Cleanups: < * Allow a database in tablespace t1 with tables created in > o Allow a database in tablespace t1 with tables created in 125c125 < * Allow reporting of which objects are in which tablespaces > o Allow reporting of which objects are in which tablespaces 593c593 < * Allow GRANT/REVOKE permissions to be inherited by objects based on > o Allow GRANT/REVOKE permissions to be inherited by objects based on 596c596 < * Allow SERIAL sequences to inherit permissions from the base table? > o Allow SERIAL sequences to inherit permissions from the base table? --- doc/TODO | 10 +++++----- doc/src/FAQ/TODO.html | 16 ++++++---------- 2 files changed, 11 insertions(+), 15 deletions(-) diff --git a/doc/TODO b/doc/TODO index 3621af4cc1..6cdb1e27af 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 Jun 9 14:12:22 EDT 2006 +Last updated: Fri Jun 9 14:41:37 EDT 2006 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -109,7 +109,7 @@ Administration * Tablespaces - * Allow a database in tablespace t1 with tables created in + o Allow a database in tablespace t1 with tables created in tablespace t2 to be used as a template for a new database created with default tablespace t2 @@ -122,7 +122,7 @@ Administration To fix this would require modifying pg_class in the newly copied database, which we don't currently do. - * Allow reporting of which objects are in which tablespaces + o Allow reporting of which objects are in which tablespaces This item is difficult because a tablespace can contain objects from multiple databases. There is a server-side function that @@ -590,10 +590,10 @@ SQL Commands GRANT SELECT ON ALL TABLES IN public TO phpuser; GRANT SELECT ON NEW TABLES IN public TO phpuser; - * Allow GRANT/REVOKE permissions to be inherited by objects based on + o Allow GRANT/REVOKE permissions to be inherited by objects based on schema permissions - * Allow SERIAL sequences to inherit permissions from the base table? + o Allow SERIAL sequences to inherit permissions from the base table? * CURSOR diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index db86ba12bf..6ea071e4bd 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 Jun 9 14:12:22 EDT 2006 +Last updated: Fri Jun 9 14:41:37 EDT 2006

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -120,16 +120,14 @@ first. requires a tool that will call that function and connect to each database to find the objects in each database for that tablespace.

%Add a GUC variable to control the tablespace for temporary objects +
%Add a GUC variable to control the tablespace for temporary objects and sort files
It could start with a random tablespace from a supplied list and cycle through the list.
-
Allow WAL replay of CREATE TABLESPACE to work when the directory +
Allow WAL replay of CREATE TABLESPACE to work when the directory structure on the recovery computer is different from the original -
Allow per-tablespace quotas -

Allow per-tablespace quotas

Point-In-Time Recovery (PITR)

GRANT SELECT ON ALL TABLES IN public TO phpuser; GRANT SELECT ON NEW TABLES IN public TO phpuser;

Allow GRANT/REVOKE permissions to be inherited by objects based on +
Allow GRANT/REVOKE permissions to be inherited by objects based on schema permissions -
Allow SERIAL sequences to inherit permissions from the base table? -

Allow SERIAL sequences to inherit permissions from the base table?

CURSOR

-- 2.40.0