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

Commitac7a126

Browse files
committed
Update entry:
< * Allow heap reuse of UPDATEd rows if old and new versions are on the< same heap page?> * Allow heap reuse of UPDATEd rows if no indexed columns are changed,> and old and new versions are on the same heap page?< This is possible for same-page updates because a single index row< can point to both old and new values.> While vacuum handles DELETEs fine, updating of non-indexed columns, like> counters, are difficult for VACUUM to handle efficiently. This method> is possible for same-page updates because a single index row can be> used to point to both old and new values.
1 parentfc6a229 commitac7a126

File tree

2 files changed

+14
-10
lines changed

2 files changed

+14
-10
lines changed

‎doc/TODO

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer:Bruce Momjian (bruce@momjian.us)
5-
Last updated:Sat Jun 24 19:44:48 EDT 2006
5+
Last updated:Sat Jun 24 19:47:53 EDT 2006
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1131,11 +1131,13 @@ Vacuum
11311131

11321132
http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php
11331133

1134-
* Allow heap reuse of UPDATEd rows ifold and new versionsareon the
1135-
same heap page?
1134+
* Allow heap reuse of UPDATEd rows ifno indexed columnsarechanged,
1135+
and old and new versions are on thesame heap page?
11361136

1137-
This is possible for same-page updates because a single index row
1138-
can point to both old and new values.
1137+
While vacuum handles DELETEs fine, updating of non-indexed columns, like
1138+
counters, are difficult for VACUUM to handle efficiently. This method
1139+
is possible for same-page updates because a single index row can be
1140+
used to point to both old and new values.
11391141
http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php
11401142

11411143
* Auto-vacuum

‎doc/src/FAQ/TODO.html

Lines changed: 7 additions & 5 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: Sat Jun 24 19:44:48 EDT 2006
11+
Last updated: Sat Jun 24 19:47:53 EDT 2006
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>.
@@ -1020,10 +1020,12 @@ <h1><a name="section_16">Vacuum</a></h1>
10201020
</li><li>Consider shrinking expired tuples to just their headers
10211021
<p><ahref="http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php">http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php</a>
10221022
</p>
1023-
</li><li>Allow heap reuse of UPDATEd rows if old and new versions are on the
1024-
same heap page?
1025-
<p> This is possible for same-page updates because a single index row
1026-
can point to both old and new values.
1023+
</li><li>Allow heap reuse of UPDATEd rows if no indexed columns are changed,
1024+
and old and new versions are on the same heap page?
1025+
<p> While vacuum handles DELETEs fine, updating of non-indexed columns, like
1026+
counters, are difficult for VACUUM to handle efficiently. This method
1027+
is possible for same-page updates because a single index row can be
1028+
used to point to both old and new values.
10271029
<ahref="http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php">http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php</a>
10281030
</p>
10291031
</li><li>Auto-vacuum

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp