|
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: Fri Sep 217:23:03 EDT 2005 |
| 11 | +Last updated: Fri Sep 220:41:29 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>. |
@@ -891,7 +891,8 @@ <h1><a name="section_21">Miscellaneous Performance</a></h1> |
891 | 891 | proper visibility of the row's cmin, for example, for cursors. |
892 | 892 | </p> |
893 | 893 | <p> One possible solution is to create a phantom cid which represents a |
894 | | - cmin/cmax pair and is stored in local memory. |
| 894 | + cmin/cmax pair and is stored in local memory. Another idea is to |
| 895 | + store both cmin and cmax only in local memory. |
895 | 896 | </p> |
896 | 897 | </li><li>Use a phantom command counter for nested subtransactions to reduce |
897 | 898 | per-tuple overhead |
|