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

Commit7f75537

Browse files
committed
Update TODO items:
< o Store disk pages with no alignment/padding?>> This involves having the user-specified order of columns> be different from the physical order. SELECT * would> need to reorder the physical values to match the> user-specified ordering.>> o Store disk pages with no alignment/padding?>> This necessitates adding CPU-required padding when moving> rows from disk to memory.>>>http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php>
1 parent9256b84 commit7f75537

File tree

2 files changed

+28
-5
lines changed

2 files changed

+28
-5
lines changed

‎doc/TODO‎

Lines changed: 15 additions & 2 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:Tue Sep12 17:02:34 EDT 2006
5+
Last updated:Thu Sep14 13:11:44 EDT 2006
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1350,9 +1350,22 @@ Miscellaneous Performance
13501350

13511351
* Consider ways of storing rows more compactly on disk
13521352

1353-
o Store disk pages with no alignment/padding?
13541353
o Reorder physical storage order to reduce padding?
1354+
1355+
This involves having the user-specified order of columns
1356+
be different from the physical order. SELECT * would
1357+
need to reorder the physical values to match the
1358+
user-specified ordering.
1359+
1360+
o Store disk pages with no alignment/padding?
1361+
1362+
This necessitates adding CPU-required padding when moving
1363+
rows from disk to memory.
1364+
13551365
o Support a smaller header for short variable-length fields?
1366+
1367+
http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php
1368+
13561369
o Reduce the row header size?
13571370

13581371

‎doc/src/FAQ/TODO.html‎

Lines changed: 13 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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated:Tue Sep12 17:02:34 EDT 2006
11+
Last updated:Thu Sep14 13:11:44 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>.
@@ -1217,9 +1217,19 @@ <h1><a name="section_21">Miscellaneous Performance</a></h1>
12171217
</p>
12181218
</li><li>Consider ways of storing rows more compactly on disk
12191219
<ul>
1220-
<li>Store disk pages with no alignment/padding?
1221-
</li><li>Reorder physical storage order to reduce padding?
1220+
<li>Reorder physical storage order to reduce padding?
1221+
<p> This involves having the user-specified order of columns
1222+
be different from the physical order. SELECT * would
1223+
need to reorder the physical values to match the
1224+
user-specified ordering.
1225+
</p>
1226+
</li><li>Store disk pages with no alignment/padding?
1227+
<p> This necessitates adding CPU-required padding when moving
1228+
rows from disk to memory.
1229+
</p>
12221230
</li><li>Support a smaller header for short variable-length fields?
1231+
<p><ahref="http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php</a>
1232+
</p>
12231233
</li><li>Reduce the row header size?
12241234
</li></ul>
12251235
</li></ul>

0 commit comments

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