PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Wed Mar 5 22:22:28 EST 2008
+Last updated: Thu Mar 6 12:19:28 EST 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php
-
-
Data Types
==========
* Allow MONEY to be easily cast to/from other numeric data types
-
Functions
=========
http://archives.postgresql.org/pgsql-patches/2007-08/msg00012.php
+* Prevent malicious functions from being executed with the permissions
+ of unsuspecting users
+
+ Index functions are safe, so VACUUM and ANALYZE are safe too.
+ Triggers, CHECK and DEFAULT expressions, and rules are still vulnerable.
+ http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php
Multi-Language Support
Currently client_encoding is set in postgresql.conf, which
defaults to the server encoding.
-
http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php
http://archives.postgresql.org/pgsql-hackers/2006-09/msg01458.php
+
Server-Side Languages
=====================
http://archives.postgresql.org/pgsql-hackers/2007-05/msg00289.php
+
Clients
=======
http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php
+
+
Triggers
========
* Add program to test if fsync has a delay compared to non-fsync
+
Cache Usage
===========
-
Vacuum
======
http://archives.postgresql.org/pgsql-general/2007-06/msg01645.php
+
Locking
=======
+
Startup Time Improvements
=========================
a single session using multiple threads to execute a statement faster.
+
Write-Ahead Log
===============
concurrent reads from multiple devices in a partitioned table.
+
Source Code
===========
<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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
-Last updated: Wed Mar 5 22:22:28 EST 2008
+Last updated: Thu Mar 6 12:19:28 EST 2008
</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>.
</p>
</li><li>Implement Boyer-Moore searching in strpos()
<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-08/msg00012.php">http://archives.postgresql.org/pgsql-patches/2007-08/msg00012.php</a>
+</p>
+ </li><li>Prevent malicious functions from being executed with the permissions
+ of unsuspecting users
+<p> Index functions are safe, so VACUUM and ANALYZE are safe too.
+ Triggers, CHECK and DEFAULT expressions, and rules are still vulnerable.
+ <a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php</a>
</p>
</li></ul>
<h1><a name="section_5">Multi-Language Support</a></h1>
</li><li>Set client encoding based on the client operating system encoding
<p> Currently client_encoding is set in postgresql.conf, which
defaults to the server encoding.
-</p>
-<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php</a>
+ <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php</a>
</p>
</li></ul>
<h1><a name="section_6">Views / Rules</a></h1>