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

bmomjian · bmomjian · commit ac8998f2e687 · 2005-04-23T21:45:28.000Z
&lt; * Research the use of larger page sizes
diff --git a/doc/TODO b/doc/TODO
@@ -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
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
@@ -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 @@ <h1><a name="section_19">Miscellaneous</a></h1>
   </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>
 
