PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Fri Sep 2 17:23:03 EDT 2005
+Last updated: Fri Sep 2 20:41:29 EDT 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
proper visibility of the row's cmin, for example, for cursors.
One possible solution is to create a phantom cid which represents a
- cmin/cmax pair and is stored in local memory.
+ cmin/cmax pair and is stored in local memory. Another idea is to
+ store both cmin and cmax only in local memory.
* Use a phantom command counter for nested subtransactions to reduce
per-tuple overhead
<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: Fri Sep 2 17:23:03 EDT 2005
+Last updated: Fri Sep 2 20:41:29 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>.
proper visibility of the row's cmin, for example, for cursors.
</p>
<p> One possible solution is to create a phantom cid which represents a
- cmin/cmax pair and is stored in local memory.
+ cmin/cmax pair and is stored in local memory. Another idea is to
+ store both cmin and cmax only in local memory.
</p>
</li><li>Use a phantom command counter for nested subtransactions to reduce
per-tuple overhead
OSDN Git Service
