Skip to content
Snippets Groups Projects
Commit a4ffa382 authored by Bruce Momjian's avatar Bruce Momjian
Browse files

Done: 

> * -Prevent dropping user that still owns objects, or auto-drop the objects
parent 59d1b3d9
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
doc/TODO
+ 2
− 2
View file @ a4ffa382
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Thu Jul 7 12:01:59 EDT 2005 Last updated: Thu Jul 7 22:44:34 EDT 2005
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.
...@@ -36,7 +36,7 @@ Administration ...@@ -36,7 +36,7 @@ Administration
Currently SIGTERM of a backend can lead to lock table corruption. Currently SIGTERM of a backend can lead to lock table corruption.
* Prevent dropping user that still owns objects, or auto-drop the objects * -Prevent dropping user that still owns objects, or auto-drop the objects
* 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
......
doc/src/FAQ/TODO.html
+ 2
− 2
View file @ a4ffa382
...@@ -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:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Thu Jul 7 12:01:59 EDT 2005 Last updated: Thu Jul 7 22:44:34 EDT 2005
</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>.
...@@ -39,7 +39,7 @@ first. ...@@ -39,7 +39,7 @@ first.
via an SQL function or SIGTERM via an SQL function or SIGTERM
<p> Currently SIGTERM of a backend can lead to lock table corruption. <p> Currently SIGTERM of a backend can lead to lock table corruption.
</p> </p>
</li><li>Prevent dropping user that still owns objects, or auto-drop the objects </li><li>-<em>Prevent dropping user that still owns objects, or auto-drop the objects</em>
</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 from the template1 database. copied from the template1 database.
......
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