mirror of
https://github.com/postgres/postgres.git
synced 2025-04-25 21:42:33 +03:00
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.
This commit is contained in:
parent
11b5c554c2
commit
b72fe49b9c
5
doc/TODO
5
doc/TODO
@ -2,7 +2,7 @@
|
|||||||
PostgreSQL TODO List
|
PostgreSQL TODO List
|
||||||
====================
|
====================
|
||||||
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
|
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
|
The most recent version of this document can be viewed at
|
||||||
http://www.postgresql.org/docs/faqs.TODO.html.
|
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.
|
proper visibility of the row's cmin, for example, for cursors.
|
||||||
|
|
||||||
One possible solution is to create a phantom cid which represents a
|
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
|
* Use a phantom command counter for nested subtransactions to reduce
|
||||||
per-tuple overhead
|
per-tuple overhead
|
||||||
|
@ -8,7 +8,7 @@
|
|||||||
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
|
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
|
||||||
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
|
<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/>
|
<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>
|
||||||
<p>The most recent version of this document can be viewed at<br/>
|
<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>.
|
<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.
|
proper visibility of the row's cmin, for example, for cursors.
|
||||||
</p>
|
</p>
|
||||||
<p> One possible solution is to create a phantom cid which represents a
|
<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>
|
</p>
|
||||||
</li><li>Use a phantom command counter for nested subtransactions to reduce
|
</li><li>Use a phantom command counter for nested subtransactions to reduce
|
||||||
per-tuple overhead
|
per-tuple overhead
|
||||||
|
Loading…
x
Reference in New Issue
Block a user