From 56c7614bb22fa3c0859ef07b8e0e7420258aa1ab Mon Sep 17 00:00:00 2001 From: Bruce Momjian 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 771617d7dc..6d287e88d8 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 97668d9d01..db771c3d84 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,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. @@ -1284,7 +1284,31 @@ first. There is also a developer's wiki at

http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php

-

Miscellaneous Performance

+

Background Writer

+ + +

Miscellaneous Performance

  • 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

    @@ -1351,7 +1359,7 @@ first. There is also a developer's wiki at

    http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php

    • -

    Source Code

    +

    Source Code

    -

    Exotic Features

    +

    Exotic Features

    -

    Features We Do Not Want

    +

    Features We Do Not Want