diff --git a/doc/FAQ b/doc/FAQ
index 79b12c187f75c309160b7bf7daea7d16d0eb1b8b..faf7a59c93dc2ea26398c7e4c334a66d8ba93f5a 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Tue Nov 22 10:16:48 EST 2005
+ Last updated: Tue Nov 22 10:21:51 EST 2005
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@@ -194,15 +194,14 @@
1.8) How do I submit a bug report?
Visit the PostgreSQL bug form at
- http://www.postgresql.org/support/submitbug.
-
- Also check out our ftp site ftp://ftp.PostgreSQL.org/pub/ to see if
- there is a more recent PostgreSQL version.
+ http://www.postgresql.org/support/submitbug. Also check out our ftp
+ site ftp://ftp.PostgreSQL.org/pub/ to see if there is a more recent
+ PostgreSQL version.
Bugs submitted using the bug form or posted to any PostgreSQL mailing
list typically generates one of the following replies:
* It is not a bug, and why
- * It is a known bug and is known already on the TODO list
+ * It is a known bug and is already on the TODO list
* The bug has been fixed in the current release
* The bug has been fixed but is not packaged yet in an official
release
diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index dc98fb783dda85656795a65a262c4b9756ebf35e..634286dc82937e7544b54dc2e81fe7e7031b5c13 100644
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -10,7 +10,7 @@
alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
- <P>Last updated: Tue Nov 22 10:16:48 EST 2005</P>
+ <P>Last updated: Tue Nov 22 10:21:51 EST 2005</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
@@ -247,9 +247,8 @@
<P>Visit the PostgreSQL bug form at <A href=
"http://www.postgresql.org/support/submitbug">
- http://www.postgresql.org/support/submitbug</A>.</P>
-
- <P>Also check out our ftp site <A href=
+ http://www.postgresql.org/support/submitbug</A>.
+ Also check out our ftp site <A href=
"ftp://ftp.PostgreSQL.org/pub/">ftp://ftp.PostgreSQL.org/pub/</A> to
see if there is a more recent PostgreSQL version.</P>
@@ -257,7 +256,8 @@
list typically generates one of the following replies:</P>
<ul>
<li>It is not a bug, and why</li>
- <li>It is a known bug and is known already on the TODO list</li>
+ <li>It is a known bug and is already on the
+ <A href="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A> list</li>
<li>The bug has been fixed in the current release</li>
<li>The bug has been fixed but is not packaged yet in an official
release</li>
@@ -275,7 +275,8 @@
<li>A patch has been created and will be included in the next major
or minor release</li>
<li>The bug cannot be fixed immediately and is added
- to the TODO list</li>
+ to the <A href="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A>
+ list</li>
</ul>
</li>
</ul>
@@ -290,7 +291,9 @@
<P>A feature request usually results in one of the following
replies:</P>
<ul>
- <li>The feature is already on the TODO list</li>
+ <li>The feature is already on the
+ <A href="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A>
+ list</li>
<li>The feature is not desired because:
<ul>
<li>It duplicates existing functionality that already
@@ -300,11 +303,13 @@
<li>The feature would be insecure or unreliable</li>
</ul>
</li>
- <li>The new feature is added to the TODO list</li>
+ <li>The new feature is added to the
+ <A href="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A> list</li>
</ul>
<P>PostgreSQL does not use a bug tracking system because we find
- it more efficient to respond directly to email and keep the TODO
+ it more efficient to respond directly to email and keep the
+ <A href="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A>
list up-to-date. In practice, bugs don't last very long in the
software, and bugs that affect a large number of users are fixed
rapidly. The only single place to find all changes, improvements,