Skip to content

P
Postgres FD Implementation
Commit 8d21abd7 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Add: 

>
> * Consider increasing internal areas when shared buffers is increased
>
>   http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php
parent cda6a5a5
Hide whitespace changes
Inline Side-by-side
Showing with 9 additions and 2 deletions
doc/TODO
View file @ 8d21abd7
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Wed Jun 14 18:22:53 EDT 2006 Last updated: Wed Jun 14 18:31:29 EDT 2006
The most recent version of this document can be viewed at The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
...@@ -1039,6 +1039,10 @@ Cache Usage ...@@ -1039,6 +1039,10 @@ Cache Usage
around to the beginning, rather than always starting sequential scans around to the beginning, rather than always starting sequential scans
at the start of the table. at the start of the table.
* Consider increasing internal areas when shared buffers is increased
http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php
Vacuum Vacuum
====== ======
......
doc/src/FAQ/TODO.html
View file @ 8d21abd7
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <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/> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Wed Jun 14 18:22:53 EDT 2006 Last updated: Wed Jun 14 18:31:29 EDT 2006
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <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>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
...@@ -934,6 +934,9 @@ first. ...@@ -934,6 +934,9 @@ first.
numbered buffer in the shared cache, and when reaching the end wrap numbered buffer in the shared cache, and when reaching the end wrap
around to the beginning, rather than always starting sequential scans around to the beginning, rather than always starting sequential scans
at the start of the table. at the start of the table.
</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>
</p> </p>
</li></ul> </li></ul>
<h1><a name="section_16">Vacuum</a></h1> <h1><a name="section_16">Vacuum</a></h1>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment