From b72fe49b9c28540c3fb3d129d0e4b49cec585fa2 Mon Sep 17 00:00:00 2001 From: Bruce Momjian <bruce@momjian.us> Date: Sat, 3 Sep 2005 00:41:30 +0000 Subject: [PATCH] Add idea: < 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. --- doc/TODO | 5 +++-- doc/src/FAQ/TODO.html | 5 +++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/TODO b/doc/TODO index 18cd4f7a669..64752a2bcdf 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: 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. @@ -986,7 +986,8 @@ Miscellaneous Performance 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 diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 5d6bc200ff2..8c30519f1e4 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: 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>. @@ -891,7 +891,8 @@ first. 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 -- GitLab