From: Bruce Momjian Date: Tue, 18 Mar 2008 23:32:57 +0000 (+0000) Subject: Update TODO description: X-Git-Tag: REL8_4_BETA1~1745 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=8426b5640ee33e776e60f1875f136a00885d99be;p=postgresql Update TODO description: * Speed WAL recovery by allowing more than one page to be prefetched This should be done utilizing the same infrastructure used for prefetching in general to avoid introducing complex error-prone code in WAL replay. --- diff --git a/doc/TODO b/doc/TODO index a88e56a082..4e2b8ed6d6 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 18 14:40:32 EDT 2008 +Last updated: Tue Mar 18 19:32:48 EDT 2008 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -1510,8 +1510,9 @@ Write-Ahead Log * Speed WAL recovery by allowing more than one page to be prefetched - This involves having a separate process that can be told which pages - the recovery process will need in the near future. + This should be done utilizing the same infrastructure used for + prefetching in general to avoid introducing complex error-prone code + in WAL replay. http://archives.postgresql.org/pgsql-general/2007-12/msg00683.php http://archives.postgresql.org/pgsql-hackers/2007-12/msg00497.php http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index ab1f886222..4255c6a0b1 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 18 14:40:32 EDT 2008 +Last updated: Tue Mar 18 19:32:48 EDT 2008

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -1312,8 +1312,9 @@ first. There is also a developer's wiki at
of indexes on TOAST tables.

  • Speed WAL recovery by allowing more than one page to be prefetched -

    This involves having a separate process that can be told which pages - the recovery process will need in the near future. +

    This should be done utilizing the same infrastructure used for + prefetching in general to avoid introducing complex error-prone code + in WAL replay. http://archives.postgresql.org/pgsql-general/2007-12/msg00683.php http://archives.postgresql.org/pgsql-hackers/2007-12/msg00497.php http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php