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

Commit754838c

Browse files
committed
Done:
> * -Consider shrinking expired tuples to just their headers> * -Allow heap reuse of UPDATEd rows if no indexed columns are changed,> and old and new versions are on the same heap pageNot needed anymore:< * Reuse index tuples that point to heap tuples that are not visible to< anyone?
1 parentad8fbb5 commit754838c

File tree

2 files changed

+8
-36
lines changed

2 files changed

+8
-36
lines changed

‎doc/TODO

Lines changed: 4 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
PostgreSQL TODO List
22
====================
33
Current maintainer:Bruce Momjian (bruce@momjian.us)
4-
Last updated:Fri Sep14 15:02:41 EDT 2007
4+
Last updated:Thu Sep20 14:53:32 EDT 2007
55

66
The most recent version of this document can be viewed at
77
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1208,24 +1208,9 @@ Vacuum
12081208
in hopes that empty pages at the end can be truncated by VACUUM
12091209
* Allow FSM page return free space based on table clustering, to assist
12101210
in maintaining clustering?
1211-
* Consider shrinking expired tuples to just their headers
1212-
1213-
http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php
1214-
http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php
1215-
1216-
* Allow heap reuse of UPDATEd rows if no indexed columns are changed,
1217-
and old and new versions are on the same heap page?
1218-
1219-
While vacuum handles DELETEs fine, updating of non-indexed columns, like
1220-
counters, are difficult for VACUUM to handle efficiently. This method
1221-
is possible for same-page updates because a single index row can be
1222-
used to point to both old and new values.
1223-
1224-
http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php
1225-
http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php
1226-
1227-
* Reuse index tuples that point to heap tuples that are not visible to
1228-
anyone?
1211+
* -Consider shrinking expired tuples to just their headers
1212+
* -Allow heap reuse of UPDATEd rows if no indexed columns are changed,
1213+
and old and new versions are on the same heap page
12291214
* Improve dead row detection during multi-statement transactions usage
12301215

12311216
http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php

‎doc/src/FAQ/TODO.html

Lines changed: 4 additions & 17 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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated:Fri Sep14 15:02:41 EDT 2007
11+
Last updated:Thu Sep20 14:53:32 EDT 2007
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>.
@@ -1075,22 +1075,9 @@ <h1><a name="section_15">Vacuum</a></h1>
10751075
in hopes that empty pages at the end can be truncated by VACUUM
10761076
</li><li>Allow FSM page return free space based on table clustering, to assist
10771077
in maintaining clustering?
1078-
</li><li>Consider shrinking expired tuples to just their headers
1079-
<p><ahref="http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php">http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php</a>
1080-
<ahref="http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php</a>
1081-
</p>
1082-
</li><li>Allow heap reuse of UPDATEd rows if no indexed columns are changed,
1083-
and old and new versions are on the same heap page?
1084-
<p> While vacuum handles DELETEs fine, updating of non-indexed columns, like
1085-
counters, are difficult for VACUUM to handle efficiently. This method
1086-
is possible for same-page updates because a single index row can be
1087-
used to point to both old and new values.
1088-
</p>
1089-
<p><ahref="http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php">http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php</a>
1090-
<ahref="http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php">http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php</a>
1091-
</p>
1092-
</li><li>Reuse index tuples that point to heap tuples that are not visible to
1093-
anyone?
1078+
</li><li>-<em>Consider shrinking expired tuples to just their headers</em>
1079+
</li><li>-<em>Allow heap reuse of UPDATEd rows if no indexed columns are changed,</em>
1080+
and old and new versions are on the same heap page
10941081
</li><li>Improve dead row detection during multi-statement transactions usage
10951082
<p><ahref="http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php">http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php</a>
10961083
</p>

0 commit comments

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