postgres.git / summary / log / commit / refs
commit daec16d0baa44fdc8b78f262ff993489716ca4ec
Author: Bruce Momjian <bruce@momjian.us>
Date: Fri Apr 29 05:03:02 2005 +0000
First released in: 8.1.0
Done:
> * -Implement shared row locks and use them in RI triggers
doc/TODO | 11 ++---------
doc/src/FAQ/TODO.html | 10 ++--------
2 files changed, 4 insertions(+), 17 deletions(-)
diff --git a/doc/TODO b/doc/TODO
index e43185fb32d..4a6acd554eb 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-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 eba1ec7576a..a543119efa5 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
<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:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated: Mon Apr 25 11:35:24 EDT 2005
+Last updated: Fri Apr 29 01:02:49 EDT 2005
</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>.
@@ -557,13 +557,7 @@ first.
memory. This could exhaust memory for very large trigger queues.
This item involves dumping large queues into files.
</p>
- </li><li>Implement dirty reads or shared row locks and use them in RI triggers
-<p> 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.
-</p>
+ </li><li>-Implement shared row locks and use them in RI triggers
</li><li>Enforce referential integrity for system tables
</li><li>Change foreign key constraint for array -> element to mean element
in array (?)
[parent: bedb78d386a4]