Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitccbb07d

Browse files
committed
Fix typo:
< Currently indexes do not have enough tuple tuple visibility< information to allow data to be pulled from the index without< also accessing the heap. One way to allow this is to set a bit< to index tuples to indicate if a tuple is currently visible to< all transactions when the first valid heap lookup happens. This< bit would have to be cleared when a heap tuple is expired.> Currently indexes do not have enough tuple visibility information> to allow data to be pulled from the index without also accessing> the heap. One way to allow this is to set a bit to index tuples> to indicate if a tuple is currently visible to all transactions> when the first valid heap lookup happens. This bit would have to> be cleared when a heap tuple is expired.
1 parent6f61ddd commitccbb07d

File tree

2 files changed

+14
-14
lines changed

2 files changed

+14
-14
lines changed

‎doc/TODO

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)
5-
Last updated:Fri Apr 2209:38:10 EDT 2005
5+
Last updated:Fri Apr 2211:40:08 EDT 2005
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -714,12 +714,12 @@ Cache
714714

715715
* Allow data to be pulled directly from indexes
716716

717-
Currently indexes do not have enough tupletuplevisibility
718-
informationto allow data to be pulled from the index without
719-
also accessingthe heap. One way to allow this is to set a bit
720-
toindex tuples toindicate if a tuple is currently visible to
721-
all transactionswhen the first valid heap lookup happens. This
722-
bit would have tobe cleared when a heap tuple is expired.
717+
Currently indexes do not have enough tuple visibility information
718+
to allow data to be pulled from the index without also accessing
719+
the heap. One way to allow this is to set a bit to index tuples
720+
to indicate if a tuple is currently visible to all transactions
721+
when the first valid heap lookup happens. This bit would have to
722+
be cleared when a heap tuple is expired.
723723

724724
* Consider automatic caching of queries at various levels:
725725
o Parsed query tree

‎doc/src/FAQ/TODO.html

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">
99
<h1><aname="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
11-
Last updated: Fri Apr 2209:38:10 EDT 2005
11+
Last updated: Fri Apr 2211:40:08 EDT 2005
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -653,12 +653,12 @@ <h1><a name="section_13">Cache</a></h1>
653653
to obtain tuple visibility information.
654654
</p>
655655
</li><li>Allow data to be pulled directly from indexes
656-
<p> Currently indexes do not have enough tupletuplevisibility
657-
informationto allow data to be pulled from the index without
658-
also accessingthe heap. One way to allow this is to set a bit
659-
toindex tuples toindicate if a tuple is currently visible to
660-
all transactionswhen the first valid heap lookup happens. This
661-
bit would have tobe cleared when a heap tuple is expired.
656+
<p> Currently indexes do not have enough tuple visibility information
657+
to allow data to be pulled from the index without also accessing
658+
the heap. One way to allow this is to set a bit to index tuples
659+
to indicate if a tuple is currently visible to all transactions
660+
when the first valid heap lookup happens. This bit would have to
661+
be cleared when a heap tuple is expired.
662662
</p>
663663
</li><li>Consider automatic caching of queries at various levels:
664664
<ul>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp