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?
This commit is contained in:
Bruce Momjian 2006-06-09 18:41:57 +00:00
parent c0ba4829a9
commit 9143144935
2 changed files with 11 additions and 15 deletions

View File

@ -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

View File

@ -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 Jun 9 14:12:22 EDT 2006
Last updated: Fri Jun 9 14:41:37 EDT 2006
</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>.
@ -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.
</p>
<ul>
<li>%Add a GUC variable to control the tablespace for temporary objects
</li><li>%Add a GUC variable to control the tablespace for temporary objects
and sort files
<p> It could start with a random tablespace from a supplied list and
cycle through the list.
</p>
</li><li>Allow WAL replay of CREATE TABLESPACE to work when the directory
</li><li>Allow WAL replay of CREATE TABLESPACE to work when the directory
structure on the recovery computer is different from the original
</li><li>Allow per-tablespace quotas
</li></ul>
</li><li>Allow per-tablespace quotas
</li></ul>
</li><li>Point-In-Time Recovery (PITR)
<ul>
@ -537,11 +535,9 @@ first.
</p><p> GRANT SELECT ON ALL TABLES IN public TO phpuser;
GRANT SELECT ON NEW TABLES IN public TO phpuser;
</p>
<ul>
<li>Allow GRANT/REVOKE permissions to be inherited by objects based on
</li><li>Allow GRANT/REVOKE permissions to be inherited by objects based on
schema permissions
</li><li>Allow SERIAL sequences to inherit permissions from the base table?
</li></ul>
</li><li>Allow SERIAL sequences to inherit permissions from the base table?
</li></ul>
</li><li>CURSOR
<ul>