|
8 | 8 | <bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF"> |
9 | 9 | <h1><aname="section_1">PostgreSQL TODO List</a></h1> |
10 | 10 | <p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/> |
11 | | -Last updated:Mon Apr25 11:35:24 EDT 2005 |
| 11 | +Last updated:Fri Apr29 01:02:49 EDT 2005 |
12 | 12 | </p> |
13 | 13 | <p>The most recent version of this document can be viewed at<br/> |
14 | 14 | <ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. |
@@ -557,13 +557,7 @@ <h1><a name="section_9">Referential Integrity</a></h1> |
557 | 557 | memory. This could exhaust memory for very large trigger queues. |
558 | 558 | This item involves dumping large queues into files. |
559 | 559 | </p> |
560 | | -</li><li>Implement dirty reads or shared row locks and use them in RI triggers |
561 | | -<p> Adding shared locks requires recording the table/rows numbers in a |
562 | | - shared area, and this could potentially be a large amount of data. |
563 | | - One idea is to store the table/row numbers in a separate table and set |
564 | | - a bit on the row indicating looking in this new table is required to |
565 | | - find any shared row locks. |
566 | | -</p> |
| 560 | +</li><li>-Implement shared row locks and use them in RI triggers |
567 | 561 | </li><li>Enforce referential integrity for system tables |
568 | 562 | </li><li>Change foreign key constraint for array -> element to mean element |
569 | 563 | in array (?) |
|