Done:

> * -Implement shared row locks and use them in RI triggers

diff --git a/doc/TODO b/doc/TODO
index e43185fb32d2eae212c0e76968ff1717c5ce12fb..4a6acd554eb5d77b5bf43825907aa86930de41f8 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Mon Apr 25 11:35:24 EDT 2005
+Last updated:      Fri Apr 29 01:02:49 EDT 2005
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -603,14 +603,7 @@ Referential Integrity
   memory.  This could exhaust memory for very large trigger queues.
   This item involves dumping large queues into files.
 
-* Implement dirty reads or shared row locks and use them in RI triggers
-
-  Adding shared locks requires recording the table/rows numbers in a
-  shared area, and this could potentially be a large amount of data.
-  One idea is to store the table/row numbers in a separate table and set
-  a bit on the row indicating looking in this new table is required to
-  find any shared row locks.
-
+* -Implement shared row locks and use them in RI triggers
 * Enforce referential integrity for system tables
 * Change foreign key constraint for array -> element to mean element
   in array (?)

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index eba1ec7576a0d69646d3ee0379d41a4a5a852008..a543119efa5e6833863a6b9f66006ee6375fdcb2 100644 (file)
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 
 PostgreSQL TODO List
 Current maintainer:     Bruce Momjian ([email protected])
-Last updated:           Mon Apr 25 11:35:24 EDT 2005
+Last updated:           Fri Apr 29 01:02:49 EDT 2005
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -557,13 +557,7 @@ first.
   memory.  This could exhaust memory for very large trigger queues.
   This item involves dumping large queues into files.
 
-  Implement dirty reads or shared row locks and use them in RI triggers
-  Adding shared locks requires recording the table/rows numbers in a
-  shared area, and this could potentially be a large amount of data.
-  One idea is to store the table/row numbers in a separate table and set
-  a bit on the row indicating looking in this new table is required to
-  find any shared row locks.
-
+  -Implement shared row locks and use them in RI triggers
   Enforce referential integrity for system tables
   Change foreign key constraint for array -> element to mean element
   in array (?)