Commit e6facb3b authored by Bruce Momjian's avatar Bruce Momjian

Add warning about TODO item:

<   Currently all schemas are owned by the super-user because they are
<   copied from the template1 database.
>   Currently all schemas are owned by the super-user because they are copied
>   from the template1 database.  However, since all objects are inherited
>   from the template database, it is not clear that setting schemas to the db
>   owner is correct.
parent 4942ee65
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Tue Apr 17 16:47:44 EDT 2007 Last updated: Tue Apr 17 16:50:27 EDT 2007
The most recent version of this document can be viewed at The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
...@@ -39,8 +39,10 @@ Administration ...@@ -39,8 +39,10 @@ Administration
* Set proper permissions on non-system schemas during db creation * Set proper permissions on non-system schemas during db creation
Currently all schemas are owned by the super-user because they are Currently all schemas are owned by the super-user because they are copied
copied from the template1 database. from the template1 database. However, since all objects are inherited
from the template database, it is not clear that setting schemas to the db
owner is correct.
* Support table partitioning that allows a single table to be stored * Support table partitioning that allows a single table to be stored
in subtables that are partitioned based on the primary key or a WHERE in subtables that are partitioned based on the primary key or a WHERE
......
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
Last updated: Tue Apr 17 16:47:44 EDT 2007 Last updated: Tue Apr 17 16:50:27 EDT 2007
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <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>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
...@@ -41,8 +41,10 @@ first. There is also a developer's wiki at<br/> ...@@ -41,8 +41,10 @@ first. There is also a developer's wiki at<br/>
<a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php</a> <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php</a>
</p> </p>
</li><li>Set proper permissions on non-system schemas during db creation </li><li>Set proper permissions on non-system schemas during db creation
<p> Currently all schemas are owned by the super-user because they are <p> Currently all schemas are owned by the super-user because they are copied
copied from the template1 database. from the template1 database. However, since all objects are inherited
from the template database, it is not clear that setting schemas to the db
owner is correct.
</p> </p>
</li><li>Support table partitioning that allows a single table to be stored </li><li>Support table partitioning that allows a single table to be stored
in subtables that are partitioned based on the primary key or a WHERE in subtables that are partitioned based on the primary key or a WHERE
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment