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

Commitf204274

Browse files
committed
Update TODO for short header versions:
< o Reorder physical storage order to reduce 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.<< One idea is to store the header in network byte order (high bits< first), and read the high bits to determine the header length.<http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php> One idea is to create zero-or-one-byte-header versions> of varlena data types. In involves setting the high-bit and> 0-127 length in the single-byte header, or clear the high bit> and store the 7-bit ASCII value in the rest of the byte.> The small-header versions have no alignment requirements.>http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php
1 parent5ff4f39 commitf204274

File tree

2 files changed

+15
-31
lines changed

2 files changed

+15
-31
lines changed

‎doc/TODO

Lines changed: 7 additions & 16 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:Thu Sep14 17:43:58 EDT 2006
5+
Last updated:Sat Sep16 18:06:27 EDT 2006
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1353,23 +1353,14 @@ Miscellaneous Performance
13531353

13541354
* Consider ways of storing rows more compactly on disk
13551355

1356-
o Reorder physical storage order to reduce padding?
1357-
1358-
This involves having the user-specified order of columns
1359-
be different from the physical order. SELECT * would
1360-
need to reorder the physical values to match the
1361-
user-specified ordering.
1362-
1363-
o Store disk pages with no alignment/padding?
1364-
1365-
This necessitates adding CPU-required padding when moving
1366-
rows from disk to memory.
1367-
13681356
o Support a smaller header for short variable-length fields?
13691357

1370-
One idea is to store the header in network byte order (high bits
1371-
first), and read the high bits to determine the header length.
1372-
http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php
1358+
One idea is to create zero-or-one-byte-header versions
1359+
of varlena data types. In involves setting the high-bit and
1360+
0-127 length in the single-byte header, or clear the high bit
1361+
and store the 7-bit ASCII value in the rest of the byte.
1362+
The small-header versions have no alignment requirements.
1363+
http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php
13731364

13741365
o Reduce the row header size?
13751366

‎doc/src/FAQ/TODO.html

Lines changed: 8 additions & 15 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:Thu Sep14 17:43:58 EDT 2006
11+
Last updated:Sat Sep16 18:06:27 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>.
@@ -1219,20 +1219,13 @@ <h1><a name="section_21">Miscellaneous Performance</a></h1>
12191219
</p>
12201220
</li><li>Consider ways of storing rows more compactly on disk
12211221
<ul>
1222-
<li>Reorder physical storage order to reduce padding?
1223-
<p> This involves having the user-specified order of columns
1224-
be different from the physical order. SELECT * would
1225-
need to reorder the physical values to match the
1226-
user-specified ordering.
1227-
</p>
1228-
</li><li>Store disk pages with no alignment/padding?
1229-
<p> This necessitates adding CPU-required padding when moving
1230-
rows from disk to memory.
1231-
</p>
1232-
</li><li>Support a smaller header for short variable-length fields?
1233-
<p> One idea is to store the header in network byte order (high bits
1234-
first), and read the high bits to determine the header length.
1235-
<ahref="http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php</a>
1222+
<li>Support a smaller header for short variable-length fields?
1223+
<p> One idea is to create zero-or-one-byte-header versions
1224+
of varlena data types. In involves setting the high-bit and
1225+
0-127 length in the single-byte header, or clear the high bit
1226+
and store the 7-bit ASCII value in the rest of the byte.
1227+
The small-header versions have no alignment requirements.
1228+
<ahref="http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php</a>
12361229
</p>
12371230
</li><li>Reduce the row header size?
12381231
</li></ul>

0 commit comments

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