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

Commit3bea1a3

Browse files
committed
Update wording:
< could only see committed rows from another transaction. However,> could only see rows from another completed transaction. However,981c981< proper visibility of the row, for example, for cursors.> proper visibility of the row's cmin, for example, for cursors.
1 parentda08559 commit3bea1a3

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

‎doc/TODO

Lines changed: 3 additions & 3 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 Sep 2 15:39:11 EDT 2005
5+
Last updated:Fri Sep 2 15:51:34 EDT 2005
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -972,13 +972,13 @@ Miscellaneous Performance
972972
xmax), cmin, cmax, and if the transaction was expiring a row from a
973973
another transaction, the fields stored were xmin (cmin was not
974974
needed), xmax, and cmax. Such a system worked because a transaction
975-
could only seecommittedrows from another transaction. However,
975+
could only see rows from another completed transaction. However,
976976
subtransactions can see rows from outer transactions, and once the
977977
subtransaction completes, the outer transaction continues, requiring
978978
the storage of all four fields. With subtransactions, an outer
979979
transaction can create a row, a subtransaction expire it, and when the
980980
subtransaction completes, the outer transaction still has to have
981-
proper visibility of the row, for example, for cursors.
981+
proper visibility of the row's cmin, for example, for cursors.
982982

983983
One possible solution is to create a phantom cid which represents a
984984
cmin/cmax pair and is stored in local memory.

‎doc/src/FAQ/TODO.html

Lines changed: 3 additions & 3 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 Sep 2 15:39:11 EDT 2005
11+
Last updated: Fri Sep 2 15:51:34 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>.
@@ -876,13 +876,13 @@ <h1><a name="section_21">Miscellaneous Performance</a></h1>
876876
xmax), cmin, cmax, and if the transaction was expiring a row from a
877877
another transaction, the fields stored were xmin (cmin was not
878878
needed), xmax, and cmax. Such a system worked because a transaction
879-
could only seecommittedrows from another transaction. However,
879+
could only see rows from another completed transaction. However,
880880
subtransactions can see rows from outer transactions, and once the
881881
subtransaction completes, the outer transaction continues, requiring
882882
the storage of all four fields. With subtransactions, an outer
883883
transaction can create a row, a subtransaction expire it, and when the
884884
subtransaction completes, the outer transaction still has to have
885-
proper visibility of the row, for example, for cursors.
885+
proper visibility of the row's cmin, for example, for cursors.
886886
</p>
887887
<p> One possible solution is to create a phantom cid which represents a
888888
cmin/cmax pair and is stored in local memory.

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp