Turns out our existing page size is already optimal in most cases:

< * Research the use of larger page sizes
This commit is contained in:
Bruce Momjian 2005-04-23 21:45:28 +00:00
parent f4dcb52efe
commit ac8998f2e6
2 changed files with 2 additions and 4 deletions

View File

@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Sat Apr 23 17:44:43 EDT 2005
Last updated: Sat Apr 23 17:45:11 EDT 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -903,7 +903,6 @@ Miscellaneous
* Add a script to ask system configuration questions and tune postgresql.conf
* Use a phantom command counter for nested subtransactions to reduce
per-tuple overhead
* Research the use of larger page sizes
Source Code

View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Sat Apr 23 17:44:43 EDT 2005
Last updated: Sat Apr 23 17:45:11 EDT 2005
</p>
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@ -821,7 +821,6 @@ first.
</li><li>Add a script to ask system configuration questions and tune postgresql.conf
</li><li>Use a phantom command counter for nested subtransactions to reduce
per-tuple overhead
</li><li>Research the use of larger page sizes
</li></ul>
<h1><a name="section_20">Source Code</a></h1>