PostgreSQL TODO List

====================

Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)

Last updated:Thu Jul 712:01:59 EDT 2005

Last updated:Thu Jul 722:44:34 EDT 2005

The most recent version of this document can be viewed at

http://www.postgresql.org/docs/faqs.TODO.html.

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

Currently all schemas are owned by the super-user because they are

<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">

<h1><aname="section_1">PostgreSQL TODO List</a></h1>

<p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>

Last updated: Thu Jul 712:01:59 EDT 2005

Last updated: Thu Jul 722:44:34 EDT 2005

<p>The most recent version of this document can be viewed at<br/>

<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.

via an SQL function or SIGTERM

<p> Currently SIGTERM of a backend can lead to lock table corruption.

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

<p> Currently all schemas are owned by the super-user because they are

copied from the template1 database.