From 300c43e303bbe8dd009acf65422288e9de35025b Mon Sep 17 00:00:00 2001 From: Bruce Momjian <bruce@momjian.us> Date: Sat, 3 Feb 2007 23:52:19 +0000 Subject: [PATCH] Add URLs for: * Allow sequential scans to take advantage of other concurrent sequential scans, also called "Synchronised Scanning" > http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php --- doc/TODO | 4 +++- doc/src/FAQ/TODO.html | 6 ++++-- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/doc/TODO b/doc/TODO index 695f9c5ca42..5876bbac48b 100644 --- a/doc/TODO +++ b/doc/TODO @@ -2,7 +2,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Sat Feb 3 17:32:46 EST 2007 +Last updated: Sat Feb 3 18:52:13 EST 2007 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -1060,6 +1060,8 @@ Cache Usage around to the beginning, rather than always starting sequential scans at the start of the table. + http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php + http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php * Consider increasing internal areas when shared buffers is increased diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 60c2e1d072e..f4adb92f081 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: Sat Feb 3 17:32:46 EST 2007 +Last updated: Sat Feb 3 18:52:13 EST 2007 </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>. @@ -950,7 +950,9 @@ first. There is also a developer's wiki at<br/> around to the beginning, rather than always starting sequential scans at the start of the table. </p> -<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php</a> +<p> <a href="http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php">http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php</a> + <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php</a> + <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php</a> </p> </li><li>Consider increasing internal areas when shared buffers is increased <p> <a href="http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php">http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php</a> -- GitLab