From f260edb144c1e3f33d5ecc3d00d5359ab675d238 Mon Sep 17 00:00:00 2001
From: Bruce Momjian Current maintainer: Bruce Momjian (bruce@momjian.us) The most recent version of this document can be viewed at http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php
http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php
+ http://archives.postgresql.org/pgsql-hackers/2007-03/msg00265.php
+ http://archives.postgresql.org/pgsql-hackers/2007-03/msg01214.php
+ http://archives.postgresql.org/pgsql-patches/2007-05/msg00013.php
+ http://archives.postgresql.org/pgsql-hackers/2007-07/msg00741.php
PostgreSQL TODO List
-Last updated: Sun Apr 6 22:14:10 EDT 2008
+Last updated: Thu Apr 10 14:57:53 EDT 2008
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1063,6 +1063,10 @@ first. There is also a developer's wiki at
http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php
http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php
+ http://archives.postgresql.org/pgsql-hackers/2007-08/msg00014.php
+ http://archives.postgresql.org/pgsql-hackers/2007-08/msg00487.php
This is difficult because you must upgrade to an exclusive table lock
@@ -1095,6 +1101,9 @@ first. There is also a developer's wiki at
single heap scan, and have pg_restore use it
http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php +
+http://archives.postgresql.org/pgsql-hackers/2007-03/msg01079.php
http://archives.postgresql.org/pgsql-patches/2007-10/msg00166.php + http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php