From 56c7614bb22fa3c0859ef07b8e0e7420258aa1ab Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 11 Mar 2008 21:06:10 +0000
Subject: [PATCH] Add:
* Test to see if calling PreallocXlogFiles() from the background writer
will help with WAL segment creation latency
http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php
---
doc/TODO | 52 ++++++++++++++++++++++++++-----------------
doc/src/FAQ/TODO.html | 50 ++++++++++++++++++++++++-----------------
2 files changed, 60 insertions(+), 42 deletions(-)
diff --git a/doc/TODO b/doc/TODO
index 771617d7dc8..6d287e88d8f 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,7 +1,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Tue Mar 11 16:46:16 EDT 2008
+Last updated: Tue Mar 11 17:06:02 EDT 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1474,6 +1474,36 @@ Optimizer / Executor
+Background Writer
+=================
+
+* Consider having the background writer update the transaction status
+ hint bits before writing out the page
+
+ Implementing this requires the background writer to have access to system
+ catalogs and the transaction status log.
+
+* Consider adding buffers the background writer finds reusable to the
+ free list
+
+ http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php
+
+* Automatically tune bgwriter_delay based on activity rather then using a
+ fixed interval
+
+ http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php
+
+* Consider wither increasing BM_MAX_USAGE_COUNT improves performance
+
+ http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php
+
+* Test to see if calling PreallocXlogFiles() from the background writer
+ will help with WAL segment creation latency
+
+ http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php
+
+
+
Miscellaneous Performance
=========================
@@ -1508,26 +1538,6 @@ Miscellaneous Performance
two because a heap row cannot be more than 64k in length
* Consider increasing NUM_CLOG_BUFFERS
-* Consider having the background writer update the transaction status
- hint bits before writing out the page
-
- Implementing this requires the background writer to have access to system
- catalogs and the transaction status log.
-
-* Consider adding buffers the background writer finds reusable to the
- free list
-
- http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php
-
-* Automatically tune bgwriter_delay based on activity rather then using a
- fixed interval
-
- http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php
-
-* Consider wither increasing BM_MAX_USAGE_COUNT improves performance
-
- http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php
-
* Allow user configuration of TOAST thresholds
http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 97668d9d01f..db771c3d84d 100644
--- 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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
-Last updated: Tue Mar 11 16:46:16 EDT 2008
+Last updated: Tue Mar 11 17:06:02 EDT 2008
</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>.
@@ -1284,7 +1284,31 @@ first. There is also a developer's wiki at<br/>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php">http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php</a>
</p>
</li></ul>
-<h1><a name="section_20">Miscellaneous Performance</a></h1>
+<h1><a name="section_20">Background Writer</a></h1>
+
+<ul>
+ <li>Consider having the background writer update the transaction status
+ hint bits before writing out the page
+<p> Implementing this requires the background writer to have access to system
+ catalogs and the transaction status log.
+</p>
+ </li><li>Consider adding buffers the background writer finds reusable to the
+ free list
+<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php</a>
+</p>
+ </li><li>Automatically tune bgwriter_delay based on activity rather then using a
+ fixed interval
+<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php</a>
+</p>
+ </li><li>Consider wither increasing BM_MAX_USAGE_COUNT improves performance
+<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php">http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php</a>
+</p>
+ </li><li>Test to see if calling PreallocXlogFiles() from the background writer
+ will help with WAL segment creation latency
+<p> <a href="http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php">http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php</a>
+</p>
+</li></ul>
+<h1><a name="section_21">Miscellaneous Performance</a></h1>
<ul>
<li>Do async I/O for faster random read-ahead of data
@@ -1315,22 +1339,6 @@ first. There is also a developer's wiki at<br/>
two because a heap row cannot be more than 64k in length
</li></ul>
</li><li>Consider increasing NUM_CLOG_BUFFERS
- </li><li>Consider having the background writer update the transaction status
- hint bits before writing out the page
-<p> Implementing this requires the background writer to have access to system
- catalogs and the transaction status log.
-</p>
- </li><li>Consider adding buffers the background writer finds reusable to the
- free list
-<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php</a>
-</p>
- </li><li>Automatically tune bgwriter_delay based on activity rather then using a
- fixed interval
-<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php</a>
-</p>
- </li><li>Consider wither increasing BM_MAX_USAGE_COUNT improves performance
-<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php">http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php</a>
-</p>
</li><li>Allow user configuration of TOAST thresholds
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php">http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php</a>
</p>
@@ -1351,7 +1359,7 @@ first. There is also a developer's wiki at<br/>
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php">http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php</a>
</p>
</li></ul>
-<h1><a name="section_21">Source Code</a></h1>
+<h1><a name="section_22">Source Code</a></h1>
<ul>
<li>Add use of 'const' for variables in source tree
@@ -1418,7 +1426,7 @@ first. There is also a developer's wiki at<br/>
of result sets using new statement protocol
</li></ul>
</li></ul>
-<h1><a name="section_22">Exotic Features</a></h1>
+<h1><a name="section_23">Exotic Features</a></h1>
<ul>
<li>Add pre-parsing phase that converts non-ISO syntax to supported
@@ -1445,7 +1453,7 @@ first. There is also a developer's wiki at<br/>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php</a>
</p>
</li></ul>
-<h1><a name="section_23">Features We Do <u>Not</u> Want</a></h1>
+<h1><a name="section_24">Features We Do <u>Not</u> Want</a></h1>
<ul>
<li>All backends running as threads in a single process (not wanted)
--
GitLab